[dependabot]

Security scope

Complete this existing Dependabot group instead of adding a duplicate PR. Preserve the original Dependabot commit and add the missing Vite update and regression coverage. Supersedes #13.

• MCP server/client/core: 2.3.0, addressing the four SDK advisories behind eight open alerts.
• Vite: 8.2.1 to 8.2.4 in both the direct dependency and workspace override, addressing the three bundled launch-editor advisories behind six alerts. A launch-editor-only override cannot fix Vite's embedded implementation.
• Regenerate the exact lockfile and third-party notices. Vite requires rolldown ~1.2.4; the lock resolves its supported 1.2.14 patch and matching platform bindings. No major-version upgrade, new dependency, audit exception, age-policy exception, or application feature change.

Boundaries preserved

BLACKPROOF's MCP remains local stdio only, read-only, with strict empty tool arguments, bounded framing, one private startup-selected snapshot, minimized aggregate results and redacted errors. No HTTP or OAuth endpoint is added. The SDK HTTP validation-memory/audience protections are opt-in, but those HTTP paths are absent from BLACKPROOF. This update is not a claim that an HTTP exploit was reachable in the existing static site or stdio service.

The public production artifact remains a static local-first AGPL site. No document-upload, payment, account or private-proof disclosure path is introduced. This PR does not republish an immutable MCP Registry release or overwrite an old package asset.

Regression verification

• Actual SDK server refuses a second simultaneous transport; independent actual stdio sessions retain different private V4/V5 counts without reflecting canaries, paths, identifiers or fingerprints. Expanded malformed argument forms remain redacted and valid empty input still works.
• Actual bundled Vite leaf modules are evaluated with allowlisted platform stubs, never real editor detection, subprocesses or commands: Windows post-suffix path normalization, WSL flag-like filenames, percent/CR/LF rejection, and ordinary spaces/line/column controls.
• Root, Astro, Svelte integration and Vitest must resolve the same patched Vite copy.
• Old dependencies fail the transport guard and Vite regression checks; patched targeted suites pass 15/15. Windows paths are emulated, not natively executed.
• Node 22.23.2 and pnpm 10.34.5; frozen installation and full audit passed with zero reported vulnerabilities and no suppressions. Both patched package releases predate the existing 24-hour release-age policy.
• A local browser run exposed an asynchronous fixture-preparation race: getAll request success preceded transaction completion, so close/delete could briefly block. The test now waits for transaction completion, keeping deletion's blocked failure and every byte-preservation assertion intact. The corrected scenario passed ten consecutive runs. No runtime storage behavior was changed.

Final pnpm verify:all passed: source/type/lint, unit tests, static build, Apache rendering, open-source and artifact security checks, full audit, secret/static audit, and 125 browser tests with the three pre-existing feature skips. The pre-push gate independently repeated check/test/build/audit/security successfully. GitHub CI and CodeQL are still required before merge.

Production must then use the exact successful main-branch CI artifact, verified provenance and checksums, followed by user-run privileged activation and independent live checks.