codex-slides-verification

1# Codex Slides Verification
2 
3Use two signals before reporting a presentation task complete:
4 
51. Read canonical project state with `get_project`, and read a named durable job
6   with `get_project_run` or `wait_project_run` when a `runId` was returned.
72. Follow the returned `browserHandoff` and inspect the exact visible result in
8   the Codex in-editor Browser.
9 
10## Verification sequence
11 
121. Confirm the project id rather than guessing from a similar title.
132. For a durable run, require a terminal `complete` status. Treat `error` and
14   `cancelled` as incomplete; a timed-out wait leaves the run active.
153. Confirm the expected page count, changed slide indexes, rendered images,
16   transitions, speaker notes, current workflow stage, and current deck version.
174. Open the exact handoff returned by the mutation. Preserve its `slide`,
18   `panel`, `version`, `mode`, `conversation`, `checkpoint`, and `run` query
19   parameters.
205. In Browser, confirm the intended slide or panel is focused and the visible
21   result matches the request. Do not treat a JSON response alone as visual QA.
226. Export only after the current or explicitly selected version passes review.
23 
24If the in-editor Browser is unavailable, use the project state and persisted
25slide-image endpoints as structural evidence, return the exact handoff URL, and
26state that visible Browser verification remains outstanding.
27 
28For cross-surface changes, also verify that refreshing or reopening the same
29…