Build Log
ForgeHome Deploy + Journal Fix
June 21, 2026
ForgeHome landed in Courtney's hands and the engine-health journal stopped showing stale data — two loose ends from prior sessions, both closed.
Timeline
What shipped
Ran retros for engine-prevention-loop-2026-06-20 and forgehome-event-prep-2026-06-20 — both live on forgekits.build/build-log
Added retrospective session_contract + session_audit to both 2026-06-20 session JSONs (predated enforcement layer)
Committed leashline from within leashline/ — forgekit-core extraction, predeploy hook, tsconfig paths, brand assets
Added *.tsbuildinfo to leashline/.gitignore
Deleted /api/debug/backfill-recurring and /api/debug/calendar-raw (one-time tools, used last session)
Deployed ForgeHome to home.forgekits.build — all event prep, AI brief, notebook, curriculum features now live
Fixed journal page: build-trends.mjs now dual-writes engine-health.md to docs/forge-journal/ AND forgekit-website/content/forge-journal/
journal/page.tsx reads from content/forge-journal/ — resolves correctly on Vercel
Deployed forgekit-website — journal page now shows current engine-health
“yeah, clean up and then deploy. after that, wait for me to instruct”