docs: rename book/ to docs/

Author: collinsezedike

.github/workflows/docs.yml

@@ -4,7 +4,7 @@ on:
   push:
     branches: [main]
     paths:
-      - "book/**"
+      - "docs/**"
       - "README.md"
       - "CONTRIBUTING.md"
       - "SECURITY.md"
@@ -40,13 +40,13 @@ jobs:
           echo "$HOME/.local/bin" >> "$GITHUB_PATH"
 
       - name: Build book
-        run: mdbook build book
+        run: mdbook build docs
 
       - uses: actions/configure-pages@v5
 
       - uses: actions/upload-pages-artifact@v3
         with:
-          path: book/book
+          path: docs/html
 
   deploy:
     needs: build

.gitignore

@@ -1,2 +1,2 @@
 /target
-/book/book
+/docs/html

CHANGELOG.md

@@ -19,7 +19,7 @@ Initial release: a working, tested, testnet-deployed assertion and dispute oracl
   paused.
 - `contracts/demo-consumer`: a minimal example contract calling into Tholos,
   validating the cross-contract integration pattern documented in
-  [INTEGRATION.md](book/src/INTEGRATION.md) against Tholos's real compiled wasm.
+  [INTEGRATION.md](docs/src/INTEGRATION.md) against Tholos's real compiled wasm.
 - `scripts/testnet-smoke.sh`: an end-to-end check against real Stellar testnet
   infrastructure (deploy, initialize, assert, dispute, resolve).
 - CI (`fmt`, `clippy`, `test`, wasm build) on every push and pull request.

CONTRIBUTING.md

@@ -28,15 +28,15 @@ contracts/
       test.rs            Unit tests (soroban-sdk testutils, mocked ledger and auth)
   demo-consumer/        Minimal example contract that calls into Tholos
     src/
-      lib.rs             Cross-contract call pattern from book/src/INTEGRATION.md
+      lib.rs             Cross-contract call pattern from docs/src/INTEGRATION.md
       test.rs            Validates that pattern against Tholos's real compiled wasm
 scripts/
   testnet-smoke.sh      End-to-end check against real Stellar testnet infrastructure
 .github/workflows/
   ci.yml                 Runs fmt, clippy, tests, and the wasm build on every push/PR
 ```
 
-`demo-consumer` exists to keep [INTEGRATION.md](book/src/INTEGRATION.md) honest: it's not a product, it's a
+`demo-consumer` exists to keep [INTEGRATION.md](docs/src/INTEGRATION.md) honest: it's not a product, it's a
 compiled check that the documented integration pattern actually works. If you
 change Tholos's public interface, update `demo-consumer` too if it uses the
 changed function, and re-run its test.
@@ -80,7 +80,7 @@ There are two layers, and they catch different things:
 
 ## Docs site
 
-`book/` is an [mdBook](https://rust-lang.github.io/mdBook/) that publishes this
+`docs/` is an [mdBook](https://rust-lang.github.io/mdBook/) that publishes this
 repo's docs as a site, deployed automatically from `main` by
 `.github/workflows/docs.yml`. Where a given doc's real content lives depends on
 whether GitHub treats it specially:
@@ -89,15 +89,15 @@ whether GitHub treats it specially:
   stay at the repo root, because GitHub does something with them there (README
   renders on the repo homepage, CONTRIBUTING is linked when opening an issue/PR,
   SECURITY.md powers the Security tab, and CHANGELOG.md is close enough to a
-  universal convention to keep at root regardless). Their `book/src/` copies are
+  universal convention to keep at root regardless). Their `docs/src/` copies are
   one-line `\{{#include ../../X.md}}` stubs; edit the root file, not the stub.
 - `ARCHITECTURE.md`, `CONTRACT.md`, `DEPLOYMENT.md`, `GLOSSARY.md`, and
   `INTEGRATION.md` get no special treatment from GitHub at root, so their real
-  content lives directly under `book/src/`, with no root duplicate. Edit them
+  content lives directly under `docs/src/`, with no root duplicate. Edit them
   there; they're still normal markdown files GitHub renders fine if you click into
-  `book/src/CONTRACT.md` directly, they just aren't at the repo's top level.
+  `docs/src/CONTRACT.md` directly, they just aren't at the repo's top level.
 
-Preview locally with `mdbook serve book` (requires `cargo install mdbook`).
+Preview locally with `mdbook serve docs` (requires `cargo install mdbook`).
 
 ## Before opening a PR
 
@@ -112,7 +112,7 @@ cargo test
 ```
 
 If you changed the contract's public interface (functions, types, errors), update
-[CONTRACT.md](book/src/CONTRACT.md) to match; it's meant to stay in sync with
+[CONTRACT.md](docs/src/CONTRACT.md) to match; it's meant to stay in sync with
 `lib.rs`, not drift into a separate design doc.
 
 ## Commit messages

README.md

@@ -19,12 +19,12 @@ The assertion and dispute contract (`contracts/tholos`) is implemented, tested,
 - CI (fmt, clippy, tests, wasm build): done
 - Fee-funded reward for uncontested finalizes: not yet (no fee-generating market layer exists to fund it)
 
-See [CONTRACT.md](book/src/CONTRACT.md) for the full interface and known gaps,
-[ARCHITECTURE.md](book/src/ARCHITECTURE.md) for design rationale, or
-[INTEGRATION.md](book/src/INTEGRATION.md) if you're building a contract that wants
+See [CONTRACT.md](docs/src/CONTRACT.md) for the full interface and known gaps,
+[ARCHITECTURE.md](docs/src/ARCHITECTURE.md) for design rationale, or
+[INTEGRATION.md](docs/src/INTEGRATION.md) if you're building a contract that wants
 to call into Tholos. Deploying your own instance: see
-[DEPLOYMENT.md](book/src/DEPLOYMENT.md). New to the terminology: see
-[GLOSSARY.md](book/src/GLOSSARY.md).
+[DEPLOYMENT.md](docs/src/DEPLOYMENT.md). New to the terminology: see
+[GLOSSARY.md](docs/src/GLOSSARY.md).
 
 ## Why
 
@@ -43,7 +43,7 @@ stateDiagram-v2
     Resolved --> [*]
 ```
 
-A bond gets posted, a window gives anyone the chance to dispute it, and if disputed, a resolver committee votes to decide who was right. See [CONTRACT.md](book/src/CONTRACT.md) for the function reference and events, or [ARCHITECTURE.md](book/src/ARCHITECTURE.md) for sequence diagrams of each flow.
+A bond gets posted, a window gives anyone the chance to dispute it, and if disputed, a resolver committee votes to decide who was right. See [CONTRACT.md](docs/src/CONTRACT.md) for the function reference and events, or [ARCHITECTURE.md](docs/src/ARCHITECTURE.md) for sequence diagrams of each flow.
 
 ## Tech stack
 

SECURITY.md

@@ -5,7 +5,7 @@
 Tholos has not had an external security audit. It has undergone one internal
 review pass, which found and fixed a real reentrancy vulnerability (see
 [CHANGELOG.md](CHANGELOG.md) and the "Security notes" section of
-[CONTRACT.md](book/src/CONTRACT.md)). Treat it as pre-production software: appropriate for
+[CONTRACT.md](docs/src/CONTRACT.md)). Treat it as pre-production software: appropriate for
 testnet use and further review, not for deployments securing meaningful value on
 mainnet until it has been audited.
 

book/book.toml docs/book.tomlbook/book.toml renamed to docs/book.toml

@@ -5,9 +5,12 @@ authors = ["drydocs"]
 language = "en"
 src = "src"
 
+[build]
+build-dir = "html"
+
 [output.html]
 git-repository-url = "https://github.com/drydocs/tholos"
-edit-url-template = "https://github.com/drydocs/tholos/edit/main/book/{path}"
+edit-url-template = "https://github.com/drydocs/tholos/edit/main/docs/{path}"
 additional-js = ["mermaid.min.js", "mermaid-init.js"]
 
 [preprocessor]