v1.4.3 — comfy Comfy-Compiler compatibility fix, quiet logs, tooltips

Hotfix series for the comfy "Comfy Compiler" update, plus quality-of-life cleanup. Full v1.4.0 feature set restored, so if you skipped 1.4.x over the crashes, this is the one to take.

Compatibility fix: comfy 2026-09-04 "Comfy Compiler" builds

Comfy's new model compiler + aimdo malloc-graph planner (comfy commits 804eb551, which also removed a MiniMax memory workaround in 5c23fb7b) cannot trace VDN-patched MiniMax-H3 forwards. On those builds VDN workflows failed with aimdo memory compile error or the whole process aborted mid-step.

v1.4.3 handles it automatically:

• While a VDN workflow is sampling, the node switches comfy's compiler off; the switch flips back on the moment each step ends (try/finally — cancel-safe, unload-safe, nothing persists)
• Non-VDN workflows always run with comfy's compiler fully active
• If you launch with --disable-comfy-compiler yourself, the node respects it and never touches your setting
• On comfy builds without the compiler stack, the code path never activates
• One console warning (once per session) marks when it engages

Verified against the 2026-09-04 comfy build: render, mid-run cancel, full unload, and immediate re-run all clean.

Quiet logs

• The six SDPA "kernel not used / runtime disabled" UserWarnings from the windowed-attention backend probe are gone; the one-line window SDPA backend: ... info remains
• The compile of ... failed; using eager fallback line is now debug-level (the fallback itself is unchanged and seamless)

Node polish

• Every input on both Apply VDN-H3 nodes now has a tooltip (model, checkpoint, verbose, branch_weights, retain_buffers, attention_backend on the Advanced node, fast_kernels drift note, and more)

Docs

• README (EN + ZH): new troubleshooting entry documenting the comfy compiler clash, what the node does about it, and the manual fallbacks (--disable-comfy-compiler or a pre-2026-09-04 comfy build)
• Updated example workflows

Note on 1.4.1/1.4.2

v1.4.1 briefly shipped conservative v1.3.1 defaults and a fast_kernels force-off while the crash was being traced; v1.4.2 reverted that. v1.4.3 keeps the full v1.4.0 defaults (branch_weights: auto, retain_buffers: auto, fast_kernels opt-in as before) plus the compatibility shim — downgrading behavior is no longer necessary.

Verification

• 12/12 unit tests
• Bit-identical output to v1.3.1 in default configurations (unchanged from v1.4.0; the shim only touches a comfy runtime switch)