MiniMax H3 Selective Repair Stage / 修复暂存 (Advanced)

You regenerated a segment with the bound inputs from SelectiveRepairBind. Now you have a candidate file, and you're pretty sure it's the right length and the right frames and the right timeline position. "Pretty sure" is exactly the failure mode this chain was built against. The Stage node is the verification checkpoint: it takes your candidate and checks it against the bound frame/sample/timeline contract and the base-manifest revision it was bound to, and only then hands back a staged_repair handle. It remains preview-only - it writes no repair overlay, commits nothing, and touches no accepted media.

The mechanism is contract verification, not quality judgment. It verifies that the candidate actually is what the binding said it should be: the right number of frames, the right samples, the right spot in the timeline, consistent with the base manifest revision. If the candidate is 120 frames when the bind promised 124, or the audio is a sample-rate mismatch, it fails - and it fails before anything has been accepted, which is the whole point. It can't tell you the repair looks good; that's the human review step that comes after.

Inputs

• repair_execution - the H3_T8_REPAIR_EXECUTION handle from SelectiveRepairBind. Required.
• candidate_json_path - a path to the generated candidate's JSON (the repair metadata your generation step produced alongside the media).

Outputs: staged_repair (the H3_T8_REPAIR_STAGED handle for SelectiveRepairAccept), candidate_video_path, and report_json.

Installing and the flow

In the T8mars MiniMax H3 Audio T8 pack:

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/comfyui-minimax-h3-audio-T8

or ComfyUI Manager → "MiniMax H3 Audio T8", restart. No pip deps.

The take

The chain discipline, again: Bind creates the contract, your sampler produces the candidate, Stage verifies the candidate against the contract, Accept commits with a human flag, Compose renders. This node is the tripwire that makes "I regenerated the wrong segment" cost you a re-run instead of a corrupted delivery. If you're tempted to skip it and feed candidates straight to Accept, you're bypassing the exact step that keeps the manifest honest - and the Accept node is built to be fed by this one, not by raw files. Treat a Stage failure as a gift: it means the problem is visible now, in preview, instead of baked into a 200-frame MP4 you already shipped.