gates: AGENTS.md § Gates and mcp-read-server name every intake channel behind the Upload Review Gate, not only submit (#213 close); 10.0.0-beta.12
Files changed: - AGENTS.md - CHANGES.md - VERSION - docs/reference/configuration.md - instructions/mcp-read-server.md - tools/chemenu/commands/doctor.py Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2
This commit is contained in:
1 parent
cceb9a7bfe
commit
ecefe0a033
6 files changed
+14
-10
No files matched your search
@@ -329,9 +329,11 @@ one an agent can talk itself past. This section is the one list of them.
|
||||
touch a file this session is also changing, printing the incoming commits, the overlapping
|
||||
files, their diff and the `--confirm-rebase <token>` line that rebases once the user has
|
||||
judged that the two changes do not collide logically.
|
||||
- **Upload Review Gate.** `upload accept` exits **42** on an MCP `submit` tool submission
|
||||
nobody has cleared yet, printing its manifest and the `--confirm <token>` line that promotes
|
||||
it once the user approves - same shape as the Mass-Update Gate, one submission at a time.
|
||||
- **Upload Review Gate.** `upload accept` exits **42** on a submission in the quarantine
|
||||
nobody has cleared yet - whichever intake channel delivered it: the MCP `submit` tool, a
|
||||
synced folder or a command - printing its manifest and the `--confirm <token>` line that
|
||||
promotes it once the user approves - same shape as the Mass-Update Gate, one submission at a
|
||||
time.
|
||||
- **Guideline Push Gate.** `export guidelines --push` exits **42** before writing the generated
|
||||
`GUIDELINES.md` into any captured repository, printing every target's status, the diff for
|
||||
each one it would write, and the `--confirm <token>` line that pushes exactly that set once the
|
||||
|
||||
+2
-1
@@ -14,7 +14,7 @@ place only: `instructions/dev/version-parts.md` § The candidate model.
|
||||
|
||||
---
|
||||
|
||||
## 10.0.0-beta.11 - 2026-10-12 - Eingangskanäle: der intake-Abschnitt kennt mehrere Kanäle (mcp, folder, command), alle enden in quarantine/; neues Kommando upload collect zieht Sync-Ordner und Programme in die Quarantäne
|
||||
## 10.0.0-beta.12 - 2026-10-12 - AGENTS.md § Gates and mcp-read-server name every intake channel behind the Upload Review Gate, not only submit (#213 close)
|
||||
|
||||
**Author:** Torben Nehmer
|
||||
|
||||
@@ -44,6 +44,7 @@ place only: `instructions/dev/version-parts.md` § The candidate model.
|
||||
- Testkorrektur: die Live-Tracker-Suite importiert, was ihr CalDAV-Anleger braucht
|
||||
- doctor: die Beschreibung der Strukturprüfung nennt sites/CONTRACT.md, die doctor seit den Site-Handlern der Instanz verlangt
|
||||
- raw fetch --scope ist die Entscheidung des Nutzers: raw/CONTRACT.md und wiki-ingest sagen, wer es anstößt und warum es kein Folgen von Links ist
|
||||
- AGENTS.md § Gates and mcp-read-server name every intake channel behind the Upload Review Gate, not only submit (#213 close)
|
||||
<!-- /wikitool:bumps -->
|
||||
|
||||
### Einstellungen in drei Stufen, Secrets nur per Verweis (#207)
|
||||
|
||||
@@ -4,8 +4,8 @@ The environment variables `wikitool` reads and the two tiered settings files an
|
||||
the root of an instance. None of them is needed for an instance to work: an instance installed from a
|
||||
release runs against the origin's public release feed with no configuration at all.
|
||||
|
||||
Every setting of a feature - telemetry, the publish allowlist, the task tracker, the MCP `submit`
|
||||
limits - is a section of those two files, and the shape of each section - its fields, their tier, what
|
||||
Every setting of a feature - telemetry, the publish allowlist, the task tracker, the intake
|
||||
channels - is a section of those two files, and the shape of each section - its fields, their tier, what
|
||||
an absent or a malformed section means, an example - is generated from the record `wikitool` itself
|
||||
reads it with, so it cannot describe a field the tool does not take. What a setting does around it is
|
||||
written by hand.
|
||||
|
||||
@@ -9,8 +9,9 @@ description: Run and keep current the MCP read server that serves this wiki to a
|
||||
Chemenu has a second consumer. `search`, `types`, `describe_type`, `lint` and `status` are
|
||||
served over MCP to callers that are not this terminal - the CLI and the server are two adapters
|
||||
over one core (`chemenu.api.Corpus`), not a CLI with a network interface bolted on. A sixth
|
||||
tool, `submit`, is opt-in: a checkout whose `.wikitool-local.json` has an `upload` section also
|
||||
offers a quarantined write path for documents pushed from outside - see
|
||||
tool, `submit`, is opt-in: a checkout whose `.wikitool-local.json` declares a channel with the
|
||||
handler `mcp` in its `intake` section also offers a quarantined write path for documents pushed
|
||||
from outside - see
|
||||
[instructions/ingest-queue.md](ingest-queue.md) for reviewing what lands there.
|
||||
|
||||
This document is about *operating* it: how to start it, what has to be true of the checkout it
|
||||
|
||||
@@ -1165,7 +1165,7 @@ def doctor_command(
|
||||
\f
|
||||
Dependencies, recorded tool paths, install folder length, author, git identity/remote, published skills, structure,
|
||||
personalization, KB conventions, generated files, session scoping,
|
||||
telemetry state, whether the MCP `submit` tool is armed, and which
|
||||
telemetry state, which intake channels are configured, and which
|
||||
task-tracker provider (if any) is configured for the GTD review.
|
||||
Read-only. Exits 1 only if a check FAILs."""
|
||||
checks = run_doctor()
|
||||
|
||||
Reference in new issue
Block a user