okhp3-google-gis-client-auth

Topics in the source

• okhp3-google-gis-client-auth
• Scope boundary
• Workflow
• 1. Plan
• 2. Validate
• 3. Execute
• GIS model and API facts
• Security and gotchas

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Intent: Give a static-site agent a reliable GIS token lifecycle for Google API read flows without inventing a backend or leaking a Client Secret. | In scope | Out of scope | |---|---| | GIS popup token model and GCP Web Application setup | Authorization code flow, refresh tokens, or offline access | | React/TypeScript useGoogleAuth lifecycle | Service accounts, non-Google identity providers, or multi-tenant servers | | Calendar and Tasks read requests with Bearer tokens | Calendar/Tasks create, update, or delete operations | | Expiry buffer, silent re-auth, consent fallback, and reconnect UI | Provider-specific write logic or product data persistence | LifeTrkr boundary: This skill covers authentication and read flows. Keep repo-specific write operations in src/lib/google.ts when that integration boundary exists; LifeTrkr currently splits the same boundary across src/lib/googleCalendar.ts and src/lib/googleTasks.ts. Do not move writes into the auth hook or invent a new backend. Before editing, identify the host origins, existing GIS script, client-ID source, requested read scopes, auth hook location, and existing Google API mod

This is an excerpt. Refer to the complete source and its current requirements.