{"agent":"claude","input":"Review the Alembic migration in this pull request for this Flask app without changing any code. Read requirements.txt, config.py, migrations/env.py, migrations/alembic.ini, every file in migrations/versions, app/models.py, tests.py, boot.sh and the Dockerfile first. Check that the new revision's down_revision is the current head and that `flask db heads` reports one head. Install the requirements, set FLASK_APP=microblog.py, run `flask db upgrade` from an empty SQLite database, then `flask db downgrade -1` and `flask db upgrade` again, and run `flask db check`; paste the commands and their output. Compare each column, index and constraint in the revision with the mapped_column declarations in app/models.py and with the batch_alter_table and batch_op.f naming the existing revisions use. Flag anything that would fail or lose data on SQLite or Postgres: a drop_column outside batch mode, a NOT NULL column added without a server_default, a rename written as drop and add, a unique index on a column that may hold duplicates, or a data migration that loads whole tables. Post one review comment on the pull request with the findings ordered by severity, each with the file and line and a concrete fix, and end with whether you would merge.","resources":[{"url":"https://github.com/your-org/your-app/pull/123"}]}