feat(tri): tri issues dated -- the figures re-measurement cannot judge - #3011
Merged
Merged
Conversation
Of 486 open issues, 289 state a figure in the title and 83 of those are anchored: 27 pin a revision, 31 say as-of or snapshot, 25 have already been answered in the thread. An anchored figure disagreeing with today's tree is what a snapshot IS, not a defect. The command exists because one of my own verdicts was wrong this way: I called #2160's figure stale by re-measuring it to 0, when it pins a snapshot hash, its script refuses to run once the corpus moves, the owner had already posted new figures, and the gap I measured was settled by a decision the issue predicted. `tri issues dated --list` prints #2160 as `as-of`. The revision matcher's two float rules were each redundant on this corpus -- all 486 bodies, 2 rejections, both caught twice -- so deleting either left the tests green. Mutation found it; two constructed inputs now separate them. Refs #2983 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…ither is tested Deleting either float rule from revision_pins left every test green: across all 486 open bodies both rejections were caught by both rules. A green suite proved the pair and nothing about either member -- a control that cannot fail, one level down. Coverage cannot find this; both clauses execute on every input. Only per-clause deletion answers. Refs #2983 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
Contributor
PR DashboardGenerated at: 2026-09-03 08:38:53 UTC
Summary
Seal Status
|
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
…llets) Refs #2983 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-09-03 08:42:13 UTC
Summary
Seal Status
|
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-09-03 08:55:34 UTC
Summary
Seal Status
|
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.
What
tri issues datedreads every open issue whose title states a figure and reports which of those figures a second reading can actually decide.An anchored figure disagreeing with today's tree is not a defect. An issue that pins a revision states a reading of that revision; an issue someone already answered has been judged by a person, and a fresh reading adds nothing a reader of the thread does not already have. Twenty-nine percent of the figures in this backlog are in that class and nothing distinguished them before.
The command names no issue stale and never suggests closing one.
Why
One of my own verdicts was wrong in exactly this way. I called #2160's figure stale by re-measuring it to
0. It pins a snapshot hash, its own script printsREFUSING: the corpus moved since the snapshot was frozen, the owner had already commented the new figures, and the 18 lines I read as missing were settled by a language decision the issue predicted — so I presented a confirmed forecast as a wrong number.tri issues dated --listprints #2160 asas-of.The control, and the mutation that found it was not one
A hex run of 7..=40 characters carrying at least one letter and one digit is the shape of an abbreviated commit id. It is also the shape of a chunk of a float:
s[0] = -1.7594823e-05, whose7594823ematches perfectly.`5.391247e-44`inside backticks, so "quoted like code" does not separate them either.Two rules reject them: no decimal point immediately before the run, and no
eimmediately before a sign. Across all 486 open bodies both rejections are caught by both rules — so deleting either rule left every test green. Mutation found that, reading did not.each_float_rule_decides_a_case_the_other_missessupplies the two constructed inputs that separate them (5391247e-44has no dot;1.2345678e12has no sign for theeto sit before), and removing either rule now turns it red.Verification
cargo test -p triafter_pointexponent7..=40→4..=40says_as_ofviacontainsAnchorprecedencecli/tri/src/issues.rsonly, 275 insertions, 0 deletionscargo fmt -p trirewrote seven neighbouring files through the mod graph; those were reverted, andissues.rsre-hashes identically under a secondfmt.Refs #2983
🤖 Generated with Claude Code