export: export run writes selected kb/ pages as a derived, read-only version into configured target folders (markdown and command handlers, manifest, after_publish), raw accept also refuses manifest-listed files, doctor checks the section (#214); 10.0.0-beta.13

Files changed:
- CHANGES.md
- VERSION
- 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/export-guidelines.md
- docs/how-to/export-to-a-synced-folder.md
- docs/reference/commands/README.md
- docs/reference/commands/exports.md
- docs/reference/commands/git.md
- docs/reference/commands/guideline-export.md
- docs/reference/commands/instance-health.md
- docs/reference/commands/raw-material-and-uploads.md
- docs/reference/configuration.md
- docs/reference/exit-codes.md
- instructions/setup-instance.md
- raw/CONTRACT.md
- tools/CONTRACT.md
- tools/README.md
- tools/chemenu/backup.py
- tools/chemenu/cli_contract.py
- tools/chemenu/commands/doctor.py
- tools/chemenu/commands/export_cmd.py
- tools/chemenu/commands/git_publish.py
- tools/chemenu/commands/raw/_common.py
- tools/chemenu/commands/raw/accept.py
- tools/chemenu/commands/raw/capture.py
- tools/chemenu/config_shapes.py
- tools/chemenu/guideline_export.py
- tools/chemenu/page_export.py
- tools/chemenu/reference_doc.py
- tools/chemenu/repo_capture.py
- tools/chemenu/tests/test_config_shapes.py
- tools/chemenu/tests/test_export_run.py

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

docs/reference/configuration.md

@@ -31,6 +31,7 @@ something you run.
 - [Site handlers](#site-handlers)
 - [Fetch routes](#fetch-routes)
 - [Backup to a synced folder](#backup-to-a-synced-folder)
+- [Export to a folder](#export-to-a-folder)
 - [Files of earlier versions](#files-of-earlier-versions)
 <!-- /wikitool:toc -->
 
@@ -93,7 +94,7 @@ Each file is a JSON object of sections, one per feature, beside two keys of its
 the id; the id names the directory of the secrets file below. The sections are [telemetry](#telemetry),
 [remotes](#allowed-push-urls), [tasks, superproductivity and caldav](#task-tracker) and
 [intake](#intake-channels), [sites](#site-handlers), [fetch](#fetch-routes) and
-[backup](#backup-to-a-synced-folder). `config set` names the sections it knows, and `doctor` reports a
+[backup](#backup-to-a-synced-folder) and [export](#export-to-a-folder). `config set` names the sections it knows, and `doctor` reports a
 section it does not read as a `WARN`.
 
 **One place per value.** A value in the file its tier does not name is an error naming the file,
@@ -631,6 +632,96 @@ Example:
 `config set` exits 42 for them, and only you write them. The procedure, restoring included:
 [back-up-to-a-synced-folder.md](../how-to/back-up-to-a-synced-folder.md).
 
+## Export to a folder
+
+The `export` section of `.wikitool-local.json` declares folders that hold a derived, read-only
+version of `kb/` - for a reader outside the repository, such as a Microsoft 365 tenant that indexes
+a OneDrive folder. An export is regenerated from the committed pages on every run and is never
+edited; what someone changes in the folder is refused or overwritten, never merged back. Each
+target has a handler: `markdown` writes the selected pages as Markdown files, `command` renders
+them into a staging directory and hands that to a converter of this checkout.
+
+<!-- wikitool:reference-config-export -->
+| Field | Tier | Type | Required | Default | Description |
+|-------|------|------|----------|---------|-------------|
+| `targets` | checkout, gate | object | yes | - | Target name (lower-case letters, digits and hyphens) to target; the name is the argument of `export run`. Every target has `handler` (`markdown`: the pages as Markdown files; `command`: the same Markdown run through a converter of this checkout), `path` (an absolute path outside the instance; it must not lie in or contain another target, an `intake` folder or `backup.target`) and `include` (an array of selections, each an array of `search --field` predicates: all predicates of a selection must hold, and a page that fits any selection is exported; there is no "everything"). Optional: `frontmatter` (`minimal`: only the export marker; `summary`, the default: also `title`, `type`, `summary` and `modified` where the page has them; `full`: the page's whole frontmatter), `links` (`relative`, the default: a wikilink to an exported page becomes a relative Markdown link; `text`: plain text; a link to a page that is not exported is always plain text) and `after_publish` (default false: refresh this target after every `publish` that committed). The handler `command` takes `command` (required: the name of an entry of `commands`). A field the handler does not take is an error. |
+| `commands` | checkout, names a command | object | no | `{}` | Command name to command: an array of the program and its arguments, run by the `command` handler without a shell, with stdin closed and a timeout of 300 s. The last two arguments appended are the directory holding the Markdown and an empty output directory. Exit 0 makes the regular files in the output directory the target's content; anything else leaves the target unchanged and prints the end of the program's stderr. |
+
+- **Absent:** No export: `export run` stops with exit 1 naming the section, `publish` exports nothing and `doctor` reports `OK`.
+- **Malformed:** An error. `export run` stops with exit 1 and `doctor` reports `FAIL`; `publish` stops with exit 1 before it commits anything, but only when some target sets `after_publish`. A broken section is never read as "no export".
+
+Example:
+
+```json
+{
+  "export": {
+    "targets": {
+      "work-notes": {
+        "handler": "markdown",
+        "path": "C:\\Users\\<user>\\OneDrive - <company>\\Chemenu-Lesefassung",
+        "include": [
+          [
+            "kind=system"
+          ],
+          [
+            "tags=shared",
+            "!draft"
+          ]
+        ],
+        "frontmatter": "summary",
+        "links": "relative",
+        "after_publish": true
+      },
+      "as-word": {
+        "handler": "command",
+        "command": "pandoc-docx",
+        "path": "C:\\Users\\<user>\\OneDrive - <company>\\Chemenu-Word",
+        "include": [
+          [
+            "kind=system"
+          ]
+        ]
+      }
+    },
+    "commands": {
+      "pandoc-docx": [
+        "pwsh",
+        "-NoProfile",
+        "-File",
+        "C:\\tools\\pandoc-docx.ps1"
+      ]
+    }
+  }
+}
+```
+<!-- /wikitool:reference-config-export -->
+
+Within one target, `include` is a list of selections, each a list of `search` predicates (`tags=docs`,
+`entity_type=system`, `!source_url`): a page is exported when it satisfies every predicate of at least
+one selection. Only what `include` selects is written - there is no way to exclude by default. The
+syntax is checked when the section is read, the field names against the corpus when `export run`
+runs. `path` must not lie in or contain the instance, another target, an `intake` folder or
+`backup.target`.
+
+Every Markdown file starts with a frontmatter block whose first key is `wikitool_export`, carrying
+the kind, the instance and the commit of the newest selected page. `frontmatter` decides what follows:
+`minimal` nothing, `summary` the title, type, summary and modified date, `full` the page's whole
+frontmatter. Wikilinks between exported pages become relative Markdown links (`links: relative`) or
+plain text (`links: text`); a link to a page that is not exported is always plain text. Footnote
+markers and code stay as they are.
+
+A target folder holds `.wikitool-export.json`, which lists the files a run wrote with their digests.
+A run removes only listed files that are no longer exported, creates only folders it needs and
+removes only those it created, and leaves every other file untouched. It stops before writing for a
+listed file someone changed, for a folder that is not empty and has no manifest, and for a selection
+that comes up empty. A run that finds nothing to change writes nothing, not even a modification time.
+
+`targets` and `commands` decide what leaves this checkout and which program runs, so they are marked
+`gate` and `names a command`: `config set` exits 42 for them, and only you write them. `raw accept`
+also refuses a file whose sha256 is listed in the manifest of a configured target, for an export
+that went through a converter and lost its marker. The procedure:
+[export-to-a-synced-folder.md](../how-to/export-to-a-synced-folder.md).
+
 ## Files of earlier versions
 
 Until version 10 every feature above had a file of its own at the root: `.wikitool-telemetry.json`,