Add Prayer Care with Google Calendar and Gmail exports

[ShadowWalkerNC]

Summary

• adds private Prayer Care contacts, recurring commitments, check-ins, and follow-up metadata
• adds per-user Google OAuth with encrypted tokens and least-privilege Calendar/Gmail scopes
• exports recurring prayer commitments to Google Calendar or private ICS files
• creates reviewed Gmail drafts only; BibleDesk never sends automatically
• integrates Today in Prayer into the main app and adds a Prayer Care launcher to the Chrome extension
• updates the schema, environment template, architecture, roadmap, README, agent rules, and extension docs

Security

• ownership is derived from verified Supabase bearer tokens
• private prayer tables use owner-only RLS
• Google token records are service-role-only and encrypted with AES-256-GCM
• OAuth uses a signed, expiring state value plus an HTTP-only state cookie
• sensitive commitments use neutral titles/details in calendar exports
• no Gmail send endpoint exists

Validation

• npm run lint (0 errors; 40 existing warnings)
• npm run build
• targeted integration ESLint
• Chrome extension JavaScript syntax and manifest JSON validation
• git diff --check
• secret assignment and Gmail-send path scans

Manual setup before deployment

1. Apply supabase/schema-v5.sql after schemas v1-v4.
2. Create a Google OAuth Web client and enable Google Calendar API + Gmail API.
3. Register <NEXT_PUBLIC_APP_URL>/api/google/callback as an authorized redirect URI.
4. Configure GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, and a 32-byte GOOGLE_TOKEN_ENCRYPTION_KEY in Vercel.
5. Complete authenticated smoke tests before merging/deploying.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
bible-desk	Ready	Preview	Sep 3, 2026 11:39pm UTC