Release 3.0.1

10 Oct 2026 · pinned package [email protected]

3.0.1

10 Oct 2026

notification-live.js (the bell's realtime feed) resumes from Events' opaque cursor: last_event_id is the last SSE id Events sent, handed back as it came, never a number it read from the message. A replay after a reconnect is dropped by its event_id (the last 256 heard), not by position. state() reports lastId in place of lastSeq.
release-watch.js drops a replayed release message by its event_id alone (it already resumed from the cursor).
With these, nothing in Shared reads Events' numeric seq as a position, so Events can stop accepting one (plan T7, ADR-042 decision 7). A bell on an older pin keeps working after that; a reconnect then starts at the head, and the count poll fills in.