Pro stack as platform packages: billing, sync, flags, shared edge utilities

[ElbertePlinio]

Refs pickforge/pickforge#152 (release umbrella), #132, #151, #133. Extends what's already here: @pickforge/auth (PKCE OAuth + entitlement reader) and supabase/migrations/…profiles_entitlements.sql.

Goal

The Pro stack lands as reusable platform packages, so the next Pickforge app gets accounts, billing, sync, and flags by installing packages instead of copying code. PickForge is the first consumer and the proof.

Packages

• @pickforge/billing — Stripe kit: webhook Edge Function helpers (idempotent, replay-safe), customer/subscription/credit mirroring into Postgres, credit-ledger schema + TS helpers, Checkout session helper. Pairs with the existing entitlements migration.
• @pickforge/sync — settings-sync engine from pickforge#151: field-group allowlist, LWW per group, per-machine overrides, data-boundary serialization guards. App supplies the field groups; engine stays generic.
• @pickforge/flags — minimal runtime feature flags: default-off, typed flag registry per app, settings/debug surface hook. No remote config, no percentage rollouts — this is release gating, not experimentation infra.
• supabase/functions/_shared/ — shared Edge Function utilities: entitlement check, credit debit, idempotency keys. App-specific functions (e.g. PickForge's Operator router, pickforge#133) compose these; they do not live here.

Boundary rules

• Packages are UI-free; app UI, product behavior, and offline degradation stay in app repos (same line @pickforge/auth already draws — its README's "billing stays in app repos" note gets updated to point at @pickforge/billing).
• Build with PickForge as the first consumer; nothing lands here without a consuming PR in pickforge. No speculative config or premature generality.
• Migrations here are the canonical schema; each app's Supabase project applies them.

Checklist

• @pickforge/flags (smallest, unblocks every flagged track)
• @pickforge/billing + schema migrations (consumed by pickforge#132)
• _shared/ Edge Function utilities (shipped as @pickforge/edge-shared; first consumer: stripe-webhook fn)
• @pickforge/sync (consumed by pickforge#151 — app slice pending)
• auth README boundary note updated

Validation

• Package unit tests + coverage in this repo's bun run check
• Each package's first consuming PR in pickforge passes its own validation

[ElbertePlinio]

Note for the billing/auth work here: @pickforge/auth's config param is named supabaseAnonKey — Supabase's anon key is legacy (deprecated end of 2026), replaced by sb_publishable_…. When touching the package, rename to supabasePublishableKey (with a deprecated alias for compat) and update the README example.

[ElbertePlinio]

Started @pickforge/flags (first checklist item, per pickforge/pickforge#152 start order): typed default-off registry, app-supplied override store, list/subscribe for the settings/debug surface. Zero deps, no remote config. Branch feat/flags-package, PR to follow with a consuming PR in pickforge.

[ElbertePlinio]

Progress update:

• Added @pickforge/flags package and README
• Added Vitest coverage for the frozen API semantics
• Ran bun install
• Ran bun run check

PR: pending, not pushed per task
Blocked: none
Next: review local commit / open PR when requested

[ElbertePlinio]

flags PR opened: #12 — in Codex review loop. Next after merge: lockstep publish, then the consuming PR in pickforge.

[ElbertePlinio]

PR #12 merged (clean Codex pass, CI green). Released v0.4.0 (lockstep bump) — publish workflow running. Consuming PR in pickforge is next; flags checklist box gets ticked when it lands per the boundary rule.

[ElbertePlinio]

@pickforge/flags checklist item done end-to-end: package merged (PR #12), published as 0.4.0, consuming PR merged in pickforge (pickforge/pickforge#161 — registry with 4 release-wave flags + dev-only Settings surface, tri-state so stale overrides can't shadow launch flips). Also merged #13 (advisor-driven RPC hardening on the definer trigger).

[ElbertePlinio]

Started @pickforge/billing (branch feat/billing-package, in build): billing_customers + credit_ledger + stripe_events canonical migration (RLS select-own, service-role-only writes), injected-Stripe webhook verify/process helpers (replay-safe, double idempotency via stripe_events PK + ledger stripe_event_id unique), checkout session helper, balance RPC. Credits-only v1 per pickforge/pickforge#135 decision.