Commit Graph

2 Commits

Author SHA1 Message Date
Z User
30cbaeb8f6 Switch plan.json output to the native H3 ref2va prompt format
Each scene prompt is now the six native reference sections —
subject_definitions / summary [reference generation] / retention_analysis /
detailed_description (1-2 style sentences then [Shot 1]) /
overall_soundscape / non_diegetic_music — one line per element, headers on
their own line. The full head-to-toe look (nude-not-bare) lives in
subject_definitions and is restated compressed in the [Shot 1] body; both
cast members are defined per scene against the wired subject references.
verify_plan_rules.py auto-detects the format per shot and validates the
ref2va contract (canonical order, directive, definitions, retention,
style prefix, thin floor), so legacy t2va plans keep passing. Both system
prompts, the assembler prompt and SKILL.md carry the new skeleton,
worked examples and self-checks; example_output/README.md marks the old
run as the t2va craft reference.
2026-10-30 19:28:36 +00:00
Z User
bbce37f2a5 Add example_output: full 12-scene agent workflow reference run
PROMPT A outline + user-approved guide, 12 PROMPT B scene fragments
composed one at a time with chained _handoff validation, and the
merged plan.json (PLAN OK, 2674 delivered frames = 111.42s).
Also demonstrates 10+ scene scale on the same code path.
2026-10-29 21:05:27 +00:00