feat: replay video — stitch screenshots into captioned replay.mp4#13
Conversation
- replay.ts: pure ffmpeg arg-builder + renderReplay over an exec seam; createReplayStep binds real spawn + resolved caption font. Frames letterboxed onto a uniform canvas, step labels burned in. - FindingsStore.listScreenshots(): ordered NNN-<label>.png frames with de-slugged labels — the replay's raw material. - Session: post-verdict #ensureReplay generates the clip and records its path in findings.evidence; best-effort + abort-raced (fail-soft, never blocks teardown), mirroring the summary seam. - workspace: SessionPaths.replayMp4; errors: ReplayError. - docs(workspace): document what v1 ships (burned-in captions). Co-Authored-By: Claude <noreply@anthropic.com>
- replay.ts: ffmpegOnPath() probes the binary (absolute path or PATH scan, no subprocess); createReplayStep checks it before stitching — absent → skip with a note + loud agent.log line, never spawns/crashes. - ReplayStep now returns a ReplayOutcome (rendered | skipped+note?) so the session can tell "no frames" from "ffmpeg missing". - session.ts: #ensureReplay records a skipped note as a `replay video` step in findings (terminal status, summary preserved); evidence only on a real render. - session-builder: wire logAgent into the replay step's loud sink. Co-Authored-By: Claude <noreply@anthropic.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 6 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (11)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
1 participant
Summary
replay.ts: purebuildFfmpegArgs+renderReplayover exec seam;createReplayStepbinds real spawn + resolved caption font; frames letterboxed + step labels burned inffmpegOnPath()probes before stitching — absent → skip with note + loudagent.logline, never spawns/crashesFindingsStore.listScreenshots(): orderedNNN-<label>.pngframes; session wires replay post-verdict (fail-soft, abort-raced)bun test(355 pass, 0 fail)