Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows
docs: refresh stale path references in docs/CLAUDE.md (#2739)
Worktrunk Bot3c04588ccf3f
diff --git a/docs/CLAUDE.md b/docs/CLAUDE.mdindex 99be2009a..fe7815c45 100644--- a/docs/CLAUDE.md+++ b/docs/CLAUDE.md@@ -117,12 +117,12 @@ wt <command> --help-page```The generated content includes:-1. **Conceptual documentation** — from `after_long_help` in `src/cli.rs`+1. **Conceptual documentation** — from `after_long_help` in `src/cli/mod.rs`2. **Command Reference section** — the standard `--help` output### Editing command docs-**To update command documentation, edit `src/cli.rs`**, not the markdown files directly.+**To update command documentation, edit `src/cli/mod.rs`**, not the markdown files directly.- **Conceptual content** — Edit the `after_long_help` attribute on the command- **Usage/options/examples** — Edit the clap attributes (`about`, `long_about`, doc comments on args)@@ -135,7 +135,7 @@ cargo test --test integration test_docs_are_in_sync### Command documentation structure-Each command has three documentation pieces in `src/cli.rs`:+Each command has three documentation pieces in `src/cli/mod.rs`:| Piece | Source | Purpose ||-------|--------|---------|@@ -179,7 +179,7 @@ Each command has three documentation pieces in `src/cli.rs`:### Example output expansion (wt list)-The `wt list` examples use **HTML comments + code blocks** that expand to full snapshot output. In `cli.rs`, you write:+The `wt list` examples use **HTML comments + code blocks** that expand to full snapshot output. In `src/cli/mod.rs`, you write:`````<!-- wt list -->@@ -218,7 +218,7 @@ This renders differently in each context:3. Accept snapshots: `cargo insta accept`4. Sync docs: `cargo test --test integration test_docs_are_in_sync`-The examples in `cli.rs` are just command stubs — the actual output comes from snapshots generated by integration tests. This ensures docs always match real CLI behavior.+The examples in `src/cli/mod.rs` are just command stubs — the actual output comes from snapshots generated by integration tests. This ensures docs always match real CLI behavior.### Code block convention@@ -246,7 +246,7 @@ Content in `after_long_help` must work in **both** the terminal (`--help`) and t### Post-processing for web docs-The `--help-page` generator in `src/main.rs` applies post-processing to transform CLI-friendly content into web-friendly HTML:+The `--help-page` generator in `src/help.rs` applies post-processing to transform CLI-friendly content into web-friendly HTML:| CLI Source | Web Output ||------------|------------|@@ -271,7 +271,7 @@ Include subcommand documentation as H2 sections within a parent command's docs p<!-- subdoc: subcommand-name -->```-In `cli.rs`, add the placeholder anywhere in the parent command's `after_long_help`:+In `src/cli/mod.rs`, add the placeholder anywhere in the parent command's `after_long_help`:```rustafter_long_help = r#"...main documentation...