Record the first end-to-end chapter and two stages that lie

The run completed: chapter.mp4 at 50MiB from 49 clips. layers reported
completed 116/116 with an empty bucket, so nothing has parallax, and the completed
job still carries the error string from a failure three resumes earlier. Both
recorded as caveats, neither fixed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

caveats/CLAUDE.md

@@ -36,3 +36,5 @@ a complaint, so give it one or drop it.
 | [One character id covers two different women](speaker-attribution.md#identity-over-merge) | 2026-08-11 run |
 | [The character registry carries five weeks of wrong names](speaker-attribution.md#registry-pollution) | 2026-08-11 run |
 | [One invented word still halts the chapter](speaker-attribution.md#one-word-halts-chapter) | 2026-08-11 run |
+| [A completed job keeps the error from an earlier failure](audit-open.md#stale-job-error) | 2026-08-11 run |
+| [`layers` reports success on an empty bucket](audit-open.md#layers-writes-nothing) | 2026-08-11 run |

caveats/audit-open.md

@@ -151,3 +151,23 @@ transitions, so every non-`cut` transition shortens the real video.
 Costs: reviewer timestamps drift further out of sync the further into the chapter they scrub.
 Revisit when: the review UI is used for timing work.
 Workaround: subtract the transition overlaps by hand.
+
+## A completed job keeps the error from an earlier failure {#stale-job-error}
+
+`/job/resume` does not clear `jobs.error`. Job `778297bc` finished every stage and still reports
+`status: "completed"` beside `error: "partial: 112/116 completed"`, a message from three resumes earlier.
+
+Costs: any reader of the error field sees a failure on a successful job. The review UI and any future
+alerting both read it.
+Revisit when: anything branches on `jobs.error`, or a run is judged by its status alone.
+
+## `layers` reports success on an empty bucket {#layers-writes-nothing}
+
+Measured on job `778297bc`: `layers` reported `completed 116/116` while `s3://layers/` held 0 objects.
+Every clip in that run therefore has no parallax. The stage is a sibling of
+[#inconsistent-stage-policy](#inconsistent-stage-policy), but this is the measured instance:
+`worker_layers.py`'s own self-check already fails on the missing
+`legacy/qwen_layered_workflow.json`, and the stage still reports done for every panel.
+
+Costs: a silent quality regression that no status field reveals.
+Revisit when: parallax matters for a deliverable, or before quoting this run as a full-pipeline pass.