[AGENT] Track mobile app and mobile web capture direction

[BASIC-BIT]

[AGENT]

Summary

Track the path toward a Chronote mobile app and make sure the existing mobile web UX remains usable while native capture is still future work.

Product direction

Mobile should eventually support fast personal capture, recording triage, and meeting review. Native watch capture is likely a later companion surface after the mobile/capture model is clearer.

Proposed scope

• Audit current mobile web UX for My Meetings, upload, meeting detail, and future quick capture flows.
• Define the minimal mobile app value beyond responsive web.
• Decide whether v1 native mobile focuses on quick voice capture, meeting review, upload/share sheet, or all of the above.
• Research iOS and Android recording/background constraints.
• Research watchOS and Wear OS constraints as a follow-up lane.
• Keep native app work aligned with the quick capture inbox model in [AGENT] Design quick capture inbox for notes, tasks, mobile, and watch #220.

Acceptance criteria

1. Mobile web UX is smoke-tested and obvious blockers are filed or fixed.
2. A native mobile v1 scope is documented.
3. Recording, background upload, notifications, and auth constraints are documented for iOS and Android.
4. Watch capture is either scoped as a follow-up or explicitly deferred.
5. The native/mobile plan reuses existing personal meeting and quick capture APIs where possible.