Repository navigation
NS-0B-pre repair: bind complete candidate artifacts - #9810
Merged
gunbai-bot[bot] merged 10 commits intoAug 31, 2026
Merged
Conversation
added 10 commits
August 31, 2026 10:29
…neat-otter-332-ns0b-pre-manifest-repair
…neat-otter-332-ns0b-pre-manifest-repair
…neat-otter-332-ns0b-pre-manifest-repair
gunbai-bot
Bot
deleted the
session/neat-otter-332-ns0b-pre-manifest-repair
branch
August 31, 2026 20:58
gunbai-bot Bot
pushed a commit
that referenced
this pull request
Aug 31, 2026
Main advanced by #9814 (generated-artifact drift restored to required CI), #9810, and #9844, which appends the whole-corpus frontier receipt 1 -- the successor row that was deliberately held until the digest fold was repaired, now landing on the corrected fold. Conflict was append-vs-append again, in the same file. Resolved with the check the previous one taught: the conflict region ran to EOF with NO common tail, and each side balanced independently (18/18 and 6/6), so concatenation was safe in either order. Last time the tail held the final closing brace and reordering orphaned it. Verified 127/127 after resolving, and git ls-files -u rather than a marker grep for resolution state. The substantive new fact: the duplicate wall now applies across a TWO-receipt series, and current_persisted_compile_phase_frontier_holds passes over both. That is not carried from an earlier green -- #9844's receipt did not exist when the wall was authored, and main does not contain this merge, so the composition had to be measured. Verified on the merged tree, all three arms: as authored 29/29 PASS remove phase_census_digest sort FAIL the_census_digest_is_invariant... only delete the duplicate conjunct FAIL a_receipt_whose_refused_population... only Both falsifiers still fire, and the ARM B anchor asserts exactly one match so it cannot silently retarget onto a neighbouring canonicalization. docs/design-ledgers.md is byte-identical to main, so the drift check #9814 restored has nothing to flag from this branch. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012t876A58gzqj5V69TsrB6Y
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.
Repairs the landed staged-convergence manifest wall exposed by the first real NS-0B mutation run.
The Cargo.toml CI RED is direct proof that the pre-repair manifest was incomplete: Cargo.toml was inside the purported immutable candidate artifact without any manifest row or digest binding. This head closes that gap from the producing emit population; it does not add a Cargo.toml basename exception or relax the unmatched refusal.
Focused real mutating transaction instrument passed on head a52b478: BuildBuddy invocation 178fec10-6f7c-41b4-acc3-aca12e0e024b (1 passed, 124.17s).
No NS-0B declaration-identity changes are included.