Skip to content

Prepare unsigned stable 1.0.0 with verified content and exact-draft acceptance - #239

Merged
Laymer merged 467 commits into
mainfrom
release/stable-1.0.0-version
Oct 26, 2026
Merged

Laymer merged 467 commits into
mainfrom
release/stable-1.0.0-version

Conversation

@Laymer

@Laymer Laymer commented Oct 20, 2026 •

Copy link
Copy Markdown
Owner

Prepare unsigned stable 1.0.0 with bundled world/authored content and independently reviewed schema5 exact downloaded-draft Windows acceptance. Target Forever 1.60.1.70450 retains true historical 70245/1.12 attribution, accepted unknowns, labelled estimates and explicit exclusions.

The V22 candidate repairs hosted application-data isolation: use Windows Roaming known folders, refuse pre-existing data for first start, remove disposable native-smoke leftovers, and retain the candidate database before the RC1 baseline. V21’s failed attempts remain archived; their observations are not V22 acceptance.

Actual V22 full-pack assertions passed at frozen source 3609c2b5 (80.568 s, shared Linux/WSL2); the independent reviewer’s own run passed in 80.668 s. Inventory retains 260,113 records and 274,059 accepted unknown fields. Production fingerprint a947d2f092f9ed4921676c008745c87c837325102db04b106460121871295537. Current verification and immutable identities are recorded in docs/handoffs/2026-10-24-v22-appdata-continuation.md. The installer and application remain explicitly unsigned; two operator-controlled content signatures bind separately recorded independent review.

Require fresh protected checks, per-file 90% coverage, full Linux/Windows source parity and all eight installed cases before merge. Verify fresh exact resulting-main checks and stability before tagging; independently reviewed exact downloaded-draft UI/native evidence and full readiness precede publication. No workload/suite limits are waived. Historical/shared-Linux engineering measurements are not ordinary-PC or current Windows acceptance.

V22 frozen independent review SHA6131a419; manifest SHAa912304e; prepared identity SHA744c8371 committed before key use; receipt SHA79686be6. Root and independent signed-closure verification passed: 84 resources, 89 evidence files, two packs, exactly nine pending observations and no other blockers. Final composition review is clear at 9be789e9; fresh hosted gates are next.

@Laymer
Laymer changed the base branch from release/stable-content-delivery to main October 20, 2026 10:28
Laymer added 29 commits October 20, 2026 22:59
test: separate synthetic watchdog startup allowance from pending IPC checks
Laymer and others added 28 commits October 23, 2026 17:58
The firewall refuses the 8.3 short path of provjobd (C:\Users\RUNNER~1\...)
and accepts its long form; hosted-compute-agent without an extension and the
Azure guest agents are accepted as given (probe run 39982567901).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…results

network_isolation becomes windows_firewall_runner_and_host_agents_only, since
the hosted VM agents are allowed alongside the runner. ADR 0010 records the
lost runner-only 1260 s probes, the short-path refusal and the passing 1260 s
probe 39982856528.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Correct stale scope comments, test the real infrastructure agent selection
(workload-named, missing, relative and over-limit paths refuse; absent agents
are not invented), cover allowed_infrastructure_programs in validator tests,
and note the user-writable provjobd path in ADR 0010.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Independent review: CLEAR WITH NITS over three rounds; all nits addressed.
Hosted probe 39982856528 held isolation 1260 s past the 1200 s workload
bound with exact restoration.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…firewall probes

Run 39931563703 attempts 1 and 2 (candidate 2c6fe76) were cancelled 306 s
and 280 s into HOSTED-OFFLINE; five hosted cases passed in each, offline was
interrupted and the upgrade/downgrade cases never ran. Probe reports from the
ADR 0010 engineering runs are kept beside them. No result is promoted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tion source

Tested source 1f97214 (merge of PR #285), production 7e1bb463 over 3160
entries. Cargo --no-run confirmed the cached functional executable d1745d72
and CLI fbbf4571; the actual full-pack functional run passed in 75.77 s,
peak 6206036 KiB on shared Linux/WSL2. Regenerated evidence differs from V20
prebundle only in the proof references and the source/production binding;
all nine Windows rows stay pristine pending. Exact V20 signed and functional
bytes are preserved under release/history/2026-10-23-v20-signed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Preview at adb52c5: unsigned_preparation.ready=true for evidence 0080ac37,
82 files, two packs; nine Windows rows pristine pending. CLI fbbf4571 and the
functional executable were confirmed cached by actual Cargo invocations.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
.gitignore *.log had left out two package logs and three V21 build/run logs
that history.json and verification-v21/checks.json bind by hash (found by the
independent V21 review).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Independent review of tested source 1f97214 (production 7e1bb463, 3160
entries) against evidence commit 29814d3. Content/material closure is
unchanged from V20, the ADR 0010 firewall isolation diff does not touch
the installer payload or weaken the HOSTED-OFFLINE contract, and the
reviewer reran the functional proof at 1f97214. All nine acceptance rows
remain pristine unverified; publication is not allowed by this review.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review release/v1/public-content-review-v21.json, 142226 B, SHA256
7542fb89ed8954c648f5df48d548cf99b25a8dbae6804a78421db3f111919257, binds tested
source 1f97214, production 7e1bb463 and evidence baseline 29814d3; clear for
receipt preparation only. Coordinator rechecked all 351 FileRefs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
prepare-bundle.py (tested source 1f97214, production 7e1bb463, review V21
142226 B 7542fb89) prepared 84 resources: manifest 17187 B SHA256
1ce2b62650bea680e6ff019475b544ce5be8e980c9be099883f8b2be24b0bfa4, identity
528 B SHA256 b6336b301aa26ed7cb727c8fce43c0dbee63ac2068b68e231e1388bae879fc22.
Against V20 only the review reference, tested source and production change;
the other 83 resources are identical. The superseded V20 receipt, manifest
and identity are removed here; their exact bytes are preserved under
release/history/2026-10-23-v20-signed. Its preview step compiled a debug CLI
(actual 20 s Cargo build). No key has been used for V21.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Receipt 1080 B SHA256 eccd6b63f20e67af6d1cc8ede1864d826bbf6ca38f3c84da00a04ac0817cf29c,
signed by the existing r2 operator and review-evidence keys (no rotation;
both operator-controlled) over identity b6336b30, manifest 1ce2b626, tested
source 1f97214, production 7e1bb463 and review V21 7542fb89. Verified
against the committed signers policy c4bbc54f and the independent reviewer's
pre-receipt expected payload. Only bundled_content was added to evidence.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The app resolves its data through SHGetKnownFolderPath, which ignores
$env:APPDATA, so the acceptance overrides never isolated it. RC1 opened
the candidate's database and reported recovery required, and FIRST-START
ran on the native smoke database rather than a fresh one.

Resolve the real folder, refuse leftover data at start, clear the native
smoke data in the workflow, and move the candidate's data aside (kept)
before the RC1 baseline.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Laymer
Laymer marked this pull request as ready for review October 26, 2026 08:11
@Laymer
Laymer merged commit aaa73b9 into main Oct 26, 2026
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant