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

instructions/setup-instance.md

@@ -274,21 +274,21 @@ one it needs before that.
    it, and nobody reads up on telemetry before the first file is written anyway. This step only asks
    whether the operator wants to reverse that.
 
-   Ask the user once: telemetry on? If yes, create `.wikitool-telemetry.json` in the repo root
-   (per checkout, gitignored, no `.template` - like `.wikitool-remotes.json`):
+   Ask the user once: telemetry on? If yes, run `tools/wikitool config set telemetry.enabled true`.
+   It writes the `telemetry` section of `.wikitool-local.json` (per checkout, gitignored):
 
    ```json
-   { "enabled": true }
+   { "schema": 1, "telemetry": { "enabled": true } }
    ```
 
-   The file's two optional caps and their defaults are in
+   The section's two optional caps and their defaults are in
    [docs/reference/configuration.md](../docs/reference/configuration.md#telemetry); most instances
    need not touch them. If no, do nothing - the default is already
-   off, and no file is created. `WIKI_TRACE` still overrides in both directions, should a
+   off, and nothing is written. `WIKI_TRACE` still overrides in both directions, should a
    single session need to differ.
 
    `tools/wikitool doctor` reports the result in step 12 (`telemetry`): on/off, why
-   (installation form, this file, or `WIKI_TRACE`), and the current volume against both caps -
+   (installation form, this setting, or `WIKI_TRACE`), and the current volume against both caps -
    never a `FAIL`, since both directions are a valid state. More on this:
    [telemetry-and-evaluation.md](../docs/explanation/telemetry-and-evaluation.md#whether-it-runs-at-all).
 
@@ -300,15 +300,17 @@ one it needs before that.
    end state - the pages work alone, `review` simply says so and refuses - so ask rather than
    assume.
 
-   Ask the user once: is there a task tracker to connect? If yes, create `.wikitool-tasks.json`
-   in the repo root (per checkout, no `.template`, **gitignored once it holds a token** - like
-   `.wikitool-telemetry.json` and `.wikitool-remotes.json`), with the provider's own section and
-   the three thresholds the review reads as configuration rather than schema. The shape, the
+   Ask the user once: is there a task tracker to connect? If yes, set the `tasks`
+   section (provider and the three thresholds the review reads as configuration rather than
+   schema) and the provider's own section with `tools/wikitool config set`. What the tiers decide
+   goes there too: the account's address and login are per checkout, and a token or password is
+   never typed into the chat - the user puts it into 1Password, the secrets file or a
+   `WIKITOOL_SECRET_<NAME>` variable, and the setting holds a reference to it. The shape, the
    shipped providers, and what Super Productivity in particular needs are in
    [configuration.md](../docs/reference/configuration.md#task-tracker); do not restate them here. If no, do nothing - no
-   file is created, and adding one later needs nothing from this procedure.
+   section is written, and adding one later needs nothing from this procedure.
 
-   `doctor` reports the result in step 12 (`tasks`): absent is `OK`, a malformed file is the one
+   `doctor` reports the result in step 12 (`tasks`): absent is `OK`, a malformed section is the one
    `FAIL` here (a broken opt-in must not read as "no tracker configured"), and a configured
    provider that is simply not running is never a fault.