A complete EPUB 2/3 reader and EPUB 3 writer exists as a package but is not a dependency of the conversion engine, the CLI, the MCP server, or the web UI, so no user-facing surface can reach it. Issue #802 ("Wire epub into the conversion engine, CLI, MCP server, and web UI") is closed, but the current tree contradicts that. This is the largest capability-per-effort item in the repo: the hard part (the codec) is done and only registry/pathfinder wiring remains, exactly as was done for rtf-codec under the closed #847.
Evidence
epub-codec's README: "Wiring this package into documents.js's conversion engine, document-cli, document-mcp, or the web UI is explicitly out of scope here." Verified directly: grep for "epub" across packages/documents.js/src/ returns nothing, and epub-codec appears in no dependency list for documents.js, document-cli, or document-mcp.
Affected packages: epub-codec, documents.js, document-cli, document-mcp, web
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.
A complete EPUB 2/3 reader and EPUB 3 writer exists as a package but is not a dependency of the conversion engine, the CLI, the MCP server, or the web UI, so no user-facing surface can reach it. Issue #802 ("Wire epub into the conversion engine, CLI, MCP server, and web UI") is closed, but the current tree contradicts that. This is the largest capability-per-effort item in the repo: the hard part (the codec) is done and only registry/pathfinder wiring remains, exactly as was done for rtf-codec under the closed #847.
Evidence
Affected packages:
epub-codec,documents.js,document-cli,document-mcp,webSurfaced 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.