2026-03-19 — Prakta

What shipped today

Production deployment is live at www.prakta.io. The bulk of today’s session was spent polishing the last mile: branded email templates, admin features, blog integration, and getting the production environment running.

Production deployment. The main blocker was a Vercel project mismatch — the domain www.prakta.io was assigned to a prakta project while env vars and code had been deployed to a separate web project (created when linking from the web/ subdirectory). Fixed by relinking to the correct project, pushing all 10 environment variables (Supabase, Anthropic, Stripe, Brevo, App URL), and redeploying from the monorepo root. The site now returns 200.

Admin, blog, and polish. Earlier sessions today shipped the admin nav section (#109), blog pages pulling from paulwelty.com RSS filtered by “prakta” category (#98), self-assessment settings with config lever mapping (#103), task prereqs with AI guessing (#94, #95), and various security hardening (Stripe idempotency #87, webhook error handling #88, input validation #85). The logo (#91) uses a combined P symbol + “Prakta” wordmark in the warm editorial palette.

Supabase auth config. Updated site URL to https://www.prakta.io and set explicit redirect URLs (no wildcards — Supabase rejects them in prod). Six branded email templates (confirm, reset, magic link, invite, change email, reauthentication) were generated and opened in BBEdit for manual paste into the Supabase dashboard.

Completed

• #111 — Fix production 500 error on www.prakta.io
• #109 — Create admin nav section
• #103 — Self-assessment settings questions
• #98 — Implement blog page like Authexis
• #97 — Remove blog link from footer until content exists
• #96 — Build list of use cases
• #95 — Prereqs and hard-to-start guess on task review
• #94 — Add prereqs to task parsing
• #91 — Create logo
• #88 — Error handling for Stripe webhook
• #87 — Idempotency key for Stripe checkout
• #85 — Validate task source parameter
• #84 — Track deliberate minutes for EOD
• #83 — Fix hardcoded empty string origin in Stripe routes

Release progress

March 2026: 0 open / 0 closed (milestone exists but no issues assigned)

Carry-over

• #101 — Branded email templates: 6 templates in BBEdit, waiting for Paul to paste into Supabase dashboard. Cannot be automated.
• Orphan web Vercel project: should be deleted from Vercel dashboard to avoid confusion.
• Google OAuth: needs manual Google Cloud Console setup + Supabase config.
• Stripe products/prices: need to be created in Stripe dashboard and price IDs updated.

Risks

• No test coverage. 48+ issues shipped with zero tests. First real user will be the integration test.
• Stripe price IDs likely placeholders. STRIPE_PRICE_MONTHLY and STRIPE_PRICE_ANNUAL env vars are set but may point to test/placeholder products.
• Rate limiter is in-memory (#86). Won’t work correctly on Vercel serverless — each invocation gets a fresh instance. Backlogged.

Flags and watch-outs

• Deploy from monorepo root, not web/. The Vercel project root directory is set to web/ in project settings.
• web/.vercel removed. Only /Users/paul/Projects/prakta/.vercel should exist, pointing to synaxis/prakta.
• buttonVariants server/client split — shadcn add --overwrite clobbers it. Restore button-variants.ts after any shadcn update.
• Port 3006 for local dev, always.

Next session

1. Have Paul paste email templates into Supabase dashboard (#101)
2. Delete orphan web project from Vercel dashboard
3. Test the full production flow: signup → onboarding → tasks → sequencing → wrap-up
4. Configure Google OAuth (Google Cloud Console + Supabase)
5. Create Stripe products/prices and update env vars
6. Start writing tests — at minimum, API route smoke tests
7. Check open issues (#86 rate limiter, #108 BCC emails) for prioritization