Problem
ROADMAP.md lists FLATFILES as Verified for Rust but does not call out that none of the other six bindings (CLI, MCP, REST server, FFI, Python, TypeScript, Go, C++) carry the surface. A reader assumes the surface is shipped everywhere because the table only shows the Rust API.
Proposed solution
Add a "FLATFILES — Binding Coverage" subsection under the existing FLATFILES section. List Rust as Shipped; list the other bindings as Pending with cross-reference to the binding issues. Note that the SDK-surface generator gap is the upstream blocker for the other bindings to land cleanly.
Impact
Roadmap reflects reality. Users planning around the SDK see what works in their language today.
Problem
ROADMAP.mdlists FLATFILES asVerifiedfor Rust but does not call out that none of the other six bindings (CLI, MCP, REST server, FFI, Python, TypeScript, Go, C++) carry the surface. A reader assumes the surface is shipped everywhere because the table only shows the Rust API.Proposed solution
Add a "FLATFILES — Binding Coverage" subsection under the existing FLATFILES section. List Rust as
Shipped; list the other bindings asPendingwith cross-reference to the binding issues. Note that the SDK-surface generator gap is the upstream blocker for the other bindings to land cleanly.Impact
Roadmap reflects reality. Users planning around the SDK see what works in their language today.