oficina / docs Public

Plan 5, tasks 4-5: the subscriber, and wiring it into the editor

live-updates.mjs owns the cursor, the connection policy and fetch
serialization, with everything injected so it runs under plain Node
like the two client modules beside it. editor-entry.js gets wiring
only: a currentLive replaced wholesale on every resync exactly as the
save queue and the view already are, a cursor seeded from the initial
GET's Docs-Seq, and the POST's own seq read inside the post closure
so save-queue.mjs stays untouched.

Two rules in here look like fussiness and are not. The module owns
every open and every close, because EventSource reconnects natively
on any server close — including the idle close the module just chose
and the server's own TTL — so relying on it would have a parked tab
reopening its stream forever and holding a hibernating instance
awake. And "activity" means pointermove and scroll as much as
keydown, because visibility, focus and typing all miss the same case:
someone READING a long document on a tab that is already visible and
already focused fires none of them, and that tab is the watching half
of the whole feature.

A dead stream is logged and nothing else. [docs-save-status] means
"your edit did not save", which stays false — POST is a separate path
and is unaffected. What is lost is freshness, and it heals on the
next activity.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>