main was red, and the root handoff was wrong about four things out of five - #408
Merged
Conversation
MAIN WAS FAILING BOTH DATE GATES and nobody had touched anything — the date rolled over. #405 and #404 edited the viewer without moving its version stamp, so the page claimed 2026-08-29 while git recorded both commits on 2026-08-30. Bumped, and bumped in `docs/site/viewer.template.html`, because since #404 the page is ASSEMBLED and editing the built file is exactly what `test_assembled_viewer` catches. THE ROOT HANDOFF IS THE FIRST THING EVERY SESSION READS, and every figure in it had rotted: #304 and #270 listed as in flight two days after they merged, `main` quoted at `ab1dbfd` (61 commits back), the suite at 1,391 (it is 1,571), and the board "down to 4 ACTIVE claims" while the machine-local one carried 30 — of which only 7 have a live worktree. None of that fired a gate. `tests/test_handoff_is_honest.py` only goes red when the LAST named PR closes, so this file could be wrong about four things out of five and still read as authoritative. Same shape as the scoreboard gate that could not fail and the suppression helper that went blind, and it earns the general form: a file whose whole job is to say what is true cannot be checked only on its own retirement condition. DECISION 2 IS ANSWERED. Tony asked for the orphaned branches to be merged, which settled PR #298: ADR-0003 has been on `main` since #406, all nine citations resolve, and the todo is closed rather than left waiting-on-tony. What that file got right is worth keeping — it refused to fill 0003 with anything else while the question was open, because renumbering would have broken nine citations to close one gap. Holding a number is a real option and this is the precedent. DECISION 3 ADDED, because it is now the one thing nobody can advance: `bench-background-is-not-flat` merges cleanly and fails four tests — three left red on purpose by their author ("re-baselining them would delete a finding") and one because `docs/learned/bakeoff.json` was computed on the flat field. Every tube-variant number in the 2026-08-29 handoff was measured in that environment, and it does not exist on `main`. Suite 1,571 passed, 49 skipped. Sapper clear. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
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.
mainwas failing both date gates and nobody had touched anything — the date rolled over. #405 and #404 edited the viewer without moving its version stamp, so the page claimed 2026-08-29 while git recorded both commits on 2026-08-30.Bumped in
docs/site/viewer.template.html, not in the built page: since #404 the viewer is assembled, and editingraster_viewer.htmldirectly is exactly whattest_assembled_viewercatches. It caught me.The handoff had rotted in every figure
It is the first thing the briefing reads aloud at every session start.
maingreen atab1dbfdced0da4— 61 commits backNone of that fired a gate.
test_handoff_is_honest.pyonly goes red when the last named PR closes, so the file could be wrong about four things out of five and still read as authoritative. Same shape as the scoreboard gate that could not fail and the suppression helper that went blind — and it earns the general form: a file whose whole job is to say what is true cannot be checked only on its own retirement condition.Decision 2 is answered; decision 3 is added
#298 is settled. Asking for the orphaned branches to be merged answered it — ADR-0003 has been on
mainsince #406, all nine citations resolve, and the todo is closed rather than leftwaiting-on-tony. What that todo got right is worth keeping: it refused to fill0003with anything else while the question was open, because renumbering would have broken nine citations to close one gap. Holding a number is a real option, and this is the precedent.bench-background-is-not-flatis now the one thing nobody can advance, so it is written into the handoff as a decision. It merges cleanly and fails four tests: threetest_background_curve.pytests its author left red on purpose ("re-baselining them would delete a finding"), andtest_the_server_reproduces_the_published_bakeoffat fold 3,29 != 28, becausedocs/learned/bakeoff.jsonwas computed on the flat field.Every tube-variant number in the 2026-08-29 handoff was measured in that environment. It does not exist on
main, which still describes its own bench as "Not wired into the bench".Verification
Suite 1,571 passed, 49 skipped, 0 failed. Sapper clear.
🤖 Generated with Claude Code