[adrianwebb]

Outcome

Permit provider code handoff after the trusted executor’s closed clock and verified physical teardown, preserving the original recovery journal, products and accounting holds. Active or uncertain work continues blocking handoff; guest-trust changes remain strict.

Work authority

• Work item / Issue: Current deployment backlog: retained requirements after issue consolidation #834; Continue strict acceptance binding delivery — 109 complete / 68 open sdk#424

• Proposal / decision: User-authorized coached Atlas repair strategy; bounded repair of an observed execution blocker.

• Assignment / checkpoint: Closed recovery claims for assignment_8cb5-X2RdQJpf0_dfvfxyzJBQVS1R6OY and assignment_iWKLSi4wAAilqdaS8b_n0L9XGNN17D92 blocked provider adoption.

• Actor: Codex, operating through adrianwebb's authorized account.

• Human authority: adrianwebb's explicit instruction to complete the Researcher correction and use agents to repair Atlas.

• Agent / capacity provider: Integrator repair; live evidence from provider_-rcKRK8gG2NGnOU3yGu_CV3Wz7ACppTP. No agent-authored code claim.

• Exact base ref: staging 051a011

• Exact head ref: codex/provider-closed-recovery-handoff fac9ab2

• Agent-authored under human authority

Plan

Reproduce the observed failure first, fix its earliest owning boundary, register exact tests in the existing component scene, require native complete-suite/scene checks, then ordinary staging merge and supported scoped adoption. Preserve every failed observation and all recovery custody.

Changes and commits

Regression commits 3a798583dfed12a836d4344202f6636b62d3c569 and f4c8a21158cf5d62972855cd538390ccc87e04f7 preserve the original refusal. Fix d29589904fa8ed4f6979d5335fb2056f9a72d70a and explicit scene expectations fac9ab219fd76a82f8fb1e64a30ff90843e7e686 add the bounded provider-only allowance and eight exact cases to the existing component scene. No journal or financial state is rewritten.

Verification

All five protected checks pass on the exact head: native Verify 39105308956, secret custody, uninstall VM, development backup and qualification. Strict scene prerequisites freshly passed 1342/1342 Deployment and 200/200 Reviewer assertions, zero failed/skipped/todo; all 264 component steps pass. Independent audit checks every assertion/source digest (57 files), exact selected archive assets and all ZIP digests. Tested merge 28ec95cb4390993bb712c169e33fad5eb8d4cf91, tree 443fdb810c38c66cbd7b0b3205e81548c3a44475. Archive SHA256 ddb783117f54df9b25a04fc8372610843dcec5fac8b9da6b6bd18eadd4704dc4; report SHA256 a662d876490228a10690ed9d69c5dc22e3901b3716f5de029747fffe065806d7. Native packaging and privileged disposable-host verification pass. Superseded run39104991578 remains cancelled and uncredited.

• I ran the narrowest relevant package verification and documented any checks that could not be run.

Risk and rollback

No new command, permission or execution path. Ready/running/recovery without complete original teardown, malformed/future/pre-finish teardown and uncertain stops remain denied. Default active-claim inspection still fences sandbox guest changes. Adopt the checked staging tree with the existing trsd dev host activate operation, preserve guest digest and every development selection, then read back compiled bytes. Roll back through an ordinary revert PR or the existing supported host-runtime generation recovery; never clear recovery journals.

Completion summary

Native checks and independent artifact audits pass. Ordinary staging integration and supported host adoption are next. Researcher approval and agent-led Atlas repairs remain pending; no formal acceptance completion is claimed.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.