workshop docs: add gh-aw doc links (round 4) (#1840)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: github-actions[bot]

workshop/26-manage-costs-and-budgets.md

@@ -74,7 +74,7 @@ A few techniques keep spend in check:
 - **Cache results with persistent memory** — skip re-processing unchanged data. See [Make Your Workflow Remember Across Runs](20-persistent-memory.md).
 - **Reduce run frequency** — fewer runs means fewer AIC.
 
-Three frontmatter fields enforce hard limits directly in the workflow file:
+Three [frontmatter](https://github.github.com/gh-aw/reference/frontmatter/) fields enforce hard limits directly in the workflow file:
 
 - **[`timeout-minutes`](https://github.github.com/gh-aw/reference/rate-limiting-controls/#timeouts)** cancels the entire Actions job if it exceeds the limit. The run fails and you are billed only for tokens consumed before cancellation.
 - **[`max-ai-credits`](https://github.github.com/gh-aw/reference/cost-management/#cap-ai-credits-per-run)** caps the AIC a single run may consume, enforced by the AWF firewall. The default when omitted is 1000 AIC. Set to a negative value (e.g. `-1`) to disable enforcement and token steering.

workshop/side-quest-05-01-actions-power-user.md

@@ -18,7 +18,7 @@ Review the key shift from classic Actions to agentic workflows, compare concrete
 
 ## The core mental model shift
 
-You keep the same GitHub Actions foundations — triggers, permissions, runners, repo context, and pull-request review flow — and add an agentic layer on top. In practice, this is a smooth transition: frontmatter stays Actions-compatible, while the Markdown body captures the goal and reasoning instructions for the agent.
+You keep the same GitHub Actions foundations — triggers, [permissions](https://github.github.com/gh-aw/reference/permissions/), runners, repo context, and pull-request review flow — and add an agentic layer on top. In practice, this is a smooth transition: [frontmatter](https://github.github.com/gh-aw/reference/frontmatter/) stays Actions-compatible, while the Markdown body captures the goal and reasoning instructions for the agent.
 
 ## Before and After: Classic Actions vs. Agentic Workflows
 

workshop/side-quest-05-02-aw-deep-dive.md

@@ -71,7 +71,7 @@ Should the daily report run on a schedule or wait for manual dispatch? State whi
 <details>
 <summary>Check your answer</summary>
 
-A scheduled trigger runs automatically — appropriate for a daily report. `workflow_dispatch` requires a button click in the Actions tab.
+A [scheduled trigger](https://github.github.com/gh-aw/reference/triggers/#scheduled-triggers-schedule) runs automatically — appropriate for a daily report. `workflow_dispatch` requires a button click in the Actions tab.
 
 - [ ] Schedule: runs automatically, no button click needed
 - [ ] `workflow_dispatch`: requires a manual click each run

workshop/side-quest-06-01-install-troubleshooting.md

@@ -77,7 +77,7 @@ gh extension install github/gh-aw
 
 ---
 
-## GitHub Enterprise Server (GHE/GHES) endpoint
+## [GitHub Enterprise Server](https://github.github.com/gh-aw/setup/cli/#github-enterprise-server-support) (GHE/GHES) endpoint
 
 Authenticate against your GHES hostname and install with `--hostname`:
 

workshop/side-quest-06-03-copilot-token.md

@@ -9,7 +9,7 @@
 - You have completed [Install the gh-aw CLI Extension](06-install-gh-aw.md).
 - You have access to your repository's settings (needed if you choose Method 2).
 
-## Why authentication matters
+## Why [authentication](https://github.github.com/gh-aw/reference/auth/) matters
 
 Agentic workflows call the GitHub Copilot API at runtime to run AI reasoning steps. Without a valid credential, every call returns `401 Unauthorized` and the workflow fails immediately. Configuring authentication once, before you run a workflow, ensures your agent can reach Copilot reliably on every future run.
 

workshop/side-quest-06-03a-copilot-requests-permission.md

@@ -37,7 +37,7 @@ permissions:
 ---
 ```
 
-That single line is the only workflow authentication change required for repositories that can use Method 1. Recompile and commit the lock file after changing the source workflow.
+That single line is the only workflow authentication change required for repositories that can use Method 1. Recompile and commit the [lock file](https://github.github.com/gh-aw/reference/glossary/#workflow-lock-file-lockyml) after changing the source workflow.
 
 ## ✅ Checkpoint