Files
ethanfel-ComfyUI-LoRA-Optim…/js
EthanfelandClaude Opus 4.6 ac7010390c feat: AutoTuner ↔ Optimizer bridge with opposing switches
Single model line workflow: AutoTuner → Optimizer. Only one node
merges at a time — the other is passthrough. A JS bridge syncs
the two switches as opposites when tuner_data is connected.

LoRAOptimizer:
- Add settings_source (manual/from_autotuner) and tuner_data inputs
- New execute_node entry point: from_autotuner = passthrough with
  widget sync via UI data, manual = normal merge
- Subclass safety: LoRAOptimizerSimple and WanVideoLoRAOptimizer
  explicitly set FUNCTION="optimize_merge" to bypass bridge

LoRAAutoTuner:
- Add output_mode (merge/tuning_only): tuning_only skips final
  merge and returns base model unchanged while still outputting
  scored tuner_data for downstream use
- Fix pre-existing bug: two error paths returning 5-element tuples
  instead of required 6

JS (new lora_optimizer_bridge.js):
- onExecuted: sync Optimizer widgets from applied_settings
- Opposing switch sync with recursion guard:
  from_autotuner ↔ merge, manual ↔ tuning_only

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-07 02:59:33 +01:00
..