[Experience] Run supported Flow profiles on local files from a clean install

[szmyty]

Suite roadmap: #11
Depends on: #53, #32, and #33
Coordinates with: #34 and the independently released provider contracts in #50, #51, and #52

Outcome

A clean-install user can point the supported flow CLI at ordinary local files or a declared ordered collection, discover a suitable released capability, review a concrete plan, and run a supported profile with clear output and recovery instructions. The first experience must work without editing provider manifests or importing sibling source worktrees.

Scope

• Define a small versioned local-input/profile contract for a file, bounded directory, and explicit ordered collection. State exactly which types and profiles the first release actually handles; unsupported inputs get actionable diagnostics.
• Make doctor, inspect, plan, run, status, and resume work together with explicit long-form flags, structured output, documented output locations, and stable exit behavior from [FLO-3.7] Ship the supported Flow CLI and close the vertical slice #53. Provide a short copyable walkthrough for read-only Optiflow inspection, Renderflow publication, and a released Aniflow temporal route.
• Detect type, format, relevant metadata, available provider capabilities and constraints without silently choosing a destructive operation or treating extension/MIME as proof of content. Preview expected effects, resource limits, provider/version locks, output tree, and approval requirements before execution.
• Preserve root confinement, source immutability by default, bounded traversal, symlink/unsupported-format refusal, partial/unavailable state, cancellation, and durable resume semantics from the existing Flow contracts.
• Keep publication, media transformation, and any Optiflow mutation explicitly requested and authorized under their own effects; no default write to a source path, implicit download, provider installation, network service, or GPU requirement.

Acceptance criteria

• A fresh user can follow one tested local-file invocation per available first-release provider route, with no repository worktree or hand-edited adapter registration.
• A small mixed-input/unsupported-input fixture produces deterministic route choices or typed refusal, with no misleading "success" on skipped work.
• A bounded directory/collection fixture proves stable order, identity, output separation, and no path escape; ordinary single-file use stays simple.
• Inspection and planning are non-mutating; effectful execution shows its exact approval boundary and leaves recoverable evidence.
• Clean-room synthetic smoke and docs reflect the capabilities actually published, including offline/missing-provider behavior.

Non-goals

Arbitrary media format support, invisible optimization, automatic publication, model download, or replacing domain logic in the holons.