debug-ui

# debug-ui — QA the dev-3.0 UI in a real browser See and drive the running dev-3.0 UI in headless Chromium — click, type, screenshot, read console errors — instead of guessing whether a UI change works. No desktop/native dependency; it works the same in a plain terminal session. This is **dev-internal tooling for the dev-3.0 repo** — NOT one of the skills dev3 ships to its users (those live in `src/bun/agent-skills.ts`). ## The whole flow This task's dev-server **is** the web UI: `bun run dev` serves the full app in local remote mode at a stable per-machine token and a CLI-derivable port — no separate `dev3 remote`. The loop is always the same four beats: **values → server → browser → clean up.** ```bash # 1. Values. AGENT_BROWSER_SESSION isolates THIS task's browser from every other agent's — # without it all agents share one global "default" session and stomp each other (see # Gotchas). Derived from the always-present $DEV3_TASK_ID, so this exact line is # copy-paste-safe at the top of ANY block that calls agent-browser. export AGENT_BROWSER_SESSION="dev3-${DEV3_TASK_ID%%-*}" CODE=$(cat "$HOME/.dev3.0/dev-web-access-code" 2>/dev/null || bun scripts/dev-web-code.ts) PORT=${DEV3_PORT0:-$(dev3 dev-server status | grep -oE 'DEV3_PORT0=[0-9]+' | cut -d= -f2)} # 2. Start a FRESH dev-server and wait for it to come up. (Skip the start only if one is # already running for THIS task — but see the build-snapshot gotcha: stale code needs a # restart, so when in dou...