chore: refactor tokens page

[mnkiefer]

• Visual improvements:

  • Added color-coded badges to token headers (blue for auto-provided, purple for PATs)
  • Added horizontal rule separators between token sections
  • Indented all token content under headers for better hierarchy
  • Increased vertical spacing between sections

• Structure reorganization:

  • Simplified intro from dense paragraphs to scannable bullet list
  • Created parent sections: "Which token(s) do I need?", "How do I add tokens to my repository?", " Who owns the repository?", "Token Reference"
  • Condensed "Setting up tokens" section with CLI commands front and center

• Content additions:

  • Added repository secrets UI screenshot (light/dark theme support)
  • Reduced ownership guide image sizes (side-by-side view)

[Copilot]

Pull request overview

Updates the GitHub Tokens reference doc to be more task-oriented (what tokens you need, how to add them) and to reorganize the token reference sections with new UI/CLI setup guidance and visual examples.

Changes:

• Adds “Which token(s) do I need?” and “How do I add tokens?” sections with CLI/UI instructions and screenshots.
• Restructures the token reference section formatting (new headings/badges and section wrappers).
• Removes/relocates some previously documented sections (notably GitHub App token guidance), which impacts existing deep links.

Comments suppressed due to low confidence (2)

docs/src/content/docs/reference/tokens.md:200

• In this section, there are inline <video> embeds further down the page. They currently don’t follow the docs’ standard Video component markup (container/element classes + preload="metadata" + aria-label), so styling from custom.css may not apply consistently and accessibility metadata may be missing. Consider matching docs/src/components/Video.astro’s structure for those embeds.

### `GH_AW_PROJECT_GITHUB_TOKEN` <span style="display: inline-block; padding: 0.25rem 0.75rem; border-radius: 9999px; background-color: #c084fc; color: white; font-size: 0.875rem; font-weight: 500;">Personal Access Token</span>
<div style="padding-left: 1.5rem;">
> [!IMPORTANT]
> **Required** for any GitHub Projects v2 operations (creating, updating, or reading project boards)
A specialized token for GitHub Projects v2 operations used by:
- The [`project new`](/gh-aw/setup/cli/#project-new) CLI command for creating projects

docs/src/content/docs/reference/tokens.md:193

• The heading includes additional badge text via an inline <span> ("Personal Access Token"). Since heading IDs are auto-generated from heading text, this is likely to change the slug and break existing deep links (other pages currently link to /reference/tokens/#gh_aw_project_github_token-github-projects-v2). Consider keeping the heading text stable (e.g., include “(GitHub Projects v2)” again) and/or adding an explicit anchor with the previous ID.

### `GH_AW_PROJECT_GITHUB_TOKEN` <span style="display: inline-block; padding: 0.25rem 0.75rem; border-radius: 9999px; background-color: #c084fc; color: white; font-size: 0.875rem; font-weight: 500;">Personal Access Token</span>

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

@mnkiefer I've opened a new pull request, #14936, to work on those changes. Once the pull request is ready, I'll request review from you.

[mnkiefer]

@copilot Fix docs build errors

[Copilot]

@mnkiefer I've opened a new pull request, #14937, to work on those changes. Once the pull request is ready, I'll request review from you.

[mnkiefer]

@copilot Revert actions-lock.json and action_pins.json

[Copilot]

@mnkiefer I've opened a new pull request, #14941, to work on those changes. Once the pull request is ready, I'll request review from you.