Fix final-audit confirmation replay and prepare beta.31

[Proxicon]

Why

The final beta.29 audit found five families of successful mutations whose exact confirmation retry returned an error. Beta.30 had already been tagged from the first-checkpoint repair in #335, so beta.31 retains that source and integrates the four additional findings.

Changes

• Reconcile script deletion through retained scoped ownership and content integrity, returning the original result.
• Reconcile policy replace/disable/revoke before mutable version checks and preserve the original normalized policy across later lifecycle changes.
• Reconcile artifact cleanup before cleaned-state rejection; persist actual success through response cancellation and keep cleanup metadata stable after database reload.
• Bind deleted job/run replay to the authenticated ingress owner, an unexpired consumed-success receipt, exact request hashes and original result object. The local exchange, middleware and endpoint each retain their current authorization checks; confirm proofs cannot be reused for previews or another body.
• Advance the single product version authority and update the canonical owner campaign from the final audit, preserving all 518 contexts and the pending acceptance work.

Retains #333/#334 from #335. Addresses #336, #337, #338 and #339. Release-delivery closure follows verified publication.

Verification

• Coordinated Debug build: 0 errors; no warnings in modified files.
• 427 focused tests passed, 0 failed and 0 skipped: the complete replay selection plus current managed ingress and file-delegation permission regressions. The TRX receipt passes the repository validator.
• Real TestServer exchange + signed middleware + current route-policy/confirmation/store regressions include all ten job mutation actions, both run actions, later tombstones, changed bindings, current deny/revocation/expiry, lost responses and timestamp precision.
• Slopwatch --hook --no-baseline, disclosure gate, documentation/layout checks and diff checks passed.
• Required hosted source/Release build/fast tests run through the existing generic workflow. No migration or workflow changes.

Owner deployment, fixed native/selected-consumer identity, live functional acceptance, native workflows, the exact isolated hour and original cleanup remain tracked in #282/#294 and their existing child issues.

Hosted compatibility correction

The first hosted run 39238177768 reported 13 failures in existing ordinary local delegation/relay tests (4,349 executed, 4,336 passed, 13 failed, zero skipped); the remaining two assemblies did not execute after that failure. The follow-up commit confines exact credential/client replay binding to proof-bearing assertions and restores ordinary object ownership failure precedence. Existing assertions are unchanged. Three focused regressions protect the strict proof boundary and ordinary error ordering. The corrected hosted run 39241149652 passed in 11m54s on 964f9d4092a9e127a3766623c2f4146358ed0611: 4,352 core tests, 36 API integration tests and 585 component tests, all 4,973 passed with zero failures or skips. Source/release contracts and disclosure checks also passed. The downloaded three-assembly TRX artifact matches GitHub's SHA-256 digest. The original failure remains part of the validation history.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
🔒 Security Review	✅ Completed 2026-10-19T10:36:21.257650Z	cb4cc1e	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.