v0.4.0 — Claude scene plan guides asset selection

• Feed the Claude scene plan into asset selection: --scene-plan loads a saved scene-plan.json, and each beat's ranking uses its scene's search_query terms plus a bonus for assets whose role matches the planned visual_role.
• Reject scene plans that do not match the script beat for beat; record the plan scene behind each beat and the planner model in timeline.json.
• Add synthetic placeholder assets and examples/claude-demo/compare.py; on the live demo plan, 4 of 8 beats change asset (selection-comparison.md).

Reproduce the comparison locally (no API call):

python examples/claude-demo/compare.py

NarrativeCut v0.3.0

• Add optional Claude scene planning (--plan-with-claude, narrativecut[claude]): JSON-schema constrained output, local validation of beat coverage and order, deterministic timing, and scene-plan.json output.
• Add offline tests with a fake client, an opt-in live API test, and a demo script with unedited live output in examples/claude-demo/.
• Add a Claude scene planning demo section to the project website, built from the unedited live output.
• Align package version metadata (pyproject.toml, narrativecut.__version__) at 0.3.0.

Demo output: examples/claude-demo/output/scene-plan.json

NarrativeCut v0.2.1

Changes

• Fix CLI and validation exit codes, including non-zero exit on QC failure.
• Add FFmpeg/ffprobe preflight checks and clear media failure reporting.
• Support bidirectional duration tolerance.
• Add QC for frame count, FPS, resolution, audio, and loudness.
• Add synthetic end-to-end render/QC integration test.
• Expand CI coverage for FFmpeg and the optional YAML path.

Known limitation

• SVG assets must be rasterized before rendering.

NarrativeCut v0.2.0

NarrativeCut v0.2.0 adds versioned JSON project validation and optional YAML input via the PyYAML extra, while preserving legacy JSON briefs.

• Generic asset manifest validation checks required source, rights, and subject metadata, adjacent JSON sidecars, optional path references, duplicate or conflicting IDs, and duplicate file content.
• Synthetic tests cover valid and invalid manifests; CI passes.
• No required runtime dependencies were added.
• Backward compatibility: legacy JSON briefs and existing timeline output remain supported.

Known limitations: YAML input needs the optional PyYAML extra; rights metadata is user-supplied and is not a legal warranty; validation checks sidecars and file-level references but does not decode media contents.

v0.1.0

Initial OSS baseline.

• Deterministic timeline generation
• SRT generation
• License report generation
• CLI
• 9-test suite
• CI
• Known limitations: early baseline; platform-specific media/tooling behavior may vary.