Repository navigation
master red: four newly parsed type names renamed, HttpStatus leaves the ledger (Closes #10389) - #10390
Merged
Conversation
…Status leaves the ledger, five specs resealed (Closes #10389) #10370 made specs parse that did not before, so Context, MatchResult, UnsubscribeResult and ProofTrace gained a second definition. Renamed on the side #10370 touched: LocalhostContext (security.t27), RouteMatchResult (router.t27), SchemaUnsubscribeResult (bus/schema.t27), CoaProofTrace and DatalogProofTrace. HttpStatus has one definition again, so its ledger line and classified row are dropped. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
#10389) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Contributor
gHashTag
enabled auto-merge (squash)
October 18, 2026 10:53
gHashTag
added a commit
that referenced
this pull request
Oct 18, 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.
Closes #10389
The required check "Corpus Ratchet" (
tri types ratchet) was red on master: ledger 108, observed 111. #10370 made specs parse that did not parse before, so four type names gained a second definition. The cause is fixed by renaming, and the ledger is not blessed for them.ContextLocalhostContextMatchResultRouteMatchResultUnsubscribeResultSchemaUnsubscribeResultProofTraceCoaProofTrace,DatalogProofTraceIn each pair the renamed side is the one #10370 made compile; the other keeps its name. The types keep their fields; none of the five is imported by another spec (checked with grep). Rename only touches non-comment lines.
HttpStatushas a single definition again (specs/server/http.t27), so its ledger line is dropped bytri types ratchet --bless(the only change that bless made), and its row is removed fromdocs/reports/type_conflicts_classified.jsonanddocs/TYPE_CONFLICTS.md(tri types classifiedwould otherwise report it STALE).Side effect: the
unsubscribe_result_createpair no longer has identical text (its return type differs), so its line leavestools/duplicate_bodies_baseline.txt(hand-removed, no bless).Checks (Railway lab, none on the Mac)
tri types ratchet: ledger 107, observed 107, RATCHET: CLEANtri types classified: OKt27c seal --save(11 files, siblings included);t27c seal-auditnames none of the fivepython3 tools/dupe_scan.py: okOnly
.t27files, seals, data and doc tables changed.🤖 Generated with Claude Code