chore(cargo)(deps): bump victauri-test from 0.8.5 to 0.8.7 in /src-tauri

[dependabot]

Bumps victauri-test from 0.8.5 to 0.8.7.

Release notes

Sourced from victauri-test's releases.

v0.8.7

• release: 0.8.7 — bridge cold-start fix + adversarial-audit hardening (#58) (ca0cea0)
• security(cli): round-2 audit follow-ups on the bridge (#57) (8a5da40)
• harden(cli): pre-audit hardening of the bridge cold-start change (#56) (3a066d1)
• fix(cli): bridge connects in a fresh terminal even when the app is down (#55) (c192083)
• chore(security): pre-push GATE 0 blocks re-introducing the private external-verifier name (dcd35d0)

v0.8.6

[0.8.6] - 2026-07-08

Security-focused release prep for the repo-local Verax pre-push gate. No public Rust API change and no runtime plugin behavior change for Victauri users; the hardened files are repo developer tooling and are not included in the published crates.

Security

• Closed a tracked core.hooksPath bypass in the gate installer. If a maintainer had configured core.hooksPath=.githooks, the installer wrote its verifier into the tracked .githooks/pre-push file itself. A hostile branch could then replace that tracked hook and execute on git push before any integrity check ran. The installer now refuses to install when Git's active pre-push hook path is tracked by the repo, preserving the invariant that the verifier lives only in untracked hook storage.
• Fixed Windows-native core.hooksPath normalization under Linux/WSL-style bash. Git can report a configured D:\...\hooks path as a repo-prefixed pseudo-path when that config is read by Linux Git from a mounted Windows checkout. The installer now normalizes Windows drive paths for the active shell before writing or asserting the hook location, preventing false-success installs into a path Git will not execute.
• Expanded the integrity pin set for gate tooling. The installed verifier now pins .githooks/pre-push, .verax/gate.json, tools/install-gate.sh, and tools/test-install-gate.sh, so the local gate cannot run a branch-modified helper script through a fixed gate.json command.
• Retained the unconditional .verax/gate.json absent sentinel from the round-2 release candidate. A branch that adds gate.json after install still reads as drift and fails closed.

Added

• tools/test-install-gate.sh regression harness. Covers default-hook drift, add-after-install gate.json, tracked .githooks refusal, Windows-native hook path normalization, relative custom hooks, and Husky-v9 .husky/_ hooks. The local Verax gate now includes this cheap installer harness before the Rust fmt/clippy/test jobs.

Fixed

• Cleared RUSTSEC-2026-0204 in the lockfile by bumping crossbeam-epoch from 0.9.18 to 0.9.20. The dependency is reached through Criterion benchmarks/dev-dependencies, not Victauri runtime code.

Changelog

Sourced from victauri-test's changelog.

[0.8.7] - 2026-07-13

A victauri-cli-only release (the plugin and other crates are unchanged): the victauri bridge stdio proxy now connects in a fresh terminal even when the app isn't running yet, and the change was hardened through an internal three-lens red-team, an external GPT adversarial audit, and a two-lens round-2 verification before shipping.

Security (external GPT adversarial audit round)

• The bridge re-resolves the trusted backend on every forwarded request instead of reusing a cached (port, token). Previously, after the app shut down (its discovery entry gone), a subsequent tool call could POST the cached Bearer token to whatever process had since bound the freed port — an attacker could receive the token and relay forged tool results. The token is now only ever sent to a currently-live, trust-checked, identity-matched discovery entry; the poller also drops the cached connection/session when the backend goes away. Regression test added.
• Malformed/empty successful backend responses can no longer corrupt the stream or hang the client. A non-SSE 2xx body is relayed only if it is valid JSON, and a request that yields no payload (empty/non-JSON 2xx, or 202) gets a synthesized JSON-RPC error for its id instead of hanging.
• tools/list_changed can no longer precede the initialize response. The "ready for notifications" flag is now set on the client's notifications/initialized ack, not when the bridge answers initialize. A round-2 pass found the ack could then miss a backend-up edge that occurred during the handshake window, so the ack handler now emits the refresh once if the backend is already up.
• A non-SSE 2xx body is relayed as compact single-line JSON, not verbatim — a valid but pretty-printed body can no longer be split across stdout lines and break a newline-delimited client (round-2 follow-up; the SSE path already had this rigor).

Hardened (pre-release adversarial audit of the bridge cold-start change)

• The availability poller is now the sole owner of the "backend up" state, so a tool call that reconnects inside the 1.5s poll window can no longer silently consume the down→up edge and leave the client stuck on the baked fallback tool list — tools/list_changed always fires on the real transition.
• stdin is read on a dedicated OS thread feeding an async channel, so the blocking read never parks a tokio worker; the poller (and thus auto-go-live) now works even on a single-vCPU host.
• The poller no longer emits notifications before the client's initialize, and backs off to a slower cadence once the backend is up (no needless tasklist/ps probe every 1.5s all session).
• The local initialize no longer advertises resources.subscribe — mirroring the plugin, which deliberately omits it (no server-initiated push exists), so a client can't subscribe and wait forever.
• The backend MCP lifecycle is completed for stateful servers: after the bridge's backend handshake it replays notifications/initialized to the backend.
• ps/tasklist/kill are invoked by absolute path (System32 / /bin / /usr/bin), not via PATH, closing a PATH-hijack surface the poller would otherwise exercise continuously.
• Mutex locks recover from poisoning instead of cascading a single panic into the death of the bridge (or, silently, the reconnect poller); a 202 response to a request no longer leaves the client's id hanging.
• Swept the vestigial --wait from README / MIGRATION / getting-started examples.

... (truncated)

Commits

• ca0cea0 release: 0.8.7 — bridge cold-start fix + adversarial-audit hardening (#58)
• 8a5da40 security(cli): round-2 audit follow-ups on the bridge (#57)
• 3a066d1 harden(cli): pre-audit hardening of the bridge cold-start change (#56)
• c192083 fix(cli): bridge connects in a fresh terminal even when the app is down (#55)
• dcd35d0 chore(security): pre-push GATE 0 blocks re-introducing the private external-v...
• 9db5d99 Merge pull request #53 from 4DA-Systems/fix/gate-r2-01-hardening
• 6b21237 ci: run the gate-installer integrity harness in CI (enforce R2..R7 regression...
• 0622d08 fix(security): close R7-01 (nested submodule) + R7-02 (symlink to any tracked...
• 4897506 fix(security): close R6-01 (submodule/gitlink hook dir) + R6-02 (quoted non-A...
• 48e1832 fix(security): close R5-01 with filesystem-IDENTITY tracked-hook check (ends ...
• Additional commits viewable in compare view

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
4da-home	Ready	Preview, Comment	Jul 17, 2026 11:10pm

[runyourempire]

@dependabot rebase