see-it-livelisted

# See it live Type-check passing and green tests are **not** proof the change works. Behaviour lives in the running app. Before you say "done," start the thing and observe the specific change with your own eyes (or a screenshot / a response body). ## Pick the launch path by project type | Project type | How to launch | What to observe | |---|---|---| | **Godot** | `godot --headless --quit` (catches parse/script errors fast); `godot --path . <boot scene>` for interactive; `godot --headless --script tests/<x>_check.gd` for a domain path | Scene loads with no errors; the changed behaviour happens | | **Web frontend** | Start the dev server (`npm run dev` / framework equivalent), open the changed route | Golden path renders AND the error state; screenshot it | | **Backend / API** | Start the server, `curl` the changed endpoint with a real payload | HTTP status + response shape match expectations | | **CLI / library** | Run the command/binary with real args | `stdout`/`stderr` AND exit code are correct | Match the project's actual run command - check its README / `CLAUDE.md` / `package.json` scripts / `justfile` first, don't invent one. ## Confirm the *specific* change, not just "it boots" - Before launching, write down the one thing you expect to see that proves the change works ("the Save button now shows a spinner", "`/api/jobs` returns `status: queued`"). - Launch, reproduce the exact path that exercises the change, and check for that specific signal. - "The app still st