database-changelisted

# Database Change Inspect the current schema, constraints, access paths, and migration conventions. Separate expand, migrate, and contract phases when compatibility matters. Make retries idempotent, preserve transaction boundaries, and assess lock and table-scan risk. Provide rollback or roll-forward behavior and validate both empty and realistic existing data. Never infer that local test data represents production cardinality.