Working State — Last Updated Feb 17, 11:02 PM ET

Right Now

Upwork pipeline running smoothly — Pub/Sub push trigger is primary, 5-min polling fallback
2 major proposals submitted today — Claude Code Coach ($85/hr) + GovGPT Python Backend ($65/hr)
19 connects remaining — low, be selective
CRESyncFlow at /tmp/CRESyncFlow — mostly built, needs Anthropic OAuth wiring + Reonomy scraper fix
Ecomm portfolio v2 live at ecomport.mcpengage.com
Spin360 ad creatives done — 28 images in spin360-ads/

Email pipeline (every 30 min fallback): checks Gmail for new Upwork job alerts → scores → auto-applies
- Cron: upwork-email-pipeline (id: 2205ac65) — reduced from */5 to */30, push is primary now
- Processed tracker: upwork-pipeline/processed.json
Gmail Pub/Sub push trigger (LIVE, PRIMARY): pull daemon receives Gmail notifications → hits hooks/wake → triggers pipeline instantly
- Daemon: pull-daemon.mjs via launchd com.clawdbot.gmail-pubsub-daemon
- GCP topic: upwork-email-notifications, subscription: upwork-email-sub
- Hooks endpoint: http://127.0.0.1:18789/hooks/wake (local gateway)
- Hook token: qnLSLAojTmhgdA4vktyaDsoDyvL9yUT_fPVR32vSdxk
- Gmail watch expires ~2026-02-24, auto-renewed by gmail-watch-renewal cron (every 3 days)
- Fixed Feb 17: was hitting wrong endpoint (/api/cron/run → 405), now uses /hooks/wake → 200 OK
Deep scan (4x daily at 8,12,16,20): browser search for jobs not in email alerts
- Cron: upwork-pipeline-scan (id: 116d2c44)
$50/hr MINIMUM on all proposals (Jake directive)
Connects remaining: ~107-122

Monitor first few pipeline triggers to make sure it works end-to-end
Upgrade to true push trigger (Gmail Pub/Sub → CF Worker) if cron latency is an issue
Follow up on Robert Hartline / CallProof meeting