Promote approved unresolved-usage recovery documentation

[adrianwebb]

Outcome

Promote checked staging documentation to main; record human-approved unresolved active-usage recovery without weakening acceptance or inventing measurements.

Work authority

• Work item / Issue: Capacity provider and Agent acceptance: checked repair delivery and SDK golden completion (continuation of #633) #634
• Proposal / decision: N/A — human “Approve explicit unresolved-usage recovery”
• Assignment / checkpoint: expired Reporter assignment_mYh-sJNy-VlyPeey4MFFj4mkjM_cgoHk
• Actor: adrianwebb with Codex assistance
• Human authority: adrianwebb
• Agent / capacity provider: Codex desktop; no managed execution asserted
• Exact base ref: main aa1811f
• Exact head ref: staging 394db4e
• Agent-assisted under human authority

Plan

Record explicit approved contract; checked staging/main promotion and temporary branch deletion. No functional Platform code/tag/UI.

Changes and commits

1682b79 adds matching explicit recovery paragraphs to original docs/agent-architecture.md and docs/agent-assignments.md. Exact version/admin/reason/key; independently closed workspace; original assignment/report/failure/provider evidence unchanged; existing audit records unresolved NOT zero or settled. Terminal concurrency only, period claims held; never elapsed-derived usage or accepted failed run.

Verification

git diff --check PASS. Owning implementation/unit/native/component scene evidence in SDK376, API515, Agent368 and CLI274; SDK563/563 before two component scenes checked, API16/16 focused and Agent913/913 local full. Documentation-only staging Actions37845759687/job113546099003 PASS; main checks pending; no claim of managed recovery/SDK golden.

Risk and rollback

Records only explicit human-approved exception. No canonical schema, time or coverage changes. Ordinary checked revert retains histories.

Completion summary

Required checks and promotion pending. No new SDK run until actual operator recovery resolved.

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.