Skip to content

types ledger: remove the resolved ParsedCommand entry (Closes #13151) - #13166

Merged
gHashTag merged 2 commits into
masterfrom
repair/types-ledger-parsedcommand
Nov 3, 2026
Merged

gHashTag merged 2 commits into
masterfrom
repair/types-ledger-parsedcommand

Conversation

@gHashTag

@gHashTag gHashTag commented Nov 3, 2026

Copy link
Copy Markdown
Collaborator

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.

#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.
@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-11-03 12:30:45 UTC

Summary

Status Count
Total Open PRs 27
PRs with Failing Checks 24
PRs with All Checks Green 3
READY 2
FAILING 24
PENDING 0
NO CHECKS YET 0

These columns do not partition: 2 + 24 + 0 + 0 = 26, and there are 27 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=e75b498e5e79 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

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.
@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-11-03 12:43:55 UTC

Summary

Status Count
Total Open PRs 26
PRs with Failing Checks 23
PRs with All Checks Green 3
READY 2
FAILING 23
PENDING 0
NO CHECKS YET 0

These columns do not partition: 2 + 23 + 0 + 0 = 25, and there are 26 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=e75b498e5e79 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit 57f1653 into master Nov 3, 2026
31 checks passed
@gHashTag
gHashTag deleted the repair/types-ledger-parsedcommand branch November 3, 2026 13:13
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant