Data integrity and migrations
Development and production share a database
Local runs, previews or agent sessions point at the production connection string.
Termsmigration (a scripted change to the database schema that ships with a release and should be reversible) · staging environment (a copy of production, without customer data, where release candidates are tested) · protected branch (the git branch that cannot be pushed to directly and is the only source of production deploys)
criticalseverity if found in a releasesources verified 2026-09-21
Why AI-assisted code produces it
After the July 2025 deletion the platform announced separate development and production databases as the fix; before that, one database was the default.
After the deletion, the platform announced separate development and production databases, a planning-only mode, forced documentation checks and one-click restore.
Source: The Register, 2025-07-22 · verified 2026-09-21
How we detect it
Read every environment's connection configuration, including tools and agents.
Most associated with
Tools: Cursor, GitHub Copilot, Claude Code, Windsurf, Lovable, Bolt
Checklist items that catch it
Development and production data stores are separate
manual Read the connection configuration for every environment and every tool or agent with database access.
No development, preview or agent environment holds a production connection string.
Dots: Starter, Growth, Scale. The item runs on every release for the plans marked.
More in data integrity and migrations
- critical
- high
- high
- high
Check your codebase for this pattern
The coverage audit lists which catalogue patterns apply to your critical flows. 5 business days, $1,200, credited to a first month.