- 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
- TaskSegmentEditor continuity (Shot/Context) combo, ref image size combo and
MiniMax prompt placeholder now use isMoxieEditorFormat: they stay available
even when the format widget value is missing or unrecognized (the pack ships
exactly one video format)
- __init__.py now serves dist/release/index.js with Cache-Control: no-cache:
the entry file keeps a stable URL while chunk names rotate every build, so a
stale cached entry file used to request deleted chunks (404) and silently
break the editor; hashed chunks remain cacheable
- bundle marker bumped to 2026-09-28.1; release rebuilt; vitest 566/567 (same
pre-existing URL.revokeObjectURL env failure)
- normalizeFormatValue now trims and accepts missing values; new
isMoxieEditorFormat helper treats the pack's single video format as
enabled even when the format widget value is empty or unrecognized
- TaskSegmentEditor normalizes its format prop once (continuity combo,
ref image size combo, MiniMax prompt placeholders, system prompt
template matching all follow); TrackArea audio lock and the
PreviewArea continuity/ref-size gates use the same helper
- the extension logs a bundle version marker on setup
([Moxie Multimedia Suite] editor bundle 2026-09-27.2) so a stale
browser-cached build is immediately visible
- release bundle rebuilt; vitest 566/567 (one pre-existing
URL.revokeObjectURL env failure on HEAD)
- T2V selections (editor default mode, explicit [start-end,t2v] override
tags, raw t2v values) now resolve to r2v in every task-type resolver
(h3_task_type, _multitrack_task_type, frontend getMultiTrackTaskType);
h3_generation_mode maps raw t2v to reference conditioning as belt and
braces. Reference-mode with zero reference media renders text-only
locally; the cloud path falls back to its native t2va request instead
of raising. i2v/l2v/v2v/edit flows unchanged.
- MoxieMultimediaLoader now presents a single model picker: LoRA, video
VAE, audio VAE, and CLIP widgets removed and auto-selected from the
pack's models/ folders (first sorted file, loud error when missing,
LoRA applied at strength 1.0 when bundled). Outputs and load order
unchanged; saved workflows keep working (extra widget values ignored).
Verified: py_compile; scripts/test_t2v_r2v_and_loader.py 50/50;
frontend vitest 566/567 (one pre-existing env failure on HEAD);
bun run build; scripts/test_rtx_upscale_integration.py all pass.
- 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.