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/gates.md

@@ -86,29 +86,30 @@ puts a private corpus on a public repository. That is not cheaply reversible: a
 the branch, but the objects stay fetchable by SHA until someone expires the server's reflogs and
 runs `git gc --prune=now` on the bare repo.
 
-`.wikitool-remotes.json` names the push URLs a checkout permits:
+The `remotes` section of `.wikitool-local.json` names the push URLs a checkout permits:
 
 ```json
-{ "schema": 1, "allowed_push_urls": ["ssh://git@example.net:22/you/your-wiki.git"] }
+{ "schema": 1, "remotes": { "allowed_push_urls": ["ssh://git@example.net:22/you/your-wiki.git"] } }
 ```
 
 It pins **URLs, not remote names** - a name-based list would wave through a `publish` whose
 `origin` had been repointed, which is the failure it exists to catch. It reads the remote's
 `pushurl` when one is set, because that is where `git push` actually writes.
 
-The file is per-checkout and gitignored, for the same reason `ENVIRONMENT.md` is: two clones push
+The list lives in the per-checkout settings file, which is gitignored, for the same reason `ENVIRONMENT.md` is: two clones push
 to two different places, so a committed copy would tell a private clone that a public remote is a
 legitimate target for its own content. **Absent means unrestricted** - a single-remote
 checkout with nothing private in it has nothing to protect, and `doctor` reports which state a
 checkout is in, WARNing only when there is more than one remote and no allowlist. A malformed
-file is an error rather than "no restriction": a corrupted safeguard must not read as a disabled
+section is an error rather than "no restriction": a corrupted safeguard must not read as a disabled
 one.
 
 **This gate has no `--confirm` token, on purpose.** The others clear with a token because the
 question they ask ("is this change right?") is one the agent can put to the user and the user can
 answer for that one changeset. This one asks "does this content belong to that repository?", which
 is a standing property of the checkout, not a per-push judgment. The way past it is for the user
-to add the URL to the file. **An agent must never edit `.wikitool-remotes.json` to get past a
+to add the URL to the list - `config set` exits 42 for it, because the field is marked `gate`.
+**An agent must never edit `remotes.allowed_push_urls` to get past a
 refusal** - that is opening a gate on your own initiative, which AGENTS.md invariant 6 forbids.
 
 Arm it *before* a second remote is added and before the first `publish` to it: added afterwards
@@ -116,7 +117,7 @@ it leaves open exactly the window it closes.
 
 ### Upload Review Gate
 
-The MCP server's opt-in `submit` tool (`.wikitool-upload.json`) writes into a
+The MCP server's opt-in `submit` tool (the `upload` section of `.wikitool-local.json`) writes into a
 quarantine, `mcp-upload/`, that no other command reads. This gate is the only door out of it:
 `wikitool upload accept <id>` refuses without a matching `--confirm <token>`, printing the
 submission's manifest in full - filename, size, sha256, submitter, and `submitter_source` (the
@@ -159,7 +160,7 @@ with exit 0 and no gate.
 
 **Not the Publish-Remote Gate.** That one stays on `publish`. The targets here are declared by
 the committed `_capture.json` manifests under `raw/`; asking for the same URLs in
-`.wikitool-remotes.json` as well would be a second declaration of the same thing. What this gate
+`remotes.allowed_push_urls` as well would be a second declaration of the same thing. What this gate
 asks instead is the per-run question - whether this content belongs in these repositories now -
 which is the kind a token answers.