Acceptance — UI

Drive the app in a real browser the way a user will: click, type, submit, reload, and assert on what's actually on screen. Component tests mock the network and prove the component's own logic; this proves the wired stack — render, request, response, re-render, persistence.

Invoked by acceptance-check with a slice of the acceptance ledger, or run directly against a frontend change. Work through the ledger in order.

1. Get the app running — and persist how

Read docs/agents/project.md for Run locally (dev). Start the frontend (and any backend it calls) with the recorded commands; if absent, discover them, start the app, confirm it loads in a browser, then WRITE them into project.md under ## Run locally (dev). Done when: the app loads AND the commands are recorded.