feat: Rust/Tauri server port + tab-continuity safety trio

.cargo/config.toml

@@ -0,0 +1,14 @@
+# Additive cross-compile config for the freshell Rust port (worktree-local).
+#
+# This file ONLY configures the Windows GNU cross target so a Windows
+# `freshell-server.exe` can be produced from this WSL2 host for the test matrix
+# ("Windows server" leg). It does NOT touch the default (host Linux) build: the
+# `[target.x86_64-pc-windows-gnu]` table applies solely when that target is
+# selected via `--target x86_64-pc-windows-gnu`.
+#
+# Toolchain: `rustup target add x86_64-pc-windows-gnu` + Debian/Ubuntu
+# `mingw-w64` (provides `x86_64-w64-mingw32-gcc`, used both as the linker and as
+# the C compiler the `cc` crate picks up for rusqlite's bundled SQLite).
+[target.x86_64-pc-windows-gnu]
+linker = "x86_64-w64-mingw32-gcc"
+ar = "x86_64-w64-mingw32-ar"

.gitignore

@@ -38,3 +38,24 @@ artifacts/perf/
 .opencode/
 sdk.session.snapshot
 .kata.local.toml
+
+# --- Rust/Tauri port (additive; port-scoped so the Node repo is undisturbed) ---
+# Cargo build output for the workspace at this worktree root.
+/target
+**/*.rs.bk
+# Note: Cargo.lock IS committed for the workspace (it will host binaries).
+
+# claude sidecar deps (npm install in the sidecar dir; not vendored in git)
+crates/freshell-claude-sidecar/node_modules/
+
+# --- vm-bridge session scratch (SECURITY: mandatory, per 2026-07-10 adversarial
+# security review). The bridge watchers EXECUTE any *.cmd that appears in an
+# inbox. If an inbox file were ever committed, `git pull`/checkout would drop it
+# into a watched folder and it would run on any machine with a watcher live --
+# i.e. git becomes an RCE channel. These patterns keep every bridge artifact
+# (inboxes, outboxes, liveness beacons, quarantine, outbound bundles) out of git.
+port/vm-bridge/inbox-*/
+port/vm-bridge/outbox-*/
+port/vm-bridge/quarantine-*/
+port/vm-bridge/alive-*.txt
+port/vm-bridge/outbound/

AGENTS.md

@@ -32,6 +32,10 @@ Freshell is a self-hosted, browser-accessible terminal multiplexer and session o
 - Use `npm run test:vitest -- ...` for a repo-owned direct Vitest path. Raw `npx vitest` is not a coordinated workflow.
 - `test:unit` is the exact default-config `test/unit` workload, `test:integration` is the exact server-config `test/server` workload, and `test:server` stays watch-capable unless you pass an explicit broad `--run`.
 
+## Destructive Test Sandbox
+- Process-kill, config-corruption, and restart-storm suites run inside a disposable Docker sandbox, never directly on host: `scripts/sandbox-test.sh "<command>"` (or `npm run test:sandbox -- "<command>"`).
+- See `docs/development/test-sandbox.md` for the safety guarantees, the `--corpus` read-only real-data flag, and cache-volume management.
+
 ## Kata
 - `.kata.toml` is committed project configuration. Always commit it after modifying it.