tools, instructions: Query-Log - reine Lesevorgänge nicht mehr in kb/log.md, Reconcile erzeugt den Katalog bei reinem Log-Zusatz nicht neu (#223); 10.1.1-beta.1

Files changed:
- CHANGES.md
- VERSION
- docs/explanation/architecture.md
- docs/reference/commands/catalog-and-log.md
- docs/reference/commands/git.md
- instructions/publish-cycle.md
- instructions/session-setup.md
- instructions/wiki-query/SKILL.md
- tools/CONTRACT.md
- tools/chemenu/commands/git_publish.py
- tools/chemenu/commands/log_append.py
- tools/chemenu/dist_templates/log.md
- tools/chemenu/tests/test_git_publish.py

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

instructions/publish-cycle.md

@@ -30,7 +30,7 @@ consistent.
 3. **Append the audit entry** - one per operation:
 
    ```bash
-   tools/wikitool log append --op ingest|query|lint|create|update|delete|rename|move \
+   tools/wikitool log append --op ingest|lint|create|update|delete|rename|move \
      --title "<what>" --body "<outcome>"
    ```
 

instructions/session-setup.md

@@ -88,7 +88,8 @@ the session instead of discovering the drift only at the very end.
 never commits and never pushes. Files `wikitool` generates are never a reason to stop: when the
 catalog or `kb/log.md` changed on both sides, `sync` keeps both sides' log entries and
 regenerates the catalog and `kb/provenance.md`, which it leaves as an uncommitted change for the
-next `publish`. Uncommitted work that the incoming commits do not touch stays where it is.
+next `publish`. An open log entry alone is no such case: the incoming catalog stays and only the
+entry is appended again. Uncommitted work that the incoming commits do not touch stays where it is.
 **Exit 42 (rebase-review)?** Same as any exit 42 - read the
 diff it prints, judge whether it conflicts with what you are about to do, summarize that to the
 user, then `tools/wikitool sync --confirm-rebase <token>` before continuing. See

instructions/wiki-query/SKILL.md

@@ -12,10 +12,11 @@ description: Answers a question using the LLM wiki's compiled knowledge - read-o
 **Before the first `wikitool` call:** `instructions/session-setup.md`.
 
 **Hard rule:** read-only with respect to wiki *content*. Never modify, hand-edit, or scaffold a
-page while answering. Two exceptions, both mechanical: step 7 (filing a valuable answer through
-`wikitool new`, never by hand) and step 8 (one audit entry via `wikitool log append`). If the
-wiki has no confident source, say so - per AGENTS.md's "never file an unsourced answer"
-invariant - rather than synthesizing a plausible-sounding answer from general knowledge.
+page while answering. One exception, mechanical: step 7 (filing a valuable answer through
+`wikitool new`, never by hand). A query writes no `kb/log.md` entry - a read changes nothing the
+wiki learned. If the wiki has no confident source, say so - per AGENTS.md's "never file an
+unsourced answer" invariant - rather than synthesizing a plausible-sounding answer from general
+knowledge.
 
 ## Steps
 
@@ -98,19 +99,16 @@ invariant - rather than synthesizing a plausible-sounding answer from general kn
    find again than a sentence in a chat log.
 
 7. **File back what survived.** Scaffold it - `tools/wikitool new ...` - and follow
-   `wiki-manage`. Never write the page by hand, and never file an answer no source backs.
-
-8. **Log it.**
-
-   ```bash
-   tools/wikitool log append --op query --title "<question>" --body "<outcome>"
-   ```
+   `wiki-manage`, which logs it as a `create` through `publish-cycle.md`. Never write the page by
+   hand, and never file an answer no source backs.
 
 ## Decision points
 
 - **Nothing found?** Try the structural query before concluding the wiki is silent - a page may
   exist under different words. Then say the wiki has no confident source, and offer to ingest
-  one.
+  one. If the user wants the gap kept, file it as an inbox item on their say-so:
+  `tools/wikitool task new --inbox --title "<the question>"`. Without a configured tracker the
+  offer stays in the chat. Never log it.
 - **The question asks for the wording** - "what exactly does rule 16:3e say", "which value is
   in table 4"? Find the page that carries the substance first (steps 2-3), then step 4's route
   to the passage. A paraphrase from the page is not the wording, and searching `raw/` is not a
@@ -129,7 +127,7 @@ invariant - rather than synthesizing a plausible-sounding answer from general kn
 
 ## wikitool commands used
 
-`search`, `log append`. If filing an answer back: `new`, `xref add`, `sources rebuild-index`,
+`search`. If filing an answer back: `new`, `xref add`, `sources rebuild-index`,
 `index rebuild`, and `publish` only if asked.
 
 ## Output