- 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
Root cause of the persistent missing Shot/Context combo on task segments 2+:
the 5e53555 rebuild ran before the rebase that brought the normalization
source in, so the shipped bundle still contained the pre-fix raw
format === 'MiniMax' gates (verified: zero 'Moxie Multimedia' literals in the
5e53555 chunks). The fix never reached users in that build.
- dist/release rebuilt from current source: normalization present, no raw
MiniMax gates in the editor chunk, marker 2026-09-28.1, chunk refs intact
- speakerReferenceTooltip no longer leaks the internal model name (en+zh)
- vitest 566/567 (same pre-existing URL.revokeObjectURL env failure)
- 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)
The dist/release bundle was last committed at repo init, so none of the
frontend changes since then were being served. The old bundle still
compared the raw format widget value against 'MiniMax', while workflows
now save the 'Moxie Multimedia' display label - which hid every
MiniMax-gated editor feature: the Shot/Context continuity combo, the
reference image size combo, the audio lock toggle, and MiniMax prompt
placeholders. Rebuilt with bun run build:release; bundle now contains
normalizeFormatValue at the widget read point and the T2V-to-R2V task
type resolver. vitest 566/567 (one pre-existing URL.revokeObjectURL env
failure on HEAD).