canon-frames-readlisted

# Canon frames read ## Guards - If no recording path is given, stop: `❌ No recording path. Pass the video canon demo run wrote.` - Never write a pass-fail judgment, a "looks correct" line, or a "looks broken" line, anywhere in the report. A frame read is evidence a person weighs, not a verdict this skill hands them. - Never drive the application. Everything this skill touches is the frame files the verb already wrote, and it opens no browser and clicks nothing. - Never edit, trim, or otherwise modify the recording. The frames verb writes new files beside it, and this skill only reads what that writes. ## Step 1: extract frames Run: ```bash canon demo frames <video> --json ``` Branch on the record's `reason` rather than the exit code: - `video-missing`: report that the path does not resolve and stop. - `converter-missing`: report that ffmpeg is not installed and stop. `canon demo frames --help` names the install line. - `extraction-failed`: report the record's `message` and stop. - No `reason` key, meaning frames were written: continue to Step 2 with the record's `frames` array. ## Step 2: read every frame Read each path in `frames`, in array order, with the Read tool. Do not skip any and do not sample a subset, since a gap in the sequence is a gap in what the report covers. ## Step 3: report One numbered list entry per frame, each a plain description of what is on screen: the visible UI state, on-screen text, cursor position, and anything that changed from the entr