Restore GitBook GitHub sync for docs.thorchain.org (stale published content)

[dimitri-circle]

Summary

The source updates for docs.thorchain.org are not reaching the published GitBook site. Kenton Ralph Toews: please verify this finding, confirm the responsible GitBook/GitHub administrator, and approve the recovery plan below. No GitHub assignee is set because your account identity has not been verified.

Evidence rechecked September 4, 2026

• The current default branch is master, at b6a0096b (August 22). Its README.md uses the decentralized-exchange introduction approved in PR #121.
• The live introduction still uses the older cross-chain liquidity-protocol wording.
• The live site's GitBook metadata still reports installationProvider: github, installationStatus: unauthenticated, and published revision ujvKhO39A1ZLVHGJEvBM. This reproduces the September 1 audit finding. HTTP availability alone is not proof of a successful sync.
• This issue belongs to thorchain/docs and GitBook. It is separate from the GitLab THORNode developer site at dev.thorchain.org.
• All open and closed repository issues were checked before filing; no existing sync-recovery issue was found.

Administrator recovery plan (requires owner verification and approval)

1. Confirm the live GitBook space, owning THORChain organization, repository thorchain/docs, branch master, and root-content configuration. Confirm who can administer both sides; the precise reason authentication was lost still needs administrator evidence.
2. Preserve the current GitHub commit and GitBook revision/history, and review any GitBook-only edits or open change requests before synchronizing. Do not force-push or overwrite newer source content.
3. In the THORChain GitHub organization's installed-app settings, reauthorize/configure GitBook with access to thorchain/docs only as needed. A GitBook administrator/creator should then reconnect the correct space and branch.
4. For recovery, select GitHub → GitBook, preview the differences, and stop if unexpected content would be removed. Do not choose GitBook → GitHub against the newer source branch. No DNS/Cloudflare changes are proposed.
5. Complete the approved sync/publication and verify the canonical site. Preserve the pre-recovery snapshots for an administrator-led rollback if verification fails.

Acceptance criteria

• Kenton verifies the issue and confirms the responsible administrator and recovery approval.
• GitBook authentication is healthy; a successful sync is recorded against the intended current master commit.
• The canonical homepage displays the approved DEX introduction; representative navigation and changed pages match source and return successfully.
• Newer GitHub content and intentional GitBook-only edits are preserved or explicitly reconciled by the owner.
• Record the source SHA, GitBook revision, verification time, and tested URLs here. Confirm normal ongoing synchronization with the next approved documentation update.

Official guidance: Git Sync and administrator roles, authentication recovery, initial sync direction.

This issue records the problem and requested owner action; no integration, repository content, DNS, or production settings were changed by filing it.