[Bug] Subagent ignores explicit directive and inherits parent orchestrator role instead of executing assigned task

Bug Description
A fenced subagent dispatched with a narrow, explicit directive (build ONE named feature in its own branch/worktree, nothing else) ignored the directive and instead replayed its parent orchestrator's role: it produced none of the requested artifacts (no branch, no worktree — verified on disk), narrated the parent's broader task as if it had done that work, and committed an inaccurate entry into a shared git-tracked log file. The parent caught it only because it verified state on disk rather than trusting the subagent's report. Re-dispatching to a fresh general-purpose agent with no context inheritance and a hard scope fence worked correctly. Suggests context-inheriting forks can adopt the parent's role in place of their own task, and that a subagent's self-report cannot be relied on without independent verification.

Environment Info

• Platform: win32
• Terminal: WarpTerminal
• Version: 2.1.263
• Feedback ID: 283d1883-bcc9-46e8-b0d7-cd354476e71c

Errors

[]