Insights report doesn't distinguish between separate projects

Description

The /insights report merges all sessions into a single project narrative, even when the user is actively building multiple distinct applications across different repositories.

Example

I'm building two separate apps across different repos:

• App A — A PWA + Expo mobile app (two repos)
• App B — A separate app with different purpose and architecture

The insights report treated everything as one project (App B), never mentioning App A by name. The project areas section listed "App B - Core Features" but had no equivalent area for App A, despite significant session time spent on it.

Expected behavior

Insights should recognize distinct repositories/working directories as separate projects and:

• Name each project separately in the narrative
• Show per-project session counts and patterns
• Avoid attributing one project's patterns to another

Why it matters

The usage pattern suggestions (debugging loops, build checks, etc.) are still generally valid, but the narrative misidentifying projects makes the report feel less trustworthy and harder to act on. Users working on multiple projects — which is common — should see their work accurately reflected.

Environment

• Claude Code CLI
• macOS