The paste payload builds the full task timeline, but easy multiTrackTaskOutput
emits ONE task segment per pass, selected by its task_index int (default 0 =
first clip only). A single-segment workflow therefore renders only the first
scene no matter how many prompts the override carries. SKILL.md step 5A and the
builder's delivery print now say so, point to the pack's
MinimaxH3_ForLoop_MultiShot.json example (TASK_COUNT -> loop total, loop index
-> task_index, mergeVideosFromPaths after the loop) and offer the manual
task_index 0..N-1 queue fallback.
The multitrack editor node consumes its prompt_override input as a
minimax_prompt_override JSON payload (type/version/prompts/duration/
generation_type/continuity_mode/system_prompt/track locks). Any other
JSON pasted there falls back to the '|'-separated text parser and
renders ONE clip over the whole timeline - the reported single-clip
failure - so the paste payload is now the primary deliverable.
- verify_track_rules.py: build_prompt_override() assembles the payload
from validated fragments (one prompt per row, <Picture N>/<Audio N>/
<Video N> tokens by inventory position, duration 2-15s, per-segment
generation/continuity, tail reuse like the runtime); validate_prompt_
override() checks type, field set, prompt count, duration/mode
agreement with the outline, exact reference-token sets, pipe-free
prompts, and track locks; new 'override' sub-command; suite 25->34.
- build_track_plan.py: merge now writes prompt_override.json (one line,
ASCII) next to plan.json and validates it before reporting.
- references/track-schema.md: full prompt_override section with the
single-clip fallback warning and slot-position convention.
- SKILL.md: delivery restructured (5A paste default, 5B patch script
alternative), smoke test extended, read-cap sizes refreshed.
- examples/prompt_override.json: shipped example payload (runtime-checked
against the cloned node pack parser: 3 task segments, 720 frames).
Portable self-contained skill (%USERPROFILE%\.agent\skills\easy-media-track-gate\):
- references/track-schema.md: full English translation of the node pack's Chinese
multitrack-schema.md (resolution DynamicCombo rules, time semantics, task segment
content, context/context_drift joins, audio locks, shared media, project params,
patch plan shape); field names cross-checked against patch_workflow.py source.
- verify_track_rules.py (66 KB, stdlib only): mirrors every check the node pack's
patch_workflow.py performs at apply time (ids, sorting, overlap, frames, source_type
field matching, <=9 images, continuity enums, one locked audio + one locked video,
locked-media task coverage, shared_reference rules, resolution tokens, project
fields) and adds the gates upstream leaves to discipline: outline pins (id/frames/
modes/image set diffed per fragment AND at the merge), verbatim media contract
(file_path character-for-character vs media_inventory, closest-match hint on
rewrite), context prompt rules (self-contained in all modes, keep-then-change
opener for joins, end-in-motion tail when another join follows), drift all-or-
nothing + consecutive 10s split unless lengths_user_pinned. Subcommands: outline/
segment/trackdata/plan/suite; no-outline runs stay schema-only. Embedded suite
25 cases, prints ~0.7 KB (far under Cline's 8k cap).
- build_track_plan.py: merge re-walks every fragment against the guide, assembles
TRACK_DATA (task track from fragments; locked master-audio/reference-video tracks
built from the outline, never retyped), writes plan.json + track_data.json with
stable UUIDv5 ids; --check mode re-validates.
- examples/: worked 3-segment rooftop example (outline, 3 fragments, plan.json,
track_data.json) - merge is byte-deterministic and the generated plan dry-run-
applies to the bundled v1.3.0 blank template with graph_preserved: true.
- SKILL.md: five-move procedure with Cline cap workarounds (never read the 66 KB
validator, @@CONTINUE@@ split, never read back generated plans), Step 0 media
paths (upload only on explicit request; never invent a path), approval pause,
prompt craft rules, delivery through the node pack's own patch_workflow.py
(dry-run -> --write to a NEW file -> inspect); queueing stays the node pack's
own flow on explicit user request.