2 Commits

Include renames

Author	SHA1	Message	Date
aarbitandClaude Sonnet 5	7fbe53f025	Fix Woodpecker event name: deployment, not deploy ... Caught from the linter warnings on the first real pipeline run (#1) — the production-promotion step's event filter used \`deploy\`, an invalid event name, so it would never have matched Woodpecker's actual deploy-button event (\`deployment\`) and the production step would have silently never run. Staging's own deploy (a push-triggered step) was unaffected and verified working on that same run. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017DUU6CnxECCDeqDNYJgr5x	2026-09-29 15:49:44 -05:00
aarbitandClaude Sonnet 5	d847a0f255	Add CI/CD pipeline: Woodpecker, auto-staging / manual-prod ... Adds .woodpecker.yml (lint + typecheck on every push, auto-deploy to a shared staging environment on every push, manual Deploy-button promotion to production on main) and env.staging blocks in both wrangler configs so staging gets its own Workers (diagrav-app-staging/diagrav-site-staging at staging-app.diagrav.com/staging.diagrav.com) rather than sharing anything with production. Staging also got its own fully separate Supabase Cloud project (own database, own Auth config reusing the same Google OAuth client with an extra redirect URI, own Resend-backed SMTP) — migrated, seeded with the public catalog, and verified end-to-end with a real sign-in through the deployed app before wiring any of this into CI. Updates deployment-plan.md's CI/CD section to match what actually got built, superseding the earlier manual-pushbutton-for-both-environments version of the plan. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017DUU6CnxECCDeqDNYJgr5x	2026-09-29 10:36:15 -05:00