[Feature Request] Expand `/usage` analytics to enable profiling of user optimizations for Claude Code

Description

Given how much we're randomly adding to Claude Code these days, it would not be surprising if we end up creating messes of our own that hurt Claude Code's performance.

It may be worth it to build out /usage and its underlying systems more to support better analysis of how your various modifications to Claude Code are really affecting performance, both in the day to day, and also in terms of how often results meet expectations vs. baseline for Claude Code, or for people with similar use cases.

Automated local profiling could also automatically raise issues about config that users of Claude Code just hadn't thought about.

Environment Info

• Platform: darwin
• Terminal: ghostty
• Version: 2.1.136
• Feedback ID: 76313038-cc47-4b5e-8374-cc8eaace0bd6