instructions, docs, tools: Export - setup-instance und How-to nennen auch die ganze KB, page_export-Docstring nennt die Index-Dateien (#217 close); 10.1.0-beta.22

Files changed:
- CHANGES.md
- VERSION
- docs/how-to/export-to-a-synced-folder.md
- instructions/setup-instance.md
- tools/chemenu/page_export.py

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

CHANGES.md

@@ -14,7 +14,7 @@ place only: `instructions/dev/version-parts.md` § The candidate model.
 
 ---
 
-## 10.1.0-beta.21 - 2026-10-16 - Export: include "all" wählt die ganze KB, index: true schreibt index.md und INDEX.md im Ziel
+## 10.1.0-beta.22 - 2026-10-16 - Export: setup-instance und How-to nennen auch die ganze KB als Exportumfang, page_export-Docstring nennt die Index-Dateien (#217 close)
 
 **Author:** Torben Nehmer
 
@@ -43,6 +43,7 @@ place only: `instructions/dev/version-parts.md` § The candidate model.
 - publish-and-ci: CI-Wartezeiten auf gemessene Laufzeiten gesetzt - ein Runner, Jobs nacheinander, ca. 12 Min bis zum letzten grünen Lauf (Konverter ca. 22), Aufgeben nach 25 (35) statt 15 Min
 - publish-and-ci: hält fest, dass der Runner derzeit keine parallelen Jobs fährt, und dass die Wartezeiten neu zu messen sind, sobald er es tut
 - publish-and-ci: Wartezeit zählt ab freiem Runner, nicht ab dem Push - offene Läufe eines früheren Pushs laufen zuerst, und der Runner hält die Push-Reihenfolge nicht ein
+- Export: setup-instance und How-to nennen auch die ganze KB als Exportumfang, page_export-Docstring nennt die Index-Dateien (#217 close)
 <!-- /wikitool:bumps -->
 
 ### Konverter-Tests gegen echte Dokumente im privaten Repository

VERSION

@@ -1 +1 @@
-10.1.0-beta.21
+10.1.0-beta.22

docs/how-to/export-to-a-synced-folder.md

@@ -1,8 +1,8 @@
 # Export to a synced folder
 
-Give a reader outside the repository a read-only version of part of `kb/`: the selected pages,
+Give a reader outside the repository a read-only version of part or all of `kb/`: the selected
-written as files into a folder - typically one a sync client such as OneDrive uploads, so that a
+pages, written as files into a folder - typically one a sync client such as OneDrive uploads, so
-Microsoft 365 tenant can index them. The export is derived. It is regenerated from the committed
+that a Microsoft 365 tenant can index them. The export is derived. It is regenerated from the committed
 pages on every run, nobody edits it, and nothing in it flows back into the wiki. What the settings
 look like: [configuration reference](../reference/configuration.md#export-to-a-folder).
 

instructions/setup-instance.md

@@ -131,7 +131,7 @@ one it needs before that.
      procedure is [docs/how-to/back-up-to-a-synced-folder.md](../docs/how-to/back-up-to-a-synced-folder.md).
      Until it is done, treat the instance as local.
    - A reader outside the repository - a Microsoft 365 tenant that indexes a OneDrive folder, say
-     - who should get a read-only version of part of `kb/`: offer an export. The user writes the
+     - who should get a read-only version of part or all of `kb/`: offer an export. The user writes the
      `export` section of `.wikitool-local.json` by hand (its fields are gates, so `config set`
      refuses them); then run `tools/wikitool export run`. The whole procedure is
      [docs/how-to/export-to-a-synced-folder.md](../docs/how-to/export-to-a-synced-folder.md).

tools/chemenu/page_export.py

@@ -13,7 +13,8 @@ properties that carry that, each with a test:
 - **Deterministic.** A file depends on its page, the selection it links into
   and the commit that last touched that page - no timestamp, no `HEAD` - so a
   run on an unchanged corpus writes nothing, not even a file's modification
-  time, and a commit to one page rewrites that page's file alone.
+  time, and a commit to one page rewrites that page's file alone - plus,
+  with `index: true`, the index files that list it (`chemenu.export_index`).
 - **Only its own files are touched.** What an earlier run wrote is recorded in
   a manifest in the target (`.wikitool-export.json`, with a digest per file).
   A run removes only manifest files that are no longer exported, leaves every