Add AEO citation blocks (40-60 word summaries) to key pages (#63)

* Add AEO citation blocks (40-60 word summaries) to 15 key docs pages

Add answer-first introductory paragraphs to Tier 1 docs pages to improve
AI answer engine citability. Each citation block is a concise 40-60 word
summary placed at the top of the page that directly answers 'What is this
feature?' in a self-contained, extractable format.

Pages updated:
- Site root (index.mdx), quickstart, agents overview
- Local agents, cloud agents, CLI agents overviews
- Capabilities, MCP, Warp Drive, Blocks, Code, Editor overviews
- Oz CLI and API/SDK references, Enterprise overview

Co-Authored-By: Oz <oz-agent@warp.dev>

* Reduce em dash usage in citation blocks by ~50%

Replace 5 of 9 em dashes with commas, periods, or rewording. Keep em
dashes only where they serve as strong contrast or parenthetical asides
(cloud agents, code, blocks, editor).

Co-Authored-By: Oz <oz-agent@warp.dev>

* Apply suggestion from @oz-for-oss[bot]

Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com>

* Add Phase 2 citation blocks and fix 'open source' hyphen

Add 40-60 word answer-first citation blocks to 9 more pages:
- Model choice, Agent Profiles, Teams, Admin Panel
- Code Review, Command Palette, Sessions, Supported Shells
- Plans and billing

Also fix 'open-source' -> 'open source' on index.mdx per style guide.

9 Phase 2 pages already had good intros and were left unchanged:
Skills, Rules, Codebase Context, Environments, Secrets,
Integrations, Planning, Code Editor, Managing Cloud Agents.

Co-Authored-By: Oz <oz-agent@warp.dev>

* Add Phase 3 citation blocks to 32 high-value pages

Add 40-60 word answer-first citation blocks to remaining high-value pages:
- Capabilities: Full Terminal Use, Slash Commands, Task Lists
- Cloud agents: Slack integration, cloud providers, demo issue triage
- Local agents: Active AI, code diffs, interactive code review,
  interacting with agents, terminal/agent modes, generate, voice,
  and all 5 agent-context sub-pages (blocks, images, selections,
  URLs, @ context)
- Code: Vim keybindings, file tree, find and replace
- Warp Drive: Workflows, Notebooks, Prompts, Environment Variables,
  Agent Mode Context, Warp on the Web
- Reference: CLI agent profiles, troubleshooting, Warp Drive context,
  reference index
- Getting started: Agents in Warp, Agent FAQs

42 pages already had good intros and were left unchanged.
10 deep procedural pages (self-hosting) were skipped.

Co-Authored-By: Oz <oz-agent@warp.dev>

---------

Co-authored-by: Oz <oz-agent@warp.dev>
Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com>

Author: 3 people

src/content/docs/agent-platform/capabilities/agent-profiles-permissions.mdx

@@ -6,6 +6,8 @@ description: >-
 ---
 import { Tabs, TabItem } from '@astrojs/starlight/components';
 
+Agent Profiles let you configure how Warp's agents behave in different situations, including autonomy level, base model, tool access, and command permissions. Create multiple profiles for different workflows, control which commands run automatically, and set MCP server access rules per profile.
+
 ## Agent Profiles
 
 Agent Profiles let you configure how your Agent behaves in different situations. Each profile defines the Agent's autonomy, base models, and tool access. You can create multiple profiles and edit them directly in **Settings** > **Agents** > **Profiles**.

src/content/docs/agent-platform/capabilities/full-terminal-use.mdx

@@ -7,7 +7,7 @@ description: >-
 import { Tabs, TabItem } from '@astrojs/starlight/components';
 import VideoEmbed from '@components/VideoEmbed.astro';
 
-Full Terminal Use lets Warp's agent operate directly inside interactive terminal applications, such as database shells, debuggers, text editors, long-running servers, and more.
+Full Terminal Use lets Warp's agent operate directly inside interactive terminal applications like database shells, debuggers, text editors, and long-running servers. The agent can see the live terminal buffer, write commands, respond to prompts, and hand control back to you at any time.
 
 The agent can see the live terminal buffer (terminal state), write to the PTY to run commands, respond to prompts, and continue working inside the running process while you stay in control.
 

src/content/docs/agent-platform/capabilities/index.mdx

@@ -5,9 +5,7 @@ description: >-
   what context they have access to, and how they execute tasks.
 ---
 
-These capabilities are the foundational building blocks that define how agents operate. These include the context sources agents can access, the rules that guide their behavior, and the tools they can use.
-
-Understanding these capabilities helps you get the most out of agents by configuring them to match your workflows and preferences.
+Agent capabilities are the core building blocks that define how Warp's agents operate, including the context sources agents can access, the rules that guide their behavior, the tools they can use, and the models they run on. Configure these capabilities to match your workflows and preferences.
 
 ## Capabilities in this section
 

src/content/docs/agent-platform/capabilities/model-choice.mdx

@@ -7,6 +7,8 @@ description: >-
   auto-select the best model).
 ---
 
+Warp lets you choose from a curated set of large language models to power your agents, or let Warp auto-select the best model for each task. Models from OpenAI, Anthropic, Google, and open source providers are available, with configurable reasoning levels and per-profile defaults.
+
 ## Available models
 
 Warp lets you choose from a curated set of Large Language Models (LLMs) to power your Agentic Development Environment.

src/content/docs/agent-platform/capabilities/slash-commands.mdx

@@ -5,7 +5,7 @@ description: >-
   built-in actions or saved prompts without leaving the input field.
 ---
 
-When using Agent Mode or Auto-Detection Mode, typing `/` in the input field opens the Slash Commands menu.
+Slash Commands are quick actions and saved prompts you can invoke by typing `/` in Agent Mode or Auto-Detection Mode. They provide instant access to built-in actions like starting conversations, creating environments, switching models, and running saved prompts from Warp Drive.
 
 <figure>
 ![Slash Commands menu](../../../../assets/agent-platform/slash-commands-menu.png)

src/content/docs/agent-platform/capabilities/task-lists.mdx

@@ -6,9 +6,7 @@ description: >-
   time.
 ---
 
-The Agent can automatically break down complex requests into clear, trackable steps in the form of a task list with to-do items.\
-\
-When you make a sufficiently complex request that requires multiple actions, the Agent will automatically create a list of steps, execute them in order, and track progress from start to finish. There’s no need to adjust settings or enable a special mode—the Agent detects and creates task lists automatically.
+Task Lists let Warp's agent automatically break down complex requests into clear, trackable steps. When a request requires multiple actions, the agent creates a structured list, executes each step in order, and tracks progress in real time. No configuration is needed—the agent detects and creates task lists automatically.
 
 <figure>
 ![An example of a task list in progress.](../../../../assets/agent-platform/in-progress-tasklist.png)

src/content/docs/agent-platform/cloud-agents/integrations/cloud-providers.mdx

@@ -6,11 +6,7 @@ sidebar:
   label: "AWS, GCP, and other cloud providers"
 ---
 
-Cloud agents can securely access cloud providers using short-lived OpenID Connect credentials.
-
-This page explains how to configure a cloud agent environment to automatically authenticate to your
-cloud provider. Oz has built-in support for AWS and GCP, and can work with any provider that
-supports OIDC tokens.
+Cloud agents can securely access AWS, GCP, and other cloud providers using short-lived OpenID Connect (OIDC) credentials. Configure your cloud agent environment to automatically authenticate to your cloud provider without storing long-lived keys, using Warp's built-in OIDC federation support.
 
 ---
 

src/content/docs/agent-platform/cloud-agents/integrations/demo-issue-triage-bot.mdx

@@ -8,6 +8,8 @@ sidebar:
 ---
 import VideoEmbed from '@components/VideoEmbed.astro';
 
+This demo shows how to trigger Warp's coding agent from a GitHub Action to automate bug report handling. The agent evaluates whether a report is actionable, requests missing details when needed, and escalates directly into a draft pull request when the issue is ready for a fix.
+
 <VideoEmbed url="https://www.youtube.com/watch?feature=youtu.be&v=dK2eohQ2Yow" />
 
 :::note

src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx

@@ -7,6 +7,8 @@ description: >-
   pull requests.
 ---
 
+The Slack integration lets your team trigger Oz cloud agents directly from Slack conversations. Tag @Oz in a message or DM the bot to start a cloud agent that clones your repos, works through the task, posts progress updates, and opens pull requests back into the same thread.
+
 ### Overview
 
 The Slack integration lets your team trigger agents directly from conversations in Slack. When you tag **@Oz** in a message or DM the bot, Warp will start an agent in the cloud, clone the repositories defined in your environment, and begin working through the task with full context from your codebase and the Slack thread.

src/content/docs/agent-platform/cloud-agents/overview.mdx

@@ -8,7 +8,7 @@ sidebar:
 ---
 import VideoEmbed from '@components/VideoEmbed.astro';
 
-Cloud agents are **cloud-connected**, **background agents** that run on the [Oz Platform](/agent-platform/cloud-agents/platform/).
+Cloud agents are autonomous, background agents that run on Warp's cloud infrastructure or your own, triggered by system events, schedules, or integrations like Slack and GitHub. They execute tasks with full observability — every run is tracked, auditable, and shareable across your team.
 
 **New to cloud agents?** Start with the [Cloud agents quickstart](/agent-platform/cloud-agents/quickstart/) to run your first cloud agent in ~10 minutes.