Reconcile flow's current implementation and continuation documentation #82

Outcome

Make flow's current entry documentation and continuation instructions describe the merged kernel and read-only native adapter accurately, with clear navigation to the remaining released-provider, CLI, installation and release work.

Audit evidence

Current audit, finding AUDIT-002, inspected flow af68afa5732a04c237df5fbeee6bc5e901a5c6fd.

The README's unconditional status still asks for PR #60 / #46 / #29 closeout and names #30 next. The architecture's current boundary still excludes real adapters despite the native optiflow v0.1.1 adapter. System/capability baselines and some strategic active-step prose predate the durable kernel. The existing documentation handoff still calls merged roadmap PR #79 draft. Newer maintained roadmap notes correctly preserve their dated snapshots; retain that useful history.

Scope

• Reconcile README status, current architecture/system/capability entrypoints, root roadmap navigation and the existing continuation handoff against exact merged source and freshly queried issues/releases.
• Preserve archives, historical validation receipts, full issue scopes and original decision bodies; date or label older snapshots instead of rewriting them as current facts.
• Keep first installed candidate, stable audited suite and optional product backlog distinct.

Acceptance criteria

• Current entrypoints agree that the durable library/kernel and native read-only optiflow adapter are merged, while the supported product CLI, remaining released adapters and flow release are still separate tracked work until proven.
• Obsolete unconditional next-up instructions are replaced with one reviewable current continuation route; dated historical notes remain discoverable.
• Capability matrix entries identify source snapshots versus actual releases and retain unsupported/native-unverified states honestly.
• The maintained map's October 6 JSON/graph and October 15 provider refresh remain correctly date-bound; no current counts are fabricated and no old node/history is dropped.
• Proposed ADRs keep human-review status; merge activity alone does not accept them.
• Relative links and current-status claims are checked without changing runtime source, provider contracts, release assets or validation requirements.

Dependencies and boundary

Ready now. #62 is the separate scenario gallery and #12 is the later post-roadmap audit, so neither needs to absorb this focused repair. Use the repository's existing documentation/handoff convention; adopting a new root continuity framework is not a prerequisite for this issue.

Roadmap: #11

October 22, 2026 — completed in PR #85

Merged PR #85, implementation 3ec24e06b3639f7cb2a002abc2bc1c04a7149401, merge 69952725fb4eeb1daeb0e5c8bea7d8d82ba40670. Current README, architecture/system/capability entrypoints, roadmap navigation and the existing handoff now agree on the merged durable kernel and native read-only Optiflow adapter. The continuation handoff points to #15 next and retains CLI/release/provider/optional-scope gates. Older snapshots and original decision bodies are preserved; ADR-0011/0012/0013 remain proposed.

All six acceptance criteria above are reconciled in the documentation receipt: 136 relative targets resolved, external URLs syntax-checked, metadata/relationship graph and repository agent-framework validators pass, and 23 protected artifacts plus historical handoff/map/snapshot text remain byte-preserved. Independent source and ledger reviews pass. Runtime source, provider contracts, release assets and validation requirements are unchanged. Product tests/lint/native execution and hosted CI were not run for this documentation checkpoint; existing qualification remains with #34 and the provider owners.