chore(proof-interceptor): install from the root npm workspace

[ofir-starkware]

Stacked on #1007 (PR 2 of the npm-workspace stack).

What

• Adds proof-interceptor to the root workspace. Its SDK dependency changes from file:../sdk to ^0.14.3-rc.8, which npm resolves by linking the local sdk/.
• Merges proof-interceptor/package-lock.json into the root lockfile, adding no package versions that weren't already locked. starknet stays a single shared copy. 100 entries that conflict with versions already hoisted at the root stay under proof-interceptor/node_modules.
• Dockerfile: one npm ci -w sdk -w proof-interceptor, then build and prune both. The image drops from 339 MB to 291 MB.
• CI:
  • proxy-ci installs from the root.
  • e2e-devnet builds the interceptor with npm run build -w proof-interceptor.
  • The path filters in proxy-ci and proof-interceptor-docker now include the root package.json and lockfile.

Why

• Same goal as chore(client): move sdk and client into an npm workspace with a peer SDK dependency #1007: one lockfile, one shared copy of each dependency, no file: links between packages in the workspace.
• The path-filter fix also covers a gap chore(client): move sdk and client into an npm workspace with a peer SDK dependency #1007 opens: its Dockerfile already reads the root lockfile, but the image workflow didn't trigger on changes to it.

Verification

• Fresh root npm ci works.
• sdk: build and lint pass, and test:fast passes 27/27 files.
• client: build and lint pass, and tests pass 66/66.
• proof-interceptor: build and lint pass, and tests pass 200/200.
• Docker image builds, /health returns 200, and dev dependencies are confirmed pruned.
• E2E devnet suite, run locally: 15/15 files, 28/28 tests.

🤖 Generated with Claude Code

---

This change is 

[semgrep-code-starkware-libs]

High severity vulnerability may affect your project—review required:
Line 9625 lists a dependency (vite) with a known High severity vulnerability.

ℹ️ Why this matters

Affected versions of vite and vite-plus are vulnerable to Exposure of Sensitive Information to an Unauthorized Actor / Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). Vite's server.fs.deny blocklist—which protects sensitive files such as .env and certificate files from being served—can be bypassed on Windows using alternate path representations (NTFS Alternate Data Stream syntax like /.env::$DATA?raw, or 8.3 short filenames), allowing an attacker to read otherwise-denied files when the dev server is exposed to the network.

References: https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-38303, GHSA, CVE

To resolve this comment:
Check if you expose the Vite dev server or vite-plus to the network by configuring a non-loopback address using the --host CLI flag on Windows.

• If you're affected, upgrade this dependency to at least version 6.4.3 at package-lock.json.
• If you're not affected, comment /fp we don't use this [condition]

💬 Ignore this finding

To ignore this, reply with:

• /fp <comment> for false positive
• /ar <comment> for acceptable risk
• /other <comment> for all other reasons

_{You can view more details on this finding in the Semgrep AppSec Platform here.}

[semgrep-code-starkware-libs]

Critical severity vulnerability introduced by a package you're using:
Line 7305 lists a dependency (tinypool) with a known Critical severity vulnerability. Fixing requires upgrading or replacing the dependency.

ℹ️ Why this matters

Affected versions of tinypool are vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'). Tinypool builds worker options by spreading them into a plain object, so inherited properties from a polluted Object.prototype (such as execArgv or env.NODE_OPTIONS) are passed to every spawned worker. An attacker who can pollute Object.prototype anywhere in the process can gain arbitrary code execution in all pool workers, including those created internally by Vitest.

References: https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-91718, GHSA, CVE

To resolve this comment:
Upgrade this dependency to at least version 2.1.1 at package-lock.json.

💬 Ignore this finding

To ignore this, reply with:

• /fp <comment> for false positive
• /ar <comment> for acceptable risk
• /other <comment> for all other reasons

_{You can view more details on this finding in the Semgrep AppSec Platform here.}

[semgrep-code-starkware-libs]

Critical severity vulnerability may affect your project—review required:
Line 9701 lists a dependency (vitest) with a known Critical severity vulnerability.

ℹ️ Why this matters

Affected versions of vitest are vulnerable to Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') / Missing Authorization. When the Vitest UI server is listening, the deprecated isFileServingAllowed check is applied without normalizing the URL before filesystem operations, allowing path traversal that lets an attacker read, write, and execute arbitrary files outside the project directory.

References: https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-44391, GHSA, CVE

To resolve this comment:
Check if you run the Vitest UI on Windows, or you expose the Vitest UI server to the network with the --api.host flag or api.host config option.

• If you're affected, upgrade this dependency to at least version 3.2.6 at package-lock.json.
• If you're not affected, comment /fp we don't use this [condition]

💬 Ignore this finding

To ignore this, reply with:

• /fp <comment> for false positive
• /ar <comment> for acceptable risk
• /other <comment> for all other reasons

_{You can view more details on this finding in the Semgrep AppSec Platform here.}