Add Missing You x Seedance 2.0 and Take Me Stars MV pipelines

[virtari]

Summary

• Missing You MV — Full Seedance 2.0 pipeline: character reference generation (FLUX Pro), 36 scene generation with numbered filenames, iterative scene fixes, and assembly to chef8080_missing_you_FULLMV_720p.mp4
• Take Me Where The Stars Go MV — colorbalance fix applied, final 70.7 MB assembly
• Scene improvements — Camera movement added to all scenes (push-in, dolly, tracking); two rounds of iterative fixes; ending changed to reunion-on-bridge (scene 036)
• Memory / learnings — Production notes saved: Seedance moving camera, Character Bible, Anchor-and-Extend, tempostrategia, professional lighting terminology, bookend structure

New files

File	Purpose
missing_you_seedance_mv/mv_generate_chars.py	FLUX Pro character ref image generation
missing_you_seedance_mv/mv_generate_scenes.py	36-scene Seedance 2.0 generation pipeline
missing_you_seedance_mv/mv_assemble.py	FFmpeg assembly — concat, mix audio, fade

Test plan

• python mv_generate_chars.py generates 4 character reference images
• python mv_generate_scenes.py --anchor-only generates anchor clips (001–003)
• python mv_generate_scenes.py generates remaining 33 production scenes
• python mv_assemble.py outputs chef8080_missing_you_FULLMV_720p.mp4

🤖 Generated with Claude Code

[calesthio]

Integrating Seedance 2.0 is a great idea. It is currently one of the strongest video generation models, so having a real OpenMontage path for it would be valuable.

That said, this PR does not feel mergeable in its current form because it is adding project-specific production scripts rather than integrating Seedance into the platform architecture.

Main issues:

• The scripts hardcode author-specific local paths, local downloads, and output locations (C:\Users\ari_v\..., specific MP3 inputs, local ffmpeg path), so they are not portable or runnable for other contributors.
• The implementation bypasses the repo’s pipeline-first design. OpenMontage expects new production capability to flow through pipeline manifests, stage skills, tool registry discovery, and the existing project/artifact conventions rather than direct one-off fal_client scripts in the repo root.
• Several files look like personal production workspace state or cached references rather than reusable product code (take_me_stars_mv/refs/*, uploaded URL caches, project-specific assets/scripts).
• There is no tool-level integration, no pipeline integration, and no test coverage showing how this becomes a supported capability in OpenMontage.

I think the underlying direction is good, but I would recommend re-scoping this before merge. A stronger version of this contribution would be one of:

• a proper Seedance provider/tool integration discoverable through the tool registry,
• a pipeline/stage integration that uses the existing OpenMontage workflow, or
• a clearly isolated example/template under an examples or experiments area, with all machine-specific paths removed.

So: strong idea, but this needs to be productized and aligned with the repo architecture before it makes sense to review deeply for merge.