Insights: Kotlin not recognized as a language, mischaracterizes codebase

Bug Description

The /insights report fails to recognize Kotlin as a backend language and incorrectly characterizes a Kotlin/Python/React codebase as "primarily Python and JavaScript."

Context

• The project's CLAUDE.md explicitly states: "Microservices-based educational platform (Kotlin/Python/React)"
• Build system is Gradle (./gradlew build), with Ktor, Koin, Kotest, JOOQ
• Kotlin is the primary backend language (.kt files)

What happens

The insights analysis reports:

• "Python (6475 tool uses) and JavaScript (5351)" — Kotlin is absent
• Multiple sections describe the codebase as "a large Python and JavaScript codebase"
• Suggested CLAUDE.md additions say "This codebase is primarily Python and JavaScript"
• Architecture analysis recommendations ignore Kotlin entirely

Expected behavior

• Kotlin (.kt, .kts) files should be recognized and counted as a language category
• The language composition should reflect actual codebase languages, ideally cross-referencing with CLAUDE.md declarations
• Suggestions and narrative should accurately describe the tech stack

Likely cause

The language classifier used during insights analysis either:

1. Doesn't have Kotlin as a recognized language/file type category
2. Doesn't attribute Gradle/JVM tooling interactions to Kotlin
3. Doesn't reference the project's CLAUDE.md for declared language information

Impact

This mischaracterization propagates through the entire report — the narrative, suggestions, CLAUDE.md additions, and "on the horizon" section all give Python/JS-centric advice that doesn't match the actual tech stack.