chore(db): publish flattened dist/schema.prisma for external consumers (#2677)

The native v7 multi-file schema refactor (c58045f) removed the legacy
combine-schemas step that produced a single-file schema in dist/. That
worked inside the monorepo (apps read prisma/schema/ directly), but
broke external consumers like comp-private's enterprise-api/cx-dashboard/
framework-editor/trust apps, which all run

  cp ../../node_modules/@trycompai/db/dist/schema.prisma prisma/schema.prisma

at build time. The 2.0.1 publish was the first to consume the post-
refactor build, and shipped without dist/schema.prisma — breaking every
consumer's db:getschema script and blocking SALE-49's comp-private PR.

Add scripts/build-dist-schema.js: concatenates prisma/schema/*.prisma
(schema.prisma generator+datasource first, models alphabetically after)
into dist/schema.prisma during build. Output matches the v2.0.0 shape
exactly so consumers don't need to change. Wire into the build script
after tsc.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: Marfuen

packages/db/package.json

@@ -44,7 +44,7 @@
     },
     "scripts": {
         "backfill:framework-versions": "bun src/scripts/backfill-framework-versions.ts",
-        "build": "rm -rf dist && node scripts/generate-prisma-client-js.js && tsc",
+        "build": "rm -rf dist && node scripts/generate-prisma-client-js.js && tsc && node scripts/build-dist-schema.js",
         "check-types": "tsc --noEmit",
         "db:generate": "node scripts/generate-prisma-client-js.js",
         "db:migrate": "prisma migrate dev",

packages/db/scripts/build-dist-schema.js

@@ -0,0 +1,37 @@
+#!/usr/bin/env node
+/**
+ * Builds dist/schema.prisma from prisma/schema/*.prisma so consumers that
+ * pull from the published @trycompai/db package (e.g. comp-private apps,
+ * which run `cp .../@trycompai/db/dist/schema.prisma prisma/schema.prisma`)
+ * receive a single, ready-to-use schema.
+ *
+ * Native multi-file Prisma v7 schemas live in `prisma/schema/`. Inside the
+ * monorepo, consumers can read those files directly. Outside the monorepo
+ * they cannot, so we ship a flattened copy in dist/.
+ */
+const fs = require('fs');
+const path = require('path');
+
+const root = path.join(__dirname, '..');
+const schemaDir = path.join(root, 'prisma/schema');
+const distDir = path.join(root, 'dist');
+const outFile = path.join(distDir, 'schema.prisma');
+
+if (!fs.existsSync(distDir)) fs.mkdirSync(distDir, { recursive: true });
+
+// schema.prisma (generator + datasource) must come first; everything else
+// after, in deterministic order.
+const all = fs.readdirSync(schemaDir).filter((f) => f.endsWith('.prisma'));
+const ordered = [
+  'schema.prisma',
+  ...all.filter((f) => f !== 'schema.prisma').sort(),
+];
+
+const parts = ordered.map((file) => {
+  const body = fs.readFileSync(path.join(schemaDir, file), 'utf8').trimEnd();
+  if (file === 'schema.prisma') return body;
+  return `// ===== ${file} =====\n${body}`;
+});
+
+fs.writeFileSync(outFile, parts.join('\n\n') + '\n');
+console.log(`[build-dist-schema] wrote ${outFile} (${ordered.length} files)`);