docs: remove em-dashes from docs pages; ban them in AGENTS.md

Replace em-dashes with commas, colons, and parentheses across the docs content, fix the broken /quickstart card link (now /local/cli), and add a no-em-dash rule to AGENTS.md.

Author: RhysSullivan

AGENTS.md

@@ -84,6 +84,10 @@ Code is very cheap to write. Do not give time estimates; with agents, code is
 practically instant to generate. Unless stated otherwise, time to implement is
 not a blocker.
 
+Never use em-dashes (the `—` character) anywhere: prose, docs, code comments,
+commit messages, or PRs. Use commas, colons, parentheses, or separate sentences
+instead.
+
 ## Reference Repos
 
 Repos in `.reference`, such as Effect and effect-atom, are available for

apps/docs/README.md

@@ -1,8 +1,8 @@
 # Executor docs
 
 The Executor documentation site, built with [Mintlify](https://mintlify.com).
-This is a standalone Mintlify project (no `package.json` — it is not part of the
-bun workspace; Mintlify builds it in its own cloud).
+This is a standalone Mintlify project (no `package.json`, so it is not part of
+the bun workspace; Mintlify builds it in its own cloud).
 
 ## Develop
 

apps/docs/concepts/connections.mdx

@@ -4,8 +4,8 @@ description: "A connection is a configured instance of an integration. One integ
 ---
 
 A **connection** is a configured instance of an [integration](/concepts/integrations).
-A single integration can have many connections — for example, the same API authenticated
-for two different accounts.
+A single integration can have many connections: the same API authenticated for two
+different accounts, say.
 
 A connection doesn't have to be authenticated: public APIs and public MCP servers can be
 connected with no credentials. When credentials are required, Executor stores them and

apps/docs/concepts/integrations.mdx

@@ -1,6 +1,6 @@
 ---
 title: Integrations
-description: "An integration is something Executor connects to — defined by an MCP server, an OpenAPI spec, or a GraphQL endpoint."
+description: "An integration is something Executor connects to, defined by an MCP server, an OpenAPI spec, or a GraphQL endpoint."
 ---
 
 An **integration** is something Executor can connect to. Each integration is defined by
@@ -13,6 +13,6 @@ a source that describes the available tools:
 The integration describes the catalog of tools; on its own it isn't a live, authenticated
 connection. To actually call tools, you create a [connection](/concepts/connections).
 
-<Card title="Add your first integration →" href="/quickstart" horizontal>
-  See the quickstart for adding an integration from the web UI or the CLI.
+<Card title="Add your first integration →" href="/local/cli" horizontal>
+  See the CLI page for adding an integration from the web UI or the CLI.
 </Card>

apps/docs/concepts/policies.mdx

@@ -5,9 +5,9 @@ description: "Policies control whether each tool is always allowed, requires app
 
 A **policy** controls what an agent can do with each tool:
 
-- **Allow** — the tool runs without interruption.
-- **Require approval** — the call pauses until a human approves it.
-- **Block** — the tool can't be called.
+- **Allow**: the tool runs without interruption.
+- **Require approval**: the call pauses until a human approves it.
+- **Block**: the tool can't be called.
 
 Policies start from a sensible default derived from the integration's spec. For example,
 read-only `GET` operations on an OpenAPI spec are allowed by default, while writes can be

apps/docs/hosted/cloud.mdx

@@ -1,6 +1,6 @@
 ---
 title: Executor Cloud
-description: "Use hosted Executor Cloud — no setup, with a free tier."
+description: "Use hosted Executor Cloud: no setup, with a free tier."
 ---
 
 {/* TODO: write this page */}

apps/docs/index.mdx

@@ -1,23 +1,23 @@
 ---
 title: Introduction
-description: "Executor is the open-source integration layer for AI agents — one catalog for every tool, shared across every agent you use."
+description: "Executor is the open-source integration layer for AI agents: one catalog for every tool, shared across every agent you use."
 ---
 
-Configure every integration once — MCP servers, OpenAPI specs, GraphQL
-endpoints — with authentication and per-tool [policies](/concepts/policies),
+Configure every integration once (MCP servers, OpenAPI specs, GraphQL
+endpoints) with authentication and per-tool [policies](/concepts/policies),
 then use that same catalog from any MCP-compatible agent.
 
 ## Get started
 
 Choose how to run Executor:
 
-- **[CLI](/local/cli)** — a background service on your machine, from the terminal
-- **[Desktop app](/local/desktop)** — the same runtime, as a desktop app
-- **[Executor Cloud](/hosted/cloud)** — hosted, with a free tier; nothing to run yourself
-- **Self-host** — your own infrastructure, via [Docker](/hosted/docker) or [Cloudflare](/hosted/cloudflare)
+- **[CLI](/local/cli)**: a background service on your machine, from the terminal
+- **[Desktop app](/local/desktop)**: the same runtime, as a desktop app
+- **[Executor Cloud](/hosted/cloud)**: hosted, with a free tier; nothing to run yourself
+- **Self-host**: your own infrastructure, via [Docker](/hosted/docker) or [Cloudflare](/hosted/cloudflare)
 
 ## Concepts
 
-- **[Integrations](/concepts/integrations)** — what Executor connects to
-- **[Connections](/concepts/connections)** — configured instances of an integration
-- **[Policies](/concepts/policies)** — what each tool is allowed to do
+- **[Integrations](/concepts/integrations)**: what Executor connects to
+- **[Connections](/concepts/connections)**: configured instances of an integration
+- **[Policies](/concepts/policies)**: what each tool is allowed to do

apps/docs/local/cli.mdx

@@ -3,7 +3,7 @@ title: CLI
 description: "Run Executor as a local background service and drive it from the command line."
 ---
 
-The CLI runs a small HTTP runtime on your machine — a durable background service
+The CLI runs a small HTTP runtime on your machine: a durable background service
 that any MCP-compatible agent can connect to. Your integrations, credentials, and
 policies stay local.
 
@@ -45,8 +45,8 @@ throwaway foreground runtime instead, run `executor web --foreground`.
 
 ## Connect an agent
 
-Add Executor to any MCP client (Claude Code, Cursor, OpenCode) with `npx add-mcp` —
-it detects the client and writes its config for you. Connect over HTTP or through
+Add Executor to any MCP client (Claude Code, Cursor, OpenCode) with `npx add-mcp`.
+It detects the client and writes its config for you. Connect over HTTP or through
 the CLI:
 
 <Tabs>
@@ -63,7 +63,7 @@ the CLI:
   </Tab>
   <Tab title="CLI (stdio)">
     With the `executor` CLI on your PATH, the client launches `executor mcp`
-    directly — no URL needed:
+    directly (no URL needed):
 
     ```bash
     npx add-mcp "executor mcp" --name executor
@@ -74,7 +74,7 @@ the CLI:
 
 ## Add an integration
 
-From the web UI, click **Add Source** and paste an OpenAPI, GraphQL, or MCP URL —
+From the web UI, click **Add Source** and paste an OpenAPI, GraphQL, or MCP URL.
 Executor detects the type, indexes the tools, and handles auth. Or add one from the
 CLI:
 

apps/docs/style.css

@@ -1,4 +1,4 @@
-/* Logo wordmark — Instrument Serif, the brand display font (--font-display in
+/* Logo wordmark: Instrument Serif, the brand display font (--font-display in
    the app console and the marketing wordmark/accent treatment). The navbar
    default is a bold sans; Instrument Serif ships a single 400 weight, so drop
    the faux-bold and tight tracking. */