settings: the four per-feature files .wikitool-remotes/-telemetry/-upload/-tasks.json move into the three tiers and disappear; new command config migrate; 10.0.0-beta.1 (#208)

Files changed:
- .gitignore
- AGENTS.md
- CHANGES.md
- INSTALL.md
- VERSION
- docs/explanation/knowledge-and-commitment.md
- docs/explanation/telemetry-and-evaluation.md
- docs/explanation/why-gates-are-code.md
- docs/how-to/run-the-weekly-review.md
- docs/how-to/set-up-the-mcp-server.md
- docs/how-to/trace-and-score-sessions.md
- docs/how-to/troubleshoot.md
- docs/reference/commands/README.md
- docs/reference/commands/configuration.md
- docs/reference/commands/finding-and-checking.md
- docs/reference/commands/git.md
- docs/reference/commands/instance-health.md
- docs/reference/commands/pages.md
- docs/reference/commands/raw-material-and-uploads.md
- docs/reference/configuration.md
- docs/reference/exit-codes.md
- instructions/dev/doc-pull-through.md
- instructions/dev/tracker-testing.md
- instructions/gates.md
- instructions/ingest-queue.md
- instructions/mcp-read-server.md
- instructions/migrate-corpus.md
- instructions/migrations/10.0.0-settings-tiers.md
- instructions/setup-instance.md
- raw/CONTRACT.md
- reports/CONTRACT.md
- tools/CONTRACT.md
- tools/README.md
- tools/bugreport.py
- tools/chemenu/cli_contract.py
- tools/chemenu/commands/_util.py
- tools/chemenu/commands/config_cmd.py
- tools/chemenu/commands/docs_verify.py
- tools/chemenu/commands/doctor.py
- tools/chemenu/commands/export_cmd.py
- tools/chemenu/commands/git_publish.py
- tools/chemenu/commands/new_page.py
- tools/chemenu/commands/review_cmd.py
- tools/chemenu/commands/task_cmd.py
- tools/chemenu/commands/upload_cmd.py
- tools/chemenu/config.py
- tools/chemenu/config_shapes.py
- tools/chemenu/legacy_settings.py
- tools/chemenu/mcp/__main__.py
- tools/chemenu/mcp/server.py
- tools/chemenu/reference_doc.py
- tools/chemenu/review.py
- tools/chemenu/settings.py
- tools/chemenu/tasks/__init__.py
- tools/chemenu/tasks/caldav.py
- tools/chemenu/tasks/config.py
- tools/chemenu/tasks/superproductivity.py
- tools/chemenu/telemetry/policy.py
- tools/chemenu/tests/conftest.py
- tools/chemenu/tests/record_sp_fixtures.py
- tools/chemenu/tests/test_bugreport.py
- tools/chemenu/tests/test_caldav.py
- tools/chemenu/tests/test_config_shapes.py
- tools/chemenu/tests/test_doctor.py
- tools/chemenu/tests/test_git_publish.py
- tools/chemenu/tests/test_legacy_settings.py
- tools/chemenu/tests/test_mcp_server.py
- tools/chemenu/tests/test_new_page.py
- tools/chemenu/tests/test_review.py
- tools/chemenu/tests/test_settings.py
- tools/chemenu/tests/test_sp_recorded.py
- tools/chemenu/tests/test_superproductivity.py
- tools/chemenu/tests/test_task_cmd.py
- tools/chemenu/tests/test_tasks_config.py
- tools/chemenu/tests/test_telemetry_policy.py
- tools/chemenu/tests/test_tracker_live.py
- tools/chemenu/tests/test_upload.py
- tools/chemenu/tests/tracker_live.py
- tools/chemenu/upload.py

Co-Authored-By: Claude Code <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2

docs/how-to/run-the-weekly-review.md

@@ -18,8 +18,8 @@ syncing: [knowledge-and-commitment.md](../explanation/knowledge-and-commitment.m
 
 ## What you prepare
 
-A task tracker, configured for this checkout in `.wikitool-tasks.json`. Super Productivity and
-CalDAV (for example Nextcloud Tasks) are supported. The file's shape, and the difference between a
+A task tracker, configured in the settings (the `tasks` section and the section of its provider). Super Productivity and
+CalDAV (for example Nextcloud Tasks) are supported. Their shape, and the difference between a
 tracker the wiki can only read and one it can write to, is in the
 [configuration reference](../reference/configuration.md#task-tracker). Without a tracker, the
 review has nothing to join against. That is a valid state, though, and the pages work without one.

docs/how-to/set-up-the-mcp-server.md

@@ -160,10 +160,10 @@ reviewed yet.
 
 ## Optional: the submit path
 
-Without this, `submit` does not exist as a tool - not unused, but not registered. A file
-`.wikitool-upload.json` in the served corpus turns it on. Its fields, defaults and what a malformed
-file does are in the [configuration reference](../reference/configuration.md#mcp-submissions); a
-broken file never means "no limits", it stops the server from starting.
+Without this, `submit` does not exist as a tool - not unused, but not registered. An
+`upload` section in the served checkout's `.wikitool-local.json` turns it on. Its fields, defaults and what a malformed
+section does are in the [configuration reference](../reference/configuration.md#mcp-submissions); a
+broken section never means "no limits", it stops the server from starting.
 
 **With `submit` on, the middleware has a second duty.** It has to set the identity header itself, on
 every authenticated request, and discard any copy the client sent. The server trusts that header as

docs/how-to/trace-and-score-sessions.md

@@ -21,13 +21,13 @@ score means are covered in [telemetry-and-evaluation.md](../explanation/telemetr
 
 **Turn tracing on, if it is off.** It is on in a clone of the origin repository and off in an
 instance installed from a release. `tools/wikitool doctor` reports which state this checkout is in,
-and why. To turn it on for one checkout, create `.wikitool-telemetry.json` at the root:
+and why. To turn it on for one checkout, set it in the per-checkout settings:
 
-```json
-{ "enabled": true }
+```bash
+tools/wikitool config set telemetry.enabled true
 ```
 
-The file and its other keys are in the [configuration reference](../reference/configuration.md#telemetry).
+This writes the `telemetry` section of `.wikitool-local.json`. The section and its other keys are in the [configuration reference](../reference/configuration.md#telemetry).
 Everything stays on this machine: traces land under `reports/telemetry/`, which is gitignored, and
 no exporter is configured.
 

docs/how-to/troubleshoot.md

@@ -46,11 +46,11 @@ a valid state.
 
 ## `doctor` reports `telemetry: WARN`
 
-`.wikitool-telemetry.json` holds something telemetry does not read as written: unreadable JSON, a
-value that is not an object, an `enabled` that is not `true` or `false`, a cap that is not a
+The `telemetry` section of `.wikitool-local.json` holds something telemetry does not read as
+written: an unreadable settings file, a value that is not an object, an `enabled` that is not `true` or `false`, a cap that is not a
 positive whole number, or a key it does not know. Telemetry itself never stops on this. It ignores
-the file or the value, or reads `"no"` as on, and the line names the field. Correct the file to the
-shape in the [configuration reference](../reference/configuration.md#telemetry), or delete it to
+the file or the value, or reads `"no"` as on, and the line names the field. Correct the section to the
+shape in the [configuration reference](../reference/configuration.md#telemetry), or remove it to
 get the default back.
 
 ## `new` stops with "No author configured"
@@ -67,10 +67,10 @@ list and the exact `--confirm <token>` line that publishes once you approve.
 
 ## `publish` ends with exit 42 (Publish-Remote Gate)
 
-This checkout has a `.wikitool-remotes.json`, and the remote being pushed to is not listed in it.
+This checkout has a `remotes.allowed_push_urls` list in `.wikitool-local.json`, and the remote being pushed to is not listed in it.
 Also not an error: the output names the push URL it would write to and the URLs that are allowed.
 Unlike the Mass-Update Gate, there is **no token and no flag** here. If the target really is right,
-you add its URL to the file yourself. An agent that edits the file to get past the refusal is
+you add its URL to that list yourself. An agent that edits the list to get past the refusal is
 opening a gate on its own initiative, which it must never do.
 
 ## Setup or an update fails, and you want to report it