terminal-perf-testlisted

# Terminal rendering performance test Runs the real stack locally — `gravityd` with the deterministic `double` runtime, the Vite-served desktop frontend in Chrome — then seeds terminals with more output than the daemon's 1 MiB scrollback ring and stress-tests the paths that have historically broken: bulk replay after eviction, rapid bot switching, live streaming, scrolling under load. Why the double runtime: it echoes every `input` byte back as terminal output (so a driver script can pump arbitrary ANSI at any rate), and it prints a `[resize CxR]` marker for every pty resize — making the forced-repaint nudge (shrink to rows-1, restore ~50 ms later; see `REPAINT_NUDGE_DELAY` in `crates/gravityd/src/supervisor.rs`) visible on screen. ## Setup Use Node 22+ for the driver and the prerequisites in `CONTRIBUTING.md`. Run from the repository root in a dedicated terminal. Verify test ports 49555 and 1420 are free first; choose unused ports consistently if needed. ```bash umask 077 PERF_DIR=$(mktemp -d "${TMPDIR:-/tmp}/gravity-perf.XXXXXX") PERF_DIR=$(cd "$PERF_DIR" && pwd -P) export GRAVITY_HOME="$PERF_DIR" export GRAVITY_WS=ws://127.0.0.1:49555/ws cargo build -p gravityd cat > "$GRAVITY_HOME/gravityd.toml" <<EOF home = "$GRAVITY_HOME" bind = ["127.0.0.1"] port = 49555 negotiate_port = false runtime = "double" supervision_interval_ms = 500 EOF ./target/debug/gravityd --config "$GRAVITY_HOME/gravityd.toml" > "$PERF_DIR/gravityd.log" 2>&1 & PERF_DAEMON_PID=$! ``` Wait for `$GRAVI