Feature: Break down Bash tool usage by command type in /insights

Feature Request

Problem

The /insights command aggregates all Bash tool usage into a single "Bash" category. This makes it hard to understand where time and tokens are actually being spent — e.g., how much goes to build system commands (bazel), version control (git), package management (npm/pnpm), vs. other shell operations.

Proposed Solution

Categorize Bash tool calls by command type in /insights reports. Each Bash invocation already includes a description field — this metadata (or the command itself) could be used to bucket usage into categories like:

• Build (bazel, make, gradle, cargo, etc.)
• Version control (git, gh)
• Package management (npm, pnpm, pip, brew)
• Other

The /insights output could then show something like:

Bash usage breakdown:
  bazel    — 45% (build/test)
  git      — 30% (status/diff/commit)
  npm      — 15% (install/test)
  other    — 10%

Why This Matters

In a monorepo with Bazel, a significant portion of Bash tool usage goes to builds and tests. Understanding this breakdown would help users:

• Identify if they're spending too many tokens on repeated build failures
• See whether an MCP integration (e.g., for their build system) would be worth setting up
• Get more actionable suggestions from /insights