Feature request: SubagentStart hook stdin should carry the Task tool description for subagent attribution

Building a fleet dashboard driven by Claude Code hook events (SubagentStart/Stop, Pre/PostToolUse). The SubagentStart hook stdin carries agent_id/session_id but NOT the Task tool invocation's description argument that spawned the subagent — so a dashboard cannot truthfully show WHAT a subagent was asked to do. Correlating via the parent's PreToolUse (which does carry the description) is structurally unsound: it fires before the subagent/agent_id exists, and FIFO session-level pairing misattributes descriptions whenever multiple subagents spawn in parallel (the standard fan-out pattern). Request: include the spawning Task tool's description (and ideally subagent_type) in SubagentStart hook stdin. This is orchestrator-authored structured data (a tool arg), not model output, so it is safe for hooks to expose.