[EAdamesJ]

Summary

• add the optional persistent Editorial JeyTid subsystem under src/server/editorial/
• add SQLite state, revisions/canon, durable task leases, budget reservations, eleven role profiles, artifacts, rights/provenance, audit/release approvals and recovery backups
• add mock/OpenAI text and image adapters, EPUB/PDF/render/package generation, KDP preparation/assisted mode, Telegram long polling with owner/chat authorization, optional Mastodon publishing, CLI, API and authenticated /editorial dashboard
• keep the base Agent Office path compatible with Node 20 by dynamically loading Editorial only when EDITORIAL_ENABLED=1; Editorial requires Node 22.5+ for node:sqlite

Verification

• npm run typecheck ✅
• npm run build ✅
• node --import tsx --import=#tests/css --test tests/editorial.test.ts ✅ (6/6)
• browser verification of authenticated /editorial in isolated local browser ✅
• npm test was started; the base suite still reports existing clone/DSH/interaction failures and did not finish cleanly in the available run. Editorial tests remained green.

Limits made explicit

• no live Telegram, OpenAI, KDP or Mastodon credentials were available, so no real external publication was attempted
• KDP is preparation/assisted only; MFA/CAPTCHA/login/submission remain owner actions
• PDF generation is a minimal text PDF with structural validation, not print-preflight software
• the optional Agent Office floor adapter records/dispatches to a configured floor; local Editorial provider execution remains the result authority

Closes no issue. The feature is intentionally opt-in and documented in docs/editorial.md.