[Adapter] Orchestrate the released Aniflow music-video profile

[szmyty]

Suite roadmap: #11
Depends on: #51 and egohygiene/aniflow#40
Does not block the first Flow release (#54).

Outcome

Expose the independently released Aniflow selective-repair, resumable-upscale, and verified music-video delivery profile as an explicit Flow workflow, keeping Aniflow's frame, timing, provider, and validation semantics authoritative.

Acceptance criteria

• Pin the exact Aniflow release/digest, profile and structured contract versions, optional repair/upscale/model/toolchain capabilities, and supported platform/media subset.
• Plan selected frame ranges, source/audio streams, outputs, resource and provider needs, validation layers, and human approvals before running. Unsupported VFR/HDR/codec/hardware and missing optional providers refuse or report unavailable as declared.
• Preserve Aniflow stage/checkpoint references, source frame/time identity, selective unchanged-frame evidence, audio passthrough/timing, lossless master versus lossy delivery distinctions, and exact model/tool identities in Flow's durable aggregate state.
• Prove clean-installed synthetic positive, partial/interrupted, stale-provider, missing-model, insufficient-validation, cancellation, and resume cases. Never use private song/video assets in tests.
• Publish a new Flow compatibility manifest, capability matrix, CLI walkthrough, and recovery docs without importing Aniflow source or making experimental [FLO-3.2c] Verify locked packages and executable subjects #39 part of the default profile.

Non-goals

Reimplementing media assembly or repair in Flow, assuming every GPU works, silent downloads, public upload, or creative approval.