fix: remove vulnerable runtime dependencies in 1.0.3-5

[lightsifter]

Change

Fixes #111. Release 1.0.3-5 updates the pinned MCP SDK to 1.31.0 and Transformers.js to 4.3.1. The resulting runtime dependency tree uses sharp 0.35.5 and ONNX 1.30.0/global-agent 4.1.3, removes the old roarr/sprintf-js/boolean chain, and refreshes compatible SDK transitive dependencies.

The inference cache generation advances to v3 so new embeddings cannot reuse vectors from the previous runtime. The pinned offline model, public search contract, and host configuration defaults are preserved. Plugin manifests and bundles were regenerated by the normal build.

Validation

• bun run check
• bun run check:local: 533 passed, 3 skipped, 0 failed; 4,019 assertions; generated artifact checks, lint/types, Node stdio/HTTP smoke, benchmark passed.
• bun run pack:check: npm publish dry run passed.
• bun run test:concept: 8 passed, 0 failed against the real offline multilingual model.
• Clean packed consumer installed with Vite+/pnpm and audited against the official npm registry: pnpm audit --prod --json reports 0 vulnerabilities.
• Real Claude Code 2.1.292 and Codex 0.160.1 MCP consumer checks passed, including the packed artifact; OMP native exact/structure/outline/inspect/concept/hybrid checks passed.
• Reviewed the final diff and shipped artifacts twice; first-review findings were corrected and reviewed again.

Private regressions retained locally (per contribution policy): the previous-runtime cache record failed before the cache generation change and passes after it; the real-model hybrid fixture now isolates independent short files and asserts actual supplement paths while retaining long Chinese retrieval/cache coverage. The OMP fixture explicitly enables vectors. Jev checks found no gate evasion in those test changes.

Compatibility and risks

Transformers crosses a major version; real inference and cache invalidation were verified. Existing model assets are reused; embeddings are recomputed under v3.

The repository-wide development dependency audit still reports brace-expansion, ip-address, tinypool, and undici advisories. Those dependencies are not in the clean production consumer tree; this PR does not claim the entire development tree is vulnerability-free. Mirror audit API returned 404, so security verification used the official registry. An npm audit without a package-lock on the pnpm layout failed internally; the official npm advisory service check via pnpm completed successfully.

Documentation

• Changelog updated for 1.0.3-5.
• No private tests, internal documents, credentials, or logs are included.

AI assistance

Implemented and reviewed by Codex (GPT-6 family). Executed the checks listed above, with Baoer Jev supervision. No separate human review is claimed.