verify-katacodelisted

# Verify Kata Code (web) This skill is for a cold agent that has never seen the app. It launches a disposable Kata Code web stack, pairs a browser the way a user does, drives one mapped feature, and leaves proof on disk. The primary surface is the **web client** at `apps/web`, served with the local server. Desktop wraps the same routes in Electron. Mobile is a separate React Native app. Marketing is a separate site. Do not claim those other clients are verified because the web app worked. Iterative human testing against a kept-alive worktree stack is the sibling `test-t3-app` skill. This skill is stricter: dedicated `--home-dir`, never attach to a stack you did not start, always capture evidence, always tear down what you started. ## Launch From the repository root, load the printed values into the current shell: ```bash eval "$(.agents/skills/verify-katacode/bin/launch)" ``` `launch` writes progress on stderr and only `KEY=value` lines on stdout, so `eval` exports `RUN_ID`, `RUNNER_PID`, `HOME_DIR`, `VERIFY_ROOT`, `WEB_ORIGIN`, `SERVER_PORT`, `WEB_PORT`, `EVIDENCE_DIR`, `ENV_FILE`, and `PAIRING_URL`. The same exports are also written to `$ENV_FILE` (`${TMPDIR:-/tmp}/katacode-verify-<RUN_ID>/run.env`) for a later `source "$ENV_FILE"`. That starts `node scripts/dev-runner.ts dev --home-dir <disposable>` with no `--browser`, no `--share`, and with `VITE_HTTP_URL` / `VITE_WS_URL` unset. Dev is single-origin. Vite proxies `/api`, `/oauth`, `/.well-known`, and `/ws`. Bakin