browser-checklisted

# Checking the work in a browser 1. Start the app's dev server from /work/repo in the background, bound to 127.0.0.1, or to 0.0.0.0 when the briefing names a preview port; keep its pid (`server_pid=$!`). Wait for its ready line and note the port. 2. `browser_navigate` to http://127.0.0.1:<port>/<path>. Read state with `browser_snapshot`, the accessibility tree, which is cheaper and more exact than a screenshot; act through the refs it lists with `browser_click`, `browser_type` and `browser_fill_form`. 3. Check the acceptance criteria in the browser one at a time, and read `browser_console_messages` for errors after each step. Do one pass with the keyboard alone: Tab order, Enter and Escape, visible focus. 4. Take `browser_take_screenshot` of every change a user can see, and of any other evidence the reviewer or the human needs. Files land in /tmp/browser. In a work session copy the screenshots of the result into /out/chat and name them in `ho_report`'s `files`, so the human sees them in the office chat; in a review name them in your findings. Copy the ones that belong in the repository into the repository and commit them with the change. 5. Close the pages and stop the dev server before you report, so the check command runs on a quiet machine. Stop it with the pid you kept (`kill "$server_pid"`), never with `pkill -f <pattern>`: the pattern also matches the shell running your own command, which then dies with exit 144 and the rest of th