[decebal]

Summary

• Bind installed toolkit and host identity when runtimes drift, freeze independent serialization expectations, and qualify immutable final artifacts through native skills.
• Preserve raw evidence and runtime dependencies before cleanup, recover archived Prime context through its engine, and distinguish forge merge settings from check enforcement.
• Verify these methods on a real AllSource Prime repair with authenticated Claude planning/review/QA, Codex implementation and Codex → Claude → Codex ownership handoffs. Application: AllSource PR #370.

Test plan

• Exact commit 41b69a43592d467b24485925372acc7a1a192596 passes all eight unchanged native gates: 74 toolkit tests with two configured skips, eight expense-example tests, four handoff-fixture tests, strict lint and format checks.
• Four updated skills pass structural validation. Seven bundled methods and fourteen generated host variants match intended source, with conflict preservation checked.
• Installed executable SHA-256 c06e006476f9aa10c4bffd447ac2d1c3af5963ac76bb27910ee32841be5b9af9 matches 280 binary build-input files on this commit. Previous installation retained as a backup.
• AllSource negative baseline and repaired candidate use the same frozen 375-case reference corpus and 78-property MCP persistence harness. Exact application commit passes 165 tests, with five existing environment-dependent ignores.
• Independent Claude executes final-artifact corpus checks and complete five-property retained-store JSON/TOON equality. Archived Prime engine returns 13 context nodes with matching report digest.
• Native ship confirms remote heads, Chronis completion and Prime publication outcomes. Required receipts, separate raw streams, source documents and runtime inputs retained outside disposable worktrees.

Design and evidence

Accepted design · Qualification report.

Same-machine authenticated hosts and local lexical Prime memory only. Hosted sync, vector retrieval, merge and deployment were not exercised. Main has no branch protection or applicable rules, so CI remains advisory. Rebase-only merge settings do not enforce green checks.