- frontend/src + messages restored byte-identical to upstream v1.3.3:
format normalization shims, isMoxieEditorFormat gates, bundle marker,
tooltip reword, and their tests all removed; editor bundle rebuilt from
that pristine source so the editor behaves exactly like upstream
- format combo shows 'MiniMax' again (options=[MiniMax]); legacy queued
'Moxie Multimedia' values still normalized to MiniMax at execution
- T2V resolves natively again: t2v stays t2v in h3_task_type,
_multitrack_task_type and getMultiTrackTaskType; generation-mode t2v
mapping and the zero-media cloud fallback removed (upstream behavior);
Python tests and stub scripts updated accordingly
- editor delivery fix: core lets WEB_DIRECTORY overwrite the pack's
EXTENSION_WEB_DIRS entry, so the /extensions listing never contained
dist/release and a fresh browser never imported the editor (it only
ever appeared from stale browser cache). web/js/editor-loader.js now
imports the editor entry from the pack's own static mount, which
serves index.js with no-cache (chunks stay cacheable); the
/extensions/<pack>/index.js route was removed as a 404 trap
- shipped Moxie*.json templates carry format value MiniMax
Verified: frontend diff vs upstream = 0; bundle string checks + chunk
refs; vitest 565/566 (same pre-existing jsdom URL.revokeObjectURL env
failure); py_compile; test_t2v_r2v_and_loader.py ALL PASS;
test_rtx_upscale_integration.py ALL PASS
MoxieCombine now exposes exactly images / audio / fps - the leftover
VIDEO and FILENAME_PREFIX outputs are gone, so the output file name is
chosen on easy saveVideo itself. The base easy multitrackProjectVideoCombine
keeps its VIDEO and FILENAME_PREFIX outputs for legacy workflows.
The shipped Moxie-consolidated template is rewired accordingly: fps/images
links follow the new slot indices (2/0), the filename_prefix link is replaced
by the same project-scoped literal the removed output produced, and the
TEMPLATE's save location is unchanged.
pytest: new schema/execute/blocker coverage for MoxieCombine via a
_load_moxie_combine helper; base-combine assertions untouched.
- the format combo on MultiTrack Editor and MultiTrack Project now
shows 'Moxie Multimedia' (FORMAT_DISPLAY_LABEL); every queued value
is normalized back to the internal 'MiniMax' value at both execute
entries and check_lazy_status, so tracks_info, conditioning caches,
saved manifests and frontend lookups are unchanged
- frontend: normalizeFormatValue() maps the display label back at the
format-widget read point so MiniMax-specific editor features keep
working; shipped templates carry the new label
- removed the per-run 'Output upscale' console line; the restore now
happens silently (one-shot fallback diagnostics kept)
Note: workflows saved before this change need the format re-picked
once, since 'MiniMax' is no longer a combo option.
The Moxie model set is MiniMax H3-only, so no other model choices are
exposed in the editor:
- Moxie Multimedia Loader: removed the clip_type dropdown (which listed
every CLIPType recipe in ComfyUI). The H3 Qwen3-VL text encoder is now
always loaded with CLIPType.MINIMAX; older ComfyUI builds raise a
clear error instead of silently loading the wrong encoder.
- Moxie Multimedia Loader: outputs are now exactly model, clip,
video_vae, audio_vae - the legacy FAST_MODEL_LOADER (model_loader)
bundle output is removed. The model output keeps the attention
backend and LoRA applied.
- Moxie MultiTrack Project: takes model, clip, video_vae and audio_vae
as required direct inputs instead of a bundled model_loader; the
fallback plumbing is removed while EasyMultiTrackProject keeps its
model_loader input for non-Moxie workflows.
- Moxie Preview Override: dropped the model_loader pass-through slots
and patches the model input directly.
- Moxie-consolidated.json reference workflow updated to the new slots.
- Added tests/test_moxie_nodes.py covering the schema contracts, the
attention -> LoRA -> output chain, the MINIMAX lock and the project
loader synthesis.