Revert the motion capability: the page clock, the probe and the filmstrip (#433) #435

Merged
cmoriarty merged 1 commit from revert-motion-433 into main 2026-11-08 13:09:42 -05:00
Owner

Closes #433. Closes #429.

Run 182's Visual check showed each part of the motion capability failing (braid#425, findings 14, 17, 18):

  • the filmstrip helper resolved the Playwright CLI symlink before walking up to the package, so Node found no playwright and no strip was ever composed on production;
  • the judge wrote 36 freezes of its own instead of running the pasted probe, which cannot wait for a server's reply;
  • the paused clock held a page script for 1,200 s twice, about 50 minutes of the step.

What goes. Braid's page clock and its install by the browser server (OSF_BRAID_CLOCK), the motion probe, the filmstrip helper and script, the brief's paragraphs on them and the rule "never write a freeze of your own", the init_script option of mcp_config, their tests, the clock journeys in ui/e2e/judge-probes.spec.ts, and the motion-filmstrip capability (retired at archive). The guide keeps one sentence saying what is left and where the research is (#434).

What stays. The judge sees motion as before braid#407: act and freeze in one browser_evaluate (braid#346), in the browser prompt and the judge's own-browser rules. The 180 s page-script bound (#428) stays, on the plain timer. The text and canvas probes are untouched.

Checked. ./tools/test.sh green (531 unit, 44 journeys); ./tools/sim.sh judge-requirement-by-name passes with the brief no longer naming the filmstrip; openspec validate revert-motion-capability --strict passes.

🤖 Generated with Claude Code

Closes #433. Closes #429. Run 182's Visual check showed each part of the motion capability failing (braid#425, findings 14, 17, 18): - the filmstrip helper resolved the Playwright CLI symlink before walking up to the package, so Node found no `playwright` and no strip was ever composed on production; - the judge wrote 36 freezes of its own instead of running the pasted probe, which cannot wait for a server's reply; - the paused clock held a page script for 1,200 s twice, about 50 minutes of the step. **What goes.** Braid's page clock and its install by the browser server (`OSF_BRAID_CLOCK`), the motion probe, the filmstrip helper and script, the brief's paragraphs on them and the rule "never write a freeze of your own", the `init_script` option of `mcp_config`, their tests, the clock journeys in `ui/e2e/judge-probes.spec.ts`, and the `motion-filmstrip` capability (retired at archive). The guide keeps one sentence saying what is left and where the research is (#434). **What stays.** The judge sees motion as before braid#407: act and freeze in one `browser_evaluate` (braid#346), in the `browser` prompt and the judge's own-browser rules. The 180 s page-script bound (#428) stays, on the plain timer. The text and canvas probes are untouched. **Checked.** `./tools/test.sh` green (531 unit, 44 journeys); `./tools/sim.sh judge-requirement-by-name` passes with the brief no longer naming the filmstrip; `openspec validate revert-motion-capability --strict` passes. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
revert(judge): take out the page clock, the motion probe and the filmstrip (#433)
All checks were successful
test / suite (pull_request) Successful in 55s
0a19d9c080
Run 182 showed each part failing: the filmstrip helper could not find
Playwright through the CLI symlink and never composed a strip, the judge
wrote its own freezes instead of the pasted probe, and the paused clock
held a page script for 1,200 s twice. The judge sees motion as before
braid#407: act and freeze in one browser_evaluate (braid#346). The 180 s
page-script bound stays, on the plain timer. The motion-filmstrip
capability is retired; braid#434 holds the research into a method.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
cmoriarty deleted branch revert-motion-433 2026-11-08 13:09:42 -05:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid!435
No description provided.