AZ610: Not a development database

rowfence push (and rowfence dev, and the MCP server's push) changes a policy straight away, so it only changes a development database: one marked as one. The first push to a database that never had a policy marks it. This one has a policy and no mark (or had one: rowfence remove leaves it as it was, marked or not): if it is production, it takes migrations (rowfence migrate, then your migration tool); if it is a development database (say, one your migrations set up), mark it once with rowfence push --development.

Reported by the command, against a database.