intake: several configured intake channels (mcp, folder, command) all end in quarantine/ (was mcp-upload/), and upload collect pulls the synced-folder and command channels into it (#213); 10.0.0-beta.11

Files changed:
- .gitignore
- CHANGES.md
- VERSION
- docs/explanation/architecture.md
- docs/explanation/pipeline-rationale.md
- docs/how-to/README.md
- docs/how-to/back-up-to-a-synced-folder.md
- docs/how-to/collect-from-a-synced-folder.md
- docs/how-to/ingest-a-source.md
- docs/how-to/set-up-the-mcp-server.md
- docs/reference/commands/README.md
- docs/reference/commands/git.md
- docs/reference/commands/instance-health.md
- docs/reference/commands/raw-material-and-uploads.md
- docs/reference/configuration.md
- instructions/gates.md
- instructions/ingest-queue.md
- instructions/mcp-read-server.md
- instructions/migrations/10.0.0-settings-tiers.md
- instructions/wiki-ingest/SKILL.md
- raw/CONTRACT.md
- tools/CONTRACT.md
- tools/README.md
- tools/chemenu/cli_contract.py
- tools/chemenu/collect.py
- tools/chemenu/commands/backup_cmd.py
- tools/chemenu/commands/docs_verify.py
- tools/chemenu/commands/doctor.py
- tools/chemenu/commands/raw/pending.py
- tools/chemenu/commands/upload_cmd.py
- tools/chemenu/config.py
- tools/chemenu/config_shapes.py
- tools/chemenu/legacy_settings.py
- tools/chemenu/mcp/server.py
- tools/chemenu/reference_doc.py
- tools/chemenu/tests/test_backup.py
- tools/chemenu/tests/test_collect.py
- tools/chemenu/tests/test_config_shapes.py
- tools/chemenu/tests/test_doctor.py
- tools/chemenu/tests/test_legacy_settings.py
- tools/chemenu/tests/test_mcp_server.py
- tools/chemenu/tests/test_upload.py
- tools/chemenu/tests/test_upload_cmd.py
- tools/chemenu/upload.py

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

instructions/gates.md

@@ -117,11 +117,13 @@ it leaves open exactly the window it closes.
 
 ### Upload Review Gate
 
-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:
+The intake channels (the `intake` section of `.wikitool-local.json`: the MCP server's opt-in
+`submit` tool, a synced `folder`, a `command`) write into a quarantine, `quarantine/`, 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
-*header* the submitter's name came from, not a verified fact) - plus the exact re-run line.
+submission's manifest in full - filename, size, sha256, submitter, `submitter_source` (the
+*header* the submitter's name came from, not a verified fact; the handler for a channel with no
+sender, whose `submitter` is `unknown`), and `channel`, `handler` and `origin` - plus the exact re-run line.
 
 Same shape as the Mass-Update Gate, scoped to one submission instead of a changeset: the token
 digests id/filename/size/sha256/submitter, so an edited or superseded manifest invalidates it the
@@ -132,7 +134,7 @@ Mass-Update Gate's review report versus this file's exit-42 procedure.
 
 `wikitool upload reject <id> --reason "<why>"` is the other way out, and it has **no gate at
 all** - rejecting needs no clearance, only accepting a stranger's file into the pipeline does. It
-deletes the material and keeps only the reason and a sha256 in `mcp-upload/ledger.jsonl`.
+deletes the material and keeps only the reason and a sha256 in `quarantine/ledger.jsonl`.
 
 ### Guideline Push Gate