[FEATURE] /insights report over-indexes on single examples, reducing overall value

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

The /insights feature is genuinely useful for understanding usage patterns, but the generated report has a repetition problem that dilutes its value.

Issue:
A single incident (editing the wrong file due to similar naming) appeared in 4 separate sections:

• Friction Analysis - as an example
• CLAUDE.md Additions - as rationale
• Usage Patterns - as a suggestion
• Fun Ending - as the headline anecdote

This over-representation makes one minor incident feel like my primary problem, overshadowing other significant friction points that only got single mentions:

• Sessions ending mid-implementation (many partially achieved outcomes)
• TypeScript build errors requiring troubleshooting
• Incorrect initial API assumptions requiring pivots
• Export errors causing deployment failures

Environment:
Claude Code CLI
~3000 sessions analyzed

Proposed Solution

• Deduplicate examples across sections - if an incident is used in Friction Analysis, don't reuse it in Usage Patterns and Fun Ending
• Distribute examples more evenly across identified friction categories
• Consider weighting by frequency/impact rather than narrative convenience

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_