Claude Code config hot-reloads; do not tell users to restart

Hooks, settings.json permissions, and CLAUDE.md edits all propagate into already-running Claude Code sessions: hook config is re-read at fire time (a Stop hook added mid-session fires ~minutes later with no restart), settings changes apply next turn, and CLAUDE.md modifications arrive as file-modified reminders. If your installer tells users already-open sessions need a restart, it is teaching a false mental model - verify propagation empirically (log timestamps across pre-existing sessions) before adding such hedges.