You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A focused quality pass to ship a stable, bug-free v1.0.0 by the end of July. Exercise the full freemium flow end to end (free use, hitting the quota, upgrade via Stripe, entitlement refresh, Pro features, BYO-key, cancellation and downgrade), fix what breaks, and raise automated coverage for the new paths.
The repo already has a strong test suite (283 tests); this extends it to the monetization surface and adds an end-to-end smoke test.
Why
Monetization adds new failure modes (network, auth, billing, quota, revocation) that can directly cost revenue or block a paying user. A deliberate hardening pass before launch catches the edge cases that unit tests alone miss and gives confidence to hit the end-of-July target without shipping regressions.
Why CI doesn't catch it
Much of the freemium flow crosses process boundaries (extension to backend to Stripe to OpenAI) and depends on timing, real webhooks, and entitlement expiry. Unit tests with mocks pass while the integrated path can still fail, so we need explicit end-to-end and error-injection tests plus manual verification.
Acceptance Criteria
End-to-end smoke test covering free use, over-quota, upgrade, Pro unlock, and downgrade
Description
A focused quality pass to ship a stable, bug-free v1.0.0 by the end of July. Exercise the full freemium flow end to end (free use, hitting the quota, upgrade via Stripe, entitlement refresh, Pro features, BYO-key, cancellation and downgrade), fix what breaks, and raise automated coverage for the new paths.
The repo already has a strong test suite (283 tests); this extends it to the monetization surface and adds an end-to-end smoke test.
Why
Monetization adds new failure modes (network, auth, billing, quota, revocation) that can directly cost revenue or block a paying user. A deliberate hardening pass before launch catches the edge cases that unit tests alone miss and gives confidence to hit the end-of-July target without shipping regressions.
Why CI doesn't catch it
Much of the freemium flow crosses process boundaries (extension to backend to Stripe to OpenAI) and depends on timing, real webhooks, and entitlement expiry. Unit tests with mocks pass while the integrated path can still fail, so we need explicit end-to-end and error-injection tests plus manual verification.
Acceptance Criteria
Resources
pnpm test(283 tests, Vitest);app/QA-PROMPT.md