Config object key references resolve

A reference like config.stripe.priceIds.pro that does not exist in the config object evaluates to undefined at runtime, which then propagates into a Stripe API call as { price: undefined } and produces a confusing No such price error in logs — not a crash at the config call site. Reference integrity at the configuration layer matters because the failure surfaces far downstream, often in a webhook handler where the original intent is lost. AI tools invent config keys confidently.

Define the config object as the single source of truth in src/lib/config.ts and use as const so TypeScript catches typos at build time under tsc --noEmit:

export const config = {
  stripe: {
    priceIds: { pro: 'price_xxx', team: 'price_yyy' },
  },
} as const

Either add the missing key to the object or fix the reference to match the real path.