User story · Persona: All app users. Users need tapping a notification to take them to the relevant screen, so that the action can be completed without hunting through the app.

Extend the Phase 1 notification panel so tapping a row marks it as read and navigates the user to the right screen. Define the target-mapping contract so every new trigger added in P2.2 (and beyond) plugs in cleanly.

• Event-payload contract: Every notification event payload carries the navigation target (screen identifier plus parameters such as ASHA ID and month). The panel resolves the deeplink at tap time, so the dispatch service does not need to know app navigation internals.
• Initial target mapping: ASHA Claim Rejected goes to ASHA claim screen in resubmission mode. Supervisor Verification Reminder goes to Supervisor Dashboard with the month pre-selected. Supervisor Auto-routing Alert goes to Supervisor Dashboard. CHO and ANM Verification Reminders go to the CHO or ANM Dashboard with the month pre-selected. ASHA Stage-Change goes to the ASHA claim screen showing current stage. ASHA Submission Reminder goes to the ASHA claim entry screen for the current month.
• Fallback handling: If the target requires data that is no longer valid (for example, a deleted ASHA-month), fall back to the relevant dashboard home screen and show a toast explaining the fallback.
• Affected modules: Notification service (event payload schema update). FLW Android app (panel tap-to-deeplink logic, navigation handlers per target screen).