M001 / S03
v0.1.0 · build 2026-04-21T08:34:53.150Z
Minimal PWA outbound delivery and notification handling proof
This homepage truthfully exposes install shell readiness, service worker lifecycle, notification permission, push subscription enrollment, backend persistence results, user-triggered outbound delivery diagnostics, and notification click-handling proof for the current runtime.
Platform truth
Runtime status panel
This panel reports capability evaluation, service worker registration lifecycle, notification permission, push subscription persistence, and user-triggered outbound test-send diagnostics from the actual browser context.
- Install shell readiness
- blockedInstall shell is blocked because service worker support or required browser constraints are missing.
- Service worker support
- unsupportednavigator.serviceWorker is missing.
- Notification support
- unsupportedNotification API is not available.
- Push prerequisites
- unsupportedPushManager is not exposed in this runtime.
- Install prompt signal
- pendingNo install event detected yet in this context.
- Standalone display mode
- pendingApp is currently running in a normal browser tab.
Runtime facts are evaluated on the client after hydration.
Registration not attempted yet.
Notification permission/subscription not attempted yet.
Wait for hydration before attempting permission or subscription work.
Capability facts are not actionable until the client hydrates.
No subscription persistence result captured yet.
No outbound test send attempted yet.
This sends a user-triggered test notification to the current process-local subscription list and reports per-subscription delivery diagnostics; it does not imply background durability or guaranteed delivery.
Test send is blocked because push prerequisites are unsupported in this runtime.
Long-run push test is not configured yet.
This server process can send a background test notification every hour on the hour until you stop it. It is intentionally best-effort and resets if the deployment restarts.
No long-run scheduler state captured yet.
On iPhone and iPad, Safari or another WebKit browser must be added to the Home Screen and relaunched in standalone mode before push-related work is considered viable.
- info: Capability evaluation: install shell blocked, push prerequisites unsupported, permission unknown.
- Capability evaluation is intentionally truthful and only reports what this runtime exposes now.
- On iPhone and iPad, push remains blocked until a WebKit browser is added to the Home Screen and relaunched standalone.