Archived: Adventure Weddings ops software (Astro app)

Salvaged from apps/adventure-weddings/ before that app was deleted on 2026-08-07. Reference material — nothing here is wired up or deployed.

Why this exists

The app’s own CLAUDE.md (added 2026-08-02, 8c5e5b4) marked the site deprecated but explicitly called out what was still worth keeping:

The ops/software work, which was never part of the marketing site: supabase/ (schema + edge functions), src/pages/portal/ (client portal), src/pages/admin, src/pages/api (ceremony-script flow), and docs/.

This directory preserves that list, minus src/pages/admin (see below). The ceremony-script flow is archived separately under ../adventure-weddings-astro-ceremony/.

What’s here

Path	Contents
supabase/functions/	29 edge functions — Stripe + payment webhooks, magic-link auth, client-portal auth, email send/warmup, inquiry scoring and autoresponder, lead nurture and scoring, gallery share/notify, contract generation, weather monitoring, permit-expiry checks, anniversary and post-wedding follow-ups, WhatsApp webhook, scheduled task runner
supabase/schema.sql, migrations/, seed.sql	the ops database schema
src/pages/portal/	96 client-portal pages
docs/	wedding-ops-strategy.md, wedding-ops-audit.md, ceremony-flow.md, and three plan documents (officiant booking funnel, wedding planning loop, AI ceremony script generation)

What is NOT here

src/pages/admin/ — 509 pages, 4.6MB — was not archived. 365 of those are the generated social-media content planner, and only 3 pages touched Supabase at all; the rest render build-time sample data. It is all still in git history. To get it back:

git checkout 9f0c969 -- apps/adventure-weddings/src/pages/admin

9f0c969 is the last commit before the deletion. The same command works for anything else from the app, including the ~500 marketing pages under src/pages/.

Important caveat

The Supabase project these functions ran against no longer exists. piyugutiwimbsfkvfnpc.supabase.co NXDOMAINs — the project was deleted before the app was. So none of this has a live backend, the schema has never been verified against a running database in its final state, and secrets referenced by the edge functions are gone.

The live Adventure Weddings Supabase is blksxqiqivuwfvwjzpmi, belonging to the Lovable site at ~/Projects/adventure-weddings. It is Lovable-managed and has a different schema. Reviving any of this means porting to that project (or a new one), not reconnecting.

Per the wedding-ops decision recorded on 2026-06-28, the plan was to build ops greenfield rather than continue this codebase. Treat these as reference for what was built and why, not as code to redeploy.