[Artifact Forest 9/9] Prove the multi-family artifact forest and hand it to Flow

[szmyty]

Parent: #421
Depends on: #422, #423, #424, #425, #426, #427, #428, #429
Coordinates with: egohygiene/flow#11

Outcome

Prove the complete concept with one redistribution-safe integration fixture and publish a stable downstream contract that Flow can orchestrate.

Fixture scenarios

Screenplay source

Fountain
 ├── FDX
 ├── FadeIn
 ├── OSF
 ├── screenplay JSON
 ├── formatted PDF
 └── analysis report

The original Fountain is referenced, not regenerated.

PDF recovery source

PDF
 ↓
extracted/recovered screenplay
 ├── Fountain
 ├── FDX
 ├── FadeIn
 └── OSF

PDF is not regenerated unless explicitly requested.

Media source

video/audio
 ├── embedded timed text where present
 └── local speech transcript
       ├── SRT
       ├── WebVTT
       ├── JSON
       └── text

Deliverables

• Versioned artifact-forest request/plan/run/evidence contract.
• Exact target membership and output tree.
• Stable artifact IDs, hashes, source lineage, provider/toolchain fingerprint, loss/review state.
• One-command dry-run and execution fixture.
• Negative fixtures for cycles, duplicate targets, missing providers, malformed source, recovery ambiguity, and transcription unavailability.
• Generated capability matrix/documentation.
• Downstream Flow handoff identifying what Flow may orchestrate without importing Renderflow implementation details.
• Reconcile [EPIC][Artifact Forest] Build truthful screenplay, transcript, and exhaustive derivative workflows #421, 🧬 Expand format coverage, validate conversion paths, and maximize deterministic artifact extraction #338 capability truth, README/docs, and ROADMAP.md.

Acceptance criteria

• The integration forest executes without cycles or duplicate targets.
• Every artifact explains why it exists, how it was produced, and what information loss/review state applies.
• Source-format suppression works across screenplay and PDF recovery scenarios.
• Provider absence produces a partial truthful forest rather than false success.
• Flow can consume the released contract/artifact evidence without source dependency.
• Stable/MSRV, contracts, fixtures, docs, package and adversarial validations pass.

Non-goals

Flow implementation itself, consumer publication, or creative approval.