Build Log · June 19, 2026
ForgeHome — Google Calendar Two-Way Sync
Built full two-way Google Calendar sync for ForgeHome — OAuth connect flow, calendar picker, pull events into Today's Route, push new appointments back to Google. Deployed to home.forgekits.build.
- ForgeHome
- Google Calendar
- OAuth
- Sync
- Database
- New DB tables / columns added
- 3
- New files created
- 8
- OAuth flow end-to-end
- 1
- Sync directions (pull + push)
- 2
- Debug blockers resolved
- 3
- New self-correction rule saved
- 1
New DB tables / columns added
New files created
OAuth flow end-to-end
Sync directions (pull + push)
Debug blockers resolved
New self-correction rule saved
Timeline
Start
Session kickoff
Build order saved from last session — Google Calendar first
Phase 1
Schema + OAuth
calendar_tokens, calendar_sync_settings tables, googleEventId on route_items, OAuth routes
Phase 2
Sync engine
Pull: Google → ForgeHome. Push: ForgeHome appointments → Google write target
Phase 3
Settings UI
Calendar picker with Pull + Write Target toggles, Sync now button, auto-sync on Today load
Debug
OAuth + API errors
proxy.ts re-export bug, redirect_uri_mismatch, Calendar API 403, 500 error handling
Ship
Live at home.forgekits.build
Courtney can connect Google Calendar and see her events in Today's Route
“Week now shows events from Google Calendar.”