mobile-notifications — Canonical Skill

Purpose

Preserve the verified PushNotifications + community FCM implementation and its navigation contract.

When to use

Permission/register/unregister flows, token sync, topic subscribe, foreground toasts, tap navigation, logout cleanup.

Required reading

• skills/mobile/NOTIFICATIONS.md
• skills/mobile/LIFECYCLE.md (cold-start/readiness)

Relevant project locations

• src/composables/useNotification.ts, src/stores/notificationStore.ts
• capacitor.config.ts (PushNotifications.presentationOptions: [])

Mandatory rules

1. Web path is a no-op via isWeb(); never register on web.
2. Flows: check → request → register; logout → unsubscribe + unregister.
3. onNotifyView targets /post/view/:id for SYSTEM_ANNOUNMENT/LIKE_POST; that route is absent from src/router/index.ts. CHAT is a no-op.
4. addNotifyListeners() (received/tap) is not called anywhere; wiring it needs a real tap destination, replace-not-stack handles like addListeners, and router/auth readiness for cold start.

Implementation workflow

1. Trace permission → registration → token → topic → listener chain.
2. Handle foreground/background/cold-start distinctly.
3. Never log FCM tokens (the registration listener no longer does); do not copy values into docs/tests.
4. Verify per mobile-testing; device required for real delivery proof.

Verification

Mocked listener/navigation tests on web; delivery/tap on emulator/device only.