The batch after run 182: helper tab, review briefs, wait cap, Depends on, what is seen, framework and web layer #437
Loading…
Reference in a new issue
No description provided.
Delete branch "batch-2026-11-08b"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The batch after run 182, six OpenSpec changes from the review of its findings (#425). Closes #424. Closes #426. Closes #427. Closes #430. Closes #431. Closes #432. #419 stays open for the next run's measurement.
What changes
window.__apphook: in scope by Braid's rule, never a finding.browsercheck waits at most 6 times, 5 s each (boundWait,browserWaitsin the guard); the seventh wait is refused with the words to report UNCLEAR; the judge's briefs say one state per brief, reached beforebrowseris sent.visual.jsonreason that cites the implementer's own check and names no appearance counts for nothing: the scenario stays uncovered and "Where the scenarios stand" says to write the test or say what a person sees. Run 182's 28 reasons split 16 kept, 11 rejected, as read by hand. The apply's look line drops "by default".deliverable-judgespec's purpose names the two layers and lists the web layer's eleven requirements; seven framework requirements and two brief sentences drop their browser words; a test holds the framework's bodies to neutral words. No behaviour changes on a web run.Also the wall-time analysis of runs 172 to 182 (
docs/design/measurements/2026-11-08-runs-172-182-wall-time.md).Checked on the laptop.
./tools/test.shgreen (545 unit, 113 vitest, 45 journeys, including the two new Ask journeys and the new tests for each change);./tools/sim.sh --smoke7 of 7;./tools/sim.sh judge-requirement-by-namepasses; every changeopenspec validate --strict. Not done: the scripted replays of run 182's propose, review, apply and judge steps named in the tasks; the next Scratch run is the measurement.🤖 Generated with Claude Code
Depends on:line, so the planner leaves it off #430browsercheck takes 5 to 7 minutes #419Depends on:line, so the planner leaves it off #430