沐阳 H3 · 导演台计划（内部）

Some nodes do work; some nodes are plumbing that makes other nodes' work visible. 沐阳 H3 · 导演台计划（内部） (H3DirectorPlanValue) is the second kind, and it's the piece that makes the Director's progress panel function at all. The source comments call it the one place in the whole flow that simultaneously holds the complete segment plan and the panel's ID - every path into the Director, whether manual storyboard, smart script split, or action transfer, converges here.

What it does is deceptively simple: it takes a plan_json, optionally stamps a progress_owner onto it, and returns it. But that stamp is the point. The progress_owner is the ID of the Director's panel instance, and the node uses it to broadcast a "plan ready" event to the frontend (_send_plan_ready), which is what tells the panel UI which run the plan belongs to. Without this handshake, the Director's web panel wouldn't know what to show. It's also why the output is a modified plan JSON rather than a passthrough - the owner ID rides along inside the plan so downstream nodes know where their progress reports should go.

Inputs and outputs

• plan_json - the segment plan. If a progress_owner is supplied, the node validates it's a JSON object and merges the owner in; invalid JSON raises a clear error rather than silently passing garbage through.
• progress_owner - the panel/run ID. Empty string means "no owner, just pass the plan through."

Outputs: plan_json (STRING) and fps (FLOAT) - the fps is a fixed 24.0, consistent with the pack's 24fps timeline.

Install and why you'll never touch it

Pack install is the usual: ComfyUI Manager search "ComfyUI-MiniMaxH3-Myang", or git clone https://github.com/civilcoco/ComfyUI-MiniMaxH3-Myang into custom_nodes, restart.

Realistically you won't wire this by hand - it's internal, it sits inside the Director's expanded graph, and the README's "nodes marked 内部 ... normally do not need manual wiring" applies squarely. File it under "good to know exists when debugging." If the Director panel shows no plan and the console is quiet, this is the node that would be doing the handshake. And the pack's standing caveat applies regardless: H3's local weights are territory-restricted by community license (US/EU/UK/South Korea excluded).