Audited Stagewise paid-launch and entitlement boundary
Directed by Nicholas Lee · Produced with ChatGPT + Lovable read-only source inspection + Supabase configuration/schema inspection
Verified the current Stagewise billing boundary and identified a release-state mismatch plus subscription-to-entitlement identity hardening needed before paid acquisition is treated as production-ready.
Stagewise has a substantive billing foundation: public database-backed pricing, authenticated checkout creation, official Stripe webhook signature verification, entitlement projection, cancellation/resume controls, and an atomic five-score monthly Free quota. The audit found that the public checkout runtime flag is enabled while the repository's own paid-launch gate remains blocked, so the release state should be reconciled before acquisition. It also found that subscription lifecycle events should be bound to the configured Stagewise Pro product and price before they can become entitlement authority. Acceptance is to make paid-launch readiness and checkout availability consistent, quarantine unrelated subscription identities, and keep Pro access receipt-backed and retry-safe. No customer/payment records were read, no checkout was invoked, and no sale or fulfilled revenue is claimed.