====== Updating the wiki ====== ===== Development-cycle instruction ===== 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. - Pull live content and commit human edits before modifying pages. - Run the preparation helper to compare source hashes and Git history where available. - Inspect changed definitions, callers, scopes, UI, rules and assets. - Use the source map to update only affected documentation sections. - Update implementation status, navigation, metadata and development release notes. - Select meaningful existing assets and supply descriptive captions. - Validate links/images/source mappings, then publish through native saves. - Verify live rendering/search/access and checksums before advancing the baseline. - Commit the final content and report what changed. ===== Commands ===== 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. ===== Release-cycle instruction ===== **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. ===== No scheduled automation yet ===== The update helper and agent instructions are repeatable, on-demand workflows. No recurring scheduler or unattended semantic updater has been enabled.