[jjoonleo]

Summary

• Advances [Release] Prepare full-screen intent declaration and justification #445; references parent track [Release Track] Android permissions and alarm policy #465.
• Adds Play Console USE_FULL_SCREEN_INTENT declaration wording for the alarm use case.
• Documents implementation evidence showing full-screen intent is reserved for user-scheduled schedule alarms.
• Links the declaration/evidence checklist from the release checklist.

Verification

• git diff --check: passed
• flutter analyze: failed because generated Dart files are absent in this checkout (database.g.dart, di_setup.config.dart, *.g.dart, mock files); no Dart source was changed in this PR.

Remaining human tasks

• Submit the full-screen intent declaration in Play Console from an authorized account.
• Run release-candidate Android QA and record device/OS/build evidence.
• Attach screenshots or recordings showing full-screen UI only for user-scheduled alarms and not generic/promotional notifications.
• Leave [Release] Prepare full-screen intent declaration and justification #445 open until Play Console submission and QA evidence are complete.

Track impact

• [Release] Prepare full-screen intent declaration and justification #445 is advanced, not fully solved, because final completion requires external Play Console access and real-device QA.
• Next parent-track item after [Release] Prepare full-screen intent declaration and justification #445 is [Release] QA alarm and notification flows on Android #457, but it remains blocked by [Release] Build a signed release Android App Bundle #452 and release-candidate QA prerequisites.