Starlight docs migration with best practices

[Copilot]

Migrating docs to starlight with proper best practices implementation.

Changes Made

• Scaffold: Set up Starlight project structure
• Content Migration: Moved all markdown files to proper Starlight directory structure
• Frontmatter: Added proper Starlight frontmatter with titles and descriptions to all documentation pages
• Index Update: Updated main documentation index with proper navigation structure
• Best Practices: Applied Starlight authoring best practices including:
  • Converted GitHub-style callouts (> [!TIP], > [!CAUTION]) to Starlight syntax (:::tip, :::caution)
  • Added proper language specifications to code blocks for enhanced syntax highlighting
  • Improved content structure and organization
  • Fixed broken cross-references and navigation links

The documentation now follows Starlight conventions and builds successfully, providing a better authoring and reading experience.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• telemetry.astro.build
  • Triggering command: node /home/REDACTED/work/gh-aw/gh-aw/docs/node_modules/.bin/astro build (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)