Repository navigation
docs: bless dupe-bodies and type-conflict ledgers after the 10-10 burst (Closes #8534) - #8535
Merged
Merged
Conversation
…st (Refs #8534) - duplicate bodies: crc_byte/crc_step 2->3 -- third copy of the table-driven CRC32C landed with #8490 (specs/fpga/eth_reply.t27; lineage packets.t27 -> eth_beacon.t27 -> eth_rx.t27); specs are self-contained, the copy is the honest shape, the ledger records it - type conflicts: Episode, Pair, SkipList new (85->88), all from port PRs keeping upstream type names; readings written: SkipList DRIFT (generic SkipList(T) vs the concrete gen_skiplist_impl port), Episode and Pair DISTINCT (provenance record vs loop-step; fixture vs manifest vs payload) - regenerated with a fresh tri/t27c build on the Railway lab at 32b8632; tri types classified passes: 88/88 judged, 0 stale Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
gHashTag
enabled auto-merge (squash)
October 10, 2026 11:52
Contributor
dmitrii-f-t27
added a commit
to dmitrii-f-t27/t27
that referenced
this pull request
Oct 10, 2026
This was referenced Oct 10, 2026
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.
Bless the two corpus ledgers that drifted red on master after the 2026-10-10 morning burst. Closes #8534. Refs #6063 (steward lane).
Duplicate Body Ratchet --
crc_byte/crc_stepcopied [2] -> [3]: the third byte-identical copy of the table-driven CRC32C arrived with #8490 (specs/fpga/eth_reply.t27; lineagepackets.t27->eth_beacon.t27->eth_rx.t27). Specs are self-contained modules, so the copy is the honest shape;python3 tools/dupe_scan.py --blessrecords it (182 groups, 667 bodies).Corpus Ratchet type names -- three new conflicts (85 -> 88), all from the port PRs that keep upstream type names:
Episode-- DISTINCT:specs/memory/graph/ingest.t27:63provenance record vsspecs/queen/lotus.t27:65Lotus loop-step entry.Pair-- DISTINCT: u8 fixture pair (zig_empty_typed_array.t27:16) vs manifest pairing row (igla_coder_manifest.tri:36) vs i32 test-generator payload (port/tools/verify_multitarget.t27:13).SkipList-- DRIFT: the collections spec's genericSkipList(T)vs the concrete port inspecs/port/trinity/src/tri/gen_skiplist_impl.t27:31(fixed [32]/[16] pools; same SKIP_W/SKIP_P).tri types ratchet --blessrewrotedocs/reports/type_conflicts.json(+3), the three readings live indocs/reports/type_conflicts_classified.json(DRIFT 51 / DISTINCT 37) anddocs/TYPE_CONFLICTS.mdmirrors them.Verification: built fresh
tri+t27con the Railway lab at master32b8632and rantri types classifiedthere:88 conflicted name(s) ... OK: every conflicted name in the tree has a written verdict, and every written verdict is about a name that is still conflicting.The classified json keeps the file's existing ASCII-escape style (diff is the 3 rows + the two counts, nothing reformatted).🤖 Generated with Claude Code