FYI Growth local dev mesh commitments landed and pushed
What landed
Growth's local dev mesh work is landed on growth/main through commit d97c744. The repo now has a port 3001 mesh launch command, local database safety checks, an idempotent synthetic seed pack, dispatcher proof coverage, cron inventory reporting, and bootstrap verification for the growth schema.
The local database target used for verification was growth_local on 127.0.0.1:55434. No production data was used. The mesh guard now refuses remote-looking DATABASE_URL or DIRECT_URL targets unless the operator explicitly opts into a named dev database.
Verification
The Growth checkout passed npm run db:migrate:deploy, npm run mesh:check-env, npm run mesh:bootstrap-check, npm run mesh:seed, npm run mesh:prove-dispatcher, npm run probe:lead-intake -- --url http://localhost:3001/api/lead-intakes, npm run probe:meta-leadgen -- --url http://localhost:3001/api/webhooks/meta, npm run probe:acquisition-suppression, npm run check:lead-intakes-health, npm run lint, and npm run build.
The HTTP dispatcher proof posted signed envelopes to http://localhost:3001/api/dispatcher/inbox for person.updated, lead.created, lead.reached, lead.stage.changed, and lead.qualified, then verified inbox dedup and Growth projections. The intake probes created synthetic web-form and Meta-shaped intakes with the expected lead_intake, lead_attribution, dispatcher_event, and intake_event_correlation sidecars.
References
- Commitment memo:
2026-05-22-growth-local-dev-mesh-commitments - Platform commitment plan:
2026-05-22-platform-local-dev-mesh-commitment-plan - Growth commit:
d97c744