[Adapter] Orchestrate released Optiflow exact-dedup transactions with explicit authority

[szmyty]

Suite roadmap: #11
Depends on: #50 and egohygiene/optiflow#93
Follows the first read-only Flow release path; does not block #53/#54.

Outcome

Add separately authorized Flow orchestration of the exact-duplicate v0.2.0 Optiflow quarantine, status/resume/restore, and retained-copy finalization capabilities after their immutable release is qualified. The initial #50 read-only adapter can close against v0.1.1 without claiming mutation.

Acceptance criteria

• Pin the independently verified v0.2 asset digest, structured CLI/schema versions, supported OS/filesystem matrix, release qualification, and capability identities; reject earlier read-only releases for mutation.
• Map Flow effect class, plan/approval fingerprints, root/subtree and resource bounds, volume identity, and explicit finalization authority into Optiflow's own versioned transaction contract without forging historical records.
• Preserve provider journal/evidence references and distinguish in-flight, quarantined, restored, irreversible-finalized, ambiguous, and refused states in aggregate Flow evidence.
• Fail closed on stale identity, disconnect/remount, insufficient reserves, unsupported host, approval mismatch, and version skew. No implicit mutation from an inspect/plan request.
• Prove synthetic same/cross-volume success, refusal, interruption, recovery, and logical-versus-observed-physical accounting through clean-installed artifacts; no private user media.
• Publish a new Flow compatibility manifest and operator runbook. Existing Flow/provider releases and original read-only capabilities remain immutable.

Non-goals

Direct deletion, PNG optimization, automatic finalization, or applying plans to real user media as a test.