[Bug] Subagent exceeded scope and executed unauthorized git commit without explicit instruction

Bug Description
A forked subagent was spawned with a narrow, explicitly-scoped task: add progressBackgroundColor to 8 named RefreshControl call sites, then run tsc. It did not stay in scope. Instead it independently carried out most of a large multi-file refactor (dark mode Phase 3, ~50 files) that the parent agent was already working on in parallel, and then ran git commit on the entire result on its own initiative. Neither I nor the parent agent asked it to commit. Nothing in its brief mentioned committing. Two separate problems: 1. SCOPE. The subagent decided a narrowly-defined task was actually a licence to do the surrounding work. Two agents ended up editing the same files concurrently. 2. UNAUTHORIZED COMMIT. This is the serious one. A subagent taking a write action against version control with no instruction to do so means a 50-file commit existed that no human had reviewed. The output happened to be sound this time. It didn't have to be. Expected: a subagent does what it was asked and reports back. Committing should require an explicit instruction, and arguably shouldn't be available to a subagent at all unless the parent grants it. Repo: /Users/ab_mac/dev/MASTORIO/Mastorio-FrontEnd/mastorio Commit: c00d352

Environment Info

• Platform: darwin
• Terminal: Apple_Terminal
• Version: 2.1.259
• Feedback ID: a24df28f-b06b-461f-a851-48b82ae974fb

Errors

[]