attaching-browser-recordingslisted

# Attaching Browser Recordings ## Core principle For a browser-visible change, PR evidence includes a short recording of verified behavior. Exercise the real flow and attach it in the same authorized PR operation. ## Decide whether to record | Change | Action | | --- | --- | | UI, interaction, responsive behavior, animation, or rendered fix | Record the shortest reviewer-relevant flow. | | No meaningful browser behavior | Skip and state why. | | Flow or recorder unavailable | Report the blocker; never fabricate verification. | If creating or updating the PR is in scope, attaching its evidence needs no separate confirmation. Otherwise stop before `gh` mutates GitHub and report the local path. ## Record and verify 1. Identify the changed behavior and expected final state. Use sanitized test data. 2. Prepare the page first. Exclude secrets, personal data, unrelated UI, and dead time. 3. Create a task-specific directory outside the worktree with `mktemp -d`. 4. Use the available browser automation's native recorder. With `agent-browser`: ```bash recording_dir="$(mktemp -d)" video_path="$recording_dir/profile-update.webm" agent-browser open http://127.0.0.1:3000/settings/profile agent-browser record start "$video_path" agent-browser snapshot -i agent-browser fill @e2 "Ada Lovelace" agent-browser click @e3 agent-browser wait --text "Profile updated" agent-browser record stop ``` 5. Inspect the final state. Confirm the video exists, plays, shows the intended result, and is