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
CI / verify (push) Successful in 8m49s
CI / pwsh (push) Successful in 2m40s
Release / release (push) Successful in 35s
Release / wiki-mirror (push) Skipped

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
This commit is contained in:
torbenandClaude Opus 5.5 committed 2026-10-13 06:39:19 +02:00
1 parent 99945c4841
commit d92800f372
4 files changed
+16 -2

No files matched your search

+6
View File
@@ -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: