chore: align CI with Cloud Build + rewrite README_CLOUDRUN

[avireddy0]

Summary

Wave I+J cleanup for Envision-Construction/gmail. Aligns the deploy path with the platform rule "push triggers Cloud Build — never gcloud run deploy," removes a redundant scheduler script, and rewrites README_CLOUDRUN.md to match what's actually deployed.

Commits

1. docs: rewrite README_CLOUDRUN.md to match deployed reality (98 +/107 -)

   • Documents push-to-main -> Cloud Build (cloudbuild.yaml steps deploy-cloud-run, delete-old-scheduler, create-scheduler).
   • WIF auth — drops the legacy SA-key copy instructions; references Secret Manager gmail-scraper-sa-key as break-glass only.
   • Removes obsolete ./deploy.sh and manual gcloud run deploy paths.
   • Fixes the API contract section per main.py: surfaces incremental (default true, scheduler depends on it) and the full response shape — mode, skipped_duplicates, completed_at, status: started|completed|failed, error. Health-check JSON now includes mode: "incremental".

2. chore: route deploy through Cloud Build, drop setup_scheduler.sh (6 +/90 -)

   • .github/workflows/deploy.yml now runs gcloud builds submit --config=cloudbuild.yaml instead of deploy-cloudrun@v2 + shelling out to setup_scheduler.sh.
   • Verified cloudbuild.yaml create-scheduler step preserves: schedule (*/5 * * * *), URI, body ({"incremental": true, "max_per_user": 100}), Content-Type header, America/New_York time zone.
   • Deletes setup_scheduler.sh — was redundant with cloudbuild.yaml and self-contradictory (echoed "Every hour at minute 0" while creating */5 * * * *).

Files changed

• README_CLOUDRUN.md — full rewrite
• .github/workflows/deploy.yml — switched from deploy-cloudrun@v2 to gcloud builds submit
• setup_scheduler.sh — deleted

Notes for follow-up

• gunicorn is dead in requirements.txt. The Dockerfile runtime CMD is functions-framework --target=run_scraper --port=8080; nothing invokes gunicorn. Confirmed with grep -r gunicorn . — only hit is requirements.txt:5. Suggest removing in a separate small PR (kept out of this scope to keep the diff focused).
• cloudbuild.yaml was already in the repo and known-good but not wired to a trigger; this PR makes it the active path. The cloudbuild.yaml create-scheduler --attempt-deadline=3600s is intentionally higher than the prior setup_scheduler.sh value of 1800s; if 30m is the desired ceiling, follow-up commit dee6b4e's reduction needs to be re-applied to cloudbuild.yaml.

Test plan

• Merge to main and watch the Actions run — confirm Cloud Build job succeeds and gmail-scraper revision rolls out.
• gcloud scheduler jobs describe gmail-scraper-5min --location=us-central1 — verify schedule, URI, body, deadline match expectations.
• gcloud scheduler jobs run gmail-scraper-5min --location=us-central1 — manual trigger; confirm 200 and a row appears in claude-mcp-457317.gmail_analytics.messages.
• curl https://<service-url>/ — confirm health-check JSON now includes mode: "incremental".

🤖 Generated with Claude Code