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/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