Repository navigation
types ledger: remove the resolved ParsedCommand entry (Closes #13151) - #13166
Merged
Merged
Conversation
#13096 renamed the clade-local ParsedCommand away, which resolved its conflict, but the sweep missed the types ledger line -- a resolved name fails the ratchet on purpose, so every branch inherited a red Corpus Ratchet from master. Ledger 142 -> 141, ratchet CLEAN. The #13159 dupe-ledger shrink is a different file; untouched here.
Contributor
The classified-verdict file still held the ParsedCommand record, so the ratchet job failed its verdict step after the ledger line was removed. Both files swept; self-ratchet CLEAN 141/141 on the head.
Contributor
PR DashboardGenerated at: 2026-11-03 12:43:55 UTC
Summary
Seal Status
|
This was referenced Nov 4, 2026
cursor Bot
pushed a commit
that referenced
this pull request
Nov 9, 2026
…ne commit (Closes #13182) (#13183) * claw: type_conflict_sweep -- a resolved name leaves both ledgers in one commit (Closes #13182) Encodes the #13166 lesson as a decision spec: a type rename that resolves a conflict must drop the name from BOTH docs/reports/type_conflicts.json and type_conflicts_classified.json in the same commit, else the identity-keyed ratchet reads a resolved-name failure and Corpus Ratchet goes red master-wide. t27b native: 3 passed / 0 failed, 1 invariant held; t27c seal verify all MATCH; dupe scan clean. Also records the merge-campaign experience in docs/now. * claw: blocker_attribution -- whose blocker is it before a PR is declared blocked (Refs #13182) The OWN / SHARED / FOREIGN / UNSEEN triage from #13183: a red whose offending file is another lane's just-merged work is a hold with a tracking request, never a fix. t27b native: 4 passed / 0 failed, 1 invariant held; seal verify all MATCH; dupe scan clean. --------- Co-authored-by: tri-claw <claw@t27.ai>
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.
One line: the types ledger still listed ParsedCommand after #13096 resolved its conflict by renaming the clade-local struct. The ratchet treats a resolved name as a failure on purpose, so master's Corpus Ratchet has been red and every PR branch inherited it (the seven ratchet reds in the current queue are this, not author defects).
Repair: delete the one ledger line. tri types ratchet on the head: ledger 141, observed 141, RATCHET CLEAN. The #13159 dupe-ledger shrink touched a different file and is not affected.