kami
ff6a512630
Working tree (including .git) was lost to an rm. Rebuilt by replaying Write/Edit/ Read/attachment events from 25 Claude sessions and 22 successful codex apply_patch blocks into one timestamp-ordered timeline. Verified against ground truth recorded in the transcripts: wc -l on 10 files and ls -l on 5 files at 2026-07-18T13:13:44Z both match exactly; 18 files are byte-identical to their newest ~/.claude/file-history blob. See HANDOFF.md for sources, gaps, and how to rebuild .venv. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
24 lines
867 B
Markdown
24 lines
867 B
Markdown
# Repository guidance
|
|
|
|
## Video analysis
|
|
|
|
When diagnosing render motion, transitions, timing, or visual artifacts, use
|
|
`scripts/analyze_video_frames.sh` instead of manually seeking through the video.
|
|
|
|
```bash
|
|
scripts/analyze_video_frames.sh VIDEO [OUTPUT_DIR] \
|
|
--window START:DURATION [--window START:DURATION ...]
|
|
```
|
|
|
|
The script creates:
|
|
|
|
- timestamped overview contact sheets sampled at 2 fps;
|
|
- scene-change frames and a `scene-timestamps.txt` index;
|
|
- optional dense 10-fps contact sheets for specified transition windows.
|
|
|
|
Inspect the overview first, then request dense windows around transitions or artifacts. Sampling and
|
|
scene sensitivity can be adjusted with `OVERVIEW_FPS`, `WINDOW_FPS`, and `SCENE_THRESHOLD`.
|
|
|
|
The generated files are analysis artifacts and belong in `/tmp` or another requested output directory;
|
|
do not commit them to the repository.
|