DOCUMENTATION · SPEC v3.2

Implementation path

Implement the real first path and test the changed behavior.

Required first result

page goal
→ generated userscript
→ ScriptCat registry
→ target execution
→ observed effect
→ repair or rollback

Narrow evidence

Run the normal extension build, the specific provider/target test, and one real browser interaction that distinguishes success from failure. Do not replace this with scaffolding, schemas, or a future network plan.

Current boundary

The public repository and site exist. The full integrated ScriptCat extension, Torsion Node, Debian runner, and participant edge pilot remain to be completed and verified as a single product path.

Acceptance matrix →