MiniMax H3 Hybrid Artifact Maintenance / 混合补丁安全维护 (Advanced)

The maintenance half of the hybrid-artifact system - for when the content-addressed patches from Hybrid Artifact Builder pile up, go stale, or get interrupted mid-write. By default it does the safe thing: inspect_only, no side effects. Every other action is gated behind explicit confirmation and a positive, single-use operation epoch, and nothing is ever permanently deleted - files move inside models/h3_hybrid_artifacts/_recycle, a recoverable quarantine, instead.

The safety model is the interesting part. action defaults to inspect_only; the mutation actions (quarantine a verified artifact pair or stale build residue, restore a quarantined pair, recover an interrupted transaction) all require confirm_action = true plus a positive operation_epoch. The epoch is your transaction key: use a new positive value for each quarantine, then reuse that exact value to restore or recover that same transaction. Mismatched epochs refuse. It's a deliberate, auditable, human-in-the-loop design - the node would rather be annoying than destructive.

The stale_after_minutes gate (60) only applies to stale build-residue cleanup and stale maintenance-lock recovery, and it has a nice guard: a lock whose owner is still running is refused. So if another process is mid-build, you can't accidentally sweep its files out from under it. The other boundary, stated plainly in the description: it never scans or deletes diffusion checkpoints. This node's universe is the hybrid artifacts directory and nothing else.

Inputs: hybrid_plan (to identify which exact content-addressed artifact you're acting on), action, confirm_action, operation_epoch, stale_after_minutes. Outputs: mutation_performed (BOOLEAN), artifact_path, and report_json. It's an output node, so it terminates the branch and hands you the audit trail.

When you'd use this: you built a bunch of hybrid artifacts, some are stale from experiments you abandoned, a build got interrupted mid-write and left residue, or you quarantined something and now want it back. The flow is always the same - inspect first, read the report, then act with a fresh epoch, then reuse that epoch to restore if you change your mind. There is no "delete forever" path, which is a design choice that will either feel like a feature or a mild annoyance depending on how much disk you're cleaning.

The honest note: this is research-infra housekeeping for the hybrid-model corner of the pack. If you're not building hybrid artifacts, it's a no-op for your workflow. But if you are, this is how you keep the content-addressed patch store from becoming a landfill.

Install: ComfyUI Manager → "MiniMax H3 Audio T8", or:

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

Restart after. No forced pip deps, no downloads - everything happens inside ComfyUI/models/h3_hybrid_artifacts and its _recycle subdirectory.