Skip to content

Use Config.segments_all for CLI narration and scene-spec --all - #125

Merged
cursor[bot] merged 2 commits into
mainfrom
cursor/cli-segments-all-2ccd
Sep 7, 2026
Merged

cursor[bot] merged 2 commits into
mainfrom
cursor/cli-segments-all-2ccd

Conversation

@jmjava

@jmjava jmjava commented Sep 7, 2026 •

Copy link
Copy Markdown
Owner

narration-generate --all and scene-spec-generate --all read raw["segments"]["all"] or []. Missing all with a populated segments.default raised segments.all is empty even though Config.segments_all (TTS, timestamps, lint, pipeline) falls back to default.

This PR uses cfg.segments_all. An explicit empty all: [] still errors (same as Config after #124).

Milestone: milestones/cli-segments-all.md. No clock / compile change.

Local gates

  • ruff check src/ tests/ — pass
  • pytest tests/ — 717 passed, 1 skipped
  • docgen benchmark — meets src/docgen/benchmark_data/baseline.json (no --update-baseline)
Open in Web Open in Cursor 

cursoragent and others added 2 commits September 7, 2026 22:38
narration-generate --all and scene-spec-generate --all read raw
segments.all and treated a missing key as empty, so a bundle that
only sets segments.default raised even though TTS/lint/pipeline use
Config.segments_all (default fallback). Empty all: [] still errors.

Co-authored-by: jmjava <jmjava@gmail.com>
ruff, pytest (717 passed, 1 skipped), and docgen benchmark all green.

Co-authored-by: jmjava <jmjava@gmail.com>
@jmjava
jmjava marked this pull request as ready for review September 7, 2026 22:39
@cursor
cursor Bot merged commit a2f53db into main Sep 7, 2026
6 checks passed
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