docs: clean up README after supervisor removal

- Drop leftover Supervisor references from README and README-CN
- Trim Configuration Merge Strategy section to a concise paragraph
- Note these doc changes under [Unreleased] in CHANGELOG

Author: guyskk

CHANGELOG.md

@@ -15,6 +15,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - Removed slash command files (supervisor.md, supervisoroff.md)
   - Project rebranded as "Claude Code Configuration Switcher"
 
+### Changed
+
+- Streamlined README/README-CN: trimmed the Configuration Merge Strategy section
+  and removed leftover Supervisor references now that supervisor mode is gone.
+
 ## [0.3.0] - 2026-01-16
 
 ### Added

README-CN.md

@@ -84,26 +84,11 @@ ccc validate --all
 
 ## 配置合并策略
 
-**你的配置永远不会丢失！** ccc 遵循以下原则合并配置：
-
-- **优先级**：用户的 `settings.json` 配置具有最高优先级
-- **提供商配置**：ccc.json 中的提供商特定配置覆盖基础设置
-- **基础设置**：ccc.json 中的 `settings` 字段作为共享模板
-
-#### 保留的内容
-
-- ✅ 用户安装的插件（`enabledPlugins`）- 不会被覆盖
-- ✅ 手动编辑的 `settings.json`（权限、沙箱等）- 完全保留
-- ✅ 用户配置的其他 hooks（PreToolUse、SessionStart 等）- 被尊重
-- ✅ 用户在 `settings.json` 中手动设置的环境变量 - ccc 不会修改
-
-#### 管理的内容
-
-- 🧹 Supervisor Stop hook - 如果存在旧版本的 hook，会自动清理
+运行 `ccc` 时，会读取你已有的 `settings.json` 并与 ccc.json 深度合并。优先级：**用户 `settings.json` > 提供商 > 基础 `settings`**。你手动编辑的配置、插件、hooks 都会被保留；提供商的环境变量通过命令行传递，不会写入 `settings.json`。
 
 #### 环境变量冲突（硬守卫）
 
-Claude Code 的 `settings.json` `env` 字段会**覆盖**ccc 启动 claude 时传入的环境变量（实测已验证）。如果 `settings.json` 中存在会遮蔽 provider env 的 key，切换 provider 会静默失效（用错 base_url / token / model）。
+Claude Code 的 `settings.json` `env` 字段会**覆盖** ccc 启动 claude 时传入的环境变量。如果 `settings.json` 中存在会遮蔽 provider env 的 key，切换 provider 会静默失效（用错 base_url / token / model）。
 
 **当检测到此类冲突时，ccc 会拒绝启动 claude，`ccc validate` 同样会被拒绝。** ccc 不会静默修改你的文件，而是会打印冲突的 key（不打印 value，避免泄露密钥）并告诉你如何修复。**ccc 不会修改你 `settings.json` 的 `env` 字段。**
 
@@ -113,16 +98,6 @@ Claude Code 的 `settings.json` `env` 字段会**覆盖**ccc 启动 claude 时
 
 **修复方法**：从 `~/.claude/settings.json` 的 `env` 中删除这些 key，并把 provider 相关配置改到 `~/.claude/ccc.json` 的 `providers.<name>.env` 中。
 
-#### 工作原理
-
-当你运行 `ccc` 时：
-1. 读取现有的 `settings.json`（如果存在）
-2. 按优先级合并配置：`用户 > 提供商 > 基础`
-3. 提供商的环境变量通过命令行传递（不写入 `settings.json`）
-4. 清理遗留的 Supervisor hooks
-
-这样可以确保你的手动配置永远不会丢失！
-
 ## Patch 命令：用 ccc 替代 `claude` 命令
 
 通过替换系统中的 `claude` 命令，让任何调用 `claude` 的工具都使用配置了提供商的 `ccc` 命令。

README.md

@@ -103,45 +103,20 @@ Config file location, default: `~/.claude/ccc.json`
 
 ### Configuration Merge Strategy
 
-**User settings are preserved.** ccc follows these principles when merging configuration:
-
-1. **Priority**: User's `settings.json` configuration has the highest priority
-2. **Provider settings**: Provider-specific configuration from ccc.json overrides base settings
-3. **Base settings**: The `settings` field in ccc.json serves as a shared template
-
-#### What Gets Preserved
-
-- ✅ User-installed plugins (`enabledPlugins`) - never overwritten
-- ✅ Manual `settings.json` edits (permissions, sandbox, etc.) - fully preserved
-- ✅ User-configured hooks (PreToolUse, SessionStart, etc.) - respected
-- ✅ Environment variables you manually set in settings.json - ccc never edits them
-
-#### What Gets Managed
-
-- 🧹 Supervisor Stop hook - automatically cleaned up if present from previous versions
+When you run `ccc`, your existing `settings.json` is read and deep-merged with ccc.json. Priority: **user `settings.json` > provider > base `settings`**. Your manual edits, plugins, and hooks are preserved; provider env is passed via command line and never written into `settings.json`.
 
 #### Environment Variable Conflicts (Hard Guard)
 
-Claude Code's `settings.json` `env` field **overrides** environment variables passed by ccc when launching claude (empirically verified). If `settings.json` contains keys that would shadow the provider env, switching providers silently fails (wrong base_url / token / model).
+Claude Code's `settings.json` `env` field **overrides** environment variables passed by ccc when launching claude. If `settings.json` shadows provider env, switching silently fails (wrong base_url / token / model).
 
-**ccc refuses to start claude — and refuses to run `ccc validate` — when it detects such conflicts.** Instead of silently editing your file, ccc prints the offending keys (without their values, to avoid leaking secrets) and tells you how to fix it. ccc never modifies the `env` field of your `settings.json`.
+**ccc refuses to start claude — and refuses to run `ccc validate` — when it detects such conflicts.** It prints the offending keys (without values, to avoid leaking secrets) and never modifies your `settings.json` `env` field.
 
 A key is considered conflicting if it:
 - starts with `ANTHROPIC_` or `CLAUDE_`, **or**
 - collides with any key defined in ccc.json's base / provider `env`.
 
 **How to fix:** remove those keys from `~/.claude/settings.json`'s `env` and move provider-related configuration into `providers.<name>.env` in `~/.claude/ccc.json`.
 
-#### How It Works
-
-When you run `ccc`:
-1. Your existing `settings.json` is read (if it exists)
-2. Configuration is merged with priority: `user > provider > base`
-3. Environment variables from provider are passed via command line (not written to settings.json)
-4. Leftover Supervisor hooks are cleaned up
-
-This ensures your manual configuration is never lost!
-
 ```json
 {
   "settings": {