The approved Ubuntu default repair is released as v0.10.0 through DSR. The final documentation commit aff6199215cf6396e3ace3053cad1dc4e26ce7cc is on main/master and is the peeled v0.10.0 tag. Public release ID402263782 is neither draft nor prerelease and has zero assets, matching the existing source-only installer venue. Independent uncached release, inventory, notes, and source readback passed.
Ordinary installs preserve supported 22.04/24.04 LTS releases. An explicit target requests an upgrade, and skip wins in either argument order. The mandatory system checkpoint guard still runs before package changes. A completed root-owned 0600 checkpoint is read through trusted sudo without changing its evidence.
Patch qualification through the required remote test lane: 53 entrypoint tests, 62 main/CLI/privileged-reader tests, and 97 LTS runtime assertions passed. Actual CLI parsing, real privileged stat/jq reads, hidden root-only parents, malformed/active state refusal, and unchanged checkpoint bytes/modes/inodes are covered. Bash syntax, warning-level ShellCheck for all installer scripts, and manifest/internal-checksum drift checks passed. These prove tested policy and filesystem behavior; they do not prove a full factory installation or reboot/resume upgrade.
The complete unchanged-suite comparison is now terminal. Exact v0.9.0 web: 241 passed, zero failed. Current web: 803 passed, 48 failed. Of those failures, 43 stop in a closed test-harness import mapping that omits the status page's actual useInstallationHealth dependency; behavioral assertions remain unqualified. Independent source review classifies four failures with names that also passed at v0.9.0 as stale assertions: JSX line wrapping preserves the complete-guide disclosure; two setters intentionally accept document-memory fallback when localStorage is blocked (6fb5ad51); and missing readiness OS now remains unknown rather than fabricated 25.10 (cd75899a), with new malformed/missing-image tests passing. The remaining profile-review failure needs its own fixture/harness diagnosis. No full web green is claimed.
Exact v0.9.0 manifest: 473 passed, zero failed. Final current manifest under a genuine non-root user, no inherited SUDO variables, and explicit umask0022: 959 passed, four failed, five skipped. Remaining failures are two plugin/schema documentation-integration assertions and two Bun5000ms runtime/process-group timeouts. These are non-default plugin/rehearsal surfaces; under the October 2 release-owner ruling, document them without claiming they are pre-existing or that the suite is green. Earlier root/SUDO/umask-contaminated results are superseded by this final run.
New resume-trust/safety harnesses were absent at v0.9.0. Current resume-trust is 18 passed/two failed (fixtures omit schema_version3); resume-safety is 84 passed/48 failed (extracted-function fixture omits resume_recovery_directory_safe). Those fixture failures do not establish a live reboot defect. The manifest edge-cases script is absent at both refs and was not executed. Full info-level ShellCheck is SC2329-only at both refs; warning-level checks pass.
Remaining release qualifications:
- The real stock factory qualification on source1eff0be0 used a disposable Ubuntu24.04 VM with systemd and a real kernel; it retained24.04 and passed8/8 critical smoke checks. Full installer exit1 reflects UV/DCG checksum refusals in #427; repeat-install, zero-warning doctor, subsequent services, and opt-in26.04 upgrade remain unqualified. The exactv090 factory disconnected/exit255 during guest kernel preparation before reaching those installers, so no full-factory parity is claimed. Separate stock component comparison qualified four old/current guard receipts rejecting today's identical upstream bytes and effective main pins, with zero rejected-installer executions; this is current-byte component evidence only.
- Required local external-checker validate, list, and check --dry-run --local ALL passed inside the actual Ubuntu qualification guest using its pinned published Linux executable. This is metadata/planning proof, not proof that rejected upstream installers executed. The Mac-native checker remains unrun due to RCH#83 Darwin flock interface; no development/test shim or source lock was bypassed.
- External uv/antigravity byte drift (#422/#423/#424/#425) remains unapproved. No checksum authorization is implied by this issue.
Follow-up acceptance: preserve assertions and evidence; repair stale harnesses separately from product behavior; independently authorize or reject upstream installer bytes in #427; qualify full isolated installation, repeat/doctor/services, and explicit upgrade/resume paths. The approved LTS/default fix can ship under the release-owner ruling with these limits recorded in CHANGELOG and release notes. Published-tag execution and final DSR public readback are now terminal; their proof limits are recorded below. Isolated harness-owned temporary cleanup is authorized; user files/data, services, locks, and peer work remain preserved.
Final published-tag qualification (2026-10-03 UTC): the stock factory ran against v0.10.0/aff6199215cf6396e3ace3053cad1dc4e26ce7cc in an actual fresh Ubuntu24.04.5 guest with systemd PID1. The exact tagged source archive transferred to the checker matched in controller and guest: 2c620554c43ba70fef74821ffcd639ceed1f7e0910f10df468f4518913663f58. It retained24.04 and passed8/8 critical smoke checks with zero smoke warnings. All three required guest-local commands of the pinned published external checker passed. Full first-install returned1: UV checksum verification refused at02:11:31 UTC, and DCG checksum verification refused at02:28:08 UTC, with the same expected/downloaded hashes in #427. Later UV binary availability does not qualify its rejected verified installer. Repeat installation, zero-warning doctor, subsequent independent services, and explicit26.04 upgrade/resume remain unqualified. The owned test container was stopped successfully; independent inspection reported Runningfalse, OOMKilledfalse, Pid0. Scratch VM disks were retained.
The installed checksum metadata hash26db10c836ad60383a6684ec2c9954043e473d0d42f3457f8ecb6bd6adeb44f2 differs from tagged979081cb6a7efab6679989696e1b508a42aec6db141f8ba1ab84ba508aea2075 solely because the unchanged installer uses command substitution and printf to remove the final line feed. Exact tagged bytes with that one trailing LF removed reproduce the installed hash. All effective UV/DCG pins remain unchanged and unapproved. This serialization difference is not checksum drift or installer authorization.
A fresh source-only dependency audit adds a release gate to this existing qualification issue.
The authoritative root lock still selects Next 16.1.4/Sharp 0.34.5. Current primary metadata matches 38 Next advisories, including AVIF image optimization; the Sharp vendor's newest librsvg fix requires 0.35.5. Source uses App Router and next/image with restricted owner/repository remotePatterns. Attacker control, deployment/runtime and exploitability were not tested; no live RCE claim is made. Windows-specific entries do not establish a Windows deployment.
Actual published Next 16.4.0 package bytes passed npm digest verification and request Sharp ^0.35.4; a newly accepted lock must resolve at least 0.35.5. Empty current catalog queries for these targets are research metadata, not a working/security/performance pass. Preserve CPUs=1; qualify normal native optional packages, production build, wizard/cloud/lesson/image/API behavior and actual supported runtime/architecture before a new release.
Blind TypeScript 7.0.2 selection is incompatible with captured source: its root JS exports only version fields, while fifteen ACFS tests use transpileModule and latest TypeScript-ESLint supports <6.1. Latest GA SDK majors require Node >=22; latest Lucide removes the current Github icon; web Zod 4 conflicts with the unused adapter's Zod 3 peer. These are migration gates, not failures alleged against currently locked APIs.
The audit covered all 45 declarations, both tracked Bun locks (687 distinct versions), locked optional/target metadata and ignored Yarn separately. No canonical/dependency/tracker change or package/compiler/native/installer/service test ran. Initial 4c96363c and timestamped df06d2e7 source/public captures agree on all 103 selected inputs; root independently verified all 109 expanded source-input hashes unchanged at canonical/public 3e30d33a809f163c0305842f6e3e3db355ef3ba2 at 03:00 UTC, also selected by the 03:13 UTC preflight. All ten mirror tags matched public releases at their recorded audit capture times; HEAD/asset metadata does not replace actual bundle/hosted acceptance.
A subsequent public update,
aa5d186b7c8042c1c391995a5686accae4e0af25, changes the Beads source ledger and the Agent Mail/SLB installer checksum pins plus their generated internal digest. The selected dependency manifests and Bun locks remain unchanged. This audit does not transfer the commit message's checker result to a new live installer or provisioning pass.A new tag remains held on existing factory/checker/build/performance gates, owner-held installer/monitor bugs and genuine per-dependency acceptance. No release, issue or bead is closed by this research update.