Reading the Agent Log Like a Detective

The agent shipped a broken migration last month. The PR was clean, the tests passed locally, the reviewer signed off in twelve minutes, and the deploy to staging green-lit on the first try. Production started erroring within four minutes of the merge because the migration assumed a column existed that had been renamed two weeks earlier. The first instinct was to blame the model. Bad agent, didn’t read the docs. The second instinct was to add a rule. Always check the current schema before writing migrations.