Context A Node.js application modifies the database schema manually in production, causing inconsistencies between environments and no rollback capability. The Problem There is no migration tracking, so schema changes are applied inconsistently across development, staging, and production environments. Constraints Use the node-pg-migrate or Knex migration system. Write a versioned up and down migration for adding a new table. Integrate migration execution into the application startup sequence. Document how to roll back a migration. Expected Deliverable A Node.js project with a versioned migration system, at least one up/down migration pair, and startup-time migration execution.