0.9.2 single-runtime reconstruction brief

This is the recovery ledger for rebuilding pull request #817 around one runtime architecture. It is both the implementation brief and the status record. Every phase ends in a recoverable Git commit, and this table is updated with the exact commit and verification result before the next phase begins.

Identity and recovery sources

• Reconstruction branch: codex/reconstruct-0.9.2-final
• Approved release input: c5c82c32da4b959c0b7d6ea9554f06a82c2f592e
• Pull request: #817 (release/0.9.2 into main)
• Working clone: .claude/worktrees/codex-reconstruct-final
• Primary recovery journal: /home/founder3/.codex/sessions/2026/08/17/rollout-2026-08-17T11-02-55-01a01076-2c53-7813-ab6b-e8af90d836c9.jsonl
• Show-review recovery journal: /home/founder3/.codex/sessions/2026/08/23/rollout-2026-08-23T11-24-21-01a02f6f-f438-7543-8503-8b9e9511df5f.jsonl
• Parsed call ledger: /home/founder3/code/github/itlackey/akm/.claude/reconstruct-recovery-calls.json
• Parsed mutation ledger: /home/founder3/code/github/itlackey/akm/.claude/reconstruct-mutations.txt

The prior damaged replay and partial temporary replays are evidence only. No file or commit is promoted from them without replaying the original successful operation against the approved input and verifying the result.

Required architecture

1. Legacy task files are accepted only by the explicit v2-to-v3 migrator. Normal loading, scheduling, projection, and execution accept task v3 only.
2. Markdown and GitHub-shaped YAML workflow sources compile into one source IR. That IR freezes into durable plan v4 and one workflow engine executes it.
3. Durable plan v4 is the only executable or resumable stored workflow plan. Pre-v4 plans are rejected; they do not enter a parallel decoder/replayer.
4. Command, task, and workflow execution use one resolver and lowering path. Shared lowering replaces superseded dispatchers instead of wrapping them.
5. Compatibility is confined to deliberate input and storage boundaries. It is not threaded through the current runtime.
6. Semantic inference uses the normal external @huggingface/transformers package/build input. There is no copied runtime under src/vendor, no installed-consumer dependency policy, and no second semantic package tree.
7. A contract boundary is tested once. Distinct fault, security, durability, and platform behavior remains covered; duplicated characterization and consumer-by-consumer ownership tests are removed.

Upgrade behavior that remains

• akm upgrade remains the ordinary package/binary updater.
• Explicit akm migrate status, dry-run, and apply retain the task-v2-to-v3 conversion path, including fail-closed ambiguous inputs.
• Released additive database migration ledger entries remain recognized and current managed databases apply known additive DDL on open.
• A durable-v4 workflow resumes from its frozen plan without rereading source, configuration, or index state.

These are product upgrade paths. They do not authorize general compatibility runtimes, three-database cutover machinery, old config-shape coordinators, or pre-v4 workflow replay.

Explicit deletion and replacement ledger

Every deletion is checked for callers, documentation, package closure, and a remaining owner. A green test alone is not evidence that two architectures are acceptable.

Pull-request review fixes that must survive reconstruction

• show renders only indexed entries; physical ownership may arbitrate source identity but cannot become a content fallback.
• Frozen standalone scripts preserve true entry semantics for guarded .js and .ts scripts.
• A leading bare akm in a task shell command is bound safely to the current installation without rewriting explicit paths.
• Scheduler-originated nested command/agent runs preserve the closed five-key AKM directory context without reopening arbitrary runtime environment override.

Replay rules

• Replay only operations whose original tool result succeeded.
• Preserve original timestamp order within each phase.
• Replay dynamic apply_patch programs, not merely literal patch headers.
• Include the recorded mechanical renames/import rewrites, lock helper rename, and task-v2 fixture restoration at their original positions.
• Exclude temporary diagnostics, generated build output, failed patches, and ephemeral .codex progress artifacts.
• If a patch no longer applies, stop and classify it; do not force a fuzzy or guessed edit.
• Record the exact resulting commit and gates here before continuing.

Checkpoint plan and live status

Phase 8 remote ledger

• Complete-history candidate d5540702e7 (tree 68769622da) was verified in an independent no-hardlinks clone and approved twice with no P1/P2 findings. GitHub release/0.9.2 was fast-forwarded from c5c82c32da to that exact SHA; no force-push or history rewrite occurred.
• Fresh CI passed both workflow-syntax runs and both akm-eval smoke runs, but its unit lane found two failures in appendevent-hot-path.test.ts. A clean local reproduction without the developer-installed opencode binary proved that the direct-reflect fixtures configured defaults.llmEngine but no canonical defaults.engine; the host fallback had masked the missing test selector. Production fail-closed resolution is correct. The remediation must select the named test engine explicitly and prove the injected chat seam ran. PR body, review threads, and milestone comments remain untouched pending a reviewed replacement SHA and fresh green CI.

Phase 3 recovery checkpoints

• 9bc401d7a — removed parallel runtime compatibility paths.
• d9e873466 through d5143fccf — removed runner, connection, adapter, journal, and duplicate boundary compatibility.
• 99894b1b0 — converged model resolution on one model-map boundary.
• 35fd98167 — removed harness aliases, split runtime identities, the OpenCode JSON session reader, and their duplicated tests. Focused result: 315 passed, zero failed; tsc --noEmit passed.
• 44f5bb992 and 7cbd8d607 — closed the current session-source boundary and canonicalized adapter input layouts. The session checkpoint received an independent APPROVE; 199 focused tests passed across the two checkpoints and tsc --noEmit passed.
• 5b16768fc — reduced akm migrate to the explicit task-v2-to-v3 status, dry-run, and apply path. Focused result: 74 passed; tsc --noEmit passed.
• 988e69c60 — deleted 21,179 lines of general config/content/ref migration, three-database cutover, backup/restore, crash-recovery, and duplicated characterization code/tests. Focused result: 486 passed; tsc --noEmit passed.
• 8055cd1e4 — replaced the copied semantic runtime and installed-consumer policy with the ordinary external @huggingface/transformers dependency. Build and 126 focused checks passed; neither src/vendor nor a copied semantic tree under dist/vendor remains.
• 991906409 and 497ea3c7e — removed the stored-command agent alias and legacy execution ownership exemptions. The remaining command/task/workflow paths lower through current execution owners; focused checks and TypeScript passed.
• f91d23c3e, a0329bcaf, and f453927b4 — made the released state ledger advance automatically on managed open, removed the general migrator's synchronous lock writer, and separated current runtime ownership from immutable migration history. Known prefixes advance; unknown ledgers fail closed. The released migration ids and DDL were not rewritten.
• 0070d6313 — replaced a 936-line registry meta-analyzer with four boundary ownership contracts while preserving behavioral transport coverage. Focused registry tests passed 58/58 outside the localhost-restricted sandbox.
• c03a0927e through cab9d1fb7 — tests-first proposal ingress convergence: workflow proposals now compile peer .md/.yml sources through the shared source-IR compiler. Independent review approved the exact checkpoint.
• d1be1f00a through 2a64bbace — tests-first removal of the pre-resolved reflect RunnerSpec injection seam. Reflect now resolves its named engine, process overlay, and immutable config/profile snapshots through current lowering without raw runner or explicit-engine ingress. Independent review approved the final checkpoint after 91 focused tests, TypeScript, Biome, and a real-dispatch mutation probe passed.

Phase 4 recovery checkpoints

• 8ac4dc34a through c949a8da8 — tests-first index-only show repair. Only the indexed entry may render; physical ownership is retained solely to stop lower-priority retargeting and diagnostics. Focused result: 88/88 and TypeScript passed. The final combined review approved this repair.
• 5fd5d7c5b through 0b18cac8b — tests-first standalone script entry repair. Frozen .js and .ts scripts observe true main-entry semantics during the snapshot import, with Bun.main restored in finally. Source-entry and compiled standalone scheduler controls pass. The final combined review approved this repair.
• 987e81ba4 through 8460f684e — tests-first runner repair. A leading bare akm binds to the current installation while explicit paths remain authored; scheduled nested command/agent preparation freezes only the five AKM directory keys and refuses arbitrary caller overrides. Focused result: 83/83, including a real PATH-stripped scheduled run; TypeScript and build passed. The final combined review approved this repair.

The post-phase audit confirmed the core task-v3-only, workflow-v4-only, source-IR, external semantic dependency, and shared lowering cutovers. It also identified the following remaining cleanup owned by phase 5: remove the dual legacy/current derived-index schema, gate destructive historical state-ledger upgrades safely, decide and pin the prompt-free interactive agent boundary, remove exact-version Hugging Face fallback branches, remove the health session-log compatibility result, and consolidate duplicated boundary, execution, scheduler-backend, and credential-safety tests without deleting unique fault/security/durability/platform invariants.

Phase 5 recovery checkpoints

• 39ecd0ee8 through 4bfa15f29 — removed the always-pass raw session-log health compatibility check, result field, collectors, and text/HTML/docs surface. The current session-extraction health boundary remains. The full health/report matrix and TypeScript passed; the GREEN removed 155 lines.
• fc67dd5ba through 2cb329e06 — removed old Transformers result-shape and catch-all per-item retry branches. The exact external 4.2 runtime now has one validated batch Tensor path and propagates inference failures without duplicate execution. Focused result: 124/124 and TypeScript passed.
• 84eb49d02 — consolidated execution-boundary tests around one production AST lint, one hostile analyzer-evasion contract, and behavioral task-v3/source-IR/ durable-v4 suites. Six duplicate consumer/source-text suites and redundant production inventory assertions were removed (642 lines); the central lint and 194 focused behavioral checks passed.
• df8c6afde — removed the requireLlmConfig/getDefaultLlmConfig convenience API and its duplicate config-level resolution tests. The canonical engine resolver, credential materialization, and dispatch boundary remain covered; 102 focused tests, the execution-boundary lint, and TypeScript passed. Net change: 160 lines removed.
• 6cffb18e6 — deleted retired akm info shape fallbacks, an unused test JSON serializer, and a duplicate migration prose contract. Current info/runtime boundary tests and TypeScript passed. A pre-existing renderer golden mismatch remains separately tracked for final gate remediation.
• 2871ee70f through 0afb771cb — tests-first strict website input boundary. Website page/depth limits, robots policy, and crawl timeout now accept exact typed values only; coercion-shaped strings/nulls/booleans/fractions fail closed. A duplicate 166-line resolved-request projection suite was deleted. Focused result: 208/208 and TypeScript passed.
• df196e1d5 through 803b134e5 — replaced the retired judge-calibration profile/config projection with one selected current LLM engine plus the current distill-only improve strategy. A bundle-local .akm/config is now explicitly inert for this evaluation path. Focused result: 13/13 and TypeScript passed.
• 41b86e1a0 and b145c5706 — removed active prose and comments that still described deleted runtime aliases, source arrays, and compatibility shapes. The current bundle/provider and inert-sidecar narratives are now explicit; 49 focused tests and TypeScript passed after the final slice.
• 27fc949c3 through aff0c11c6 — tests-first replacement of the prompt-free interactive akm agent raw resolver/runner bypass. Native and SDK launches now use the shared private interactive lowering boundary, retain TTY/profile semantics and lease redaction, and no longer need command-layer execution exceptions. Independent review approved the source candidate; the adapted reconstruction series passed 15 focused tests, the production boundary lint, TypeScript, and build.
• d6bff9b8a — fixed Markdown-only workflow authoring template validation to pass a real .md identity into the one source-IR compiler. The former OKF native-workflow failure is closed without an alternate parser or extension exception; 37 authoring/adapter tests and TypeScript passed.
• 1f92e6ccd — repaired current renderer projection at the owning boundaries: workflow step instructions now come from the same source-IR derivation used by execution, and absent command/agent/script metadata is omitted rather than materialized as undefined. The previously red renderer golden and 151 focused source-IR/show/renderer checks passed with TypeScript.
• 25679d388 and de98b5f0a — tests-first deletion of the final proposal filesystem compatibility reader in akm-eval. Proposal-quality evaluation now requires the current state.db queue and fails closed when it is absent; the retired .akm/proposals tree is neither a runtime nor an evaluator input. The GREEN deleted 108 lines and passed 21 proposal/eval checks plus TypeScript.
• a1d83f571 — removed the last active proposal/provider comments that still described retired filesystem proposal ingestion and provider compatibility.
• d00afc70d — removed the test-loader exception from executable preflight. Every non-terminal workflow run now revalidates its canonical v4 row and hash before acquiring a lease; the loader remains assertion-only and cannot suppress durable-plan authority. Frozen-plan, lease, and native-engine coverage passed 71/71 with TypeScript.
• 2c6827b34 through 95b3bf7ea — independently approved consolidation of copied execution value-state assertions. One table-driven contract now runs direct, task, and workflow preparation through cascade resolution, canonical encode/decode, authorization, alias expansion, and lowering while preserving omitted/null/false/zero/empty distinctions. The unique lease, redaction, hostile-accessor, transport, fault, and durable-resume cases remain in their owning suites. The integrated matrix passed 129/129 with TypeScript.
• ccd812d2e — re-designated the two intentionally changed health goldens after deletion of the retired sessionLogAdvisories result. The designation ledger, captured-at-head checks, and health golden suite passed; full lint then completed successfully.
• 07d2b3fbc — consolidated the 1,464-line registry credential safety suite around one complete unsafe-URL case table and one proof per real boundary: config mutation/persistence, provider fetch refusal, fetch/log egress, and public projections. Depth, candidate-count, decoded-byte, malformed-percent, invalid-UTF-8, redirect, and safe-negative cases remain. The file is now 1,047 lines (net 417 lines removed); 76 direct tests / 34,583 assertions and 245 adjacent registry tests passed, with TypeScript green.
• 2be58310a — corrected active lint/index comments that still named direct parseWorkflow ingress. Production value-imports now visibly converge on compileWorkflowSource; 88 source-IR/lint tests and TypeScript passed.
• 301be606b through 092400a19 — independently approved scheduler-backend consolidation. Cron, schtasks, and launchd now run one shared 14-case CAS, ownership, snapshot, rollback, and context-signature contract while retaining their platform-specific parsing, encoding, stabilization, compensation, and failure cases. Rejected create/update/remove operations prove zero native mutation on every backend. The four-file test diff is net 290 lines smaller; 206 tests / 680 assertions and TypeScript passed after integration.
• fb4f37dea and c1dab14aa — tests-first removal of the ordinary CI job that still invoked the deleted three-database cutover property suite and workflow v3 engine suite. A current workflow contract now rejects every explicitly named test path that does not exist, so retired architecture cannot survive as a broken release gate. The focused CI/workflow/Node-24 matrix passed 14/14.
• 113959c8a — removed four deleted workflow-v3/duplicate-engine suites from the test-isolation grandfather list and lowered its shrink-only ratchet from 65 to 61. The existing stale-path contract moved from one deterministic failure to 3/3 green, and the isolation linter reports zero violations.
• 198c4e542 — restored two exact assertions requested by independent review of the registry consolidation: every representative invalid CLI mutation is pinned to usage exit 2, and the mixed top-level/encoded credential URL is pinned to the fail-closed (invalid registry URL) projection. The direct suite remains 76/76 green. Fresh independent re-review approved the final consolidation after 245 adjacent registry tests, TypeScript, Biome, and the exact fail-closed assertions passed.
• 877195a18 — repaired two stale test fixtures exposed by the first full unit gate. OpenCode conformance now rejects the deleted singular skill/ alias and round-trips only canonical skills/; the durable-v4 workflow fixture now supplies an explicit empty exact-model map instead of reading the installed models.json. The formerly deterministic failures pass 40/40, and the OpenCode SDK file's shard failures were classified by a 38/38 isolated pass.
• 49394d8d3 — completed the test-only durable-v4 freezer by persisting the same paired working-directory and executable identities production freezes for a CLI agent runner. The decoder remained strict; the formerly failing manual frozen-judge case and its SDK/LLM peers pass 50/50. Fresh independent review approved both fixture repairs after 360 focused tests / 4,177 assertions and TypeScript passed.
• Full unit checkpoint after the fixture repairs: 3,812 pass / 0 skip / 0 fail across all eight process shards and 283/283 files with normal local process/listener access. The earlier npm-pack, SDK-lease, and OpenCode-startup failures were restricted-namespace interference; their three files also pass together 126/126 outside that namespace.
• fb4f37dea through b4e6175c1 — independent review approved deletion of the obsolete slow-gated CI job and its stale isolation/docs references. The job's only payload was the already-deleted three-database cutover and workflow-v3 suites. Active workflows now reject missing explicit test paths; the final focused review passed 23 tests / 205 assertions plus lint, TypeScript, Biome, and workflow YAML parsing.
• 74dec1687 through 70023007f — repaired all eight deterministic failures from the first full-integration checkpoint without restoring a general migrator, historical proposal projection, workflow-v3 work-list field, or stale scheduler diagnostic. The seven implicated files now pass together 96/96 with 379 assertions.
• 1660919bd through 885a85d0c — integrated the independently approved state-ledger safety series as its original tests-first checkpoint chain. Ordinary managed opens automatically advance only classified safe prefixes; historical destructive migration 018 requires explicit upgrade intent. An existing unversioned or empty-ledger database is rejected byte-for-byte by ordinary open, while explicit upgrade holds one verified BEGIN IMMEDIATE window across the descriptor-bound pre-001 snapshot, ledger creation, and immutable migrations 001/002. The pre-018 snapshot and immutable 018 also share one writer-exclusion window. Phantom/lost transactions fail closed; randomized O_EXCL/O_NOFOLLOW backup reservation, inode binding, WAL inclusion, owner-only mode, and no-unlink-on-failure are pinned. Released 002/018 SQL bytes are unchanged. Fresh review approved exact source head cb56cf989; after integration, state/upgrade focused tests pass 73/73.
• e004633aa and 7fe9818a5 — the first post-integration full gate exposed that the new durable-file reservation treated SQLite's exact :memory: identity as a filesystem path. The tests-only RED proved a literal zero-byte :memory: file was created and the next handle was rejected as unversioned. The GREEN bypasses only the exact SQLite in-memory identity, installs the current schema as a fresh isolated database, and leaves the durable inode/snapshot path unchanged. The regression and extraction tracking suites pass 36/36; TypeScript and targeted Biome are green. Fresh independent review approved the exact RED/GREEN pair after Bun 1.3.14 and Node 24.18 both proved 22 migrations, isolated handles, and no literal file; its broader state/extract matrix passed 112/112 with lint, TypeScript, and build.
• 4f93a217a through 6cbe88052 — integrated the independently approved canonical-index series as its original 23-commit tests-first history. The derived database established one exact v21 entries generation at that checkpoint; hidden columns, non-binary identity, missing AUTOINCREMENT, malformed indexes, and partial current-version schemas are rejected/rebuilt before serving. Durable usage links are re-resolved by canonical item ref across v20-to-v21 ID reuse; enrichment caching uses the same identity; removed-source cleanup and improve/consolidate/salience writability use configured bundle ownership, never ancestor path containment. Bundle-identity and evaluator snapshot readers share the generation preflight. Independent review approved source head ed36107fe after reproducing all seven frozen RED groups and checking a 564-test union. The adapted release tree exactly matched the disposable composition tree, retained index-only show, and passed all 58 changed test files: 869/869 with 3,246 assertions.
• Authoritative full-integration checkpoint after the phase-5 remediations: 5,586 pass / 52 skip / 0 fail across all eight process shards and 412/412 files with normal listener/process access. The preceding run's 21 failures were all the now-fixed :memory: identity regression; the earlier eight architecture-contract failures remain green in their combined 96/96 run.
• Authoritative full-unit checkpoint after the approved state integration and SQLite-memory repair: 3,833 pass / 0 skip / 0 fail across all eight process shards and 283/283 files with normal subprocess/listener access.

Phase 7 recovery checkpoints

• b42b04d63 and ad22ceb38 — tests-first closure of a destructive test isolation bug. Bun 1.3.14 keeps os.homedir() bound to the process's real home even after the preload changes HOME; the OpenCode availability test therefore created and recursively removed the real /home/founder3/.local/share/opencode directory during the first post-canonical aggregate. Broad test lanes were stopped immediately. The directory was subsequently observed with only empty log/ and repos/ directories; no recovery or replacement was attempted. The test now injects a unique temp-owned database path, and a new zero-allowlist isolation rule rejects recursive cleanup of fixed paths derived from os.homedir(). The focused isolation/provider set passes 22/22; the isolation lint and TypeScript pass. Full aggregate execution remains paused until the remaining deterministic fixture failures are repaired and the safety rule is part of the committed tree.
• a26cde223 and 8832b8ae0 — widened that zero-allowlist guard to the synchronous, async/promise, named-import, and direct-inline Node removal forms. Both the original fixed-path and the new variants reproduce at RED; the GREEN isolation contract passes 5/5 and the repository isolation scan remains at zero violations.
• The paused aggregate also identified twelve deterministic stale fixtures: six tests attempted an impossible nullable canonical index row, three graph fixtures wrote the wrong bundle identity, two evaluator snapshots created a noncanonical derived index, and one improve-memory fixture omitted its configured writable bundle. Those fixtures must converge on the current canonical boundaries; production fallbacks are not permitted. A separate Node 24 compatibility case returns internal exit 70 instead of its public fail-closed exit, and the final architecture audit found a .meta symlink escape that must be closed before release.
• 4a2325c6a and fd55bff16 — aligned all twelve deterministic canonical-index fixture failures without weakening production. Physical-owner coverage no longer fabricates impossible nullable identity rows; graph seeds derive the same installation/component identity as the indexer; evaluator snapshots build an exact current derived-index schema; and live improve declares the writable bundle whose rows it indexed. The four formerly failing files pass together 72/72; TypeScript and targeted Biome pass. dd61325e6 records the formatter-only follow-up. Broad aggregate execution remains paused pending the .meta security repair and Node 24 exit-code diagnosis.
• 4ad1b85ed and 9053e6f8d — tests-first .meta direct-read confinement candidate. The RED reproduces file, .meta-root, and intermediate-directory symlink escapes, including the public show path. The GREEN refuses every symlink component, proves lexical and real-path containment, opens the final file with O_NOFOLLOW, compares the opened descriptor with the validated path inode, and reads only from that descriptor. Normal/index-only show and ownership coverage passes 89/89; TypeScript and targeted Biome pass. Independent review approved the exact pair after focused/adjacent show, TypeScript, lint, and build passed and generic errors proved content-free. The reviewer recorded one P3 defense-in-depth limit: a same-privilege actor already able to mutate the configured bundle could attempt a precisely timed multi-swap race (especially where Windows lacks O_NOFOLLOW); no P1/P2 release blocker or ordinary/static escape remains.
• a264d4a035, 062136b39a, and adc6ac3721 — independently approved tests-first repair of the Node 24 exit-70 failure. Route-only workflow steps had skipped gate-judge resolution and reached a raw missing-judge invariant. The GREEN resolves a judge for every gated step while skipping only unit resolution for route-only steps. Its public regression exits 1, records the blocked step/judge failure, and dispatches zero units. Independent review passed all 28/28 Node compatibility cases and 175/175 adjacent source-IR/frozen-plan/native-executor/gate tests plus TypeScript and build.
• de805bb477 through 1aee64eb98 — independently approved correction of every active-document contradiction from the final architecture audit. The migration guide states that pre-v4 runs restart; index/storage/current-truth docs described the then-current exact v21 generation and rebuild; the permanent OKF SQL uses current identity/document columns; deleted cutover/restore/journal and historical stashDir fallback claims are gone; the remaining maintenance barrier is tied only to live snapshots, task migration, locks, leases, and state. SQLite prose now matches the shared 30-second busy timeout, configurable WAL/DELETE/TRUNCATE modes, and network-filesystem fallback. Independent review executed the OKF SQL against a canonical fixture and passed focused documentation/SQLite contracts with lint and TypeScript.
• f424f2b368 through 5daaf11048, followed by the simplifying sequence acf76d5f through 82f2710e64 — independently approved closure of the remaining real-home deletion boundary. The first tests-first implementation proved formatter, binding, import, and operation-identity gaps, but its single-file value-flow analyzer and duplicate fixtures added 952 lines and still could not be sound across modules. It was deliberately replaced, not retained beside the new path. The final boundary removes the sole general test that created and deleted a directory beneath os.homedir(), rejects a test file that combines a real imported homedir() call with a real imported Node filesystem removal operation, and seeds a unique temp HOME before Bun starts in every unit/integration shard. One consolidated table covers the operation identities once. The replacement deletes 701 net lines from the approved intermediate candidate; focused setup/preload/isolation tests, live isolation lint, TypeScript, Biome, full static lint, shell syntax, and diff checks pass. Independent review found no P1/P2 and accessed no real-home application data.
• 9af328f4cb — first safe broad-gate checkpoint after the real-home boundary was approved. bun run check:changed passed; bun run test:unit completed 3836 pass / 0 fail across all 284 files; bun run test:integration completed 5606 pass / 52 intentional skips / 0 fail across all 414 files. Both sharded runners established their unique temp HOME before Bun started, and the branch remained unchanged throughout the three gates.
• f99fbff6bb and e3fc10bb9a — independently approved repair of the only failures in the first official release-check attempt. Three proposal/reflect fixtures hard-coded /tmp/akm-propose-* while production correctly honored the release gate's unique TMPDIR. RED reproduced exactly 30 pass / 3 fail under a non-/tmp path containing spaces; GREEN derives the prefix from os.tmpdir() and passes 33/33 under both that path and literal /tmp. Production is unchanged. The blocked release-check had already passed workflows, lint, TypeScript, build, package acceptance, 113/113 setup/install tests, standalone, and all 3836 unit tests; it intentionally stopped before Docker and must rerun completely on this replacement SHA.
• 97e74bf93e through 9279d23597 — independently approved tests-only repair from the second official release-check attempt. The state migration safety-copy assertion extracted a valid path with [^\s]+, so it failed when the release runtime used a TMPDIR containing spaces even though the migration and verified backup succeeded. RED reproduced 23 pass / 1 fail; GREEN performs line-bounded prefix extraction, requires the producer's terminal .bak. punctuation, and proves exactly one matching regular backup at the parsed path. It passes 24/24 under both spaced and ordinary external temp roots plus 77/77 adjacent state tests. Production is unchanged. Ten other failures from that attempt were reviewer-environment artifacts caused by placing TMPDIR beneath the repository; their exact files passed when rerun under an external temp root and require no candidate change.
• 89cd5e3977 — complete official release gate on the replacement candidate. release-check.sh passed workflow contracts, lint, TypeScript, build, package acceptance, 113/113 setup/install tests, standalone, 3836/3836 unit tests across all 284 files, and integration with 5606 pass / 52 gated skips / 0 fail across all 414 files. The Docker matrix passed all seven targets with 26/26 smoke assertions each (182/182). The packed 0.9.2 tarball contains 711 files, is 2,445,934 bytes, and has SHA-256 e6962b980e85724bfddce057c8b34d060d1183718c3ef643673d08da76fb6d77. The detached release clone remained clean at tree d06f9edd31903f9cf3caffbbce2a837b1228bbaa; evidence is preserved under /var/tmp/akm-release-check-third.I6zV7v.
• The same product tree passed the non-default release lanes in detached no-hardlinks clones: Node 24 smoke 9/9, full Node compatibility 28/28 (354 assertions), self-update 50/50, real Hugging Face semantic E2E 9/9, current v4/source-IR/rekey slow contracts 204/204 (945 assertions), packed Node and Bun semantic indexing with byte-identical search output, ordinary missing-dependency fail-soft behavior, and Linux standalone scheduling. No src/vendor, dist/vendor, or dist/tests exists; the semantic runtime remains the declared external @huggingface/transformers@4.2.0 dependency.

Rejected phase 5 candidates

• State-ledger candidate 4acfdf392 is not integrated. Independent review reproduced three blockers: its backup ran before writer exclusion and could omit a concurrent row that migration 018 then deleted; a source database with mode 0600 produced a backup with mode 0644; and path selection used an existence check followed by an unconditional unlink, allowing a collision/TOCTOU deletion. Remediation must hold one writer-exclusion window across snapshot verification and migration, preserve owner-only mode, and reserve the backup path atomically and symlink-safely before re-review. First remediation 6a49859f2 also received REQUEST CHANGES: pre-existing unversioned databases could be mutated before explicit backup, failed-snapshot cleanup could unlink a raced replacement, and the VACUUM connection was not bound to the exact inode held under the migration writer lock. A second tests-first remediation closed those three findings, but head 9f71ff7b7 also received REQUEST CHANGES: a pre-existing database with an empty schema_migrations table was treated as versioned, allowing migration 002 to drop unknown operator data before either rejection or backup. A third tests-first remediation is active; no state-ledger candidate is integrated. Its first head 2b348f5a0 also received REQUEST CHANGES: writer exclusion ended between migrations 001 and 002, so a committed update could land after the snapshot and then be dropped by 002; and the generic write-lock helper did not verify db.inTransaction, allowing Bun's documented phantom BEGIN IMMEDIATE to run migration 018 in autocommit before the final COMMIT failed. The next RED must pin both races; the GREEN must keep one exclusion window through 001/002 and enforce pre-/post-body transaction invariants before re-review. Those findings were subsequently closed by tests-first head cb56cf989, which received a fresh independent APPROVE and is now integrated as 1660919bd..885a85d0c; the rejected heads remain listed here only as the immutable review ledger.
• Canonical-index candidate ebb2cc50e is not integrated. Independent review found that one read preflight could serve a populated old-generation database, the v21 shape check did not validate required constraints/indexes, and the obsolete graph rename/copy compatibility migrator remained live. Tests-first remediation must route every serving path through generation validation, fingerprint the complete current schema, and discard rather than copy incompatible derived graph tables. Remediation head ae3a9a96b also received REQUEST CHANGES. Its schema fingerprint used table_info/index_info, so generated transitional columns and a NOCASE unique item_ref index could pass as canonical; two refs that differ only by byte case then collapsed into one row. It also left an obsolete nullable-provenance compatibility test that fails under the current NOT NULL contract, and two evaluator readers bypassed generation validation. A new tests-first remediation must use table_xinfo/index_xinfo, prove byte-wise case identity and hidden-column rejection, replace the obsolete test, and route every evaluator reader through the shared validator. The next head adffb6724 closed those exact schema/evaluator findings but is also not integrated: fresh review proved that its cache preflight still used a retired physical key, removed-source cleanup deleted a configured nested bundle by path ancestry, and improve classified a read-only nested bundle as writable through its writable parent. The last defect produced an actual unauthorized source-file mutation. The active remediation is pinned by tests-only RED a025eeac4; GREEN must use canonical item-ref cache keys and configured bundle identity for cleanup and writability across every consumer before another independent review. The review was frozen at a complete seven-item ledger: the two P1s were read-only nested-bundle mutation and v20-to-v21 durable usage-event ID mislinking; the five P2s are parent-removal deletion of a still-configured nested bundle, the retired enrichment-cache key, raw bundle-identity-guard reads, raw installation-snapshot publication, and failure to prove the required AUTOINCREMENT table invariant. Tests-only REDs a025eeac4, a6d58af3a, and b8f664c0c preserve every failure before the narrow GREEN; each finding was subsequently closed and independently approved at exact source head ed36107fe. The full series is now integrated as 4f93a217a..6cbe88052; the rejected heads remain listed here only as the immutable review ledger.
• b7b917848 through 4ee428e55 — review remediation for the single index mutation authority. The immutable RED pins three failures: a caught inner FTS error leaking an entry through an outer commit, full-rebuild orphaning of scoped utility rows, and a hostile v21 generation reopening with stale FTS dirty state. The GREEN always gives upsertEntry its own nested savepoint, routes full-generation entry/FTS/vector/utility removal through the shared deletion authority, and advances the regenerable index generation to v22. There is no compatibility decoder: v21 is discarded and rebuilt. Vector invalidation remains hard-fail and transactional; child cleanup retains its established best-effort behavior.

Required final evidence

• src/vendor absent and package closure resolves semantic dependencies through the declared external package.
• Searches for task v2, pre-v4 workflow execution, old dispatchers, migration coordinators, and retired aliases have an explicit zero-hit or justified boundary ledger.
• Source and test diff-size breakdown versus origin/main, including the exact remaining net additions and the largest owning modules.
• Focused task migration/runtime, source-IR/workflow-v4, shared lowering, storage ledger, semantic package, and PR-comment regression suites.
• Biome write pass on touched source/tests/scripts, lint, TypeScript, build, check:changed, full unit, full integration, package acceptance, and release check on one immutable SHA.
• Clean tree, no dist/tests, verified bundle, and independent review with no unresolved P1/P2 findings before the release branch or PR is updated.