[docs-linker] workshop docs: add gh-aw doc links

workshop/side-quest-06-04-install-local.md

@@ -74,7 +74,7 @@ Expected result: a success message confirming GitHub CLI authentication. If it f
 
 ## Initialize [agentic workflow](https://github.github.com/gh-aw/introduction/overview/) skills
 
-Before you author your first workflow, initialize and push the generated skill files:
+Before you author your first workflow, initialize and push the generated [skill files](https://github.github.com/gh-aw/reference/glossary/#skill-files):
 
 ```bash
 gh aw init

workshop/side-quest-07-01-compile-workflow.md

@@ -10,7 +10,7 @@ You'll use `gh aw compile` as a fast feedback loop while you edit workflow files
 
 ## What `gh aw compile` does
 
-`gh aw compile` checks your workflow source file, validates the [frontmatter](https://github.github.com/gh-aw/reference/frontmatter/) and Markdown body structure, and generates the compiled [lock file](https://github.github.com/gh-aw/reference/glossary/#workflow-lock-file-lockyml) GitHub Actions runs. It catches formatting and schema mistakes before you commit or trigger a workflow.
+`gh aw compile` checks your workflow source file, validates the [frontmatter](https://github.github.com/gh-aw/reference/frontmatter/) and Markdown body structure, and generates the compiled [lock file](https://github.github.com/gh-aw/reference/glossary/#workflow-lock-file-lockyml) [GitHub Actions](https://github.github.com/gh-aw/guides/github-actions-primer/) runs. It catches formatting and schema mistakes before you commit or trigger a workflow.
 
 Run it any time you edit a workflow file:
 
@@ -60,7 +60,7 @@ Each save triggers another compile, so you get immediate feedback instead of dis
 
 When `gh aw compile` fails, start with the first line number it reports. YAML errors are often caused by the line above or below the reported line, especially when indentation is off.
 
-The examples below show `gh-aw` source files before compilation, so values like `schedule: daily` and `schedule: daily on weekdays` are valid shorthand here. The error is the indentation, not the schedule value itself.
+The examples below show `gh-aw` source files before [compilation](https://github.github.com/gh-aw/reference/compilation-process/), so values like `schedule: daily` and `schedule: daily on weekdays` are valid shorthand here. The error is the indentation, not the schedule value itself.
 
 ```markdown
 ---

workshop/side-quest-07d-billing-paths.md

@@ -1,6 +1,6 @@
 # Side Quest: Copilot Billing Paths
 
-Choose exactly one billing path for your first workflow, configure it, and commit the updated lock file.
+Choose exactly one [billing](https://github.github.com/gh-aw/reference/billing/) path for your first workflow, configure it, and commit the updated lock file.
 
 ## Quick reference
 
@@ -53,7 +53,7 @@ Use this path for a personal repository, or when the owning organization does no
 > When `copilot-requests: write` is present, the workflow ignores `COPILOT_GITHUB_TOKEN`. Remove that permission line before adding the secret.
 
 1. Open `daily-report-status.md` and remove `copilot-requests: write`.
-2. Generate a fine-grained PAT with **Copilot requests: Read-only** at [github.com/settings/tokens](https://github.com/settings/tokens).
+2. Generate a [fine-grained PAT](https://github.github.com/gh-aw/reference/glossary/#fine-grained-personal-access-token) with **Copilot requests: Read-only** at [github.com/settings/tokens](https://github.com/settings/tokens).
 3. In your repository go to **Settings** → **Secrets and variables** → **Actions**.
 4. Add a repository secret named `COPILOT_GITHUB_TOKEN` and paste the PAT.
 5. Recompile and commit:
@@ -68,7 +68,7 @@ For a browser-only walkthrough, see [Method 2 (UI-only): COPILOT_GITHUB_TOKEN](s
 
 ## Confirm engine
 
-Open `daily-report-status.md` and verify there is no `engine:` line. The workflow defaults to GitHub Copilot — no Anthropic or OpenAI key is needed for this first run.
+Open `daily-report-status.md` and verify there is no `engine:` line. The workflow defaults to GitHub Copilot — no Anthropic or OpenAI key is needed for this first run. To compare available [AI engines](https://github.github.com/gh-aw/reference/engines/), see the engine reference.
 
 To switch engines later, see:
 - [Side Quest: Configure an Anthropic API Key](side-quest-11-06-anthropic-key.md)