Record current self-host qualification

reports/audit/completion-audit-report-2026-09-27.md

@@ -43,10 +43,12 @@ Passing local tests do not close any live/provider/install/deployment gate.
   viewports. The refined mobile page had zero horizontal overflow; keyboard tab
   selection, the routing-board interaction, and the installed `torch bootstrap`
   onboarding command were exercised successfully.
-- An isolated temporary self-host qualification built commit `6740f33` as
-  candidate `0.1.0-alpha.0`, recorded passing test/lint/syntax evidence,
-  atomically activated it, and executed its stable `torch` launcher. The
-  installed artifact excluded the pre-existing untracked owner fixture.
+- An isolated temporary self-host qualification built current commit
+  `6e60b09` as candidate `0.1.0-alpha.0`, bound it to tree digest
+  `967af8dee88f1ad889729a5df4eff0ac1ecdaf046639ef1b00f96348b15cc73a`,
+  recorded all 22 required acceptance categories plus passing test/lint/syntax
+  evidence, atomically activated it, and executed its temporary stable `torch`
+  launcher. The artifact excluded the pre-existing untracked owner fixture.
 - No stable version, system service, timer, COMBATRIG state, remote branch, or
   public deployment was changed.
 - The pre-existing untracked `test-torch-config-host-uQKdqL/` fixture remains
@@ -62,7 +64,7 @@ Passing local tests do not close any live/provider/install/deployment gate.
 | 3. Claude reference fleet | Control plane, MCP, Claude adapter, identity/presence/messages, manager-assigned background-ID capture, down/resume; wind-down refusal for active work, Git operations, leases, checks/measurements, and landing; provider session plus managed-worktree ownership verification before stop; durable final worker status and tracked resume brief; virtualized lifecycle scenarios | Implemented virtually and aligned to installed CLI | Run a bounded live Claude multi-domain task and resume it with owner-approved provider quota. |
 | 4. Verification and integration | Exact-SHA checks, FIFO resources, guarded convergence, integration queue, main protection, local bare canonical, reversible forge attachment, delivery-state separation, and read-only doctor evidence for drift count/age, Git operations, runtime availability, and recoverability; `SCN-exact-sha-checks`, `SCN-resource-fifo`, `SCN-safe-convergence`, `SCN-native-integration`, `SCN-local-canonical`, `SCN-forge-migration`, `SCN-delivery-lifecycle`, `SCN-bootstrap-acceptance`, `SCN-worktree-bootstrap` | Implemented locally | Real release/deployment adapters and live receipts remain release-scoped operational qualification. |
 | 5. Runtime portability | Claude and Codex capability adapters, mixed plans, invocation-scoped identity-bound MCP on create/resume without global config mutation, parse-compatible safety and resume option ordering, provider-specific runtime-ID capture and durable fallback; `SCN-mixed-runtime`, `SCN-mcp-stdio` | Implemented virtually and aligned to installed CLIs | Run one authorized live mixed Claude/Codex shared-boundary task. |
-| 6. Self-hosting | Clean-commit bounded candidate staging, exclusion of arbitrary untracked files, internal dependency-link validation, mode-aware tree hashing, acceptance receipts, side-by-side versions, conflict-safe stable launcher, atomic activation/reconciliation/rollback; self-host scenarios plus an isolated real-checkout build/activation of `6740f33` | Mechanics implemented and temporarily qualified | Install a stable TORCH in the user location and use it to manage/test/promote a later candidate of this checkout. Persistent installation approval required. |
+| 6. Self-hosting | Clean-commit bounded candidate staging, exclusion of arbitrary untracked files, internal dependency-link validation, mode-aware tree hashing, acceptance receipts, side-by-side versions, conflict-safe stable launcher, atomic activation/reconciliation/rollback; self-host scenarios plus an isolated exact-commit build/activation of current commit `6e60b09` with 22/22 acceptance categories | Mechanics implemented and temporarily qualified | Install a stable TORCH in the user location and use it to manage/test/promote a later candidate of this checkout. Persistent installation approval required. |
 | 7. COMBATRIG re-import | Read-only portable importer and report preserving 33 areas, 570 backlog records, checks/resources/schedules/release boundaries | Analysis implemented; cutover blocked | Owner must resolve 56 scope/exclusion gaps across all 33 areas, then authorize install/operation. |
 | 8. Product surface | Redesigned site and dispatch-board story; installed-launcher onboarding; responsive qualification ledger; keyboard-operable command tabs; local read-only Console covering ownership graph, worktree drift, recoverability, acknowledgements, checks, integration, delivery, resources, schedules, decisions, provider health, and context evidence; desktop/mobile Chromium rendering with zero mobile overflow and exercised interactions; `SCN-package-distribution` packs and installs the CLI offline in an isolated consumer | Local surface and standalone artifact implemented and visually qualified | Registry publication and public deployment remain open. |
 
@@ -77,7 +79,7 @@ Passing local tests do not close any live/provider/install/deployment gate.
 | E. Forge-backed to local | `SCN-forge-migration` detaches the remote and continues local operation. | Proven locally | None. |
 | F. Forge outage | `SCN-forge-migration` makes the remote unavailable while local state and operations survive and synchronization risk remains visible. | Proven locally | None. |
 | G. Mixed runtimes | `SCN-mixed-runtime`, `SCN-codex-adapter`, `SCN-claude-adapter`, durable messages, and the real stdio MCP handshake prove a shared provider-independent control plane with corrected installed-CLI plans. | Implemented virtually | One authorized live Claude/Codex shared-boundary change must demonstrate actual coordination. |
-| H. TORCH builds TORCH | Candidate staging, complete acceptance receipts, stable launcher mechanics, activation, rollback, and isolated real-checkout execution are proven. | Mechanics implemented; exit gate open | An installed stable release must manage development, testing, and promotion of a successor from outside this checkout. |
+| H. TORCH builds TORCH | Candidate staging, complete acceptance receipts, stable launcher mechanics, activation, rollback, and isolated execution of exact current commit `6e60b09` are proven. | Mechanics implemented; exit gate open | An installed stable release must manage development, testing, and promotion of a successor from outside this checkout. |
 | I. COMBATRIG compatibility | The read-only import preserves 33 areas, 570 backlog records, prompts, checks, resources, schedules, and authority while refusing 56 unresolved boundary gaps. | Analysis implemented; exit gate open | The owner must resolve boundaries and authorize TORCH installation and operation in COMBATRIG without core special cases. |
 
 The definition-of-first-usable-release sequence therefore remains unproven as