docs: neue Config-Felder + Migration-Fixture-Falle in den CLAUDE.md-Dateien

src/ClaudeDo.Worker/CLAUDE.md

@@ -245,14 +245,21 @@ non-obvious, behaviour-changing. A fixed bug is git history, not a finding.
 - `db_path`, `sandbox_root`, `log_root`
 - `worktree_root_strategy` (`sibling` | `central`), `central_worktree_root`
 - `queue_backstop_interval_ms` (30000) — also the gate/throttle recovery timer
-- `signalr_port` (47821), `claude_bin`
+- `signalr_port` (47821), `claude_bin` — `claude_bin` is the one field the UI can write
+  (Settings → Dateien → CLAUDE CLI, hub `GetClaudeBin`/`SetClaudeBin`). It edits the DI-singleton
+  `WorkerConfig` in place *and* persists via `SaveClaudeBin`, so it applies to the next spawn
+  without a restart. Every other field here is hand-edit only.
 - `usage_poll_interval_seconds` (60, clamped to min 15 on load)
 - `online_inbox` — `enabled` (false by default; when false the entire `Online/` stack is not registered), `api_base_url` (must be HTTPS or loopback, validated at startup), `poll_interval_seconds` (60), `zitadel.authority`/`client_id`/`scopes`. The refresh token is **not** in this file — DPAPI-encrypted at `~/.claudeDo/online-inbox.token`.
 
 Per-list config (`list_config` in DB) provides defaults for `model`, `system_prompt`,
-`agent_path`, `max_turns`, `session_skills`; tasks override each individually. `verify_command` is
-list-only — there is no task-level override — and is written via `set_list_config`'s
-`verifyCommand` parameter (`ConfigMcpTools`), the only writer besides the UI's list config editor.
+`agent_path`, `max_turns`, `session_skills`, `permission_mode`; tasks override each individually
+(resolution lives in `EffectiveRunConfigResolver`, so `TaskRunner` and
+`get_effective_run_config` can't drift). `verify_command` and `serialize_on_file_overlap` are
+list-only — no task-level override. `verify_command` is written via `set_list_config`'s
+`verifyCommand` parameter (`ConfigMcpTools`) and the UI's list config editor;
+`serialize_on_file_overlap` and `permission_mode` are UI-only (`set_list_config` preserves but
+does not expose them).
 
 ## Notes