Only odt, ods, odp, and odg read and write; the other three ODF members are permanently read-only, and the .odb database-table-export subsystem is listed as not yet built at all. Since the MCP server and CLI both expose .odb and .odm tooling on top of these readers, any user workflow that reads one of these and wants to write it back dead-ends. Verified by grep: no writeOdfFormula*, writeOdm, or writeOdb* function exists anywhere in the package.
Evidence
README intro lists only ".odt, .ods, .odp, and .odg all read and write"; Status section: "Not yet built: ... the .odb database-table-export subsystem." Confirmed by grep across src/ -- no writer function exists for any of the three.
Affected packages: odf.js, documents.js, document-cli, document-mcp
Surfaced by a full-repository gap survey (feature/fidelity/write-support gaps), cross-checked against the existing issue history so it does not duplicate prior work.
Only odt, ods, odp, and odg read and write; the other three ODF members are permanently read-only, and the .odb database-table-export subsystem is listed as not yet built at all. Since the MCP server and CLI both expose .odb and .odm tooling on top of these readers, any user workflow that reads one of these and wants to write it back dead-ends. Verified by grep: no writeOdfFormula*, writeOdm, or writeOdb* function exists anywhere in the package.
Evidence
Affected packages:
odf.js,documents.js,document-cli,document-mcpSurfaced by a full-repository gap survey (feature/fidelity/write-support gaps), cross-checked against the existing issue history so it does not duplicate prior work.