Add local operator inspection and reconciliation for quarantined resource leases, including atomic audit-backed FIFO handoff and recovery protocol support.\n\nPreserve capability tokens in the authoritative store and reject non-loopback or ordinary client transport for recovery mutations.\n\nChecked packaged templates and packaged authoring skill references; none need updating. The task-owned docs note records shared README and skill reference follow-up for docs-fold.
1.1 KiB
Inspected resource recovery
The operator recovery contract now keeps quarantined resource ownership and its audit transactionally coupled to FIFO handoff. Inspection is redacted and reconciliation is accepted only over a loopback operator connection with the exact owner visit plus positive cleanup/restoration evidence. The persisted capability remains private to the authoritative live store; missing waiter channels fail closed without changing owner or audit state.
Use the configured PIPELINES_URL endpoint, not a disposable URL. First run
the redacted resource inspection, then reconcile only after the parked visit
has been inspected and quiesced, supplying its exact run/stage/sequence and
explicit evidence (including no mutating action occurred where applicable).
The old deployed server does not support this action; deploy a compatible
server before attempting recovery. This is an operator trust boundary, not an
OS sandbox or unrestricted authorization grant.
The shared README and packaged OpenCode skill references should be updated by
the manual docs-fold process; they are intentionally not edited here.