change cookbook docs links (#2231)

Co-authored-by: Nando Vieira <me@fnando.com>

Author: ElliotFriend

.cargo-husky/hooks/pre-commit

@@ -2,5 +2,8 @@
 
 set -ex
 
-cargo fmt --check || (cargo fmt && exit 1)
-make generate-full-help-doc
+make docs > /dev/null
+make fmt > /dev/null
+
+set +x
+git diff --exit-code > /dev/null || (echo "\nERROR: Staged files were modified by hooks. Please review and stage the changes." && exit 1)

.cargo-husky/hooks/pre-push

@@ -10,4 +10,4 @@ cargo clippy --all -- -Dwarnings
 
 cargo build
 cargo test --all || (echo "might need to rebuild make build-snapshot" && exit 1)
-make generate-full-help-doc
+make docs

.github/copilot-instructions.md

@@ -7,23 +7,27 @@
 Stellar CLI is a Rust-based command-line tool for interacting with the Stellar network. It's organized as a Cargo workspace with multiple crates and uses both Cargo and Make for build automation.
 
 ### Bootstrap and Build
+
 - Install system dependencies: `sudo apt-get update && sudo apt-get install -y libudev-dev libdbus-1-dev build-essential`
 - Install Rust toolchain: `rustup update` (Rust 1.89.0+ required)
 - Add WebAssembly target: `rustup target add wasm32v1-none`
 - Build main CLI: `cargo build --bin stellar` -- takes 45 seconds. NEVER CANCEL.
 - Install CLI: `make install` -- takes 3 minutes with potential network timeouts. NEVER CANCEL. Set timeout to 10+ minutes.
 
 ### Core Development Commands
+
 - Format code: `make fmt` -- takes 2 seconds
 - Run linting: `make check` -- takes 7 minutes. NEVER CANCEL. Set timeout to 15+ minutes.
 - Build main CLI only: `cargo build --bin stellar` -- takes 45 seconds. Use this for quick iterations.
 
 ### Testing
+
 - Test main soroban-cli library: `cargo test --package soroban-cli --lib` -- takes 52 seconds. NEVER CANCEL.
 - Test individual crates: `cargo test --package <crate-name>` -- typically takes 40 seconds per crate.
 - **WARNING**: Full test suite via `make test` requires building WebAssembly test fixtures and consumes significant memory and disk space. It may fail with "No space left on device" in constrained environments.
 
 ### CLI Usage and Validation
+
 - Test CLI installation: `stellar --version`
 - Basic CLI validation: `stellar --help`
 - Generate test keys: `stellar keys generate <name>`
@@ -39,6 +43,7 @@ Stellar CLI is a Rust-based command-line tool for interacting with the Stellar n
 ## Common Tasks
 
 ### Repository Structure
+
 ```
 /home/runner/work/stellar-cli/stellar-cli/
 ├── cmd/
@@ -55,6 +60,7 @@ Stellar CLI is a Rust-based command-line tool for interacting with the Stellar n
 ```
 
 ### Key Commands Reference
+
 ```bash
 # Development workflow
 cargo build --bin stellar        # Quick build (45s)
@@ -74,6 +80,7 @@ stellar keys address test      # Test key operations
 ```
 
 ### Build Time Expectations
+
 - **NEVER CANCEL** any build or test command before these timeouts:
   - `cargo build --bin stellar`: 2 minutes timeout minimum
   - `make install`: 10 minutes timeout (network issues common)
@@ -82,25 +89,30 @@ stellar keys address test      # Test key operations
   - Core library tests: 5 minutes timeout minimum
 
 ### Known Issues
+
 - **Network timeouts**: `make install` frequently encounters network timeouts with crates.io. This is normal in CI environments.
 - **Memory constraints**: Full workspace build and test may fail with OOM or "No space left on device" errors in constrained environments.
-- **Documentation generation**: `make generate-full-help-doc` may fail due to disk space constraints.
+- **Documentation generation**: `make docs` may fail due to disk space constraints.
 
 ### Working Around Constraints
+
 - Use `cargo build --bin stellar` instead of full workspace build for development
 - Test individual packages with `cargo test --package <name>` instead of full test suite
 - Use `cargo install --force --locked --path ./cmd/stellar-cli` as alternative to `make install`
 
 ## Critical Warnings
+
 - **NEVER CANCEL builds or tests** before the specified timeout periods
 - **Always validate changes** by building and testing the CLI before committing
 - **Network issues are common** - retry `make install` if it fails with timeouts
 - **Use surgical builds** when possible to avoid memory/disk issues
 
 ## CI/CD Integration
+
 The project uses GitHub Actions with workflows in `.github/workflows/`:
+
 - `rust.yml`: Main CI pipeline with formatting, linting, building, and testing
 - `e2e.yml`: End-to-end system tests
 - `binaries.yml`: Multi-platform binary builds
 
-Always run `make fmt` and `make check` locally before pushing to ensure CI passes.
+Always run `make fmt` and `make check` locally before pushing to ensure CI passes.

.github/workflows/docs.yml

@@ -6,7 +6,8 @@ on:
   pull_request:
 
 concurrency:
-  group: ${{ github.workflow }}-${{ github.ref_protected == 'true' && github.sha || github.ref }}
+  group:
+    ${{ github.workflow }}-${{ github.ref_protected == 'true' && github.sha || github.ref }}
   cancel-in-progress: true
 
 jobs:

.github/workflows/rust.yml

@@ -31,9 +31,8 @@ jobs:
     if: always()
     needs:
       [
-        fmt,
         cargo-deny,
-        check-generated-full-help-docs,
+        check,
         build-and-test,
         build-and-test-macos,
         build-and-test-windows,
@@ -42,18 +41,9 @@ jobs:
       ]
     runs-on: ubuntu-latest
     steps:
-      - if:
-          contains(needs.*.result, 'failure') || contains(needs.*.result,
-          'cancelled')
+      - if: contains(needs.*.result, 'failure') || contains(needs.*.result, 'cancelled')
         run: exit 1
 
-  fmt:
-    runs-on: ubuntu-latest-8-cores
-    steps:
-      - uses: actions/checkout@v5
-      - run: rustup update
-      - run: cargo fmt --all --check
-
   cargo-deny:
     runs-on: ubuntu-latest
     strategy:
@@ -67,15 +57,15 @@ jobs:
         with:
           command: check ${{ matrix.check }}
 
-  check-generated-full-help-docs:
+  check:
     runs-on: ubuntu-latest-8-cores
     steps:
       - uses: actions/checkout@v5
       - uses: stellar/actions/rust-cache@main
-      - run: rustup update
       - run: sudo apt update && sudo apt install -y libudev-dev libdbus-1-dev
-      - run: make generate-full-help-doc
-      - run: git add -N . && git diff HEAD --exit-code
+      - run: rustup update
+      - run: npm install
+      - run: make check
 
   build-and-test:
     strategy:
@@ -96,9 +86,7 @@ jobs:
           rust-version: ${{ matrix.rust }}
 
   build-and-test-macos:
-    if:
-      github.ref == 'refs/heads/main' || startsWith(github.ref,
-      'refs/heads/release/') || startsWith(github.head_ref, 'release/')
+    if: github.ref == 'refs/heads/main' || startsWith(github.ref, 'refs/heads/release/') || startsWith(github.head_ref, 'release/')
     strategy:
       fail-fast: false
       matrix:
@@ -117,9 +105,7 @@ jobs:
           rust-version: ${{ matrix.rust }}
 
   build-and-test-windows:
-    if:
-      github.ref == 'refs/heads/main' || startsWith(github.ref,
-      'refs/heads/release/') || startsWith(github.head_ref, 'release/')
+    if: github.ref == 'refs/heads/main' || startsWith(github.ref, 'refs/heads/release/') || startsWith(github.head_ref, 'release/')
     strategy:
       fail-fast: false
       matrix:

CONTRIBUTING.md

@@ -2,84 +2,76 @@
 
 Thanks for taking the time to improve stellar-cli!
 
-The following is a set of guidelines for contributions and may change over time.
-Feel free to suggest improvements to this document in a pull request.We want to make it as easy as possible to contribute changes that help the Stellar network grow and
-thrive. There are a few guidelines that we ask contributors to follow so that we can merge your
-changes quickly.
+The following is a set of guidelines for contributions and may change over time. Feel free to suggest improvements to this document in a pull request.We want to make it as easy as possible to contribute changes that help the Stellar network grow and thrive. There are a few guidelines that we ask contributors to follow so that we can merge your changes quickly.
 
 ## Getting Started
 
-* Make sure you have a [GitHub account](https://github.com/signup/free).
-* Create a GitHub issue for your contribution, assuming one does not already exist.
-  * Clearly describe the issue including steps to reproduce if it is a bug.
-* Fork the repository on GitHub.
+- Make sure you have a [GitHub account](https://github.com/signup/free).
+- Create a GitHub issue for your contribution, assuming one does not already exist.
+  - Clearly describe the issue including steps to reproduce if it is a bug.
+- Fork the repository on GitHub.
 
 ## Setting up development environment
 
 There are 2 ways to begin developing stellar-cli:
 
-### Installing all required dependencies 
+### Installing all required dependencies
 
-You may want to install all required dependencies locally. This includes installing `rustup`, `make`, `libudev`, `jq` from your package manager. After all dependencies are installed, you can start with running `make install` to build `stellar-cli` and install it! 
+You may want to install all required dependencies locally. This includes installing `rustup`, `make`, `libudev`, `jq` from your package manager. After all dependencies are installed, you can start with running `make install` to build `stellar-cli` and install it!
 
 ### Using `nix`
 
 If you don't want to install necessary dependencies from above, you can run development shell using [nix](https://nixos.org/guides/how-nix-works/) (make sure to [install](https://nixos.org/download/) version above 2.20). After installing `nix`, simply run `nix develop` that will start new `bash` session in your current terminal. If you want to use different shell (e.g. `zsh`) you can run `nix develop -c zsh`
 
 This session will have:
+
 1. All required dependencies installed
 2. `stellar` alias (overwriting your existing `stellar` installed via cargo, if any)
 3. Configured auto-complete for the working git branch
 
 You can add extra configuration in your `local.sh` file (for example, if you want to export some extra variables for your devshell you can put following in your `local.sh`:
+
 ```shell
 #!/usr/bin/env bash
 export STELLAR_NETWORK=testnet
 ```
-Note that all of dependencies and configurations mentioned above is available only in your local development shell, not outside of it.
 
+Note that all of dependencies and configurations mentioned above is available only in your local development shell, not outside of it.
 
 ### Minor Changes
 
 #### Documentation
 
-For small changes to comments and documentation, it is not
-always necessary to create a new GitHub issue. In this case, it is
-appropriate to start the first line of a commit with 'doc' instead of
-an issue number.
+For small changes to comments and documentation, it is not always necessary to create a new GitHub issue. In this case, it is appropriate to start the first line of a commit with 'doc' instead of an issue number.
 
 ## Finding things to work on
 
-The first place to start is always looking over the current GitHub issues for the project you are
-interested in contributing to. Issues marked with [help wanted][help-wanted] are usually pretty
-self-contained and a good place to get started.
+The first place to start is always looking over the current GitHub issues for the project you are interested in contributing to. Issues marked with [help wanted][help-wanted] are usually pretty self-contained and a good place to get started.
 
-Stellar.org also uses these same GitHub issues to keep track of what we are working on. If you see
-any issues that are assigned to a particular person or have the `in progress` label, that means
-someone is currently working on that issue this issue in the next week or two.
+Stellar.org also uses these same GitHub issues to keep track of what we are working on. If you see any issues that are assigned to a particular person or have the `in progress` label, that means someone is currently working on that issue this issue in the next week or two.
 
 Of course, feel free to create a new issue if you think something needs to be added or fixed.
 
-
 ## Making Changes
 
-* Fork the stellar-cli repo to your own Github account
+- Fork the stellar-cli repo to your own Github account
+
+- List the current configured remote repository for your fork. Your git remote should initially look like this.
+
+  ```
+  $ git remote -v
+  > origin  https://github.com/YOUR_USERNAME/stellar-cli.git (fetch)
+  > origin  https://github.com/YOUR_USERNAME/stellar-cli.git (push)
+  ```
 
-* List the current configured remote repository for your fork. Your git remote
-should initially look like this. 
-   ```
-   $ git remote -v
-   > origin  https://github.com/YOUR_USERNAME/stellar-cli.git (fetch)
-   > origin  https://github.com/YOUR_USERNAME/stellar-cli.git (push)
-   ```
+- Set the `stellar/stellar-cli` repo as the remote upstream repository that will sync with your fork.
 
-* Set the `stellar/stellar-cli` repo as the remote upstream repository that will
-sync with your fork. 
   ```
   git remote add upstream https://github.com/stellar/stellar-cli.git
   ```
 
-* Verify the new upstream repository you've specified for your fork.
+- Verify the new upstream repository you've specified for your fork.
+
   ```
   $ git remote -v
   > origin    https://github.com/YOUR_USERNAME/stellar-cli.git (fetch)
@@ -88,38 +80,33 @@ sync with your fork.
   > upstream  https://github.com/stellar/stellar-cli.git (push)
   ```
 
-* Add git hooks for commits and pushes so that checks run before pushing:
+- Add git hooks for commits and pushes so that checks run before pushing:
+
   ```
   ./install_githooks.sh
   ```
 
-* Create a topic branch for your changes in your local repo. When you push you should be able
-to create PR based on upstream stellar/stellar-cli.
-
-* Make sure you have added the necessary tests for your changes and make sure all tests pass.
+- Create a topic branch for your changes in your local repo. When you push you should be able to create PR based on upstream stellar/stellar-cli.
 
+- Make sure you have added the necessary tests for your changes and make sure all tests pass.
 
 ## Submitting Changes
 
-* All content, comments, pull requests and other contributions must comply with the
-  [Stellar Code of Conduct][coc].
-* Push your changes to a topic branch in your fork of the repository.
-* Submit a pull request to the repo in the Stellar organization.
-  * Include a descriptive [commit message][commit-msg].
-  * Changes contributed via pull request should focus on a single issue at a time.
-  * Rebase your local changes against the master branch. Resolve any conflicts that arise.
-
+- All content, comments, pull requests and other contributions must comply with the [Stellar Code of Conduct][coc].
+- Push your changes to a topic branch in your fork of the repository.
+- Submit a pull request to the repo in the Stellar organization.
+  - Include a descriptive [commit message][commit-msg].
+  - Changes contributed via pull request should focus on a single issue at a time.
+  - Rebase your local changes against the master branch. Resolve any conflicts that arise.
 
-At this point you're waiting on us. We like to at least comment on pull requests within three
-business days (typically, one business day). We may suggest some changes, improvements or
-alternatives.
+At this point you're waiting on us. We like to at least comment on pull requests within three business days (typically, one business day). We may suggest some changes, improvements or alternatives.
 
 # Additional Resources
 
-* #dev-discussion channel on [Discord](https://discord.gg/BYPXtmwX)
+- #dev-discussion channel on [Discord](https://discord.gg/BYPXtmwX)
 
 This document is inspired by:
 
-[help-wanted]: https://github.com/stellar/stellar-cli/contribute 
+[help-wanted]: https://github.com/stellar/stellar-cli/contribute
 [commit-msg]: https://github.com/erlang/otp/wiki/Writing-good-commit-messages
 [coc]: https://github.com/stellar/.github/blob/master/CODE_OF_CONDUCT.md