max-sixty · Sep 12, 2026 · Sep 1, 2026 · Sep 1, 2026 · Sep 1, 2026 · Sep 1, 2026
diff --git a/.config/lychee.toml b/.config/lychee.toml
@@ -88,12 +88,7 @@ exclude = [
 exclude_path = [
     # Generated plugin-skills mirror: a byte-identical copy of `skills/`, synced
     # by `test_docs_are_in_sync`. Every file here is already link-checked at its
-    # authored `skills/` source, where `reference/README.md` is a symlink to the
-    # repo-root README and its relative `docs/public/logo.png` resolves. The sync
-    # dereferences that symlink into a real file, so under the mirror the
-    # repo-root-relative image path resolves to a nonexistent
-    # `plugins/worktrunk/skills/worktrunk/reference/docs/public/logo.png`.
-    # Excluding the redundant copy avoids that false positive without losing
-    # coverage (the authored source is still checked).
+    # authored `skills/` source, so checking the copy costs time and finds
+    # nothing new.
     "plugins/worktrunk/skills/",
 ]
diff --git a/.gitattributes b/.gitattributes
@@ -3,11 +3,8 @@
 # belong in the primary source (src/cli/mod.rs for command pages,
 # docs/src/content/docs/*.md for everything else).
 skills/worktrunk/reference/*.md linguist-generated=true
-# Skill-only files and the top-level README symlink are primary sources — edited
-# directly, not regenerated from docs/src/content/docs/. Exempt them so real edits stay
-# visible in PR diffs.
-skills/worktrunk/reference/README.md linguist-generated=false
-skills/worktrunk/reference/shell-integration.md linguist-generated=false
+# Skill-only files are primary sources — edited directly, not regenerated from
+# docs/src/content/docs/. Exempt them so real edits stay visible in PR diffs.
 skills/worktrunk/reference/troubleshooting.md linguist-generated=false
 # The plugin skills tree is a real-file mirror of repo-root skills/, rewritten by
 # `test_docs_are_in_sync`'s `sync_plugin_skills_mirror` stage. Nothing here is

diff --git a/CLAUDE.md b/CLAUDE.md
@@ -46,7 +46,7 @@ Load relevant skills before starting; reload when scope changes mid-session. Pro
 
 ## Documentation
 
-Behavior changes require doc updates. `src/cli/mod.rs` (`after_long_help` plus clap attributes) is the PRIMARY SOURCE for command pages; their rendered mirrors in `docs/src/content/docs/` and `skills/worktrunk/reference/` are generated, as is all of `plugins/worktrunk/skills/` — but both directories also hold hand-edited primaries (non-command docs in `docs/src/content/docs/`, skill-only pages like `shell-integration.md` in the reference dir), so check which file is primary in the sync taxonomy before editing. Ask: "does `--help` still describe what the code does?" `cargo test --test integration test_docs_are_in_sync` checks doc sync; editing help text (`after_long_help`, `about`, arg docs) also changes the rendered `--help` snapshots, which that test leaves untouched — `cargo insta test --accept --test integration -- test_help` regenerates them (the pre-merge hook runs both). Sync taxonomy, help-text authoring (three render contexts, link text, config-TOML blocks): `docs/CLAUDE.md`.
+Behavior changes require doc updates. `src/cli/mod.rs` (`after_long_help` plus clap attributes) is the PRIMARY SOURCE for command pages; their rendered mirrors in `docs/src/content/docs/` and `skills/worktrunk/reference/` are generated, as is all of `plugins/worktrunk/skills/` — but both directories also hold hand-edited primaries (non-command docs in `docs/src/content/docs/`, skill-only pages like `troubleshooting.md` in the reference dir), so check which file is primary in the sync taxonomy before editing. Ask: "does `--help` still describe what the code does?" `cargo test --test integration test_docs_are_in_sync` checks doc sync; editing help text (`after_long_help`, `about`, arg docs) also changes the rendered `--help` snapshots, which that test leaves untouched — `cargo insta test --accept --test integration -- test_help` regenerates them (the pre-merge hook runs both). Sync taxonomy, help-text authoring (three render contexts, link text, config-TOML blocks): `docs/CLAUDE.md`.
 
 ## Plugin Layout
 

diff --git a/README.md b/README.md
@@ -31,7 +31,7 @@ A quick demo:
 
 AI agents like Claude Code and Codex can handle longer tasks without
 supervision, such that it's possible to manage 5-10+ in parallel. Git's native
-worktree feature give each agent its own working directory, so they don't step
+worktree feature gives each agent its own working directory, so they don't step
 on each other's changes.
 
 But the git worktree UX is clunky. Even a task as small as starting a new
@@ -238,6 +238,18 @@ The `-x` flag runs a command after switching; arguments after `--` are passed to
 - [Open an issue](https://github.com/max-sixty/worktrunk/issues/new?title=&body=%23%23%20Description%0A%0A%3C!--%20Describe%20the%20bug%20or%20feature%20request%20--%3E%0A%0A%23%23%20Context%0A%0A%3C!--%20Any%20relevant%20context%3A%20your%20workflow%2C%20what%20you%20were%20trying%20to%20do%2C%20etc.%20--%3E) — feedback, feature requests, even a small friction or imperfect user message, or [a worktree pain not yet solved](https://github.com/max-sixty/worktrunk/issues/new?title=Worktree%20friction%3A%20&body=%23%23%20The%20friction%0A%0A%3C!--%20What%20worktree-related%20task%20is%20still%20painful%3F%20--%3E%0A%0A%23%23%20Current%20workaround%0A%0A%3C!--%20How%20do%20you%20handle%20this%20today%3F%20--%3E%0A%0A%23%23%20Ideal%20solution%0A%0A%3C!--%20What%20would%20make%20this%20easier%3F%20--%3E)
 - Share: [X](https://twitter.com/intent/tweet?text=Worktrunk%20%E2%80%94%20CLI%20for%20git%20worktree%20management&url=https%3A%2F%2Fworktrunk.dev) · [Reddit](https://www.reddit.com/submit?url=https%3A%2F%2Fworktrunk.dev&title=Worktrunk%20%E2%80%94%20CLI%20for%20git%20worktree%20management) · [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fworktrunk.dev)
 
+### Running the tests
+
+```bash
+cargo test
+```
+
+The shell integration tests need bash, zsh, fish, nushell, and pwsh, plus `jq`:
+
+```bash
+cargo test --test integration --features shell-integration-tests
+```
+
 > ### 📚 Full documentation at [worktrunk.dev](https://worktrunk.dev) 📚
 
 ### Star history

diff --git a/dev/config.example.toml b/dev/config.example.toml
diff --git a/dev/wt.example.toml b/dev/wt.example.toml
diff --git a/docs/CLAUDE.md b/docs/CLAUDE.md
@@ -114,12 +114,12 @@ There are three source categories:
    region in `docs/src/content/docs/{command}.md`, then generates the matching
    `skills/worktrunk/reference/` page.
 2. **Non-command pages**: files such as `claude-code.md`, `extending.md`,
-   `faq.md`, `llm-commits.md`, `tips-patterns.md`, and `worktrunk.md` are primary
-   in `docs/src/content/docs/`. The sync test derives the skill copy.
-3. **Skill-only pages**: files such as `shell-integration.md` and
-   `troubleshooting.md` are primary in `skills/worktrunk/reference/` and have no
-   site page. When adding one, add a `linguist-generated=false` entry to
-   `.gitattributes`.
+   `faq.md`, `llm-commits.md`, `shell-integration.md`, `tips-patterns.md`, and
+   `worktrunk.md` are primary in `docs/src/content/docs/`. The sync test derives
+   the skill copy.
+3. **Skill-only pages**: `troubleshooting.md` is primary in
+   `skills/worktrunk/reference/` and has no site page. When adding one, add a
+   `linguist-generated=false` entry to `.gitattributes`.
 
 Never hand-edit a generated mirror.
 

diff --git a/docs/astro.config.mjs b/docs/astro.config.mjs
@@ -57,6 +57,7 @@ export default defineConfig({
       },
       customCss: ['./src/styles/custom.css'],
       components: {
+        Footer: './src/components/Footer.astro',
         Head: './src/components/Head.astro',
         PageTitle: './src/components/PageTitle.astro',
         Pagination: './src/components/Pagination.astro',

diff --git a/docs/public/.well-known/agent-skills/index.json b/docs/public/.well-known/agent-skills/index.json
diff --git a/docs/public/llms.txt b/docs/public/llms.txt
diff --git a/docs/public/shell-integration.md b/docs/public/shell-integration.md
diff --git a/docs/src/components/Footer.astro b/docs/src/components/Footer.astro
@@ -0,0 +1,51 @@
+---
+// Starlight's own footer carries only the edit link, so the site had nowhere
+// to name its version, its releases, or its license, and /code-signing/ was
+// reachable only from a collapsed block on the homepage. This wraps the
+// default rather than replacing it, keeping the upstream merge surface to the
+// one element added below.
+import Default from '@astrojs/starlight/components/Footer.astro';
+
+// The published version is whatever Cargo.toml says at build time; a second
+// copy here would go stale on the next release. `?raw` resolves at build time
+// relative to this file, unlike a runtime path in the bundled output.
+import cargoToml from '../../../Cargo.toml?raw';
+
+const repository = 'https://github.com/max-sixty/worktrunk';
+
+const version = cargoToml.match(/^\[package\][\s\S]*?^version = "([^"]+)"$/m)?.[1];
+if (!version) throw new Error('No [package] version in Cargo.toml');
+---
+
+<Default />
+
+<footer class="wt-site-footer">
+  <a href={`${repository}/releases/tag/v${version}`}>v{version}</a>
+  <a href={`${repository}/releases`}>Releases</a>
+  <a href={`${repository}/blob/main/CHANGELOG.md`}>Changelog</a>
+  <a href="/code-signing/">Code signing</a>
+  <a href={`${repository}/blob/main/LICENSE`}>MIT OR Apache-2.0</a>
+</footer>
+
+<style>
+  .wt-site-footer {
+    display: flex;
+    flex-wrap: wrap;
+    gap: 0.4rem 1.25rem;
+    margin-top: 2.5rem;
+    border-top: 1px solid var(--sl-color-hairline);
+    padding-top: 1rem;
+    color: var(--sl-color-gray-3);
+    font-size: var(--sl-text-xs);
+  }
+
+  .wt-site-footer a {
+    color: inherit;
+    text-decoration: none;
+  }
+
+  .wt-site-footer a:hover {
+    color: var(--wt-copper);
+    text-decoration: underline;
+  }
+</style>
diff --git a/docs/src/content/docs/claude-code.md b/docs/src/content/docs/claude-code.md
@@ -2,7 +2,7 @@
 title: "Agent Integration"
 description: "Worktrunk plugins for Claude Code, Codex, OpenCode, and Gemini CLI: a configuration skill, wt list activity tracking, and Claude-only worktree isolation."
 sidebar:
-  order: 23
+  order: 21
 ---
 Worktrunk ships a plugin for each supported agent CLI. What a plugin provides depends on the hooks that CLI exposes:
 
@@ -11,9 +11,11 @@ Worktrunk ships a plugin for each supported agent CLI. What a plugin provides de
 | Configuration skill | ✓ | ✓ |  | ✓ |
 | Activity tracking (🤖/💬 in `wt list`) | ✓ | ✓ | ✓ | ✓ |
 | Worktree isolation | ✓ |  |  |  |
-| `/wt-switch-create` command | ✓ |  |  |  |
+| `/wt-switch-create` skill | ✓ | ✓\* |  | ✓\* |
 
-The configuration skill is documentation the agent reads to help set up LLM commits, hooks, and troubleshooting. Activity tracking shows which worktrees have running sessions. Worktree isolation needs worktree-lifecycle hooks and `/wt-switch-create` needs session working-directory switching — both Claude Code-only, so Codex, OpenCode, and Gemini users invoke `wt switch --create` and `wt remove` directly. Codex tracks activity through its own `Stop` and `SessionEnd` hooks.
+\* Codex and Gemini load the `/wt-switch-create` skill from the same shared skill set, but neither lets a skill change the session's working directory, so it does nothing there.
+
+The configuration skill is documentation the agent reads to help set up LLM commits, hooks, and troubleshooting. Activity tracking shows which worktrees have running sessions. Worktree isolation needs worktree-lifecycle hooks, which only Claude Code exposes, so Codex, OpenCode, and Gemini users invoke `wt switch --create` and `wt remove` directly. Codex tracks activity through its own `Stop` and `SessionEnd` hooks.
 
 ## Installation
 
@@ -125,7 +127,7 @@ Three things to get right:
 
 Claude Code agents can run in isolated worktrees (`isolation: "worktree"`). By default, Claude Code creates these with `git worktree add`. The plugin's `WorktreeCreate` and `WorktreeRemove` hooks route this through `wt switch --create` and `wt remove` instead, so worktrees created by agents get worktrunk's naming conventions, hooks, and lifecycle management.
 
-## `/wt-switch-create` command (Claude Code only)
+## `/wt-switch-create` skill (Claude Code only)
 
 `/wt-switch-create [<branch>] [<repo>] [-- <task>]` starts a task in a fresh worktree without leaving the session: it creates the worktree, switches into it, and runs the task (all arguments optional). The worktree shows up in `wt list`; merge or remove it with `wt merge` / `wt remove`.
 
@@ -142,6 +144,7 @@ Worktree state comes from the same cells [`wt list`](/list/) renders; Claude Cod
   <source srcset="/assets/docs/dark/wt-statusline.gif" media="(prefers-color-scheme: dark)">
   <img src="/assets/docs/light/wt-statusline.gif" alt="Claude Code statusline demo" width="1600" height="900">
 </picture>
+<figcaption>Switching to a worktree, then launching Claude Code with the statusline configured</figcaption>
 </figure>
 
 Add to `~/.claude/settings.json`:

diff --git a/docs/src/content/docs/code-signing.md b/docs/src/content/docs/code-signing.md
@@ -2,8 +2,7 @@
 title: "Code Signing Policy"
 description: "How Worktrunk's Windows release binaries are code-signed: certificate provenance, the build and signing pipeline, project roles, and per-release approval."
 sidebar:
-  order: 26
-  hidden: true
+  order: 27
 ---
 This page is Worktrunk's **code signing policy**. It describes what gets signed, which certificate is used, how the signing pipeline works, and who authorizes each release. It exists both to document the process for users and to satisfy the transparency requirements of the [SignPath Foundation](https://signpath.org/) open-source code signing program.