[FLO-13.5] Prove the static publication workflow with released providers #32

Parent: #13
Depends on: #28, #30, #31, and the real multi-provider foundation from #3
Provider evidence: renderflow#366, renderflow#412, renderflow#413, optiflow#65
Coordinates with consumer workflow: #10

Outcome

Prove one clean-room static-publication workflow through independently built or immutable Renderflow and Optiflow artifacts:

immutable synthetic source → Renderflow artifacts → Optiflow inspection/opportunity evidence → validation → aggregate ship-readiness evidence

This fixture supplies reusable orchestration proof to #10; it does not implement the complete comic-publication epic.

Dependency boundary

Use the smallest accepted immutable provider fixture subset. Full completion of every provider corpus is not required if #412/#413 and #65 publish the exact fixture artifacts and contracts needed by this scenario. Do not copy provider source or raw corpora into Flow.

Scope

• Pin exact provider artifact, contract, and fixture identities.
• Plan and execute at least one shared-intermediate multi-provider graph.
• Validate actual artifacts, digests, relationships, provenance, and provider evidence.
• Exercise one valid workflow plus capability-unavailable, corrupt-artifact, insufficient-validation, and provider-version-mismatch cases.
• Interrupt after a completed provider step and prove deterministic resume.
• Prove source or configuration changes invalidate only the affected subgraph where the accepted model permits it.
• Emit structured aggregate readiness without claiming approval or publication.

Acceptance criteria

• The workflow runs from immutable provider artifacts without sibling source imports.
• Renderflow and Optiflow remain independently executable.
• Provider exit or file existence alone cannot satisfy a step.
• Interruption and resume reuse accepted work without duplication.
• Negative cases produce typed, actionable, redacted explanations.
• No private comic content, network service, paid provider, upload, sale, deployment, or publication is required.
• Expected manifests and normalized evidence are reviewable and budgeted for the appropriate CI tier.

Non-goals

• Completing [Publication] Orchestrate exhaustive comic finalization and multilingual release workflows #10 or Renderflow's exhaustive roadmap.
• Owning Renderflow composition or Optiflow inspection logic.
• Publishing a real product.