Route Ask AI widget tickets through Help WebView log-attach flow

[joashrajin]

Summary

The Ask AI widget on the in-app help WebView is moving to a new dedicated support recipient so widget-originated tickets bypass the AI auto-reply loop.

Full context, motivation, and test plan: PCDROID-557.

Today, when a user taps the widget's "contact us here" link inside the in-app Help WebView, HelpWebViewClient intercepts the mailto: and routes it through Support.shareLogs(), which builds an Intent.ACTION_SEND with debug.txt attached. The recipient list and outgoing address are hardcoded — so once the widget renders the new recipient, the WebView would stop recognising the link, fall through to onTapUri(), and the user would email the new inbox without debug logs attached.

This PR makes the recipient address configurable end-to-end while preserving existing behaviour for every other caller of shareLogs().

Changes

• HelpPage.kt — replaced the prefix-match allowlist with an exact-recipient Set<String> (supportRecipients) that now includes the new AI-assistant recipient. Parses the recipient from the matched mailto URL and passes it through. Falls back to onTapUri() for any mailto whose recipient isn't in the set. The WebViewError "Contact support" button (shown when the help page fails to load) explicitly uses the existing support recipient.
• HelpViewModel.getSupportIntent() — accepts an optional recipient: String (default: existing support recipient) and forwards it.
• Support.shareLogs() — adds an optional recipient: String parameter (default: existing support recipient) and uses it for Intent.EXTRA_EMAIL instead of the hardcoded address. Other callers (LogsViewModel, StatusViewModel, the getFeedbackIntent path, and emailWearLogsToSupportIntent) are unaffected via the default.

Security note

The previous contactSupportAction.any { url.startsWith(it) } check matched by prefix, so a mailto: whose recipient was crafted as <allowlisted>@example.com.attacker.com would also match. This was harmless before because the to-address was hardcoded — but parsing the recipient from the URL would have made it exploitable. This PR tightens to exact-equality matching against the supportRecipients set.

Test plan

Full test plan in PCDROID-557. Highlights:

• Ask AI widget → "contact us here" link → email composer opens with the new recipient and debug.txt attached.
• Regular "Contact support" button on the Help page still uses the existing recipient and debug.txt (regression).
• Standalone Logs share flow still uses the existing recipient (regression).
• WebViewError "Contact support" button (airplane mode → help page fails) still uses the existing recipient (regression).
• A mailto: whose recipient isn't in supportRecipients falls through to the system email composer with no log attachment, no crash.

Coordination

Draft until the widget HTML swap is timed.

iOS counterpart: Automattic/pocket-casts-ios#4227.

[dangermattic]

	1 Warning
⚠️	PR is not assigned to a milestone.

Generated by 🚫 Danger