Documentation Maintenance

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

The qwertycoin-org/gitbook-docs Git repository is the reviewed source of truth. Git Sync must use master, repository root ./, and GitHub → GitBook for the initial direction. Never import stale GitBook content over a reviewed repository tree.

Release checklist

For every Core, GUI, Web Wallet, Explorer, or documentation release:

• record exact Core default-branch and release source SHAs;

• review changed CLI flags, defaults, bind addresses, and authentication;

• regenerate and review the daemon/wallet route diff with tools/extract_rpc_inventory.py;

• verify network, emission, maturity, and EPoSE parameter manifests/tests;

• compare dependency/toolchain and supported-platform workflows;

• verify release assets, checksums, signatures/notarization statements, and Docker digests;

• verify the GUI Core gitlink and Web Wallet/Explorer compatibility revisions;

• check external project links and current exchange/mining compatibility;

• update page evidence headers and development-only labels.

Required checks

python3 tools/generate_migration_manifest.py
python3 tools/validate_docs.py

Regenerate the RPC inventory from the pinned development and release Core trees and require a clean diff or review every contract change. Render every page with a GitHub-Flavored Markdown-compatible renderer and run the external-link checker before merge.

tools/import_validated_wiki.py is the auditable one-time migration helper used for this overhaul. It must not be run as routine release maintenance: GitBook content is reviewed and maintained in this repository after migration. If a future full resynchronization from another documentation source is intentionally approved, run it on an isolated branch and review the complete diff.

Safe publication

1. Work on a feature branch and open a reviewable pull request.

2. Confirm gitbook-docs.yaml defines exactly one default space with content.directory: ./.

3. Fetch master immediately before merge; do not force-push or rewrite shared history.

4. Confirm GitBook reports the repository-root connector synchronized.

5. Independently fetch https://docs.qwertycoin.org/, its sitemap, and representative new and compatibility pages.

6. Record the before/after Git SHAs and public verification time in the Validation Report.

Git Sync connected is not the same as content published. Keep DNS/custom-domain configuration unchanged unless it is independently proven wrong. Never commit GitHub or GitBook credentials.