Implementation evidence / non-normative
ScriptCat Node VM semantic prototype
Host verified; Debian 13 executor NEEDS_REPAIR
Provenance
- Upstream:
scriptscat/scriptcat - Commit:
413bee9593259179e9db72be61d98f060fcf5738 - Archive SHA-256:
0f7b10780a7ab9c71b6697c7510b0e1ae56f2d8851af029ddfe84beadbd9bcea - License: GPL-3.0
Verified host evidence
- Three Node.js modules built after syntax checks.
- Seven of seven tests passed.
- Authenticated loopback health and
system.describesmoke test passed. - The first npm-based run failed because the local Volta/npm launcher could not load
npm-prefix.js; the runner was repaired to invoke Node directly and passed on rerun.
Calls represented
system.describe, calls.list, userscript lifecycle calls, virtual tab lifecycle calls, provider bind/insert/submit/capture and bounded extension.eval.
Exact boundary
This is an executable semantic harness, not the production ScriptCat fork. Tabs and providers are virtual. The production Rust node is not implemented. Podman exists, but its Linux machine/socket is unavailable; the Debian image build exits 125 and is classified NEEDS_REPAIR.
Next packet
Wire only userscripts.install and userscripts.update into ScriptCat's canonical registry and hot-reload path, preserve identity across ten updates, prove rollback, then rerun the same campaign in a functioning Debian 13 executor.