4.2.0
Released
Features
The five plans went on sale, each named by its rarity: Common (formerly Free), Uncommon, Rare (formerly Pro), Epic and Legendary. Every surface that names a plan (pricing, Settings → Billing, the model picker, the credits banner, admin, terms, the app's Billing screen) reads the new names from one table, and copy that said "Pro" or "Free" for the plan now says the plan's name or "a paid plan". Existing Rare (Pro) subscribers keep their price, renewal date, allowance and models unchanged (#1137)
Technical changes· 5 entries for database, tooling, CI, tests and docs
Database
Put the plan ladder on sale in
20270109120000_plan_ladder_on_sale.sql: Uncommon, Epic and Legendary became purchasable beside Rare, which switches every storefront surface to the ladder, and Claude Haiku, GPT Luna and DeepSeek moved fromprotouncommon, with Rare still covering them by rank. The weekly AI review's and the Year Theme check's charge functions refuse with the plan their capability needs, read from the catalogue byplan_capability_requirement()("needs Rare or above"), rather than naming Pro.seed.sqlcarries the persona move (#1137)
Tooling & Configuration
Regenerated
packages/supabase-types/src/supabase.tswith the generator the pinned Supabase CLI (2.117.0) runs, postgres-meta 0.99.0, against the migrated schema. Beyondplan_capability_requirement(), it restored seven functions the file had been missing, correctedlink_guild_member_account()to returnstring[], typedintervalvalues asstringrather thanunknown, and typedfeedback.status_rankon insert as the generator does (#1137)
Tests
supabase/tests/rls.sqlcovers the ladder's access changes: Claude Haiku, DeepSeek and GPT Luna are the live Uncommon personas, a Common account can use none of them and cannot queue an investigation on Haiku, an Uncommon account can use all three and not a Rare persona, a Rare account still uses all three and can queue on Haiku, and only the service role can executeplan_capability_requirement()(#1137)
Documentation
AGENTS.md, the README,docs/billing.md,docs/schema.md,docs/pricing.md,docs/ops/feature-flags.md,docs/ai-investigations.mdand the mobile docs name the plans by their rarity, andAGENTS.mdasks for every plan name to come fromPLAN_TIER_LABELS;docs/mobile/release.mdrecords4.1.0as the first app version that understands the five plans (#1137)docs/billing.mdrecords the live Billing Portal settings for the ladder (increases apply immediately and are prorated; decreases and shorter intervals wait for the end of the period) and that the sandbox test-clock run was skipped at go-live, with what to check on the first real upgrade instead (#1137)