Add frontmatter descriptions to 19 Merge Queue pages

[samgutentag]

Summary

Add description frontmatter to all 19 Merge Queue pages that were missing it. Each description is <=160 characters and summarizes the page content in plain text.

In GitBook, frontmatter description maps to the <meta name="description"> tag, which is what search engines show in results snippets. Without it, Google pulls whatever text it finds first on the page.

Sections covered:

• Getting Started (5 pages)
• Optimizations (8 pages including parallel queues sub-pages)
• Using the Queue (3 pages)
• Reference (2 pages)
• Migrating from GitHub Merge Queue (1 page)

Test plan

• Verify frontmatter renders correctly in GitBook preview (Change Request)
• Spot-check Google Search Console after indexing to confirm descriptions appear

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

[trunk-staging-io]

Merging to main in this repository is managed by Trunk.

• To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

[claude]

Claude finished @samgutentag's task in 1m 21s —— View job

---

PR Review: Add frontmatter descriptions to 19 Merge Queue pages

• Gather context and understand the request
• Read CLAUDE.md for repo guidelines
• Review all 19 changed files for description quality
• Check for typos, grammar, formatting issues
• Post final review feedback

---

Summary

All 19 descriptions look good. The changes are purely additive frontmatter blocks — no existing content is modified.

What I checked:

• YAML frontmatter format: All use >- folded block scalar, which is correct for GitBook
• Character length: All descriptions are well under the 160-character limit (range: 76–129 chars)
• Accuracy: Cross-checked several descriptions against actual page content — all are faithful to the pages they describe
• Grammar/spelling: No issues found
• Consistent voice: Descriptions use active, imperative language consistently across the set

Minor observations (non-blocking):

• merge-queue/getting-started/README.md and merge-queue/getting-started/install-and-create-your-queue.md have similar page bodies (both mention installing the GitHub App, creating a queue, and configuring branch protection). The descriptions are helpfully differentiated — README.md is scoped to the overview, while install-and-create-your-queue.md focuses on the installation step. No change needed.
• optimistic-merging.md description ("using passing test results from later PRs in the queue to validate earlier ones") accurately reflects the page content, which states: "we can leverage results from pull requests later in the queue to merge faster."

This PR is ready to merge. ✅

[github-actions]

Auto-approved: Claude code review passed.

[claude]

Claude finished @samgutentag's task in 54s —— View job

---

PR Review: Add frontmatter descriptions to 19 Merge Queue pages

• Gather context and understand the request
• Read changed files and verify description quality
• Check for typos, grammar, and formatting issues
• Post final review feedback

---

All 19 descriptions look good. The changes are purely additive frontmatter — no existing content is modified.

What I checked:

• YAML format: All use >- folded block scalar, which correctly collapses multi-line strings to a single line with no trailing newline — appropriate for GitBook's description frontmatter
• Character length: All descriptions are well within the 160-character SEO limit
• Accuracy: Cross-checked descriptions against page content across all sections — all faithfully represent what the pages cover
• Grammar/spelling: No issues found in the added frontmatter
• Voice consistency: Descriptions use active, imperative language consistently (e.g., "Configure...", "Test...", "Bypass...", "Switch...")

Minor pre-existing issue (not introduced by this PR):

merge-queue/migrating-from-github-merge-queue.md:9 — existing body text reads "the process is straight forward" — should be one word: "straightforward". Not blocking, and not part of this PR's changes.

This PR is ready to merge. ✅

[github-actions]

Auto-approved: Claude code review passed.