Documentation Maintenance

Documentation maintenance

Verified against: Pinned source and release revisions, Qwertycoin mainnet where applicable, 2026-09-29.

Release checklist

For every Core/GUI/Web release or meaningful development-doc refresh, check:

• exact Core default-branch and release source SHAs;
• changed CLI flags/defaults and bind/authentication behavior;
• daemon/wallet route/schema diff via tools/extract_rpc_inventory.py;
• network, emission, maturity and EPoSE parameter manifests/tests;
• dependency/toolchain and supported platform workflows;
• release assets, checksums, signatures/notarization statements and Docker digests;
• GUI Core gitlink and Web Wallet/Explorer compatibility revisions;
• external project links and current exchange/mining compatibility;
• all page verification headers and development-only labels.

Run the route generator with the documented pinned worktrees, then require a clean diff or review every change. Run tools/validate_wiki.py and tools/check_external_links.py before publishing, and render every page with a GitHub-Flavored Markdown-compatible renderer. Do not maintain a second hand-written route list without the generated inventory.

GitHub Wiki has no arbitrary redirects. Preserve old page slugs as concise compatibility notices. Keep retired operational commands out of those notices; history already preserves the original text.

Never commit publication credentials. Fetch the remote wiki immediately before push, integrate intervening commits without force, rerun affected checks, then verify the visible published pages and record before/after SHAs in Validation Report.