@classytic/arc-notifications 0.8.0 → 0.10.0

package/README.md

@@ -129,6 +129,21 @@ sseHub.onConnect((userId, orgId) => backfill.onConnect(userId, orgId)); // debou
   badge's axis). Both stay host-owned in the repository.
 - All realtime is **best-effort on top of the durable feed** — a dead socket never
   fails a request or a send; clients converge via `GET /notifications/`.
+- **Cursor replay.** Pass the client's last-seen time on connect —
+  `backfill.onConnect(userId, orgId, { since: req.headers['last-event-id'] })` — and
+  a repository that also implements `listSince(org, user, since, limit)` replays the
+  gap, including rows an earlier connection received but dropped; they merge with the
+  claimed rows into the same single bulk event.
+- **List envelope and verbs.** `inAppFeedResource({ listEnvelope: 'offset' })` answers
+  repo-core's `OffsetPaginationResult` (`feedListResult` is the same conversion);
+  `{ actions: true }` also mounts `markRead` / `markAllRead` as arc action-router verbs.
+- **One push per recipient.** The package calls `port.push` once per recipient and event
+  and never publishes on a bus itself. If your port forwards frames onto an event bus,
+  give each frame its own correlation id (it is a transport hop, not a second publish of
+  one logical event), or arc's dev duplicate-publish detector will warn on every
+  multi-recipient notification.
+- **Clock.** `createUnreadCountCache({ clock })` and
+  `createRepositoryDeliveryLog(repo, { clock })` take a `{ now(): Date }`.
 
 ### 5. Durable dispatch — crash-safe bulk sends (10k+)