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

workshop/05-agentic-workflows-intro.md

@@ -50,7 +50,7 @@ Before studying the diagram, write your prediction: what two files are involved,
 - **`.md` source file** — contains [YAML frontmatter](https://github.github.com/gh-aw/reference/frontmatter/) (trigger, permissions, runner) and your plain-English task brief. You author and edit this file.
 - **`.lock.yml` compiled file** — [`gh aw compile`](https://github.github.com/gh-aw/reference/compilation-process/) generates it from the `.md`. GitHub Actions runs this file, not the `.md`. Never edit it by hand.
 
-**Activity 1 — identify the parts:** Open any `.lock.yml` file in your repo and find the `on:` key. That is the compiled trigger that came from your frontmatter.
+**Activity 1 — identify the parts:** Open any `.lock.yml` file in your repo and find the `on:` key. That is the compiled trigger that came from your [frontmatter](https://github.github.com/gh-aw/reference/frontmatter/).
 
 ```
 # Example: open .github/workflows/my-workflow.lock.yml

workshop/06-install-gh-aw.md

@@ -60,7 +60,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/07-your-first-workflow.md

@@ -115,7 +115,7 @@ For follow-up edits, keep using an agent with the `agentic-workflows` skill and
 ## :white_check_mark: Checkpoint
 
 - [ ] Copilot access was confirmed in Copilot CLI before starting (test prompt received a reply)
-- [ ] `.github/workflows/daily-report-status.md` exists and contains an `on: schedule:` trigger in the frontmatter
+- [ ] `.github/workflows/daily-report-status.md` exists and contains an `on: schedule:` trigger in the [frontmatter](https://github.github.com/gh-aw/reference/frontmatter/)
 - [ ] The file includes `permissions` with `copilot-requests: write`
 - [ ] `gh aw compile` exits with no errors and produces `daily-report-status.lock.yml`
 - [ ] Both `daily-report-status.md` and `daily-report-status.lock.yml` are committed and pushed to `main`

workshop/07d-confirm-model-access.md

@@ -45,7 +45,7 @@ If you arrived from the step 07 access check and the test prompt succeeded, retu
 > [!NOTE]
 > For golden-ticket workshops, billing is pre-provisioned by your org. Use the **Organization centralized billing** path unless your instructor says otherwise.
 
-Follow the full setup steps in [Side Quest: Copilot Billing Paths](side-quest-07d-billing-paths.md), then return here once your workflow file and lock file are committed.
+Follow the full setup steps in [Side Quest: Copilot Billing Paths](side-quest-07d-billing-paths.md), then return here once your workflow file and [lock file](https://github.github.com/gh-aw/reference/glossary/#workflow-lock-file-lockyml) are committed.
 
 ## :white_check_mark: Checkpoint
 

workshop/08-run-your-workflow.md

@@ -16,7 +16,7 @@ You'll trigger the `daily-report-status` workflow from Step 7, watch it start in
 
 ## Pre-flight check
 
-A stale or missing lock file is the leading cause of `model-access-not-configured` failures at this step. Run these checks before triggering the workflow — each takes less than a minute.
+A stale or missing [lock file](https://github.github.com/gh-aw/reference/glossary/#workflow-lock-file-lockyml) is the leading cause of `model-access-not-configured` failures at this step. Run these checks before triggering the workflow — each takes less than a minute.
 
 **Lock file is present and current.** Open `.github/workflows/` in your repository on GitHub and confirm both files are there: