Repository navigation
Accept scoped native recovery and remove repeated paper approval - #32
Merged
seathatflowsinourveins merged 8 commits intoSep 20, 2026
Merged
Conversation
9 of 22 tasks
seathatflowsinourveins
deleted the
codex/foundation-recovery-policy-20260920
branch
September 25, 2026 18:47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The foundation catalog previously left scheduled guest reboot and native application-state recovery across hosts unqualified. Record independently reviewed Dagu/systemd guest recovery and ai-memory/Qdrant/Restic restore acceptance, with exact upstream commands, returned results, original artifact digests and explicitly declared public projections. Earlier failures remain retained; synthetic fixtures do not establish production disaster recovery or provider savings.
Apply the user's standing authorization for broker-specific paper E2E after foundation work. Paper readiness, numeric limits and measured performance/operational acceptance remain technical requirements; renewed human approval and live credentials do not block paper. No broker orders or live configuration changes occurred.
Validation includes unchanged upstream Dagu retry tests (14 leaf cases), 10 ai-memory and 4 Qdrant cases, independent original-artifact/native-response review, scoped lifecycle/catalog joins and generated publication checks. The separate recovery runs are pinned to their actual execution revisions; publication checks do not replace native acceptance.
Local publication verification passed: 669 tests with 41 explicit dependency-scoped skips; 68 components, 102 receipts and 1,158 hashed files; 16 foundation layers and 44 decisions; generated HTML and rendered Foundation counts. Review corrected a misplaced component receipt reference and a stale continuation pointer before final validation. The catalog now has 40 accepted capabilities and four explicitly partial/source-reviewed capabilities.
Reconciliation with PR31 found two active recovery plans whose frozen workflow hashes would reject a future dispatch. Refresh only those prospective bindings; retain historical execution revisions and receipts. Two local regression checks invoke the actual dispatch guards without running native recovery. Independent review confirmed all 28 active frozen-source bindings, original preparation references and unchanged workflow bytes from PR31. The documented upgrade procedure now includes this check.