Repository navigation
ledger(t27b): list spec_graph_derive, spec_graph_outline and t27mcp/find as pass (Closes #10212) - #10214
Conversation
…ind as pass (Closes #10212) #10198, #10202 and #10194 added these three specs without a row in docs/reports/t27b_expectations.json, so t27b-native-ratchet reads "UNLISTED 3" on master and on every open PR (run 39096977680 on #10185): "the reference passes it and the ledger does not name it (t27b pass)". Adds the three rows in path order with the verdict the run measured. No other row moves. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
![tri-claw[bot]](https://avatars.githubusercontent.com/in/5166765?s=60&v=4){kind=small}
There was a problem hiding this comment.
Reviewer bee verdict for head fa66e1c45712424eb1eb29c243a73899fc9e96eb (tools/bees/reviewer.py, zai glm-4.7-flash, glm-4.5-flash, 4 turns, 60 s; then glm-4.7-flash, 5 turns, 51 s).
BEE-VERDICT: APPROVE
summary: PR correctly adds the three missing specs to t27b ledger in proper order with pass verdict
criterion: "Turn t27b-native-ratchet green again on master and on every open PR" -- met -- Added specs/t27f/spec_graph_derive.t27, specs/t27f/spec_graph_outline.t27, and specs/t27mcp/find.t27 to docs/reports/t27b_expectations.json with "t27b: pass"
discounted-check: coverage -- Existing stale seal issue on master, unrelated to ledger changes
discounted-check: duplicate-bodies -- Existing duplicate bodies issue on master, unrelated to adding ledger rows
discounted-check: t27b-native-ratchet -- This is the issue being fixed (UNLISTED 3), not a new defect introduced by the head
Evidence
Analysis
Based on my review of the pull request #10214:
Does the change meet the issue requirements?
Yes, the change correctly addresses issue #10212:
-
Goal Achievement: The PR adds the three missing specs to
docs/reports/t27b_expectations.jsonwith "t27b: pass" verdict, which should turnt27b-native-ratchetfrom red (UNLISTED 3) to green (UNLISTED 0). -
Boundary Compliance: The change only affects
docs/reports/t27b_expectations.json, exactly as required. No other files are modified. -
Requirements Met:
- FR-001 ✓: Each new row carries "t27b: pass" verdict
- FR-002 ✓: Only one file changed with 3 additions, 0 deletions
- FR-003 ✓: Rows are in proper path order
-
Success Criteria:
- ✓
git diff --numstatshows3 0 docs/reports/t27b_expectations.json - The entries are correctly positioned alphabetically
- ✓
Red Checks Analysis
-
duplicate-bodies- Does NOT count against this head- This check is red on master for the same reason (duplicate bodies in existing specs)
- The PR only adds ledger rows, doesn't change spec content
-
coverage- Does NOT count against this head- This check is red on master due to a stale seal (policy_OwnLanguage.json)
- Unrelated to adding ledger rows
-
t27b-native-ratchet- Does NOT count against this head- This is the exact issue the PR is trying to fix
- It was red on master with "UNLISTED 3" for the same reason
- The PR's change should fix this, but the CI run might not reflect the final state
The changes are minimal and surgical - exactly what's needed to resolve the unlisted specs issue without affecting anything else.
Second, independent review (glm-4.7-flash): APPROVE -- All three specs listed with pass verdicts in correct path order; no changes to other specs; pre-existing failures not caused by this PR
tri-claw
Bot
added
the
bee-reviewed
…s pass (Refs #10233) t27b-native-ratchet is red on master and on #10185 with UNLISTED 3: specs/ci/suite_ledger_steward.t27, specs/jobs/suite_ledger_steward.t27 and specs/tri/pr/preflight.t27 pass on the reference and t27b but the ledger does not name them. Same shape as #10214. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…Closes #10233) (#10234) * spec(tri/pr): preflight -- drop the use path through the keyword test (Closes #10233) Since #10220 the parser discarded 7 tokens of use tri::test::report::opens_with; -- the path stops at the keyword test -- and the suite's parse-no-discard phase failed on master. preflight now builds a private opens_with on the span_is it already imports from tri::lab::receipt; the four call sites are unchanged. Seal and gen/rust are regenerated by t27c on the Railway lab. Lab, master fdb6b28 + this change: parse-complete reports nothing discarded, test-report 19/19 with 0 vacuous (same as before), and check_seal_coverage.py: OK, 2514 seals, 2392 hold. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ledger(t27b): list preflight and the two suite_ledger_steward specs as pass (Refs #10233) t27b-native-ratchet is red on master and on #10185 with UNLISTED 3: specs/ci/suite_ledger_steward.t27, specs/jobs/suite_ledger_steward.t27 and specs/tri/pr/preflight.t27 pass on the reference and t27b but the ledger does not name them. Same shape as #10214. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ledger(t27b): list spec_graph_fold as pass (Refs #10233) #10228 added specs/t27f/spec_graph_fold.t27; t27b-native-ratchet on #10234 reports it UNLISTED (reference and t27b pass it). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ledger(t27b): list specs/t27f/hot.t27 as pass (Refs #10233) Master drift from #10235: t27b-native-ratchet run 39100342521 reports UNLISTED 1 for exactly this spec. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
1 participant
Closes #10212
#10198, #10202 and #10194 each landed a spec without a row in
docs/reports/t27b_expectations.json. Since thent27b-native-ratchethas been red on master and on every open PR. On #10185 (run 39096977680) it read: "UNLISTED 3 ... the reference passes it and the ledger does not name it (t27b pass)".Change
Three rows are added in path order, each with the verdict the run measured:
specs/t27f/spec_graph_derive.t27specs/t27f/spec_graph_outline.t27specs/t27mcp/find.t27No other row moves, and no spec changes.
git diff --numstat origin/masterprints3 0 docs/reports/t27b_expectations.json. The file still parses as JSON.🤖 Generated with Claude Code