Revert the motion capability: the page clock, the probe and the filmstrip (#433) #435
Loading…
Reference in a new issue
No description provided.
Delete branch "revert-motion-433"
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?
Closes #433. Closes #429.
Run 182's Visual check showed each part of the motion capability failing (braid#425, findings 14, 17, 18):
playwrightand no strip was ever composed on production;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", theinit_scriptoption ofmcp_config, their tests, the clock journeys inui/e2e/judge-probes.spec.ts, and themotion-filmstripcapability (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 thebrowserprompt 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.shgreen (531 unit, 44 journeys);./tools/sim.sh judge-requirement-by-namepasses with the brief no longer naming the filmstrip;openspec validate revert-motion-capability --strictpasses.🤖 Generated with Claude Code