{"agent":"claude","input":"Review the Ecto migrations added in the open pull request. Read mix.exs's aliases, config/config.exs, lib/hexpm/release_tasks.ex and the ten most recent files in priv/repo/migrations for the project's conventions: reversible change blocks with from:, up and down when a file backfills with execute, and @disable_ddl_transaction with @disable_migration_lock and concurrently: true for indexes. Start a Postgres of the version the CI workflow uses with the pg_trgm and pgcrypto modules, run mix ecto.create and mix ecto.load, migrate to the pull request's base, then run the new migrations with --log-migrations-sql while a second connection watches pg_locks, then mix ecto.rollback --step for the number of new files and mix ecto.migrate again. Run mix test for the contexts the schema touches. Comment on the pull request for any statement that locks or rewrites a populated table, builds an index without concurrently and the two module attributes, adds a non-null column without a default, backfills without a down, changes a type in place, or cannot run safely from several app instances at once, each with the safe sequence from the repository's own recent migrations. Do not change the migrations yourself.","resources":[{"url":"https://github.com/your-org/your-phoenix-app/pull/123"}]}