learn-taste: support non-standard Claude Code config paths (e.g. CLAUDE_CONFIG_DIR)

Context: Some projects use a shared Claude Code config directory at a non-standard path (e.g. ~/Developer/Work/Busie/.claude/) instead of the default ~/.claude/.

Problem: The learn-taste command hardcodes session discovery to ~/.claude/projects/. For Busie's fe-main project, this meant only 11 sessions were found in the standard location, while 33 sessions existed at ~/Developer/Work/Busie/.claude/projects/-Users-jasonschulz-Developer-Work-Busie-fe-main/.

Workaround applied: Symlinked the non-standard sessions into the standard location:

ln -sf ~/Developer/Work/Busie/.claude/projects/-Users-jasonschulz-Developer-Work-Busie-fe-main/* ~/.claude/projects/-Users-jasonschulz-Developer-Work-Busie-fe-main/

Suggested fix: Add support for discovering sessions from non-standard Claude Code config directories. Options:

• Detect CLAUDE_CONFIG_DIR environment variable if set
• Add a --claude-config-dir flag to learn-taste
• Scan for .claude/projects/ relative to the project root (e.g. ../../.claude/projects/ for monorepo sub-projects)

This would make taste learning work out-of-the-box for teams using shared or project-scoped Claude Code configurations.

Commencez par la logique de découverte des sessions de la commande learn-taste et suivez la manière dont elle sélectionne actuellement ~/.claude/projects/. Comparez le comportement avec CLAUDE_CONFIG_DIR, une option --claude-config-dir et les chemins .claude/projects/ relatifs au projet ; c'est terminé lorsque les sessions provenant d'emplacements non standard pris en charge sont trouvées sans le contournement par lien symbolique.