Add guest push notifications and queue alerts

docs/prp/07-guest-pwa.md

@@ -41,6 +41,8 @@ Core Features
   - Header bell opens a drawer that merges upload queue stats with server-driven notifications (photo highlights, major achievements, host broadcasts, upload failure hints, feedback reminders).
   - Data fetched from `/api/v1/events/{token}/notifications` with `X-Device-Id` for per-device read receipts; guests can mark items as read/dismissed and follow CTAs (internal routes or external links).
   - Pull-to-refresh + background poll every 90s to keep single-day events reactive without WS infrastructure.
+  - When push is available (VAPID keys configured) the drawer surfaces a push toggle, persists subscriptions via `/push-subscriptions`, and the service worker refreshes notifications after every push message.
+  - Operations playbook: see `docs/ops/guest-notification-ops.md` for enabling push, required queues, and cron health checks.
 - Privacy & legal
   - First run shows legal links (imprint/privacy); consent for push if enabled.
   - No PII stored; guest name is optional free text and not required by default.
@@ -103,6 +105,8 @@ API Touchpoints
 - POST `/api/v1/photos/{id}/like` — idempotent like with device token.
 - GET `/api/v1/events/{token}/notifications` — list guest notifications (requires `X-Device-Id`).
 - POST `/api/v1/events/{token}/notifications/{notification}/read|dismiss` — mark/dismiss notification with device identity.
+- POST `/api/v1/events/{token}/push-subscriptions` — register a browser push subscription (requires `X-Device-Id` + VAPID public key).
+- DELETE `/api/v1/events/{token}/push-subscriptions` — revoke a stored push subscription by endpoint.
 
 Limits (MVP defaults)
 - Max uploads per device per event: 50