Repository navigation
Require atomic expected head for site publication - #802
Merged
Merged
Conversation
d6g8k5htny-coder
changed the base branch from
main
to
codex/cbz-site-recovery-20261110
November 10, 2026 03:36
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.
Current integration candidate. Recovery #801 merged normally at Main
984a608584281bca8db88a8a9ae7a837f6e9a6bb, tree134218620682f9467961f6a8eeb29fac670e9457. GitHub retargeted this PR to Main. Its new head4aec958f263c8e67b01ed83e3c43150a0098fae3merges the prior publisher headdb949860f1951f264eda92eb26310b3d87ae4d47with that exact Main commit, without changing the candidate tree275c6fb32e1ce5b6db05c6007146442ee3d8b991. The synthetic merge0f088dc3f508f1d2227aa35646509b3c637195e7has that tree and parents [Main984a6085, head4aec958f]. 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, tree275c6fb32e1ce5b6db05c6007146442ee3d8b991, has parents [previous publisher head00be825508ff782db75dd6d9ab02b141d033b89d, recomposed recovery head8cce89ac4f77a50db82bc6c3c1c05402c0751f59]. 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 incbz/evidence/site-publication-cas-20261110/.The candidate uses GitHub's atomic
updateRefswith the exact expected head, the fixed receipt ref andforce: 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(treedafca516877750f5e06603729e862ca9e7420b7a), hosted publisher controls job129613200124ran 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 job129613199744also 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(head00be825508ff782db75dd6d9ab02b141d033b89d), publisher run42751139747, job129614776701, 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. Artifact13734195859has reported SHA-25695bb65815e8be2dfcceabed2fc97da763c2c537617580f9662de7b144dee7df1.Stacked recovery controls run
42751139852, job129614779884, also completed successfully; its PR recovery-dispatch job was skipped. Its redirected detailed control results are in artifact13733836323, reported SHA-256cb73819ade3798c87efdd61cd32a5a431a63820fab9e84dac612cf466045b0f0. Readback job129618849837independently checked publisher artifact13734195859: 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
129618998455subsequently inspected both exact recomposed artifacts and completed successfully. Publisher artifact13734195859had 81 unique members; recovery artifact13733836323had 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
129618510111and129618705245failed because the inspection assumed exactly one selected failure event; job129618849837verified 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
3f05f8493afac71c6f4aac5c1db5aeb46194d98asite run42750383527, build job129614321716, 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 earlier31bc4c1fbuild failure; no new public receipt or recovery success is inferred. The post-merge site run for Main97663b478822848db5262b2fffcbacd37d6231b4was still in progress at this observation.Earlier recomposed component results
On the earlier tested merge
2ecd8b4b3b80f1b3835ea25130ebac970a2c39ec, tree275c6fb32e1ce5b6db05c6007146442ee3d8b991, publisher job129620092955ran 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 artifact13733209865was reported with SHA-2569b99f0600c3d4e573a426b407109f6776f41045f07143e85b6e716871d0bb1a6. Recovery controls job129620089706completed successfully and uploaded artifact13733353594, reported SHA-256266d0f0b9eb80bf40b145b805b931dfa4ae44a58172a29d984d3c5fd0d27c143; 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.