feat(pricing): launch Team tier across marketing surfaces + add Vector (#106)

DOC-REALITY-DELTA-2026-05-20 close-out. Team tier was fully defined in
api/plans.yaml at $199/mo with every limit -1 (unlimited) and Razorpay
plan IDs configured, but every consumer-facing surface read "coming soon".
This commit aligns the marketing pages with the launched posture:

- PricingPage.tsx: Team monthly $199 / yearly $165.83 ($1990/yr · save $398).
  Per-row "SOON" cells replaced with real limits ("unlimited" + RBAC/SLA/SAML
  checkmarks). CTA goes to mailto:support@instanode.dev?subject=Team... for
  the assisted-onboarding path while we wire the full Razorpay self-serve flow.
- PricingPage.test.tsx: regression guard — Team CTA now an <a>, asserts $199.
- PricingGrid.tsx (dashboard upsell module): Team card carries real numbers,
  same Contact Sales CTA.
- MarketingPage.tsx: homepage Team card switched from "coming soon"
  placeholder to launched-tier card. Hero prose adds "vectors" to the
  service list. SERVICES table gains a Vector row (POST /vector/new) so
  /vector/new isn't invisible to /pricing viewers.
- Dropped "small / medium" pod-size adjectives from Deploy apps row —
  there is no deployment_size field in api/internal/handlers/deploy.go,
  so the marketing copy implied a tier benefit the platform doesn't deliver.

Coverage block (per CLAUDE.md rule 17):
  Symptom:        plans.yaml had team launched ($199, unlimited); 4 surfaces
                  still rendered "coming soon"
  Enumeration:    grep -rn 'coming soon\|Team:.*soon' instanode-web/src
                  dashboard/src content/llms.txt api/plans.yaml
  Sites found:    4 (PricingPage tier card + matrix, MarketingPage homepage
                  card, dashboard PricingGrid Team card, content/llms.txt;
                  api/plans.yaml itself was already launched)
  Sites touched:  4 (this PR covers 3; content/llms.txt + dashboard
                  PricingGrid land in companion commits this sweep)
  Coverage test:  PricingPage.test.tsx regression — "$199" asserted in DOM;
                  Team CTA must be <a> not disabled span.
  Live verified:  after merge + Vercel deploy, https://instanode.dev/pricing
                  will render Team with $199 + clickable Contact Sales link
                  (replaces the "coming soon" placeholder shipped 2026-05-15).

Closes P1 from DOC-REALITY-DELTA-2026-05-20.md §2 (Team launch) + P1 §5
(Vector visibility) + P1 §5 (small/medium deploy strings).

Author: mastermanas805

src/components/PricingGrid.tsx

@@ -55,8 +55,10 @@ interface TierDefinition {
   // user is already on Pro.
   upgradesTo?: TierKey
   highlight?: boolean
-  // Set when the tier is announced but not yet purchasable (today: Team).
-  // Renders a "coming soon" badge and disables the CTA.
+  // Set when the tier is announced but not yet purchasable. As of
+  // 2026-05-20, Team is launched — no current tier sets this, but
+  // the flag is preserved as the type-system safety net for any
+  // future "announced but unbuyable" rollout (early-access waitlists).
   comingSoon?: boolean
 }
 
@@ -166,14 +168,27 @@ export const PRICING_GRID_TIERS: TierDefinition[] = [
     upgradesTo: 'team',
   },
   {
-    // Team — coming soon. No price, no yearly, no feature list. The card
-    // header and "coming soon" badge are enough; we don't promise anything
-    // about Team until launch.
+    // Team — launched 2026-05-20 (DOC-REALITY-DELTA sweep). plans.yaml:375
+    // has team at $199/mo, $1990/yr, every limit -1 (unlimited).
+    // CTA goes via buildCtaLabel('team') → "Contact sales" until the
+    // assisted-Razorpay self-serve flow ships.
     key: 'team',
     label: 'Team',
-    monthly: { price: 'coming soon', sub: '' },
-    features: [],
-    comingSoon: true,
+    monthly: { price: '$199', sub: '/mo' },
+    yearly: {
+      price: '$165.83',
+      sub: '/mo billed yearly',
+      savings: '$1990/yr · save $398 (17%)',
+      yearlyTotal: '$1990/yr',
+    },
+    features: [
+      { text: 'unlimited Postgres · Redis · MongoDB · queues · storage' },
+      { text: 'unlimited deployments · 50 custom domains' },
+      { text: 'unlimited vault entries · multi-env' },
+      { text: '90-day backups · self-serve restore' },
+      { text: 'RBAC + audit log · SSO / SAML' },
+      { text: '99.9% SLA' },
+    ],
   },
 ]
 

src/pages/MarketingPage.tsx

@@ -95,7 +95,7 @@ const ROUTES = {
 } as const
 
 type Service = {
-  id: 'pg' | 'rd' | 'mg' | 'qu' | 'st' | 'wh' | 'dp'
+  id: 'pg' | 'rd' | 'mg' | 'vc' | 'qu' | 'st' | 'wh' | 'dp'
   name: string
   curl: string
   liveIn: string
@@ -105,6 +105,9 @@ const SERVICES: Service[] = [
   { id: 'pg', name: 'Postgres',       curl: 'POST /db/new',      liveIn: '1.4s' },
   { id: 'rd', name: 'Redis',          curl: 'POST /cache/new',   liveIn: '0.9s' },
   { id: 'mg', name: 'MongoDB',        curl: 'POST /nosql/new',   liveIn: '1.2s' },
+  // Vector — added 2026-05-20. plans.yaml has vector_storage_mb on every
+  // tier (anon=10, hobby=500, pro=10240, team=-1); /vector/new is live.
+  { id: 'vc', name: 'Vector (pgvector)', curl: 'POST /vector/new', liveIn: '1.4s' },
   { id: 'qu', name: 'Queue (NATS)',   curl: 'POST /queue/new',   liveIn: '0.7s' },
   // PB04 P2 (2026-05-21): label was 'Storage (S3)' which implied AWS;
   // the live backend is DO Spaces (S3-compatible API, not AWS S3).
@@ -193,20 +196,27 @@ const PLANS: Plan[] = [
     cta: { label: 'Start pro →', href: ROUTES.signin, variant: 'primary' },
   },
   {
-    // Team tier — not launched yet. Per launch posture (2026-05-15), the
-    // homepage card shows ONLY a "coming soon" placeholder. No price, no
-    // feature list. BugBash P3-09: the CTA is rendered as a 'disabled'
-    // variant so the card shows a "Coming soon" pill instead of an empty
-    // <a href=""> dead button — and the pricing teaser's "talk to us"
-    // line links to a real contact address.
+    // Team tier — launched 2026-05-20 (DOC-REALITY-DELTA sweep).
+    // plans.yaml:375 has team at $199/mo, every limit -1 (unlimited).
+    // CTA goes via mailto: until the assisted-Razorpay flow ships; that
+    // keeps the funnel intact while honoring the support-only onboarding
+    // path for enterprise customers.
     id: 'team',
     name: 'Team',
-    tagline: 'For the engineering org. Coming soon.',
-    price: 'coming soon',
-    freq: '',
-    features: [],
-    cta: { label: 'Coming soon', href: '', variant: 'disabled' },
-    comingSoon: true,
+    tagline: 'For the engineering org. Dedicated infra + SLA + SSO.',
+    price: '$199',
+    freq: '/ mo',
+    features: [
+      'unlimited Postgres · Redis · MongoDB',
+      'unlimited deployments · 50 custom domains',
+      '90-day backups · self-serve restore · RBAC + audit',
+      'SSO/SAML · 99.9% SLA',
+    ],
+    cta: {
+      label: 'Contact sales →',
+      href: 'mailto:support@instanode.dev?subject=Team%20plan%20inquiry',
+      variant: 'secondary',
+    },
   },
 ]
 
@@ -291,7 +301,7 @@ export function MarketingPage() {
             <span className="mkt-accent">with one curl.</span>
           </h1>
           <p className="mkt-hero-sub">
-            Postgres, Redis, MongoDB, queues, storage, webhooks, and deployments.{' '}
+            Postgres, Redis, MongoDB, vectors, queues, storage, webhooks, and deployments.{' '}
             <strong>Provisioned in &lt;2 seconds.</strong>{' '}
             No signup, no Docker, no waitlist.
           </p>

src/pages/PricingPage.test.tsx

@@ -140,15 +140,28 @@ describe('PricingPage — four public tier cards present (M11 regression guard)'
     expect(hobbyPlusCells.length).toBe(0)
   })
 
-  it('paid-tier CTAs are clickable links (not disabled spans) for hobby / pro', () => {
+  it('paid-tier CTAs are clickable links (not disabled spans) for hobby / pro / team', () => {
     renderPage()
-    for (const tier of ['hobby', 'pro']) {
+    // 2026-05-20 DOC-REALITY-DELTA: Team tier launched. CTA now points at
+    // a real mailto: (contact-sales). plans.yaml has team at $199/mo with
+    // every limit -1 (unlimited). If Team flips back to "coming soon",
+    // it'll be a disabled span and this test fails — the regression guard.
+    for (const tier of ['hobby', 'pro', 'team']) {
       const cta = screen.getByTestId(`pricing-cta-${tier}`)
       // <a> with href, not <span aria-disabled>.
       expect(cta.tagName).toBe('A')
       expect(cta.getAttribute('href')).toBeTruthy()
     }
   })
+
+  it('Team tier shows $199/mo (DOC-REALITY-DELTA 2026-05-20 launch)', () => {
+    renderPage()
+    // Team launched per plans.yaml:375 ($199/mo, $1990/yr). Marketing
+    // surface must mirror the registry. Yearly CTA reuses mailto: until
+    // assisted-Razorpay flow ships.
+    const body = document.body.textContent ?? ''
+    expect(body).toContain('$199')
+  })
 })
 
 // ─── 4. B2-P1-1 / B2-P1-2: URL params + anchors (BugBash 2026-05-20) ──────

src/pages/PricingPage.tsx

@@ -80,21 +80,23 @@ const TIERS: {
     ctaHrefYearly: '/app/checkout?plan=pro&frequency=yearly',
     highlighted: true,
   },
-  // Team tier — not launched yet, but PB04 P3 (2026-05-21) surfaced
-  // the price from plans.yaml ($199/mo) so the "soon" badge reads as an
-  // availability label rather than a vaporware signal. The "soon" badge
-  // (from t.comingSoon below) renders next to the tier name; the price
-  // itself stays a real number sourced from plans.yaml. Matches the
-  // existing Hobby/Pro {price, sub} pattern. The CTA stays empty until
-  // launch — interested customers can email support.
+  // Team tier — launched 2026-05-20 (DOC-REALITY-DELTA sweep). Limits are
+  // unlimited across the board; the upsell vs Pro is dedicated infra +
+  // 90-day backup retention + SLA + RBAC + SAML. Per api/plans.yaml:375
+  // ($199/mo, $1990/yr). Razorpay plan IDs are configured server-side.
   {
     key: 'team',
     name: 'Team',
     monthly: { price: '$199', sub: '/ mo' },
-    // No yearly — annual billing wires up at launch.
-    cta: '',
-    ctaHrefMonthly: '',
-    comingSoon: true,
+    // team_yearly: $1990/yr ≈ $165.83/mo (~17% off $199 x 12).
+    yearly: { price: '$165.83', sub: '/ mo billed yearly', saveLabel: 'save $398/yr' },
+    cta: 'Contact sales →',
+    // Team checkout goes through sales rather than self-serve until the
+    // full assisted-onboarding flow ships — same pattern as enterprise
+    // ladders elsewhere. Mailto keeps the funnel intact while we wire
+    // the assisted Razorpay path.
+    ctaHrefMonthly: 'mailto:support@instanode.dev?subject=Team%20plan%20inquiry',
+    ctaHrefYearly: 'mailto:support@instanode.dev?subject=Team%20plan%20inquiry%20(yearly)',
   },
 ]
 
@@ -108,47 +110,54 @@ type Cell =
 // lock-step with the TIERS array above.
 type Row = { label: string; sub?: string; values: [Cell, Cell, Cell, Cell] }
 
-// Team-tier values use { text: '', comingSoon: true } across the board because
-// the tier hasn't launched. Marketing copy keeps Team as "coming soon"
-// until the launch ships; do not list capacity numbers here even if
-// plans.yaml has them — the source of truth for what's advertised is
-// the launch posture, not the registry.
-const SOON: Cell = { text: '', comingSoon: true }
+// UNLIMITED — Team-tier marker. plans.yaml uses -1 sentinel for "no cap"
+// on every Team limit; we render this as the visual "unlimited" cell.
+// Kept as its own helper so a future redesign can swap in a richer
+// visualisation (e.g. lightning-bolt icon) without rewriting every row.
+const UNLIMITED: Cell = 'unlimited'
 
 // Each row has 4 cells: [Anonymous, Hobby, Pro, Team]. Numbers come from
 // api/plans.yaml. 2026-05-15: Hobby Plus column removed (the tier exists
 // for upsell flows but is not part of the public ladder); Pro storage
 // bumped per PRICING-AUDIT-2026-05-15.md (Postgres 5→10 GB, Redis
-// 256→512 MB, Mongo 2→5 GB, object 10→50 GB).
+// 256→512 MB, Mongo 2→5 GB, object 10→50 GB). 2026-05-20: Team tier
+// launched — every limit -1 in plans.yaml becomes 'unlimited' here.
 const ROWS: Row[] = [
-  { label: 'Postgres', values: ['10 MB / 2 conn / 24h TTL', '1 GB / 8 conn',     '10 GB / 20 conn', SOON] },
-  { label: 'Redis',    values: ['5 MB / 24h TTL',           '50 MB',             '512 MB',          SOON] },
-  { label: 'MongoDB',  values: ['5 MB / 2 conn / 24h TTL',  '100 MB / 5 conn',   '5 GB / 20 conn',  SOON] },
+  { label: 'Postgres', values: ['10 MB / 2 conn / 24h TTL', '1 GB / 8 conn',     '10 GB / 20 conn', UNLIMITED] },
+  { label: 'Redis',    values: ['5 MB / 24h TTL',           '50 MB',             '512 MB',          UNLIMITED] },
+  { label: 'MongoDB',  values: ['5 MB / 2 conn / 24h TTL',  '100 MB / 5 conn',   '5 GB / 20 conn',  UNLIMITED] },
   // FIX-G (2026-05-14): the column used to advertise "1 000 / 5 000 / 100k
   // msg/d" but there's no backing queue_messages_per_day field on the
   // plans.yaml side — quota enforcement is on queue_storage_mb. Shipping
   // a per-day-msg counter is real scope and not in flight, so the copy
   // moves to the field we actually enforce. Numbers mirror plans.yaml
   // queue_storage_mb (anonymous=1024, hobby=5120, pro=10240).
-  { label: 'Queue',    sub: 'NATS storage', values: ['1 GB / 24h TTL', '5 GB', '10 GB', SOON] },
+  { label: 'Queue',    sub: 'NATS storage', values: ['1 GB / 24h TTL', '5 GB', '10 GB', UNLIMITED] },
+  // Vector — added 2026-05-20 to surface /vector/new alongside the other
+  // services. plans.yaml vector_storage_mb: anon=10, hobby=500, pro=10240,
+  // team=-1 (unlimited).
+  { label: 'Vector',   sub: 'pgvector', values: ['10 MB / 24h TTL', '500 MB', '10 GB', UNLIMITED] },
   // Anonymous storage: plans.yaml storage_storage_mb=10 (anonymous tier).
   // PB04 P1 (2026-05-21): cell used to render '—' which contradicted the
   // shipped backend — anonymous /storage/new returns a real 10 MB bucket.
-  { label: 'Storage',  values: ['10 MB / 24h TTL',              '512 MB',           '50 GB',          SOON] },
-  { label: 'Webhook stored', values: ['100',                   '1 000',            '10k',            SOON] },
-  { label: 'Deploy apps', values: [{ mark: 'dash' },           '1 small',          '10 medium',      SOON] },
-  { label: 'Domains',  values: [{ mark: 'dash' }, '*.deployment.instanode.dev', 'custom domain', SOON] },
+  { label: 'Storage',  values: ['10 MB / 24h TTL',              '512 MB',           '50 GB',          UNLIMITED] },
+  { label: 'Webhook stored', values: ['100',                   '1 000',            '10k',            UNLIMITED] },
+  // 2026-05-20: dropped "small / medium" pod-size adjectives — there is no
+  // deployment_size field on api/internal/handlers/deploy.go. Numbers map
+  // to plans.yaml deployments_apps (hobby=1, pro=10, team=-1 → unlimited).
+  { label: 'Deploy apps', values: [{ mark: 'dash' },           '1',                '10',             UNLIMITED] },
+  { label: 'Domains',  values: [{ mark: 'dash' }, '*.deployment.instanode.dev', 'custom domain', '50 custom domains'] },
   // Multi-env workflows (stack promotion + vault copy across envs) is a
   // shipped Pro-tier feature: POST /api/v1/stacks/:slug/promote and
   // POST /api/v1/vault/copy are live (RETRO-2026-05-12 §10.17). Hobby is
   // single-env (production only).
-  { label: 'Multi-env workflows', sub: 'stack promotion + vault copy', values: [{ mark: 'dash' }, { mark: 'dash' }, 'dev / staging / prod', SOON] },
-  { label: 'RBAC + audit', values: [{ mark: 'dash' }, { mark: 'dash' }, { mark: 'dash' }, SOON] },
-  { label: 'Vault entries', values: [{ mark: 'dash' }, '20', '200', SOON] },
-  { label: 'Vault envs',    values: [{ mark: 'dash' }, 'production only', 'multi-env', SOON] },
-  { label: 'Backups',       values: [{ mark: 'dash' }, '7-day · no restore', '30-day · 1-click restore', SOON] },
-  { label: 'SSO / SAML', values: [{ mark: 'dash' }, { mark: 'dash' }, { mark: 'dash' }, SOON] },
-  { label: '99.9% SLA',  values: [{ mark: 'dash' }, { mark: 'dash' }, { mark: 'dash' }, SOON] }
+  { label: 'Multi-env workflows', sub: 'stack promotion + vault copy', values: [{ mark: 'dash' }, { mark: 'dash' }, 'dev / staging / prod', 'dev / staging / prod'] },
+  { label: 'RBAC + audit', values: [{ mark: 'dash' }, { mark: 'dash' }, { mark: 'dash' }, { mark: 'check' }] },
+  { label: 'Vault entries', values: [{ mark: 'dash' }, '20', '200', UNLIMITED] },
+  { label: 'Vault envs',    values: [{ mark: 'dash' }, 'production only', 'multi-env', 'multi-env'] },
+  { label: 'Backups',       values: [{ mark: 'dash' }, '7-day · no restore', '30-day · 1-click restore', '90-day · self-serve restore'] },
+  { label: 'SSO / SAML', values: [{ mark: 'dash' }, { mark: 'dash' }, { mark: 'dash' }, { mark: 'check' }] },
+  { label: '99.9% SLA',  values: [{ mark: 'dash' }, { mark: 'dash' }, { mark: 'dash' }, { mark: 'check' }] }
 ]
 
 const FAQ: { q: string; a: string }[] = [