docs: title the runtime pages by their name, not by an action

"Running pi" / "Running Claude Code" put a verb in front of every sidebar
entry, which reads oddly in a list of nouns next to Agents and Getting
Started, and buries the thing the reader is scanning for. The pages are now
"Pi" and "Claude Code" -- capitalised as titles, while prose keeps the
project's own lowercase "pi".

Link text across the overview, the implementer page and between the two
runtime pages follows.

Signed-off-by: Wayne Sun <gsun@redhat.com>

Author: waynesun09

docs/.vitepress/config.ts

@@ -208,8 +208,8 @@ export default defineConfig({
           collapsed: true,
           link: "/runtimes",
           items: [
-            { text: "Running Claude Code", link: "/runtimes/claude" },
-            { text: "Running pi", link: "/runtimes/pi" },
+            { text: "Claude Code", link: "/runtimes/claude" },
+            { text: "Pi", link: "/runtimes/pi" },
           ],
         },
         {

docs/contributing/runtime-implementation.md

@@ -210,7 +210,7 @@ The `dummy` runtime executes a YAML script of operations inside the real sandbox
 
 ## pi runtime internals (#6464)
 
-User-facing pi behaviour is in [Running pi](../runtimes/pi.md). This section keeps the
+User-facing pi behaviour is in [Pi](../runtimes/pi.md). This section keeps the
 verification provenance: what was checked against pi's source, on which version, and what must be
 re-checked on a `PI_VERSION` or extension bump.
 

docs/runtimes.md

@@ -97,7 +97,7 @@ On Claude Code, pass an alias (`opus`, `sonnet`, `haiku`, `fable`) or a model id
 
 On pi, a model is `provider/id` — aliases and bare ids still work, and the provider comes from
 `FULLSEND_PI_PROVIDER` (default `anthropic-vertex`). pi reaches Claude, Gemini **and** Grok, each
-through its own provider; see [Running pi › Models and providers](runtimes/pi.md#models-and-providers).
+through its own provider; see [Pi › Models and providers](runtimes/pi.md#models-and-providers).
 
 Because harness `model:` cannot contain `/` (`validModelName` is `^[a-zA-Z0-9_.@-]+$`), a harness
 selects a pi provider with a bare `model:` plus `FULLSEND_PI_PROVIDER`.
@@ -136,8 +136,8 @@ Full per-key detail, including the exact `--tools` mapping and allowlist parsing
 
 ## Related docs
 
-- [Running Claude Code](runtimes/claude.md) — models, fallback chains, behaviour notes
-- [Running pi](runtimes/pi.md) — models and providers, behaviour differences, troubleshooting
+- [Claude Code](runtimes/claude.md) — models, fallback chains, behaviour notes
+- [Pi](runtimes/pi.md) — models and providers, behaviour differences, troubleshooting
 - [Implementing an agent runtime](contributing/runtime-implementation.md) — security matrix, interfaces, hook contract, sandbox layout
 - [Running agents locally](guides/user/running-agents-locally.md) — step-by-step local runs
 - [architecture.md](architecture.md) — where the runtime sits

docs/runtimes/claude.md

@@ -1,4 +1,4 @@
-# Running Claude Code
+# Claude Code
 
 [Claude Code](https://claude.com/claude-code) is fullsend's default runtime. Every role is supported,
 and nothing needs configuring to use it — this page is the operational detail once you are on it.
@@ -73,5 +73,5 @@ marker passes through untouched.
 ## See also
 
 - [Agent runtimes](../runtimes.md) — choosing and selecting a runtime
-- [Running pi](pi.md) — the second runtime, for Grok and Gemini
+- [Pi](pi.md) — the second runtime, for Grok and Gemini
 - [Running agents locally](../guides/user/running-agents-locally.md) — local runs

docs/runtimes/pi.md

@@ -1,4 +1,4 @@
-# Running pi
+# Pi
 
 [pi](https://github.com/earendil-works/pi) is fullsend's second agent runtime, opt-in per org or
 repo. It reaches models Claude Code cannot — **Grok** and **Gemini** alongside Claude — through the