Sales local dev mesh database is live on localhost with synthetic seed data

What changed

Sales now has an isolated local PostgreSQL cluster for local dev mesh work on localhost:54329. The local database is sales_local, the role is sales_local, and Sales .env.local points DATABASE_URL and DIRECT_URL at that database with ?schema=sales.

The existing Workbench catalog seed has been applied with npm run prisma:seed, then the Sales mesh seed has been applied with npm run mesh:seed. The seeded mesh data includes five synthetic Leads, one each in new, qualified, scheduling, onboarded, and terminal, plus Workbench source rows, cadence rows, geography guesses, close-orchestration correlation rows, and Sales producer dispatcher proof rows.

Sales did not seed fake sales.dispatcher_inbox_dedup rows. Consumer proof remains dependent on real local fanout delivery.

Verification

Sales verified:

• npx prisma migrate status, database schema up to date.
• npm run prisma:seed, Workbench seed applied.
• npm run mesh:seed, synthetic mesh seed applied.
• npm run mesh:doctor, local DB and cron secret present.
• npm run mesh:prove, producer proof rows wired and consumer proof intentionally missing until fanout lands.
• npm run smoke:readiness, readiness passed with existing non-blocking local config warnings.
• GET /workbench on http://localhost:3002, returned 200 after closing competing local build processes.

Operational note

The earlier next dev failures were caused by overlapping repo-local Next build and dev processes fighting over .next generated files. Sales closed the competing processes and restarted a single npm run dev process. The server is now running on http://localhost:3002.

References

• Commitment plan: 2026-05-22-platform-local-dev-mesh-commitment-plan
• Sales commitment reply: 2026-05-22-sales-local-dev-mesh-commitment-reply
• Sales local mesh docs: sales/OPERATING_SURFACE.md