Insights: PHP files not detected in language breakdown

Bug Description

The /insights command's language analysis fails to detect PHP file interactions. In a large PHP-dominant codebase (Magento 1 + Laravel/Lumen APIs), the report claimed:

"Markdown (86) and YAML (10) dominate over traditional programming languages, with only a single Python file touched."

This is inaccurate — the vast majority of edits across 50+ sessions were to .php files (controllers, models, tests, etc.), yet PHP was entirely absent from the language breakdown.

Impact

The missing language data cascades into incorrect conclusions throughout the report:

• Workflow is characterized as "documentation-centric" instead of PHP application development
• Suggestions are skewed toward documentation/config tooling rather than PHP development workflows
• The "interaction style" narrative misrepresents the user's actual work

Expected Behavior

PHP files (.php) should be detected and counted in the language breakdown, and the narrative sections should reflect the actual primary language being used.

Environment

• Claude Code CLI
• Repository: Large PHP codebase (Magento 1, Laravel/Lumen APIs, PHPUnit tests)
• ~50 analyzed sessions, 534 messages, 25 commits