Document the unread count in the push payload

Specifies unread and aps.badge in the push and utils notes, records
the notifications ensure-block and the index that serves the unread
read in the database note, and updates the README and the push API
docs.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-15 04:05:28 +01:00
co-authored by Claude Sonnet 5.5
parent 2452f9e85b
commit 585fab74a6
6 changed files with 13 additions and 5 deletions
+3 -1
View File
@@ -1075,7 +1075,9 @@ in real time, bridged onto the in-process pub/sub bus by a lock-owner relay:
| Issue-tracker update | reporter / admins |
`create_notification` schedules delivery as a fire-and-forget async task, so a dead
subscription or push-service error never blocks the triggering request. Delivery
subscription or push-service error never blocks the triggering request. The payload carries the recipient's unread count (`unread`, the same number as
`/notifications/counts`), which APNs presents as `aps.badge` so the app icon updates even
while the app is closed. Delivery
(`push.notify_user`) reads a user's subscriptions once, groups them by provider, builds
each provider's payload once, and sends over that provider's own HTTP client (stealth for
Web Push, a dedicated HTTP/2 client for APNs). A subscription the push service reports as