chore(release): AppGallery public release readiness — privacy policy, signing, review submission

[hungify]

What to build

M9 (PRD docs/PRD.md Section 12/13, v1.5 decision): the project now targets a public AppGallery release, not personal sideload only. This ticket covers what's needed to actually submit, which is manual/account-level work an agent can't do.

Acceptance criteria

• Write a public privacy policy disclosing the NotificationListenerService usage (what's read, what's filtered/discarded, what's sent to the watch and how).
• Complete release signing for both phone-app and watch-app via AppGallery Connect (not the personal debug/sideload cert).
• Check Huawei's current AppGallery review guidelines for apps requesting Notification access, and write submission notes that clearly justify the use case up front (see risk noted in PRD Section 11).
• Submit for review; track and address any review feedback.
• AppGallery listing states clearly which watch models are verified (GT5) vs. best-effort/untested.

Blocked by

• Notification listener (feat(phone-app): NotificationListenerService captures Google Maps navigation notifications #61) and parser (feat(phone-app): parse Google Maps notification text into turn/distance/street JSON contract #62) shipped and field-tested (M7) — don't submit before the core relay is proven reliable.

Notes

This does not require the visual-map spike (#64) or HarmonyOS NEXT (M8) — public launch can ship text/arrow-only on GT-series first.