CLAUDE.md is not hot-reloaded when modified during a session

Description

When a user modifies ~/.claude/CLAUDE.md (or a project-level CLAUDE.md) during an active Claude Code session, the changes are not picked up until a new session is started.

Expected behavior

Changes to CLAUDE.md should be hot-reloaded during the session, similar to how SKILL.md files in skills directories are watched for live changes.

Actual behavior

The CLAUDE.md content is read once at session startup and remains static for the duration of the session. Any edits made during the session (even by Claude itself) are not reflected in the active context.

Steps to reproduce

1. Start a Claude Code session
2. Edit ~/.claude/CLAUDE.md (add a distinctive line)
3. Ask Claude if it can see the new line — it cannot
4. Start a new session — the new line is now visible

Why this matters

During a session, Claude may add rules to CLAUDE.md based on user feedback (e.g., "remember to always use GET to inspect API state"). The user expects these to take effect immediately, but they don't until the next session. This creates a confusing gap where Claude writes the rule but doesn't follow it in the same session unless it independently remembers the conversation context.

Context

• SKILL.md files ARE hot-reloaded (documented: "Skills directories are watched for live changes to SKILL.md — no restart needed for skill edits")
• CLAUDE.md files are NOT hot-reloaded (observed behavior)
• This asymmetry is unexpected