docs(04-02): complete notification settings UI plan

.planning/STATE.md

@@ -3,14 +3,14 @@ gsd_state_version: 1.0
 milestone: v1.0
 milestone_name: milestone
 status: executing
-stopped_at: Completed 04-01-PLAN.md (Notification infrastructure)
-last_updated: "2026-03-16T14:00:13.196Z"
+stopped_at: Completed 04-02-PLAN.md (Notification Settings UI)
+last_updated: "2026-03-16T14:09:29.326Z"
 last_activity: 2026-03-16 — Completed 04-01-PLAN.md (Notification infrastructure)
 progress:
   total_phases: 4
   completed_phases: 3
   total_plans: 13
-  completed_plans: 11
+  completed_plans: 12
   percent: 100
 ---
 
@@ -61,6 +61,7 @@ Progress: [██████████] 100%
 | Phase 03 P02 | 4 | 2 tasks | 5 files |
 | Phase 03 P03 | 2 | 2 tasks | 0 files |
 | Phase 04-notifications P01 | 9 | 2 tasks | 11 files |
+| Phase 04-notifications P02 | 5 | 2 tasks | 5 files |
 
 ## Accumulated Context
 
@@ -107,6 +108,8 @@ Recent decisions affecting current work:
 - [Phase 04-01]: flutter_local_notifications v21 uses named parameters in initialize() and zonedSchedule() — positional API removed in v20+
 - [Phase 04-01]: Generated Riverpod 3 provider named notificationSettingsProvider (not notificationSettingsNotifierProvider) — consistent with themeProvider naming convention
 - [Phase 04-01]: nextInstanceOf exposed as @visibleForTesting public method to enable TZ logic unit testing without native dispatch mocking
+- [Phase Phase 04-02]: openNotificationSettings() not available in flutter_local_notifications v21 — simplified to informational SnackBar (no action button)
+- [Phase Phase 04-02]: ConsumerStatefulWidget for SettingsScreen — async permission callbacks require mounted guards after every await
 
 ### Pending Todos
 
@@ -120,6 +123,6 @@ None yet.
 
 ## Session Continuity
 
-Last session: 2026-03-16T14:00:13.194Z
-Stopped at: Completed 04-01-PLAN.md (Notification infrastructure)
+Last session: 2026-03-16T14:09:29.324Z
+Stopped at: Completed 04-02-PLAN.md (Notification Settings UI)
 Resume file: None