Acceptance — UI

Drive the running app in the user's Chrome or Edge through kimi-webbridge. Click, type, submit, reload, and assert on what is actually on screen. Component tests mock the network; this proves the wired stack. A fresh headless browser is a different session — it is not this drive, and this skill does not install one.

Invoked by validate-feature 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.