Skip to content

Require atomic expected head for site publication - #802

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

d6g8k5htny-coder merged 10 commits into
mainfrom
codex/cbz-site-publisher-cas-20261110

Conversation

@d6g8k5htny-coder

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

Copy link
Copy Markdown
Owner

Current integration candidate. Recovery #801 merged normally at Main 984a608584281bca8db88a8a9ae7a837f6e9a6bb, tree 134218620682f9467961f6a8eeb29fac670e9457. GitHub retargeted this PR to Main. Its new head 4aec958f263c8e67b01ed83e3c43150a0098fae3 merges the prior publisher head db949860f1951f264eda92eb26310b3d87ae4d47 with that exact Main commit, without changing the candidate tree 275c6fb32e1ce5b6db05c6007146442ee3d8b991. The synthetic merge 0f088dc3f508f1d2227aa35646509b3c637195e7 has that tree and parents [Main 984a6085, head 4aec958f]. Previous tests below remain bound to the exact earlier tested merges; fresh checks on this head and final ref guards are required. No live recovery or deployment is claimed.

Earlier recomposition after Main #803 and the recovery candidate: head db949860f1951f264eda92eb26310b3d87ae4d47, tree 275c6fb32e1ce5b6db05c6007146442ee3d8b991, has parents [previous publisher head 00be825508ff782db75dd6d9ab02b141d033b89d, recomposed recovery head 8cce89ac4f77a50db82bc6c3c1c05402c0751f59]. The complete newer recovery and #803 decisions history precedes the original publisher suffix. Main #803's workflow, dependency files and plan are retained, and publisher/recovery code and tests retain their prior blob identities. Fresh hosted checks must qualify this whole tree; Workspace #69's Main pin is stale.

The previously observed hosted checks below apply to the earlier tested merge and unchanged source blobs. They do not qualify the new whole tree; fresh hosted checks, exact composition and current-ref guards are required. Workspace #69's Main pin is now stale.

Original stacked draft, based on the #801 recovery branch. Main's normal publisher had an ancestor-rollback race: a non-force REST ref update could accept a descendant after the receipt ref moved back. The selected adverse test failed locally in both Python modes and in hosted current-site job 129610695154 (229 tests, one failure; optimized was not reached). The exact initial test tree and full hosted log are preserved in cbz/evidence/site-publication-cas-20261110/.

The candidate uses GitHub's atomic updateRefs with the exact expected head, the fixed receipt ref and force: false; it retains immutable object checks, bounded no-retry writes and readback, rejects direct REST ref patches, and adapts the stacked recovery wrapper. A failed write response can have an unknown outcome, requiring inspection of the actual ref.

At tested merge d243e1a2c833e5039b9cd0d1ceb9aa5682c78e35 (tree dafca516877750f5e06603729e862ca9e7420b7a), hosted publisher controls job 129613200124 ran 40 tests without skips per Python mode, 11 selected-oracle mutation pairs per mode, and rejected three unauthorized assertion origins and one runtime error per mode. Stacked recovery controls job 129613199744 also passed; the recovery dispatch was skipped on the pull request. Full job logs, earlier failure logs and reported artifact digests are retained; the artifact ZIPs have not been independently unpacked here. That earlier candidate added retained logs and documentation to its tested source; the current recomposition requires fresh hosted checks.

The former stacked base has since merged; the current Main-based candidate still requires fresh protected checks and current-ref guards. Authenticated GraphQL/Pages behavior, actual deployment or recovery, full G0 and CBZ-0 remain unestablished. No mathematical statements or scientific status change.

Fresh recomposed component runs

On the recomposed tested merge cd913c55ea6ff6187fedb6f5102ce0356aa38e24 (head 00be825508ff782db75dd6d9ab02b141d033b89d), publisher run 42751139747, job 129614776701, completed successfully. Its decoded log reports 40 tests without skips in each Python mode, 11 clean-baseline/selected-oracle mutation pairs in each mode, and rejection of three unauthorized assertion origins plus one runtime error per mode. Artifact 13734195859 has reported SHA-256 95bb65815e8be2dfcceabed2fc97da763c2c537617580f9662de7b144dee7df1.

Stacked recovery controls run 42751139852, job 129614779884, also completed successfully; its PR recovery-dispatch job was skipped. Its redirected detailed control results are in artifact 13733836323, reported SHA-256 cb73819ade3798c87efdd61cd32a5a431a63820fab9e84dac612cf466045b0f0. Readback job 129618849837 independently checked publisher artifact 13734195859: 81 unique members, CRCs, ZIP digest, exact tested-source hashes, 40 unit outcomes and 11 clean-baseline/authorized-selected mutation pairs in each mode, plus the recorded adverse-origin outcomes and three synthetic origin refusals per mode. That readback job then failed on a recovery-artifact filename assumption, so the recovery archive is not yet qualified by that inspection; its actual hosted control job remains a separate observed success. Other required checks, actual authenticated publication/recovery, and final federation gates remain separate.

Independent archive readback

Read-only job 129618998455 subsequently inspected both exact recomposed artifacts and completed successfully. Publisher artifact 13734195859 had 81 unique members; recovery artifact 13733836323 had 241. ZIP SHA-256 and all member CRCs matched, and selected unit logs and mutation records were bound to the exact tested-merge source hashes. The readback found 40 publisher unit outcomes and 11 selected-oracle mutation pairs per mode, plus three rejected assertion origins and one rejected runtime error per mode; for recovery it found 34 unit outcomes, 37 selected-oracle mutation pairs and three rejected assertion origins per mode. Three synthetic origin-report alterations were refused per mode for each archive. This is scoped artifact inspection, not a deployment, full G0 or CBZ qualification.

Earlier readback jobs 129618510111 and 129618705245 failed because the inspection assumed exactly one selected failure event; job 129618849837 verified the publisher archive but then failed because it assumed a source-mutant filename from its label. The correction requires all selected failure events to be authorized for the selected test and identifies a unique recorded mutant source. Preserve these inspection failures; the underlying component job outcomes are unchanged.

The two independently inspected component archives and their earlier readback failures remain bound to tested merge cd913c55ea6ff6187fedb6f5102ce0356aa38e24, not to the newly recomposed whole tree. Their decoded logs and diagnostic source are retained on the stacked #800 custody candidate. No authenticated receipt write or publication success is inferred.

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 recomposed component results

On the earlier tested merge 2ecd8b4b3b80f1b3835ea25130ebac970a2c39ec, tree 275c6fb32e1ce5b6db05c6007146442ee3d8b991, publisher job 129620092955 ran 40 tests without skips and 11 clean-baseline/selected-oracle mutations per Python mode, rejecting three unauthorized assertion origins and one runtime error per mode. Its artifact 13733209865 was reported with SHA-256 9b99f0600c3d4e573a426b407109f6776f41045f07143e85b6e716871d0bb1a6. Recovery controls job 129620089706 completed successfully and uploaded artifact 13733353594, reported SHA-256 266d0f0b9eb80bf40b145b805b931dfa4ae44a58172a29d984d3c5fd0d27c143; its detailed output is redirected to that artifact. These current ZIPs have not been independently unpacked here. The recovery dispatch was skipped on the pull request. Other applicable checks completed successfully on that stacked head; fresh protected checks on the retargeted candidate are still required.

@d6g8k5htny-coder d6g8k5htny-coder changed the title Reproduce publisher receipt head race Require atomic expected head for site publication Nov 10, 2026
@d6g8k5htny-coder
d6g8k5htny-coder changed the base branch from main to codex/cbz-site-recovery-20261110 November 10, 2026 03:36
Base automatically changed from codex/cbz-site-recovery-20261110 to main November 10, 2026 04:10
@d6g8k5htny-coder
d6g8k5htny-coder marked this pull request as ready for review November 10, 2026 04:12
@d6g8k5htny-coder
d6g8k5htny-coder merged commit 944dc55 into main Nov 10, 2026
26 checks passed
@d6g8k5htny-coder
d6g8k5htny-coder deleted the codex/cbz-site-publisher-cas-20261110 branch November 10, 2026 04:25
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