web: ship the editors and .odm tools behind real routes

[Mearman]

Closes #1096. Package/JSON and .odb had already landed under concurrent sessions (verified, untouched); this ships the two remaining stubs:

• .odm: an odm.render rpc procedure wrapping odmToPdf with a caller-supplied chapter map -- the master's external .odt references resolve from a second file picker, matched by href; OdmUnresolvedSectionError crosses the boundary as typed data, and the route renders the named still-missing chapter list as its core UX alongside the PDF in the browser's native viewer
• Editors: worker-held live-view editor sessions (open/setParagraphText/addParagraph/removeParagraph/save) over documents.js's docx/odt/doc/markdown editors -- one UI driving all four formats through the identical five procedures, save re-serialising through each format's own writer. Set-text is position-preserving; per-run styling deliberately waits for a genuine cross-format surface (stated in the route's comment)

Both tools activate in NAV_ITEMS and the PLANNED_ITEMS block is gone. Full vite build (with PWA precache) green; two new rpc round-trip tests.

Closes #1096.

[Mearman]

@codex security review

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
🔒 Security Review	✅ Completed 2026-09-10T04:54:22.788036Z	1353c3e	Manual request

Security findings

Advisory findings (1)

• 🟡 Bound expansion across repeated ODM chapters · Medium

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

🛡️ Codex Security Review

Here are some automated security review suggestions for this pull request.

Reviewed commit: 1353c3e288

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

• You comment "@codex security review"
• A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

[chatgpt-codex-connector]

🛡️ Codex Security Review

Security: Bound expansion across repeated ODM chapters

When a victim selects an attacker-supplied .odm and a matching chapter, bound cumulative chapter expansion before calling odmToPdf. A master can repeat one href thousands of times; this resolver returns the same bytes each time, and odmToPdf decodes, retains, and lays out the chapter for every section. A 14,671-byte 5,000-section master plus a 1,450-byte ODT holding 1 MiB of text materializes at least 4.88 GiB of text, exhausting the worker/tab. Zod checks only types and no cancellation signal is passed.

SECURITY.md reference: SECURITY.md:L15-L18

Useful? React with 👍 / 👎.