Updating the wiki

Tell Codex: Read UPDATE_WIKI.md and update the Wiki for this development cycle.

The root maintenance file lives in the separate CK3Wiki workspace. It points at the CK3 source folder and the live DokuWiki.

1. Pull live content and commit human edits before modifying pages.
2. Run the preparation helper to compare source hashes and Git history where available.
3. Inspect changed definitions, callers, scopes, UI, rules and assets.
4. Use the source map to update only affected documentation sections.
5. Update implementation status, navigation, metadata and development release notes.
6. Select meaningful existing assets and supply descriptive captions.
7. Validate links/images/source mappings, then publish through native saves.
8. Verify live rendering/search/access and checksums before advancing the baseline.
9. Commit the final content and report what changed.

From the CK3Wiki workspace, using an available Python 3 interpreter:

python scripts/wiki.py pull
python scripts/wiki.py prepare
python scripts/wiki.py validate
python scripts/wiki.py deploy --summary "Documentation for the current development cycle"
python scripts/wiki.py finish --release 0.0.1-development

Preparation produces a changed-file report; it does not guess semantic behavior or regenerate pages. Deployment refuses online edit conflicts or active page locks. Existing media replacements use the native media manager after review; new explanatory images can be published by the helper.

Prepare Wiki release X.Y.Z compares the explicitly identified release source to the previous documented release, finalizes release notes with actual dates/evidence, records relevant visuals, updates version references and CHANGELOG.md, retains the prior release page and saves the verified source baseline. Do not relabel all current development features as newly introduced.

The update helper and agent instructions are repeatable, on-demand workflows. No recurring scheduler or unattended semantic updater has been enabled.