feat(tri): read the one subset of open issues that re-measures itself

[gHashTag]

Refs #2983

An open issue is a claim with a date on it. This repository holds 477, and 268
carry a number in the title — a stated measurement of the tree, taken once, re-read by
nothing.

Most cannot be checked automatically: extracting the measurement from free prose is the
precision problem that killed a superlative detector one pass ago (2 real hits in 6). One
subset can, because its truth is stored outside the repository — an issue whose title
says a named workflow is red, against what that workflow last concluded on master.

  open issues read        477
  workflow files          49
  titles claiming red     9
  of those, every named workflow is green today   5
  attributed from the body, not the title         4

#2851 Seal Coverage · #2754 secret-scan + cli-tri · #2729 cli-tri · #2278
emit-bitexact · #2263 cli-tri + emit-bitexact — all green today. #2915, #2914, #2783
and #2292 are still correctly red and left alone.

What a green reading does NOT say

It does not say the issue is resolved, and the command never suggests closing one.
#2729 makes the distinction concrete: its title is stale, and its argument is not — the
workflow still carries

    paths:
      - 'cli/**'
      - 'Cargo.toml'
      - 'Cargo.lock'
      - '.github/workflows/cli-tri.yml'

which is the sentence the issue was actually about, and the same shape as #2903. A tool
that conflated "the headline is false" with "the issue is resolved" would close live work.

What a stale headline costs is real anyway: with 477 open issues, a reader stops at the
title.

The recall bug it was built around

Issues name a workflow the way GitHub displays it. seal-coverage.yml displays as
Seal Coverage, so a reader keyed on the file stem cannot see #2851 at all. Measured:
22 of 49 workflows display under a name that differs from their stem, and adding that
key moved the population from 8 to 9 — the one it added being the example I already
had the answer for.

Without that example, "no issue names this workflow" and "my reader cannot see how
issues name workflows" print the same number.

Two more decisions worth the review

The boundary treats - and _ as word characters, so cli-tri does not match inside
cli-tri-mcp — two different things here, and the subject of #2903.

Attribution is split. The claim lives in the TITLE, so the title's workflows carry it.
Falling back to the body pulled in a workflow red for its own reasons and marked two stale
headlines as still red; rows attributed from the body now say so.

Verify

cargo test --manifest-path cli/tri/Cargo.toml     # 427 passed
tri issues stale

Five tests, including the display-name case, the boundary case, and a refusal on an empty
workflow directory — because "no issue names a workflow" and "this command could not
read any workflow" must not print the same zero.

Skill 416–418. The third is self-inflicted: an unquoted heredoc ran every backticked
span in the first draft as a command and left four holes in the prose — written down here
already, from a commit message that lost four words the same way.

🤖 Generated with Claude Code

[github-actions]

📓 NotebookLM Notebook linked to this PR

• Notebook ID: b83263109fb055dc
• URL: https://notebooklm.google.com/notebook/b83263109fb055dc

This notebook contains session context, decisions, and artifacts for this work.

[github-actions]

PR Dashboard

Generated at: 2026-08-30 19:53:14 UTC

• feat(tri): read the one subset of open issues that re-measures itself #2985 feat(tri): read the one subset of open issues that re-measures itself | Created: 2026-08-30 | Updated: 2026-08-30 | 22 failing / 27 total
• fix(zig): a statement that lowered to nothing is not a semicolon (+25 deep, +26 build-obj, 0 regressions) #2984 fix(zig): a statement that lowered to nothing is not a semicolon (+25 deep, +26 build-obj, 0 regressions) | Created: 2026-08-30 | Updated: 2026-08-30 | 2 failing / 2 total
• Land the formal verification harness on master (it has never run) #2727 Land the formal verification harness on master (it has never run) | Created: 2026-08-27 | Updated: 2026-08-27 | 5 failing / 24 total
• chore(deps)(deps): bump thiserror from 2.0.18 to 2.0.20 #2693 chore(deps)(deps): bump thiserror from 2.0.18 to 2.0.20 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• chore(deps)(deps): bump hyper from 1.10.1 to 1.11.0 #2692 chore(deps)(deps): bump hyper from 1.10.1 to 1.11.0 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 33 total
• chore(deps)(deps): bump base64 from 0.22.1 to 0.23.1 #2691 chore(deps)(deps): bump base64 from 0.22.1 to 0.23.1 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• chore(deps)(deps): bump serde from 1.0.228 to 1.0.229 #2690 chore(deps)(deps): bump serde from 1.0.228 to 1.0.229 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• chore(deps)(deps): bump uuid from 1.23.2 to 1.25.0 #2689 chore(deps)(deps): bump uuid from 1.23.2 to 1.25.0 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• Unbreak FPGA CI and correct two unbacked hardware claims #2081 Unbreak FPGA CI and correct two unbacked hardware claims | Created: 2026-08-11 | Updated: 2026-08-20 | 5 failing / 27 total

Summary

Status	Count
Total Open PRs	9
PRs with Failing Checks	7
PRs with All Checks Green	2
READY	0
FAILING	7
PENDING	0

Seal Status

• ⚠️ STALE -- sha256(compiler.rs)=4eccc2f5d228 != 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).