Repository navigation
fix(ci): unbreak v4_claim_witness_corpus_a (shard_a count 19→20, #4947 drift) - #4955
Merged
Merged
Conversation
…9→20 #4947 enrolled the English emit/ingest round-trip row into claim_witness_corpus_shard_a_rows (now 20 members) and bumped the full-list count datum, but did not bump claim_witness_corpus_shard_a_row_count. The shard-a gate's count guard (projected 20 != modeled 19) exits 2, so v4_claim_witness_corpus_a fails on every branch off post-#4947 main — a tree-wide merge block (confirmed: run 27548200843 shard-a FAILURE, shard-b success). Bump the datum to match reality (shard_a genuinely has 20 members). Minimal: only the consumed shard_a datum. The full-list count (54 vs 55 members) is an unconsumed/non-gating ledger and shard_b (35) matches, so both are left alone. Throwaway: the in-flight claim-witness-corpus model-first dissolution retires the count-guard datums entirely. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Main-unbreak (P0, tree-wide merge block)
#4947enrolled the English emit/ingest round-trip row intoclaim_witness_corpus_shard_a_rows(→20 members) and bumped the full-list count datum, but did not bumpclaim_witness_corpus_shard_a_row_count(still19). The shard-a gate's count guardprojected(20) != modeled(19)exits 2 →v4_claim_witness_corpus_afails on every branch off post-#4947 main.Confirmed: post-merge run
27548200843showsv4_claim_witness_corpus_a= FAILURE,v4_claim_witness_corpus_b= success.Fix
One line: bump
claim_witness_corpus_shard_a_row_count19 → 20to match reality (shard_a genuinely has 20 members, verified by set analysis: full list 55 = shard_a 20 ⊎ shard_b 35, disjoint).Minimal by design:
54vs 55 actual members) is an unconsumed / non-gating ledger (the gate.shreads only per-shard counts) — left alone.35) matches its 35 members — left alone.Throwaway
The in-flight claim-witness-corpus model-first dissolution retires these
*_row_countcount-guard datums entirely (the rows-TSV fold over a typed List can't drop a member, so count == length by construction). This bump is the fast unbreak; the dissolution is the permanent fix. No conflict — the dissolution deletes this datum.🤖 Generated with Claude Code