Newly created ~/.claude/settings.json is ignored until restart — permission rules silently inert

If ~/.claude/settings.json does not exist when a session starts, creating it mid-session has no effect: the settings watcher only watches directories that already had a settings file at startup. Practical impact: the agent writes permission allow rules at the user's request, both believe prompts will stop, and the user sits through dozens more permission prompts until someone realizes a full restart is required to load the file.

Requests:

1. Watch for settings-file creation, not only modification.
2. Failing that, surface explicit feedback when a settings file appears mid-session ("settings file created — restart or open /hooks to load").

Environment: macOS 26.5 (arm64), Claude Desktop 1.9659.2 with bundled Claude Code; GitHub integration connected.

Related settings-loading issues, not duplicates: #58443 (symlinked settings.json regression), #64699 (hooks stop firing after editing settings.local.json) — this issue is specifically the file-creation case: a settings.json born mid-session is never watched.