feat: ai consent flow

[peterchinman]

Summary

• Adds an AI data consent dialog on native mobile to comply with Apple guidelines. Users must accept before their first AI Chat message is sent.

Behavior:

• Dialog only appears on native mobile (isNativeMobilePlatform())
• Consent is persisted in the backend (User.aiDataConsent)
• Accept → consent saved, message sends, dialog never shown again
• Cancel → message not sent, dialog reappears on next attempt
• Desktop/web is unaffected

Backend

• DB migration: Adds aiDataConsent boolean column to User table
• DB read: get_legacy_user_info returns the new field
• DB write: patch_ai_consent() function (follows patch_user_tutorial pattern)
• API response: GET /user/legacy_user_permissions includes aiDataConsent
• New endpoint: PATCH /user/ai_consent to set consent

Frontend

• Service client: getLegacyUserPermissions maps aiDataConsent; new patchAiConsent() method
• User context: Exposes aiDataConsent accessor and useAiDataConsent() hook
• Consent dialog: useAiDataConsentGate hook + ConsentDialog component (uses DialogWrapper/ClippedPanel pattern from ShareModal)
• ChatInput integration: Consent gate in sendMessage() — all send paths (Enter key, touch button) flow through it

[github-actions]

Preview: https://peter-consent-flow-jt0zfz.preview.macro.com/app (96ea6fc)

[claude]

Code Review

I found 1 issue that needs to be addressed:

CLAUDE.md Violation in useAiDataConsent.tsx

File: js/app/packages/core/component/AI/component/input/useAiDataConsent.tsx (line 24)

Issue: The code directly calls authServiceClient.patchAiConsent() instead of using Tanstack query, which violates the AGENTS.md rule.

Reference:

macro/js/app/AGENTS.md

Line 61 in 3c24090

4. Going forward, all network calls to serice clients should be done through Tanstack query in the `queries` package. **DO NOT** introduce code that calls any client from `service-clients` outside of the queries package.

Fix: Follow the pattern used by other auth mutations. Create a mutation in js/app/packages/queries/auth/mutations.ts and use it in this component instead of calling the service client directly.

---

Otherwise, the implementation looks solid. The backend properly handles the consent persistence and the UI flow correctly gates AI message sending on native mobile platforms.

[whutchinson98]

backend changes look good to me