## Web Push received

# Live Web Push E2E (production notification server)

macOS — if you see “zero” banners but the log says the push arrived:

- In System Settings → Notifications → Google Chrome: turn Notification Centre on, set alerts to Persistent (not only Temporary), and enable Play sound while testing.
- Chrome in the foreground often gets no Desktop banner for the active tab — macOS treats that like “you are already looking at the app.” Before sending, switch to Finder or another app, then click “Send test notification” (or send and then blur Chrome within a second).
- This page always opens a purple bar at the top when a push is handled — that is real delivery proof independent of the OS toast (Windows extension still uses `showNotification`; the bar mirrors what your UI could show if the OS hides the toast).

How you know it worked: by default the helper exits when the service worker reports the push (terminal: Web Push / push ack). That proves Web Push delivery and that `showNotification()` was attempted — it does not guarantee you saw an OS banner (macOS Chrome often hides them). The terminal may also print a WebSocket line: same server path as desktop clients, useful as a diagnostic only. For product sign-off, follow the macOS callout and confirm a visible notification, then click it (set `PUSH_E2E_SUCCESS=click` for that stricter exit).

Harness progress — push reached the service worker and/or Node saw the WebSocket payload. Check the terminal for details. For visible UI verification, confirm an OS or in-page notification and click it when using `PUSH_E2E_SUCCESS=click`.