Verify your application
Run the checks that exercise your account, database, subscription, or hosted application.
For source changes, run:
bun run lint
bun run typecheck
bun run test
bun run buildExpect a zero exit code from each command. Typecheck generates the MDX collection types first; build compiles the public content and application routes. Unit tests use controlled provider state for billing rules and do not call Stripe.
Verify the account flow
With local Supabase and the application running at http://localhost:3000:
bunx playwright install chromium
./coremvp e2e authThe journey creates a disposable account through Supabase Auth, verifies Dashboard/Account and the API session, signs out and in, and recovers the password using the local mailbox. It also exercises the native form POST path. Both tests must pass. A missing mailbox or local Auth service is a failed prerequisite.
Verify database and access boundaries
bun run test:integrationThis uses your real local Postgres database, Hikari’s services/repositories/API, and signed Stripe fixtures. It checks subscription state and verifies that Supabase anonymous/authenticated clients cannot read or write the billing tables. The Stripe payloads are fixtures; no Stripe API is called by this command.
Verify a real test subscription
Configure a Stripe test account, six monthly/yearly recurring prices, Customer Portal, and running local listener as described in Subscriptions, then run:
./coremvp e2e billing:subscriptionThe journey selects yearly Pro from public Pricing, preserves it through anonymous sign-in and signup, automatically opens the selected real Stripe test Checkout, waits for webhook-backed subscriber access, and opens Customer Portal. It then cancels the subscription through Stripe’s API and verifies that the webhook persists cancellation and subscriber access returns HTTP 403. Cleanup removes the disposable Stripe customer. Missing provider settings fail the journey instead of skipping it. Configure all six recurring test Price IDs in src/config/pricing.config.ts, use a test key, and use disposable customers. The journey checks Pro’s line item and persisted yearly price so a silent fallback to monthly billing or Starter fails.
If access fails, check the listener’s selected account and signing secret, successful subscription-event delivery, the configured price, and the durable subscription row. A successful Checkout return alone is insufficient.
Check a hosted deployment
./coremvp prod e2e smoke https://your-app.exampleUse the exact HTTPS origin you deployed. This checks liveness and anonymous account rejection, not hosted Auth or billing. Complete the provider-backed walkthrough in Deploy to Vercel, including recovery delivery to the users you intend to support.