Give getting-started variants unique titles and add social images (#17)

Three docs fixes from the endform.dev SEO audit: H3, M3, and the docs
part of H2. The marketing side is in endformdev/endform#2309.

## Unique getting-started titles (H3)
The 16 `/docs/guides/getting-started/{runner}/{suite}/{target}` pages
and their parent all had the title and H1 "Getting Started", so Google
treated them as near-duplicates and showed one. Each variant now names
its runner, suite and target:

| Runner | Your suite | Demo suite |
| --- | --- | --- |
| Local CLI | Run Playwright tests from your terminal against a local
server | Try the Endform demo from your terminal with a local server |
| GitHub Actions | Run Playwright tests in GitHub Actions on Vercel
previews | Try the Endform demo in GitHub Actions on Vercel previews |
| Other CI | Run Playwright tests in any CI against a remote server |
Try the Endform demo in any CI with a remote server |

(One example per runner; every combination follows the same pattern.)
The parent page becomes "Getting started" in sentence case. The GitHub
Actions variants target the same searches as our best-performing blog
post.

## Social preview images (M3)
Docs pages declared `twitter:card = summary_large_image` but had no
image. A Starlight route middleware (`src/routeData.ts`) now adds
`og:image` and `twitter:image` from `og-image.endform.dev` using the
page title, the same service the marketing site uses.

## Links to marketing pages (H2)
The docs had no links to the feature pages, pricing or blog. Now:
- **What is Endform?** links its feature bullets to `/features/speed`,
`/features/analytics` and `/features/compatibility`, and "pay only for
the exact time" to `/pricing`.
- **How your tests are run** and the **Speeding up with Endform**
tutorial link to `/features/speed`.
- **Dashboard analytics** links to `/features/analytics`.
- The **Quarantine tests** guide and two tutorials link to the matching
blog posts: flaky tests, Playwright MCP with Claude Code, and best
practices at scale.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Author: jakst

astro.config.mjs

@@ -110,6 +110,7 @@ export default defineConfig({
 			components: {
 				Sidebar: "./src/components/Sidebar.astro",
 			},
+			routeMiddleware: "./src/routeData.ts",
 			logo: {
 				dark: "./src/assets/endform-logo-wordmark-colored-on-dark-padding.svg",
 				light:

src/content/docs/explanation/dashboard-analytics.mdx

@@ -10,7 +10,7 @@ import EndformResults from "../../../assets/endform-dashboard-test-runs.png";
 
 Endform stores your suite results over time so you can understand more than the outcome of the latest run.
 
-The dashboard helps you answer questions like:
+The [analytics dashboard](/features/analytics) helps you answer questions like:
 
 - Which tests fail most often?
 - Which tests are flaky and only pass after retries?

src/content/docs/explanation/how-your-tests-are-run.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 import { Aside } from '@astrojs/starlight/components';
 
-Endform provides a distributed test runner optimized specifically for Playwright, designed to run your end-to-end tests faster and more efficiently.
+Endform provides a [distributed test runner](/features/speed) optimized specifically for Playwright, designed to run your end-to-end tests faster and more efficiently.
 Here's a brief explanation of how our test runner works.
 
 ## How it works

src/content/docs/explanation/what-is-endform.mdx

@@ -21,7 +21,7 @@ As a Playwright suite grows, a single CI worker has to start browsers, run tests
 Endform moves the expensive part of the run to managed infrastructure.
 Instead of making one machine do all the browser work, Endform can run many tests at the same time across many machines.
 
-You pay only for the exact time your tests took to run on each individual machine they ran on.
+You [pay only for the exact time](/pricing) your tests took to run on each individual machine they ran on.
 
 ## What changes when you use Endform
 
@@ -49,9 +49,9 @@ For more detail, see [How your tests are run](/docs/explanation/how-your-tests-a
 
 ## What Endform includes
 
-- **Distributed Playwright execution**: Run many Playwright tests in parallel on managed cloud runners.
-- **Dashboard analytics**: Track suite runs, test runs, pass rates, durations, failures, retries, flaky tests, and traces over time.
-- **Playwright compatibility**: Use Playwright projects, retries, global setup and teardown, web servers, reporters, storage state, and snapshots.
+- **[Distributed Playwright execution](/features/speed)**: Run many Playwright tests in parallel on managed cloud runners.
+- **[Dashboard analytics](/features/analytics)**: Track suite runs, test runs, pass rates, durations, failures, retries, flaky tests, and traces over time.
+- **[Playwright compatibility](/features/compatibility)**: Use Playwright projects, retries, global setup and teardown, web servers, reporters, storage state, and snapshots.
 - **Local and private network access**: Proxy traffic from remote runners back through the CLI to local or private services.
 - **CI support**: Run from GitHub Actions with the Endform GitHub App, or from other CI systems with an API key.
 - **Configuration with `endform.config.ts`**: Tune file transfer, environment variables, concurrency limits, regions, network proxying, reporters, and trace retention.

src/content/docs/guides/getting-started.mdx

@@ -1,5 +1,5 @@
 ---
-title: Getting Started
+title: Getting started
 description: Running your tests with Endform for the first time
 sidebar:
   order: 1

src/content/docs/guides/getting-started/github-actions/demo/local.mdx

@@ -1,5 +1,5 @@
 ---
-title: Getting Started
+title: Try the Endform demo in GitHub Actions with a local server
 description: Running the Endform demo Playwright tests with GitHub Actions against a local server
 sidebar:
   hidden: true

src/content/docs/guides/getting-started/github-actions/demo/remote.mdx

@@ -1,5 +1,5 @@
 ---
-title: Getting Started
+title: Try the Endform demo in GitHub Actions with a remote server
 description: Running the Endform demo Playwright tests with GitHub Actions against a remote server
 sidebar:
   hidden: true

src/content/docs/guides/getting-started/github-actions/demo/vercel.mdx

@@ -1,5 +1,5 @@
 ---
-title: Getting Started
+title: Try the Endform demo in GitHub Actions on Vercel previews
 description: Running the Endform demo Playwright tests with GitHub Actions against Vercel preview deployments
 sidebar:
   hidden: true

src/content/docs/guides/getting-started/github-actions/existing/local.mdx

@@ -1,5 +1,5 @@
 ---
-title: Getting Started
+title: Run Playwright tests in GitHub Actions against a local server
 description: Running your existing Playwright tests with Endform using GitHub Actions against a local server
 sidebar:
   hidden: true

src/content/docs/guides/getting-started/github-actions/existing/remote.mdx

@@ -1,5 +1,5 @@
 ---
-title: Getting Started
+title: Run Playwright tests in GitHub Actions against a remote server
 description: Running your existing Playwright tests with Endform using GitHub Actions against a remote server
 sidebar:
   hidden: true