test(notifications): add scheduler validation suite

[ucguy4u]

Summary

This PR introduces changes to the notification scheduler validation path.
Goal: make issue #515 reproducible with deterministic host-runnable coverage while documenting the remaining device-only notification checks.

Core outcome:

• suppresses duplicate reminder scheduling in the shared scheduler
• emits stable deep-link payloads for notification routing context
• adds focused scheduler tests, a Make target, and a release runbook for notification validation

Changes

Code

• Added:
  • scheduler validation test coverage in app/test/features/agent_chat/data/services/agent_notification_scheduler_test.dart
  • notification validation runbook in docs/release/NOTIFICATION_VALIDATION.md
• Updated:
  • shared scheduler duplicate suppression and payload generation in app/lib/features/agent_chat/data/services/agent_notification_scheduler.dart
  • release checklist and validation entry point in docs/release/RELEASE_CHECKLIST.md and Makefile
  • app dev dependency wiring for the async preferences platform test harness in app/pubspec.yaml

Logic

• duplicate reminder requests now return the existing scheduled notification instead of scheduling again
• zoned notifications now carry a stable JSON payload with category, schedule type, deep link, and metadata
• completion bookkeeping still awards points once and cancels daily_until_done reminders after completion
• persisted scheduled reminders are stored and reloaded in chronological order

API Changes (if any)

• No external API changes.

Database Changes (if any)

• None.

Observability / Logging

• None.

Performance Impact

• Negligible. Duplicate suppression avoids unnecessary platform schedule calls.

Risks

• Deep-link payload structure is now standardized; downstream tap-handling code should continue to treat payloads as opaque JSON.
• Device-only OS presentation and tap-routing flows still require manual verification.
• Rollback plan:
  • revert this PR to restore prior scheduling behavior and remove the validation artifacts

Testing

• Unit tests:
  • make test-notification-validation
• Integration tests:
  • none in this slice
• Manual testing:
  • adb devices -l confirmed a connected Pixel 9 is available for the device-only matrix
  • device-only notification scenarios are documented in docs/release/NOTIFICATION_VALIDATION.md

Deployment Notes

• No config changes.

Related Commits

• test(notifications): add scheduler validation suite

Notes

• This addresses the framework-owned portion of issue Validation: Notifications #515; recording/download presentation and tap-routing still need the documented Android manual matrix before the issue can close.

[github-actions]

Plugin Module Size Gate

Policy: modules over 3 MB must be delivered as plugins; plugin modules over 5 MB must document cache management.

Module	Size	Type	Status
No changed Dart/Flutter modules detected	n/a	n/a	OK

[github-actions]

🚀 PR Quick Check Summary

Check	Status	Description
PR Validation	❌ failure	Title format, docs, bundled model guardrail
Code Quality	✅ success	Analyze, formatting
Core Tests	✅ success	Core package unit tests

💡 Note: Full app tests, coverage reports, and security scans run on merge to main.

View Details

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

🚀 PR Quick Check Summary

Check	Status	Description
PR Validation	✅ success	Title format, docs, bundled model guardrail
Code Quality	✅ success	Analyze, formatting
Core Tests	✅ success	Core package unit tests

💡 Note: Full app tests, coverage reports, and security scans run on merge to main.

View Details