fix(docs): P0 quality fixes with regression tests

docs/src/content/docs/features/directives.md

@@ -26,8 +26,6 @@ Directives are team rules that persist across sessions. When you say "always" or
 
 A directive is a preference, rule, or constraint the team remembers across sessions. When you say "always do X" or "never do Y", Squad captures it as a directive, writes it to the decisions inbox, and the Scribe merges it into `.squad/decisions.md` — the team's permanent memory.
 
-## How Directives Work
-
 1. **Signal Word Detection** — The coordinator listens for: "always", "never", "from now on", "remember to", "don't", "make sure to".
 2. **Capture** — Directive is written to `.squad/decisions/inbox/{timestamp}-{brief-slug}.md`.
 3. **Scribe Merge** — Scribe consolidates inbox files into `decisions.md` during the next coordination cycle.

docs/src/content/docs/features/gitlab-issues.md

@@ -162,7 +162,7 @@ For the full command reference, see the [official GitLab CLI documentation](http
 - You don't need to assign issues to specific agents — Squad routes based on domain expertise.
 - If `glab` isn't authenticated, Squad will tell you. Run `glab auth login` first.
 - MR descriptions include `Closes #N` so merging automatically closes the linked issue, just like on GitHub.
-- See [GitLab Issues Walkthrough](../tour-gitlab-issues.md) for a step-by-step tour.
+- See the [GitLab Issues feature page](./gitlab-issues.md) for the full reference.
 
 ## Sample Prompts
 

docs/src/content/docs/features/notifications.md

@@ -19,12 +19,6 @@ Your squad sends you instant messages when they need input, hit an error, or com
 
 ## How It Works
 
-Your squad can send you instant messages when they need your input. Leave your terminal, get pinged on your phone.
-
----
-
-## How It Works
-
 Squad ships zero notification infrastructure. Instead, it uses **skills** — reusable knowledge files — to teach agents when and how to ping you. You bring your own notification delivery by configuring an MCP notification server in your Copilot environment.
 
 The flow:

docs/src/content/docs/features/parallel-execution.md

@@ -26,8 +26,6 @@ Squad launches independent work in parallel by default — multiple agents work
 
 Squad runs agents in parallel whenever possible. The fan-out pattern launches all independent agents simultaneously, waits for results, then proceeds — no sequential bottlenecks unless data dependencies or reviewer gates require them.
 
-## How Parallel Execution Works
-
 When the coordinator receives work:
 
 1. **Dependency Analysis** — Check if tasks have data dependencies (A needs output from B).

docs/src/content/docs/features/plugins.md

@@ -19,12 +19,6 @@ Plugins are community-curated bundles of agent templates, skills, and best pract
 
 ## What Are Plugins?
 
-Your Squad can discover and install **plugins** — curated collections of agent templates, skills, and instructions from community repositories. Plugins solve recurring problems: Azure cloud development, React patterns, security hardening, testing strategies, and more.
-
----
-
-## What Are Plugins?
-
 Plugins are **community-curated bundles** of reusable knowledge. Each plugin contains:
 
 - **Agent templates** — specialized role charters for common needs (e.g., "AWS DevOps", "Python Data Science")

docs/src/content/docs/features/prd-mode.md

@@ -19,12 +19,6 @@ Give Squad a product requirements document and the Lead breaks it into prioritiz
 
 ## How to Use
 
-Give Squad a product requirements document. The Lead agent breaks it into work items, assigns them to the team, and tracks progress.
-
----
-
-## How to Use
-
 Paste a PRD directly into the chat:
 
 ```

docs/src/content/docs/features/routing.md

@@ -26,8 +26,6 @@ The coordinator routes work to the right agent using named routing (explicit), d
 
 The coordinator decides who handles each piece of work using a three-layer routing system: named routing (explicit assignments), domain routing (pattern matching), and skill-aware routing (capability checking). The goal: get work to the right agent without manual triage overhead.
 
-## Routing Strategies
-
 ### 1. Named Routing
 
 You explicitly name who should do the work:
@@ -76,7 +74,7 @@ Work tagged with authentication routes to Backend or Lead based on task type (im
 
 Default assignments for common patterns.
 
-## Routing Table
+## Routes
 
 | Pattern | Owner | Reason |
 |---------|-------|--------|

docs/src/content/docs/features/streams.md

@@ -1,4 +1,4 @@
-# Squad SubSquads
+# Streams
 
 > Scale Squad across multiple Codespaces by partitioning work into labeled SubSquads.
 

docs/src/content/docs/features/team-setup.md

@@ -30,8 +30,6 @@ When you first run Squad in a repository, it doesn't impose a team — it propos
 
 By default, Squad uses the **CastingEngine** to assign agent names from fictional universes (The Usual Suspects, Ocean's Eleven, etc.). The LLM proposes roles and team composition; the engine allocates curated character names, personalities, and backstories from the selected universe. Use `squad init --roles` to opt into the base role catalog (Lead, Backend, Frontend, Tester) instead of universe casting.
 
-## How Init Works
-
 1. **Discovery** — Squad scans your repository: language distribution, file structure, test frameworks, dependencies, existing workflows.
 2. **Proposal** — Based on what it finds, Squad proposes a team roster with 3-7 members and their roles.
 3. **Confirmation** — You review the proposal and can accept as-is, add members, remove members, or change roles.

docs/src/content/docs/features/worktrees.md

@@ -19,8 +19,6 @@ Squad supports git worktrees with two strategies: **worktree-local** (each workt
 
 ## What Are Worktrees?
 
-## What Are Worktrees?
-
 Git worktrees let you check out multiple branches simultaneously:
 
 ```bash