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/explanation/knowledge-and-commitment.md

@@ -140,7 +140,7 @@ is. An instruction that said "open Super Productivity" would bake one instance's
 the shared stack, and the next instance - a different context, a different employer, a different
 set of constraints - would have to edit prose to change a setting.
 
-So the provider lives in configuration (`.wikitool-tasks.json`), the adapters live behind one
+So the provider lives in configuration (the `tasks` section of the settings), the adapters live behind one
 protocol, and a capability the provider lacks surfaces as an ordinary tool error rather than as a
 paragraph of instruction explaining what this particular tracker cannot do. A provider that
 cannot create a project, for instance, stops and asks the operator to do it - the same posture the

docs/explanation/telemetry-and-evaluation.md

@@ -142,8 +142,8 @@ where the traces are the stack's own measuring instrument. An instance commits t
 first `publish`, so a clone of it on a second machine carries the stamp and defaults to off too. It
 is a consuming instance, not a measuring stand.
 
-**Turning it on for a distributed instance** takes a per-checkout `.wikitool-telemetry.json` at the
-root, gitignored like `.wikitool-remotes.json` and for the same reason. The consent to write
+**Turning it on for a distributed instance** takes a `telemetry` section in the per-checkout `.wikitool-local.json` at the
+root, which is gitignored and for the same reason as every other setting that belongs to one checkout. The consent to write
 prompts in cleartext to *this* disk belongs to the checkout, not the corpus, so a second clone must
 not inherit it silently. The setup instruction asks about it; nothing writes it automatically. Its
 shape is in the [configuration reference](../reference/configuration.md#telemetry).

docs/explanation/why-gates-are-code.md

@@ -44,7 +44,7 @@ That's not a per-push judgment, it's a standing property of the checkout - true
 every publish that checkout will ever attempt, not just this one. A confirm token would let an
 agent clear it once and then treat the answer as settled, which is exactly backwards for a
 question whose answer shouldn't move at all mid-session. The only way past it is the user
-editing `.wikitool-remotes.json` directly, outside the gate's own flow.
+editing the `remotes` section of `.wikitool-local.json` directly, outside the gate's own flow.
 
 The Upload Review Gate asks the Mass-Update Gate's own question - *is this change right?* - at
 the opposite end of its size range: one file from a stranger instead of a changeset from the