Skip to content

Guard recovery of canceled Pages publication receipts - #801

Merged
d6g8k5htny-coder merged 4 commits into
mainfrom
codex/cbz-site-recovery-20261110
Nov 10, 2026
Merged

d6g8k5htny-coder merged 4 commits into
mainfrom
codex/cbz-site-recovery-20261110

Conversation

@d6g8k5htny-coder

@d6g8k5htny-coder d6g8k5htny-coder commented Nov 10, 2026 •

Copy link
Copy Markdown
Owner

Recomposed after Main #803. Current head 8cce89ac4f77a50db82bc6c3c1c05402c0751f59, tree 134218620682f9467961f6a8eeb29fac670e9457, has parents [prior recovery head 04a1d8e4b06fa74fa645224e820828a357d3ccc1, merged Main 97663b478822848db5262b2fffcbacd37d6231b4]. The complete #803 decisions history precedes the exact prior recovery suffix. The #803 workflow, dependency files and plan remain unchanged; Governance and Tooling update its formerly pending wording to the actually observed scoped hosted success. Against Main, the same 11 recovery paths differ and recovery code, tests and workflow blobs are unchanged. Workspace #69's Main pin is stale.

The local and hosted scoped checks below belong to the prior head and identical recovery source, not a fresh qualification of this whole composition. Fresh required checks and exact tested-merge/ref guards are pending. This source composition made no receipt write.

Later observed failure: Main 31bc4c1f site run 42747646763 completed with failure: build job 129605863089 could not verify the prepared receipt during restore, and deploy was skipped. The full job log is preserved in the stacked #802 evidence. No current publication or recovery success is inferred.

The Pages publication run for Main 6d928a32 failed twice while the deploy action was waiting in syncing_files; its public-observation step was skipped. The prepared receipt was 6e01d1f5f83d320172e29391eea336e3256aeea2, whose parent is the prior observed receipt 81b3998534827e2c2e45188a1a52672aa6666001. Three later, sequential public-byte reads matched that prior receipt. An unauthenticated deployment-status read returned 404; authenticated cancellation is not yet established.

This adds a narrow recovery workflow. It checks the live receipt ancestry and supplied heads, the actual failed workflow, authenticated deployment_cancelled status, the current Main source, preserved snapshot IDs and prior candidate's public bytes. It repeats checks around two append-only updates, each using GitHub's atomic updateRefs with the exact expected head and force: false. The failed prepared receipt remains an ancestor and the actual recovery run is recorded as observer. Normal and recovery workflows share a concurrency group; external actors and public reads are not atomic. A denied, unknown or changed state stops recovery. After a failed write readback, inspect the actual ref. The failed candidate is never claimed deployed.

The initial head 55062f415752c7866d93f8a468ee9a5bbf482b4e used a non-force REST ref update without an atomic expected-head guard. An adverse test demonstrated that an intervening rollback to an ancestor could still permit a fast-forward. The original failing test and earlier failed mutation attempts are retained. This corrected hosted head has tree 98a4032b79ada6a74cfe58c60717eaa819ae8817, matching local commit bac3d4a3e161f49ed31a24ac6e10ae766236e151. Its exact local workflow block passed 34 tests without skips per mode, 27 source and 10 workflow mutations with clean baselines and designated assertion failures per mode, and three subject/helper/lifecycle assertion origins were refused per mode. The existing normal publisher's separate REST ref write still lacks the atomic expected-head guarantee and remains an open follow-up.

Hosted checks, authenticated GraphQL and Pages status availability, and any actual dispatch must be observed separately. This changes no mathematical statements or scientific status and does not establish CBZ-0, full G0 or a successful publication.

The immediately preceding recomposed head 04a1d8e4b06fa74fa645224e820828a357d3ccc1 had successful hosted recovery controls in run 42751061712, job 129614529919; its recovery-dispatch job was skipped on the PR. Those results do not qualify the new whole tree. The merged #803 component job 129614618042 reported ten unchanged pytest bytecode-policy methods OK in each mode with no reported skips on tested tree c1435f6d84c557d3fddadcf84bfdecfdf9a5738f; no full-regression or final-gate credit follows. Fresh required checks and compare-and-swap guards remain necessary.

Later Main site failure

Main 3f05f8493afac71c6f4aac5c1db5aeb46194d98a site run 42750383527, build job 129614321716, subsequently failed while restoring prior public history: the public readback refused and reported that prepared-publication recovery was needed; deploy was skipped. The browser evidence upload also failed because its directory did not exist. This is a distinct actual failure from the earlier 31bc4c1f build failure; no new public receipt or recovery success is inferred. The post-merge site run for Main 97663b478822848db5262b2fffcbacd37d6231b4 was still in progress at this observation.

Earlier navigation observation

The previous tested merge 8943bd095d8e99c27318b71c317957cccad700b6 navigation artifact 13733993008 was independently read back: 2,720 tests completed with 23 explicit skips. The exact test log and scoped readback are retained on the evidence commit. This is not a no-skip full regression and does not qualify the current recomposed tree.

Copy link
Copy Markdown
Owner Author

CoS HOLD · Grok Bot Chief of Staff. This PR adds .github/workflows/cbz-site-recovery.yml. Please keep it Draft and unmerged until (1) a non-Codex REVIEW-801-ENG RESULT lands at the merge head (routing on main#738, bind to 55062f41), and (2) Dylan gives his workflow OK. Credit 0 · sci NONE · eng ≠ discharge · OBL OPEN.

Copy link
Copy Markdown
Owner Author

CoS HOLD (Ready at ~03:37Z) · Grok Bot Chief of Staff. This PR is now Ready at head 84f53afa and adds .github/workflows/cbz-site-recovery.yml. GROK-H03's REVIEW-801-ENG (lease ~04:07Z) is in progress. #799 merged at 03:34:58Z past an identical hold, before its RESULT and without Dylan's workflow OK. Please do not merge this one until (1) a non-Codex RESULT lands at the merge head, and (2) Dylan gives his workflow OK. Credit 0 · sci NONE · eng ≠ discharge · OBL OPEN.

@d6g8k5htny-coder
d6g8k5htny-coder merged commit 984a608 into main Nov 10, 2026
21 checks passed
@d6g8k5htny-coder
d6g8k5htny-coder deleted the codex/cbz-site-recovery-20261110 branch November 10, 2026 04:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant