chore: complete Google Health verification and CASA

[JeffOtano]

Outcome

Complete Google's external launch requirements for Roni's Google Health integration after the production Fitbit feature shipped and passed a real OAuth and sync flow in #91.

Current state

• Google Health API is enabled.
• Roni requests only activity/fitness, health metrics/measurements, and sleep read-only scopes.
• Production OAuth credentials and callback are configured.
• A production account completed OAuth with all three scopes and a manual sync succeeded after fix: use documented Fitbit filter names #611.
• OAuth branding now uses Roni and roni.coach; domain ownership is verified in Search Console.
• Branding re-verification has been submitted and is currently in progress.

Remaining external gates

• Wait for Google branding re-verification to complete.
• Submit restricted-scope data-access verification with the required end-to-end demo video and scope-specific justifications.
• Complete the Google-requested CASA security assessment and submit its Letter of Validation.
• Confirm the production consent screen shows verified Roni branding and no unverified-app warning.
• Validate a public-user OAuth flow after approval and monitor Google Health usage/error rates.

Acceptance criteria

• Google Cloud shows branding and data access verified.
• The required CASA assessment is accepted.
• Production OAuth no longer presents the unverified-app warning.
• A production connect and sync succeeds after verification without exposing credentials or user identifiers.

Tracked separately from #91 because the product integration and runtime configuration are complete; this issue covers Google-controlled compliance and launch approval only.

[JeffOtano]

Material status update:

• Google completed the branding re-verification.
• Published the verified Roni branding; Google now reports that it is verified and being shown to users.
• The restricted-scope verification form is unlocked. It confirms the three expected restricted read-only scopes and the saved health-coaching justification.
• The only form validation blocker is the required end-to-end demo video link. No incomplete verification request was submitted.

Next external step is to create a privacy-safe demo video that shows the production connect/consent/sync flow without exposing account identifiers, then submit data-access verification. CASA follows when Google's Trust and Safety process requests it.

[JeffOtano]

Verification evidence update (2026-07-29):

• Produced a 41-second, 1280×720 privacy-safe Google Health demo covering: Roni connect entry, in-app disclosure, Google's required unverified-app screen, all three read-only scope selections, connected return state, and successful manual sync.
• Reviewed the rendered output frame-by-frame; account names and email addresses are cropped or redacted.
• Restored the production Fitbit connection after the recording flow and verified the sync control is present.
• Google's live Data Access editor explicitly requires a YouTube link and says the unverified-app screen must appear; the final render now satisfies both content requirements.
• YouTube upload and Google verification submission are the remaining external actions.

Garmin is tracked separately; its public API request form is currently closed, and a scoped evaluation-access request has been sent to Garmin Connect developer support.