11 Commits

Author SHA1 Message Date
Lilleman e062f71d47 Answer stability round 1: 0 🔴, 2 🟡 (0 misread); tie the help's transcript floor to TRANSCRIPT_FLOOR, split the floor test, and name the shortfall in the judge's failure, with the prose round's wording 2026-11-20 01:24:21 +01:00
Lilleman 4fe37104aa Say that a record is read once where its text equals an earlier one's
CI / tests (pull_request) Successful in 2m49s
2026-11-20 00:48:51 +01:00
Lilleman f3af5e23fd Stop the judge rather than show it under 50,000 characters of the transcript, read a twice-named record once, test the forge timeout and decide the merge stop from the pull requests found 2026-11-20 00:45:49 +01:00
lilleman 914b8dc2d4 Answer stability round 1: 0 🔴, 4 🟡 (0 misread); a cycle's close takes the task from the cycle, a resolved thread is skipped unread, and tests run git in their own environment
CI / tests (pull_request) Successful in 3m56s
2026-11-19 14:04:11 +01:00
lilleman aafe75e16f Answer prose round 1: 0 🔴, 11 🟡 (0 misread); loop-claude and do-epic are entry points everywhere, and each new sentence holds one idea
CI / tests (pull_request) Successful in 3m40s
2026-11-19 13:44:20 +01:00
lilleman 2806a8edc9 Kill the mutants that survived on the lines the release review changed 2026-11-19 13:44:12 +01:00
lilleman cb3135bc8c Answer principles round 1: 1 🔴, 7 🟡 (0 misread); every effect is handed in as an argument, no test patches a global, and the traces principle scopes tools that run on their user's machine
CI / tests (pull_request) Successful in 3m43s
2026-11-19 12:42:03 +01:00
lilleman 8ca612b7a4 Answer architecture round 4: 0 🔴, 0 🟡 (0 misread); loop-claude's suites sit beside their modules, and what tests share across packages lives in each package's doubles.py
CI / tests (pull_request) Successful in 3m43s
2026-11-19 11:54:34 +01:00
lilleman 9bc2887ee8 Answer architecture round 3: 0 🔴, 1 🟡 (0 misread); every suite sits beside the module it tests, and test_loop_claude.py holds only loop-claude's own
CI / tests (pull_request) Successful in 5m17s
2026-11-19 11:43:38 +01:00
lilleman df210aaeca Answer architecture round 2: 0 🔴, 3 🟡 (0 misread); the cycle's and the chunk run's suites sit beside their modules, and the claim rule and the model override have one home each
CI / tests (pull_request) Successful in 3m23s
2026-11-19 11:29:32 +01:00
lilleman b8595db647 Answer architecture round 1: 0 🔴, 36 🟡 (0 misread); chunk_driver holds what both drivers share, and Jira and review-state reads have one home each
CI / tests (pull_request) Successful in 5m11s
2026-11-19 11:14:44 +01:00