release: dev → prod — enterprise foundation + B2C hardening train

[teetangh]

Production release following the #653 precedent. 526 commits, the bulk being:

• Enterprise foundation (Enterprise foundation — org CRUD, billing modes, SSO, dashboard #655): the full enterprise subsystem — orgs, contracts, programs, billing, ledger, payouts, compliance — plus the v2 mega-audit lifecycle/money-safety layer and the Enterprise state-machine and concurrency hardening: CAS transitions, optimistic locking, Serializable org PATCH, cron locks, webhook dead-letter #825/Money correctness (PR-B, stacked): overage basePaise restore/recarve + GST gross-up test coverage #826/B2C hardening (PR-C, stacked): slot mis-binding, double-booking guard, checkout idempotency, reconciliation env fix #838 state-machine hardening.
• B2C hardening train (fix: B2C CAS transition map — approval/decline/expiry/completion guards + #677 PM-1 closeout #845–test+docs: real-API chaos categories 07/09 + ADR 14 async posture + audit refresh #848): consumer-side CAS transition map ([B2C][SUBSCRIPTIONS] Approval transition read-then-decide race in subscription route #836), checkout lock budgets + tentative TTL + waitlist CAS ([SECURITY][B2C] Unbounded text fields + missing rate limiters on consumer mutation routes #831–[B2C][WAITLIST] Slot assignment runs outside the checkout transaction; partial multi-session enrollment on mid-loop failure #834), exact timezone offsets + canonical overnight resolution + CHECK-constraint sidecar (Harden date/timezone handling — 7 high-risk areas (Option C) #503/Booking subsystem production-readiness audit — master tracker #676), real-API chaos categories + ADR 14 async posture.
• Dev-green fixes (fix: RSC boundary serialization + chaos CI skip guard #851): RSC boundary serialization (toPlain), chaos CI skip guard, Upstash secrets for all 30 job workflows that were crashing post-Enterprise foundation — org CRUD, billing modes, SSO, dashboard #655.
• Capacity follow-through (chore: k6 smoke test + serverless pg pool-size knob #852): k6 smoke suite + PG_POOL_MAX serverless pool knob.

Pre-flight verified: production's DATABASE_URL resolves to the same Supabase project (postgres.pzmbxqdgibfkhjwzeprf) that received today's schema push + ledger triggers, so deploy-after-push ordering holds. PG_POOL_MAX=1 set in the Netlify production context alongside this release.

Dev at merge time: required checks green, 1337/1337 Jest, race-condition workflow green, all seven implemented chaos scenarios passing, three previously failing crons re-dispatched green.

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for familiarise ready!

Name	Link
🔨 Latest commit	fcf52b6
🔍 Latest deploy log	https://app.netlify.com/projects/familiarise/deploys/6a2a6bc46e756600081d6b70
😎 Deploy Preview	https://deploy-preview-853--familiarise.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 40 (🔴 down 18 from production) Accessibility: 90 (no change from production) Best Practices: 83 (🔴 down 9 from production) SEO: 83 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: b0ef8829-3600-49ae-a14c-36fbf82de443

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dev

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request introduces extensive updates to enterprise billing, compliance, and multi-tenant features, including new documentation, configuration updates, and a comprehensive suite of regression tests for GST splits, TDS calculations, SCIM authentication, and anti-lockout gates. It also integrates DPDP Act consent checks into Stream chat user upserts and adds organization tagging to Stream channels and meetings. The code review feedback highlights several improvement opportunities: replacing the platform-dependent shell grep helper in the audit actions test with a native Node.js implementation, restoring overridden global.fetch and process.env values in test teardowns to prevent test pollution, and optimizing the N+1 query pattern in the batch Stream user upsert by batch-fetching consent artifacts.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The rg function uses execSync to run grep, which is platform-dependent and will fail on Windows environments where grep is not available in the shell. To ensure local tests can run reliably across all developer platforms (macOS, Linux, Windows), consider implementing a native Node.js recursive file search using fs.readdirSync and fs.readFileSync with a regular expression.

function rg(pattern: string, paths: string[]): string {
  const fs = require("fs");
  const regexStr = pattern.replace("[[:space:]]*", "\\s*");
  const regex = new RegExp(regexStr);
  const matches: string[] = [];
  function search(dir: string) {
    const files = fs.readdirSync(dir);
    for (const file of files) {
      const fullPath = path.join(dir, file);
      const stat = fs.statSync(fullPath);
      if (stat.isDirectory()) {
        search(fullPath);
      } else if (stat.isFile() && /\.(ts|tsx|js|jsx)$/.test(file)) {
        const content = fs.readFileSync(fullPath, "utf8");
        const lines = content.split("\n");
        for (let i = 0; i < lines.length; i++) {
          if (regex.test(lines[i])) {
            matches.push(path.relative(REPO_ROOT, fullPath) + ":" + (i + 1) + ":" + lines[i]);
          }
        } 
      }
    }
  }
  for (const p of paths) {
    const fullPath = path.resolve(REPO_ROOT, p);
    if (fs.existsSync(fullPath)) {
      const stat = fs.statSync(fullPath);
      if (stat.isDirectory()) {
        search(fullPath);
      } else {
        const content = fs.readFileSync(fullPath, "utf8");
        const lines = content.split("\n");
        for (let i = 0; i < lines.length; i++) {
          if (regex.test(lines[i])) {
            matches.push(path.relative(REPO_ROOT, fullPath) + ":" + (i + 1) + ":" + lines[i]);
          }
        }
      }
    }
  }
  return matches.join("\n");
}

[gemini-code-assist]

Manually overriding global.fetch without restoring it can leak mock behavior to other test suites running in the same process, leading to flaky tests or unexpected failures. Consider saving the original global.fetch and restoring it in the afterEach block.

  const ORIGINAL_FETCH = global.fetch;

  afterEach(() => {
    process.env = OLD_ENV;
    global.fetch = ORIGINAL_FETCH;
    jest.restoreAllMocks();
  });

[gemini-code-assist]

Modifying process.env and overriding global.fetch without restoring them in an afterEach or afterAll block can pollute other test suites in the same test run. Consider saving their original values and restoring them after each test.

const ORIGINAL_FETCH = global.fetch;
const ORIGINAL_ENV = { ...process.env };

beforeEach(() => {
  jest.clearAllMocks();
  process.env.RAZORPAY_KEY_ID = "k";
  process.env.RAZORPAY_KEY_SECRET = "s";
  process.env.RAZORPAYX_ACCOUNT_NUMBER = "acc";
  (global as unknown as { fetch: unknown }).fetch = jest
    .fn()
    .mockResolvedValue({ ok: true, json: async () => ({ id: "pout_x" }) });
  cp.updateMany.mockResolvedValue({ count: 1 }); // claim APPROVED→PROCESSING
  ce.updateMany.mockResolvedValue({ count: 0 });
});

afterEach(() => {
  global.fetch = ORIGINAL_FETCH;
  process.env = ORIGINAL_ENV;
});

[gemini-code-assist]

Executing checkConsent individually for each user in a loop using Promise.all results in an N+1 query pattern. If the batch size of users is large, this will cause significant database load and increased latency. Consider optimizing this by batch-fetching the active consent artifacts for all user IDs in a single query.