You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
types ratchet red on master: four ported types collide with corpus types (CounterState, LRUCache, TestCase, TestRunner) #5810
ledger 77 name(s), observed 81
+ CounterState NEW conflict
+ LRUCache NEW conflict
+ TestCase NEW conflict
+ TestRunner NEW conflict
Reproduced locally on a fresh checkout of origin/master (cargo build -p tri && ./target/debug/tri types ratchet, rc 1). Every open PR inherits the red check.
tri types ratchet walks specs/ only (skipping scratch/; cli/tri/src/types_dup.rsread_specs) and counts a name when two definitions have different field lists. compiler/*.t27 is not walked, so its six TestCase definitions are not part of this.
All five newer definitions arrive from the 2026-10-03 batch of automated "Port gHashTag/trinity:..." PRs. None of the four names is a deliberate shared type: each pair is two unrelated concepts that met on a name.
Repair
Same as #5504 (Refs #5497): rename the newer definition inside its own file and leave the ledger at 77, rather than blessing four new conflicts. The porter (tools/queen/feed_roadmap.py, pick) skips any target that already exists or is already named by an issue, so it will not regenerate these files and undo a hand rename.
Acceptance: tri types ratchet RATCHET: CLEAN at 77; tri types classified OK; t27c suite --repo-root . --ratchet --corpus-only RATCHET CLEAN; tools/dupe_scan.py ok.
Activity
fix(specs): integrate corpus type renames without losing executable t…