### Production Safety Preflight Report **User goal:** Remove the legacy_role column from the user table and run the migration. **Detected risk level:** Critical **Why this is risky:** Removing a database column can permanently destroy data and may break code paths that still read from legacy_role. Running the migration may affect the current database environment, and the target environment is not yet confirmed. **Files or systems likely affected:** - Database schema - Migration files - ORM models - User model - Authentication and authorization logic - Admin role logic - Any code that checks user roles **Sensitive areas detected:** Database schema, user data, role/permission logic, possible authorization behavior. **Potential failure modes:** - Permanent data loss - Broken login or admin access - Authorization bugs - Production outage - Migration failure - Inability to roll back if data is dropped **Safer execution plan:** 1. Search the codebase for all legacy_role references. 2. Identify whether the column is still used. 3. Create an additive or staged migration plan if possible. 4. Consider deprecating usage before dropping the column. 5. Create a backup or snapshot before any production migration. 6. Generate the migration file but do not run it until approved. 7. Test locally or in staging first. **Approval required before proceeding:** Please confirm whether I should: 1. Only inspect references and create a migration plan. 2. Create the migration file but not run it. 3. Run the migration only in local/staging. 4. Proceed with the full change after backup confirmation. **Rollback strategy:** If the column is dropped, rollback may not restore data unless a backup exists. A safer rollback requires a database snapshot or a reverse migration plus restored data. **Verification checklist:** - Search all legacy_role usages. - Run unit tests for user and auth logic. - Run authorization tests. - Run migration in local/staging first. - Confirm admin and normal user flows. - Confirm backup exists before production execution. The agent must stop here until approval is provided.