Reference google calendar oauth orphaned project

The forge Google Calendar OAuth client that keeps hitting 7-day token expiry is 954659188872-.... This project number is NOT accessible via gcloud authenticated as [email protected] and does not appear in the project list. Attempting to manage it returns permission denied.

The active project Justin controls is forge-personal-assistant, which already has the Calendar API enabled and no service accounts yet.

Approved fix path: create a service account in forge-personal-assistant + share the personal Google Calendar with the service account email. This bypasses OAuth consent screens entirely, no 7-day expiry, no verification wall.

The 'requires verification' wall was hit because the shared OAuth client includes restricted Gmail scopes (gmail.modify) alongside calendar scopes. A client with restricted scopes cannot publish to Production without a paid CASA security assessment. The fix is to NOT use a shared OAuth client for calendar.

Why: Tried re-mint and Production publish paths; both blocked by orphaned project and restricted-scope verification wall. How to apply: When calendar auth breaks again, do NOT try to re-mint from the old client. Go straight to service account creation in forge-personal-assistant. gcloud is already authenticated on Console as [email protected].

[auto-memory session 5560f8c9-c807-4188-aaa2-1bb67b265559, confidence 0.85, mode direct]