Insights report incorrectly claims 'No Captured User Instructions' when CLAUDE.md exists

Bug Description

The /insights command generates a report that claims the user has "No Captured User Instructions" even when extensive CLAUDE.md files are present and actively loaded into the system prompt.

Evidence

User has 14 CLAUDE.md files configured:

• ~/.claude/CLAUDE.md (global instructions)
• ~/Documents/CLAUDE.md (project root)
• 12+ additional project-specific CLAUDE.md files

All files are properly loaded and visible in the system prompt during sessions.

What the report says

"You haven't set up persistent instructions for Claude, which means you may be re-explaining preferences or context repeatedly across your 3,200+ sessions. Adding a CLAUDE.md or user preferences could streamline recurring tasks."

This is factually incorrect for this user.

Expected behavior

The insights analysis should detect the presence of CLAUDE.md files and not recommend creating them when they already exist.

Possible causes

1. Insights analysis checks for CLAUDE.md in a different location than where Claude Code actually loads them from
2. The session metadata doesn't include information about loaded CLAUDE.md files
3. The analysis logic doesn't have access to the filesystem to verify file existence

Environment

• Claude Code CLI
• macOS