Repository navigation
tools: ledger the five helper bodies copied today (Refs #6831) - #7584
Merged
Merged
Conversation
Duplicate Body Ratchet went red on master (2749341, 2026-10-07 14:40Z): bodies written under bytes32_eq, bytes64_eq, nibble, price_tokens, and run_die_level_with are now copied twice with no ledger entry. Each copy is a deliberate per-module helper, not a pasted bug: - bytes32_eq / bytes64_eq: the fixed-width byte-compare loop, one copy per module that needs it (ed25519 beside sha256/sha512) - nibble: the hex-char-to-nibble helper, identical in sha256 and sha512 - price_tokens: the wallet pricing rule, shared verbatim by token-wallet and crm-lead-magnet - run_die_level_with: the die-binding helper, reused by independence The ledger moves in this commit: exactly five groups, nothing else (verified against the --bless diff before committing). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
gHashTag
enabled auto-merge (squash)
October 7, 2026 17:17
This was referenced Oct 7, 2026
This was referenced Oct 7, 2026
Merged
Contributor
This was referenced Oct 7, 2026
gHashTag
added a commit
that referenced
this pull request
Oct 8, 2026
corpus_merkle (2785a3a, two minutes after #7584 landed) added hex_nibble_of -- a third copy of the hex-char-to-nibble body that #7584 had just ledgered as the two-member group under nibble (sha256 + sha512). Same deliberate per-module helper class, so the ledger moves with it: nibble 2 out, hex_nibble_of 3 in. The rewrite also resorts build_tree 5 one line up into alphabetical order; no other group changes. Co-authored-by: Claude Opus 5.5 (1M context) <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.
Duplicate Body Ratchet went red on master (2749341, 2026-10-07 14:40Z): five bodies are now copied twice with no ledger entry. Each copy was checked by hand and is a deliberate per-module helper, not a pasted bug:
bytes32_eq/bytes64_eq-- the fixed-width byte-compare loop, one copy per module that needs it (ed25519 beside sha256/sha512)nibble-- the hex-char-to-nibble helper, identical in sha256 and sha512price_tokens-- the wallet pricing rule, shared verbatim by token-wallet and crm-lead-magnetrun_die_level_with-- the die-binding helper, reused by independenceSo the ledger moves in the same commit, per the scanner's own remedy. The
--blessdiff was verified before committing: exactly these five groups, nothing else.dupe_scan.pyreads clean on the branch; lefthook (own-language, foreign-budget) passes.Refs #6831 for the incident class (unledgered duplicate bodies turning every open PR red).
🤖 Generated with Claude Code