database-migration-script-generatorlisted

## Purpose & When-To-Use **Trigger conditions:** - Evolving database schema for application updates - Performing data migrations with business logic transformations - Implementing zero-downtime deployments requiring schema changes - Standardizing migration workflows across teams - Migrating between database versions or platforms - Adding indexes, constraints, or partitioning to existing tables **Not for:** - Initial database schema creation (use ORM models or DDL scripts) - One-off data fixes (use direct SQL with transaction safety) - Database backups or recovery operations - Cross-database data replication (use ETL tools) --- ## Pre-Checks **Time normalization:** - Compute `NOW_ET` using NIST/time.gov semantics (America/New_York, ISO-8601) - Use `NOW_ET` for all citation access dates **Input validation:** - `migration_tool` must be one of: liquibase, flyway, alembic - `database` must be one of: postgresql, mysql, sqlserver, oracle - `migration_type` must be one of: schema, data, hybrid - `downtime_allowed` must be boolean (true/false) - `migration_description` must be non-empty and descriptive **Source freshness:** - Liquibase docs must be accessible [accessed 2025-10-26T03:51:54-04:00](https://docs.liquibase.com/change-types/home.html) - Flyway docs must be accessible [accessed 2025-10-26T03:51:54-04:00](https://flywaydb.org/documentation/concepts/migrations) - Alembic docs must be accessible [accessed 2025-10-26T03:51:54-04:00](https://alembic.sqlalchemy.org/en/late