Skip to content

feat(validate): story_end check, scene-spec av_sync anchors, layout budgets - #60

Merged
cursor[bot] merged 1 commit into
mainfrom
cursor/story-end-av-sync-layout-afb7
Aug 1, 2026
Merged

feat(validate): story_end check, scene-spec av_sync anchors, layout budgets#60
cursor[bot] merged 1 commit into
mainfrom
cursor/story-end-av-sync-layout-afb7

Conversation

@jmjava

@jmjava jmjava commented Aug 1, 2026

Copy link
Copy Markdown
Owner

Summary

Continues the beat-sync checklist after #58 / #56:

# Change
5 story_end validation — last paced scene-spec reveal vs audio/transcript end; hard-fail in --pre-push when idle exceeds both max_early_sec (40s) and max_early_ratio (0.45)
6 av_sync prefers paced scene-spec labels as OCR anchors (falls back to long transcript words only when no specs)
9 Scene-spec LLM prompt includes computed layout_stack_budget numbers and horizontal safe width

Rebased onto main after #61.

Config

validation:
  story_end:
    enabled: true
    max_early_sec: 40.0
    max_early_ratio: 0.45
  av_sync:
    prefer_scene_spec_labels: true

Test plan

  • pytest tests/
  • ruff check src/ tests/
  • Unit: last_paced_reveal_time / pace:none ignored
  • Unit: story_end early-fail + hard pre-push
  • Unit: av_sync anchors from scene-spec labels (not unrelated long words)
  • Unit: user message includes computed layout budgets
Open in Web Open in Cursor 

…ut budgets

Catch boards that race then freeze (last paced reveal vs audio end), prefer
scene-spec labels for OCR av_sync anchors, and feed real layout_stack_budget
numbers into the scene-spec LLM prompt.

Co-authored-by: John Menke <jmjava@gmail.com>
@cursor
cursor Bot force-pushed the cursor/story-end-av-sync-layout-afb7 branch from 2db1a62 to a686653 Compare August 1, 2026 12:12
@cursor
cursor Bot marked this pull request as ready for review August 1, 2026 12:43
@cursor
cursor Bot merged commit ac98b5b into main Aug 1, 2026
5 checks passed
@cursor
cursor Bot deleted the cursor/story-end-av-sync-layout-afb7 branch August 1, 2026 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants