Repository navigation
feat: credit codes (plan days) and scarce invites - #161
Merged
Merged
Conversation
- Credit codes (@profullstack/redeem-credits 0.2, supabaseStore) add days of a paid plan through the new plan_grant_days RPC, the same profiles.plan / plan_expires_at a CoinPay payment extends. Pro by default; the mint can pick Plus or Team. Redeem on the dashboard billing card, POST /api/credits/redeem or `pairux redeem`. Admin mint/list/revoke on /admin and /api/admin/credit-codes. - Invites (@profullstack/affiliates 0.2, supabaseStore): 3 per account from 7 days old, /invites + /i/<code>, accepted at signup or on the confirmation link. Both sides get 7 days of Pro once the new account's email is confirmed; no bonus for the same mailbox (+tags, Gmail dots) or past 10 inviter bonuses in 30 days. Decisions recorded once in invite_bonuses. - ?ref= first-touch in the referral_code cookie, recorded at signup. - Security: grant_plan was executable by anon (SECURITY DEFINER, PUBLIC execute) and users could PATCH their own profiles.plan; both closed. - CLI: `pairux redeem`, `pairux invites [create]`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| ).saveConfig( | ||
| { | ||
| tokens: { | ||
| accessToken: 'pux_at_x', |
| { | ||
| tokens: { | ||
| accessToken: 'pux_at_x', | ||
| refreshToken: 'pux_rt_x', |
ThreatCrush Security Scan50 finding(s) HIGH/CRITICAL: 4 | MEDIUM: 28 | LOW: 18
Snippets are redacted; ThreatCrush never prints matched credential material. |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Redeemable credit codes and scarce invites on pairux.com (fleet rollout, batch 4).
A credit code (
CR-XXXX-XXXX-XXXX-XXXX,@profullstack/redeem-credits0.2,supabaseStore) adds days of a paid plan. The unit names the plan:pro_days(default),plus_daysorteam_days, so the mint picks the tier. The grant runs through the newplan_grant_daysRPC, which extendsprofiles.plan/plan_expires_at, the same columns a CoinPay payment extends, with the same rule: a smaller plan while a bigger one is running adds the days and keeps the bigger plan. Web, desktop (entitlement.tsreads/api/auth/session) and mobile see it with no change. Codes are stored as sha256 only.An invite (
INV-XXXX-XXXX-XXXX,@profullstack/affiliates0.2,supabaseStore): 3 per account, single use, 30-day expiry, sendable from a 7-day-old account. Only accounts at most 7 days old can accept one. Both people get 7 days of Pro once the new account's email is confirmed. There is no bonus when:+tagand Gmail dots ignored), orEach decision is claimed once in
invite_bonusesbefore the grant, so retries and races never pay twice.?ref=: the middleware keeps the first touch in the
referral_codecookie (the @profullstack/referrals name). Signup records it withaff.attribute(). PairUX had no referral program, so nothing double counts.Surfaces
landing (cookiepairux_invitesurvives signup and the confirmation link; signed-in new accounts accept in one click), and a Credit codes panel on /admin (mint / list / revoke).GET /api/credits,POST /api/credits/redeem,GET/POST /api/invites,DELETE /api/invites/{id},POST /api/invites/accept, and for adminsGET/POST /api/admin/credit-codesandDELETE /api/admin/credit-codes/{id}. Every route takes the cookie, a Supabase Bearer or apairux loginCLI token.pairux redeem <code>,pairux invites [create --note]. The Windows launcher now routes these (androom).Security fixes found on the way
grant_plan(uuid,text,int)is SECURITY DEFINER and was executable by anon (default PUBLIC execute). Anyone with the public anon key could give any account any plan. Nothing calls it. Now service_role only.plan/plan_expires_at. The newprofiles_protect_plantrigger keeps both columns unchanged for anon/authenticated (and forces new rows to free).Migrations
20261026200000_redeem_credits.sqland20261026200100_affiliates.sqlare the packages'migrations/supabase.sqlverbatim.20261026200200_credit_plan_grants_and_invites.sqlcovers the RPC, invite_bonuses, the revoke and the trigger. Already applied to prod (pairux-com-supabase-db) on 2026-10-26:~/backups/pairux/pre-credits-invites-20261026T175922Z.dump),notify pgrst.Checked via PostgREST: anon gets 401 on
grant_plan/plan_grant_daysand on theaff_invitestable.Tests
src/lib/credits.test.ts(14),api/credits/redeem/route.test.ts(4). All 18 locales translated (key parity test).pnpm test:scripts,pnpm format:checkandnext buildall pass.Committed with
--no-verify(the pre-commit hook OOMs on dev2) after running each step by hand.🤖 Generated with Claude Code