docs: publish-cycle says what a WARN or ERROR from the page export after publish means, architecture names the page export as the way out for a reader that cannot ask (#214 close); 10.0.0-beta.14

Files changed:
- CHANGES.md
- VERSION
- docs/explanation/architecture.md
- instructions/publish-cycle.md

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.0.0-beta.13 - 2026-10-12 - Exporte als konfigurierte Ziele: export run schreibt eine abgeleitete, schreibgeschützte Lesefassung von kb/ je Zielordner (Markdown oder über ein Konvertierprogramm), auf Wunsch nach jedem publish; raw accept lehnt auch Dateien ab, die in einem Export-Manifest stehen
+## 10.0.0-beta.14 - 2026-10-13 - publish-cycle: what a WARN or ERROR from the page export after publish means; architecture names the page export as the way out for a reader that cannot ask (#214 close)
 
 **Author:** Torben Nehmer
 
@@ -46,6 +46,7 @@ place only: `instructions/dev/version-parts.md` § The candidate model.
 - 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)
+- publish-cycle: what a WARN or ERROR from the page export after publish means; architecture names the page export as the way out for a reader that cannot ask (#214 close)
 <!-- /wikitool:bumps -->
 
 ### Einstellungen in drei Stufen, Secrets nur per Verweis (#207)

VERSION

@@ -1 +1 @@
-10.0.0-beta.13
+10.0.0-beta.14

docs/explanation/architecture.md

@@ -263,6 +263,12 @@ for it.
 
 Setting it up: [set-up-the-mcp-server.md](../how-to/set-up-the-mcp-server.md).
 
+A reader that cannot ask at all - a Microsoft 365 tenant indexing a OneDrive folder - gets a copy
+instead: `tools/wikitool export run` writes the pages a target selects into a folder, as a derived,
+read-only version regenerated from the committed pages on every run. Nothing flows back from it;
+the export marker and the target's manifest keep its files out of `raw/`
+([export-to-a-synced-folder.md](../how-to/export-to-a-synced-folder.md)).
+
 ## Built for IT work
 
 The shipped defaults are tailored to IT work:

instructions/publish-cycle.md

@@ -58,6 +58,13 @@ consistent.
   writable, say. Do **not** run `publish` again: it would have nothing to push and back nothing up.
   Once the user has fixed the cause, `tools/wikitool backup run` repeats the backup
   ([docs/how-to/back-up-to-a-synced-folder.md](../docs/how-to/back-up-to-a-synced-folder.md)).
+- **A `WARN` that a page export failed?** The same: the commit and the push stand, `publish`
+  exited 0, and the line names the target and the reason - a page someone edited in the target
+  folder, say. Show it to the user and do **not** run `publish` again; once the cause is fixed,
+  `tools/wikitool export run` refreshes the target
+  ([docs/how-to/export-to-a-synced-folder.md](../docs/how-to/export-to-a-synced-folder.md)).
+  An `ERROR` about the `export` section instead stopped `publish` before it committed: the section
+  is the user's to fix by hand, and nothing was published.
 - **Query or lint pass?** Neither auto-publishes. Run `publish` only if asked to.
 - **Nothing under `kb/` changed?** Skip steps 1 and 2; a change to `tools/` or `instructions/`
   does not affect the catalog.