Release readiness progress

2026-10-13 05:50 UTC — artifact build complete, native acceptance preparation

Frozen product 8fb6f413179b094288316e25845c137440ba23fa completed all18 fresh artifact cells with exit0/confirmed stop and reproducible A/B packages. Build evidence on #40 binds DEB 8edfc7709f4b5dc3da01c00a1d8c442470298e96f8c8e502cfb14e8c9e713e92, RPM a54f55e7bf1b2230e026b49d6b86023778a9648ae49b11c6bcb0d558db34a840 and provenance 97fb6cee881033db7e4bacb15e43358d330126eaa9731ba3e685e8d24778eeb4. Pip owns the frozen record. Prior candidate acceptance is historical and does not carry into this ledger.

Finite harness source corrections now have exact raw receipts: custody prefix/depth reader, browser AB/C oracle, and measured R3 transition allocation. Each successful source service stopped and its owned temporary scratch was removed. The native fixture constructor built metadata-only predecessor fixtures with unchanged payload, exit0/stopped; it does not complete the actual owner walkthrough.

The separate simulator checker registration red preserves its named absent-mechanism failure before correction. Its source green plan is prospective. Native custody integration and browser native integration are prospective, with source controls and native binding still needed. Source checks do not qualify guest, browser, outage or two-hour acceptance. #41–#46, actual owner walkthrough, ledger and publication remain incomplete; no tag or publication occurred. PRs63–66 remain in the owner merge lane; Draft67 awaits exact-head extendedCI.

Guarded shared-cache cleanup recovered52,998,701,056 physical free bytes. At05:27Z, full DATA census was32,286,188,461 bytes and available RAM22,016,053,248 bytes; no project service was running. All subsequent successful source scratch was removed. Failure evidence, package/provenance and required source/tool/image inputs are preserved. Future Cargo is cold and needs a concrete reservation; the former4GiB host estimate is inadmissible. Work continues through #59. Epic33 supersedes32.

2026-10-12 22:01 UTC — new frozen candidate build preflight

Pip's frozen record on #40 binds 8fb6f413179b094288316e25845c137440ba23fa to three green CI records. The prospective build plan pins exact serial commands, driver hashes and reservations. Both detached checkouts are prepared, guarded cache reclaim completed, and strict post-reclaim census measured 84,393,391,759 bytes. Fresh console A/B builds and their complete dist diff ran with exit 0 and confirmed cgroup stops. Guarded target cleanup and matching-DEB-image guard/control commands are published before execution; DEB/RPM builds and acceptance cells have not run. All earlier candidate results remain historical. #33 supersedes #32; no tag or publication has occurred.

Current owner decision — 2026-10-12 20:11 UTC

Owner decision on #33 requires reproducible console icons before release. After #57/#58 merge, the new frozen candidate needs two separate console/package builds and fresh #41/#42 gates. Historical service/query run 03 records six main and four full query cells that exited 0 on superseded a5dbda7a packages; none carry into the new candidate ledger. #42 remains open. Work is coordinated through #59; no tag/publication has occurred. Earlier checkpoints below retain their original candidates and outcomes.

Console command admission checkpoint — 2026-10-12

Exact candidate a5dbda7a4fd6465c94f6505b3214cbcbc2130c82 completed #40 builds and #41 finite installation acceptance. #42's first disposable smoke failed during enrollment with HTTP429 before measurement. The admission prerequisite report preserves that failure, independent red schedule control, 50 passing harness tests and a passing successor native smoke on unchanged packages. The separate harness PR and full six-main/four-query matrix remain pending. The two-per-second command schedule retains all session checks and refusals; no product admission or decision rule is relaxed. No release is qualified or published.

Replacement installation checkpoint — 2026-10-12

PR #53 is merged with its six commits preserved. Frozen a5dbda7a4fd6465c94f6505b3214cbcbc2130c82 has green matching main checks and identical-tree PR extended evidence. Exact replacement packages were built reproducibly and #40 is closed. Installation run 03 passed all four positive cells and detected all six named negative controls, with SELinux Enforcing and no remaining companion after removal. Debian/RPM hashes are 54cddf548c1a307aade8c3ac4332ede2007e2bc9603ab0cba72d8297287d6cee / 982ad6923e17f64b35700dcfafb2994ed68e32b2c6b368589a8b6a0d550cac79. #41 finite B8 is complete; #42–#46 remain open. Epic #33 supersedes #32. No tag, release or package upload has occurred.

Service-opening repair checkpoint — 2026-10-12

Epic #33 supersedes #32. The owner authorized the startup repair after frozen ca84d982 failed Debian candidate upgrade. Repair head 084d0aa0c2c67601f3996eb4f12cf24ff0e18d2a preserves every service directive and all-component link refusal through a descriptor walk. All 20 fast gates, 32 focused security tests, documentation checks, 55 checker probes and hook tests exited 0. Its native report retains the original red regression, invalid outside-scratch fixture, failed storage admission, interrupted run and cleanup.

Owner merge with a merge commit and a replacement frozen source are required before rebuilding Debian/RPM packages and repeating affected #40/#41 evidence. Old packages remain private failure artifacts; #41 and later exact-candidate gates remain open.

Frozen candidate installation failure — 2026-10-12

Epic #33 supersedes historical #32. Frozen ca84d9823b5e3f8f39f40647cedffef0acff3aac was built reproducibly; #40 is closed with explicit owner authorization. Debian/RPM package hashes are 241679e2d63d75f0ec628376baaff80a1070dc44991c7ca8c430dd9c66542219 / 43ee9a896713e60ae9fd26d92757c16661c61dfcfd60e1bee48465058ce32bad.

Installation campaign run 02 records failed rel-deb-life-01 (exit 2): predecessor baseline exit 0, candidate L1 failed, L2/removal and all later cells not run. Candidate companion exits ENOSYS and the supervisor stops. Isolated read-only probes confirm RestrictSUIDSGID=yes blocks its mandatory openat2; installed controls and candidate bytes are unchanged. Original failure and an initially inconclusive fixture-admission diagnostic remain preserved. Disposable diagnostic scratch/processes are cleaned; the stopped failure fixture is retained in the controlled evidence archive.

#41 and B8 remain incomplete. Release acceptance is stopped for the owner product-fix/new-candidate decision required by the handoff. No tag, release or package upload has occurred. Older checkpoints below retain their own revisions and outcomes.

Integration checkpoint — 2026-10-11

Console #29 and security specification #30 were merged into main 225b165. Historical qualification #26 is closed with its unique evidence and branch preserved. Security implementation #31 is now merged into main 6a3b9c9; no open PR remains at this checkpoint. Issue 32 owns the finite B1–B13 release queue. The integration review records the native-browser 429, mutation timeouts, Cargo artifact-path failure, prospective fixes and the passing 144-assertion finite browser trial.

Historical head 1777e66 passed fast/focused workflows, but extended mutation testing timed out and the remaining workflow was canceled after that failure. Successor ed4b95c completed local checks and all three matching hosted workflows. Downloaded artifacts passed independent validation: 20 fast checks, ten extended checks and 26 focused security regressions. Actual merge 6a3b9c9 has the tested tree 61f2d7a059633e145f011b1c62c1871811b5730d, preserving separate policy commits. Issue 32 B9 is complete; the exact-package/deployment acceptance queue remains. The agent execution review records repeated repair causes and a proposed Codex CLI optimization comparison. No new release or deployment qualification is claimed. Older sections below retain their original candidate identities and are historical checkpoints.

This is a progress checkpoint, not a release or deployment qualification. Work continues on the registered queue; no release tag has been published.

Historical console and package candidate

The native service, Spindle custody path and packaged Leptos/WASM console provide scoped queries, local WebAuthn passkeys, scoped human/workload/delegated access and bounded controls. Console build 09 corrects the hosted 200% zoom pagination overflow. Debian build 04 and RPM build 03 have matching 637 common payload files; their native binaries and qualification helpers are byte-identical to build 03. Exact package identities are recorded in the installation checkpoint.

The bounded native metadata cache repair preserves independent query answers; its measurements and earlier failures are in the cache investigation. Against exact Debian04/UI09 and RPM03, production million-row Segment seed1 (release-query-segment-seed1-successor-02) exited 0 in 573.940 seconds: all 200 independent oracle verdicts and all eight gates passed. Maximum p99 was 504.340 ms before restart and 447.509 ms after; native high-water memory was 82,428 KiB. Actual UI body completions advanced in both phases with zero status/transport failures, immutable identities held, and owned cleanup completed. Segment seed2 (release-query-segment-seed2-successor-02) subsequently exited 0 in 614.656 seconds: all 200 independent oracle verdicts and all eight gates passed. Maximum p99 was 422.441 ms before restart and 507.557 ms after; native high-water memory was 84,444 KiB. Actual UI body completions advanced 1→5 and 6→10 with zero failures, immutable identities held, and cleanup completed. Seed3 and the Journal cell have not run on this pair. These results are specific to this candidate and are not inherited by its successor.

New enrollment now requests resident credentials while retaining required user verification. Commit 829babe passed its two targeted native option regressions (exit 0); actual resident-key browser acceptance and the successor Debian05/RPM04 pair remain pending. Existing nonresident credentials remain usable through principal-ID sign-in. Virtual authenticator capability alone does not establish resident enrollment. The Firefox causal diagnostics retain two failed login diagnostics and a passing 127-check finite CTAP2.1 run; standalone, physical-device and resident coverage remain separate.

Historical campaigns and CI

production-soak-full-03 subsequently failed after 1,587.618 seconds, before full-soak completion, on exact Debian04/UI09 and RPM03. Its aggregate allocated-byte disk probe failed closed when two concurrent rootless package-builder directories denied traversal. The UI polling prerequisite passed; inputs and harness remained immutable, pre/post freeze checks exited 0, and all owned cleanup completed. The trial is failed, not qualified; its original ledgers and failure state remain preserved. A read-only browser witness crossed a real passkey refresh and observed visible, connected polling with increasing body completions and zero failures. No full-soak result is available yet. The final resident-auth candidate has a fresh soak and three serial 30-minute outage seeds queued; earlier interrupted attempts remain preserved in the production campaign checkpoint.

Hosted CI run 38072930139 at 8597c42 completed successfully: all 20 enabled fast receipts, dependency policy, WASM/build, packaging and actual Chrome checks passed. Firefox shell checks passed; they do not establish its full authenticated workflow. Bun CI/hooks remain disabled. The newer CI invocation at 414fb29 is in progress as reported by the release coordinator; no result is claimed for it. Hosted CI does not replace the longer exact-package browser, installed-system or service campaigns.

Acceptance evidence boundary

The queue retains final-candidate resident browser acceptance, full R2, all three outage seeds, all four fresh query cells, remaining main/pressure cells, installed/cross-family checks and final source/CI consolidation. Each cell must satisfy its original registered gates and resource admission; a smoke, interruption or historical pass is not a substitute. Raw telemetry, credentials and private keys stay in controlled local evidence. Wiki reports publish bounded results and provenance, not private artifacts.

Fixed-query caller checkpoint — 2026-10-12

The caller report retains two distinct harness failures and a fresh disposable query smoke (exit 0, all eight gates). Artifact source remains a5dbda7a. Six main cells passed their registered clearing-v2 gates; older sampled-v1 edge diagnostics failed in five cells. Four full query successors are still pending; #42 stays open. Epic #33 supersedes #32. No deployment or release qualification is claimed.