frontier-ghcp-rvas

## Constraints

- This GitHub Copilot Adoption delivery session content uses **Azure only**. Never reference AWS, GCP, or other cloud providers.
- Do NOT include README.md files in challenge folders -- all instructions go in the corresponding track file under `tracks/`.
- Do NOT provide ready-to-paste solutions for copilot-instructions, agents, or prompts. Describe WHAT to achieve, not HOW.
- Each challenge should be completable in 4-6 hours.

## Sync Rules

When modifying tracks or challenges, keep everything in sync:

- Track changes -> update the corresponding challenge starter code.
- Challenge changes -> update the track file that references it.
- Any structural change -> update the root `README.md`.
- Each challenge must have its own devcontainer configuration in `devcontainers/` and be referenced in the track file.

## Writing Style for Markdown Files

All `.md` files in this repo must read as if written by a human, not generated by AI. Follow these rules:

- **No emoji in headings.** Headings must be plain text. No `# Title 🚀` or `## Section 🎯`.
- **Minimal emoji in body text.** The only acceptable uses are `⚠️` for warnings in blockquotes, `✅`/`❌` inside code comments showing good/bad examples, `⭐` for difficulty ratings, and role-themed emojis (🔧📊☁️🎨🔍📋🧩✈️) in the track listing sections of `README.md` and `tracks/README.md`. Do not scatter emoji through prose or bullet lists.
- **No em-dashes.** Use `--` or rephrase instead of `—`.
- **No formulaic AI sign-offs.** Do not end files or sections with phrases like "Happy Hacking!", "Ready to build?", "Let's dive in!", "Embrace the agentic workflow!", or similar. End with a plain sentence or a link.
- **No hype language.** Avoid "unlock the true potential", "supercharge your workflow", "elevate your development experience", and similar marketing-speak. Be direct.
- **Use natural phrasing.** Write the way a developer would write internal docs -- short, direct, no fluff. Prefer active voice.
- **Lint compliance.** All markdown must pass `markdownlint` with the project's `.markdownlint.json` config. Code fences must have a language tag. Headings need blank lines above and below. No trailing whitespace.
- **No AI Slop.** Avoid any phrasing that sounds like it was generated by an AI without human editing, or being excessively repetitive. If it doesn't sound like something a developer would write in internal documentation, rewrite it.
- **Always humanize content.** Use the provided skill to always write in human-like form by checking for and removing AI artifacts.