workshop docs: add gh-aw doc links to steps 07a-08b (#1352)

Author: github-actions[bot]

workshop/07a-your-first-workflow-terminal.md

@@ -7,7 +7,7 @@ _Writing your first workflow is the moment theory becomes practice — let's mak
 
 ## 🎯 What You'll Do
 
-You'll create the first version of `.github/workflows/daily-report-status.md` with just two frontmatter fields:
+You'll create the first version of `.github/workflows/daily-report-status.md` with just two [frontmatter](https://github.github.com/gh-aw/reference/frontmatter/) fields:
 
 - `name` (workflow label)
 - `on.workflow_dispatch` (manual trigger)
@@ -102,3 +102,11 @@ Continue to [Part 2: Add instructions, safe outputs, and finish](07a-part2-your-
 - [ ] The frontmatter includes `name` and `on.workflow_dispatch`
 - [ ] `gh aw compile` succeeds and generates `daily-report-status.lock.yml`
 - [ ] `gh extension list` shows `github/gh-aw` is installed
+
+## 📚 See Also
+
+- [Overview of GitHub Agentic Workflows](https://github.github.com/gh-aw/introduction/overview/)
+- [Frontmatter reference](https://github.github.com/gh-aw/reference/frontmatter/)
+- [Triggers reference](https://github.github.com/gh-aw/reference/triggers/#dispatch-triggers-workflowdispatch)
+- [Compilation Process](https://github.github.com/gh-aw/reference/compilation-process/)
+- [Workflow Structure](https://github.github.com/gh-aw/reference/workflow-structure/)

workshop/07b-your-first-workflow-ui.md

@@ -15,7 +15,7 @@ You'll create a complete `daily-report-status.md` workflow in the GitHub web edi
 
 ## Understand the file
 
-An agentic workflow source file is a Markdown task brief with YAML frontmatter. GitHub Actions runs the compiled `.lock.yml`; you edit the `.md` source first, then compile it into the `.lock.yml` file before Step 8.
+An agentic workflow source file is a Markdown task brief with YAML [frontmatter](https://github.github.com/gh-aw/reference/frontmatter/). GitHub Actions runs the compiled `.lock.yml`; you edit the `.md` source first, then [compile](https://github.github.com/gh-aw/reference/compilation-process/) it into the `.lock.yml` file before Step 8.
 
 ## Create the workflow
 
@@ -96,4 +96,7 @@ Review the proposed diff. Confirm both `.github/workflows/daily-report-status.md
 ## 📚 See Also
 
 - [Overview of GitHub Agentic Workflows](https://github.github.com/gh-aw/introduction/overview/)
+- [Frontmatter reference](https://github.github.com/gh-aw/reference/frontmatter/)
+- [Triggers reference](https://github.github.com/gh-aw/reference/triggers/)
 - [Safe Outputs reference](https://github.github.com/gh-aw/reference/safe-outputs/)
+- [Compilation Process](https://github.github.com/gh-aw/reference/compilation-process/)

workshop/07c-your-first-workflow-copilot.md

@@ -24,7 +24,7 @@ The workflow must:
 - Be named "Daily Report Status"
 - Support manual runs with `workflow_dispatch`
 - Use `contents: read`, `issues: read`, and `copilot-requests: write`
-- Allow at most one comment and at most one new issue through safe outputs
+- Allow at most one comment and at most one new issue through [safe outputs](https://github.github.com/gh-aw/reference/safe-outputs/)
 - Search open issues for the issue with the most 👍 reactions and comment:
   "This issue has the most community support! We'll prioritise it in our next planning session."
 - Create an issue titled "Community Voting Test" and post the same comment if no open issues exist
@@ -57,3 +57,11 @@ Before you approve the merge, the agent presents the file changes in its session
 - [ ] You are ready to choose the workflow's billing and authentication method
 
 **Next:** [Step 7d: Confirm Model Access](07d-confirm-model-access.md)
+
+## 📚 See Also
+
+- [Overview of GitHub Agentic Workflows](https://github.github.com/gh-aw/introduction/overview/)
+- [Safe Outputs reference](https://github.github.com/gh-aw/reference/safe-outputs/)
+- [Triggers reference](https://github.github.com/gh-aw/reference/triggers/)
+- [Compilation Process](https://github.github.com/gh-aw/reference/compilation-process/)
+- [AI Engines reference](https://github.github.com/gh-aw/reference/engines/)

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

@@ -13,7 +13,7 @@ You'll choose the billing and authentication method for the first workflow, conf
 
 Open `.github/workflows/daily-report-status.md`. The Step 7 workflow has no `engine:` line, so it uses GitHub Copilot.
 
-Claude and Codex are optional engines introduced in later side quests. You do not need an Anthropic or OpenAI API key for this first run.
+Claude and Codex are optional [engines](https://github.github.com/gh-aw/reference/engines/) introduced in later side quests. You do not need an Anthropic or OpenAI API key for this first run.
 
 ## Choose one Copilot billing path
 
@@ -59,3 +59,10 @@ Open `daily-report-status.md` and confirm it matches the method you selected:
 - [ ] I am ready for [Step 8: Run and Watch Your Workflow](08-run-your-workflow.md)
 
 **Next:** [Step 8: Run and Watch Your Workflow](08-run-your-workflow.md)
+
+## 📚 See Also
+
+- [AI Engines reference](https://github.github.com/gh-aw/reference/engines/)
+- [Authentication reference](https://github.github.com/gh-aw/reference/auth/)
+- [GitHub Tools Read Permissions](https://github.github.com/gh-aw/reference/permissions/#special-permission-copilot-requests-write)
+- [Billing reference](https://github.github.com/gh-aw/reference/billing/)

workshop/08b-interpret-your-run.md

@@ -30,7 +30,7 @@ The important question is not "Can I read every line?" It is "Can I tell where t
 
 After the run finishes, scroll to the **Summary** section on the run page. This gives you the short version of what the agent believes it did, including the safe-output action it used.
 
-Then verify the real output in your repository. For **Daily Report Status**, that usually means opening the issue the agent touched and confirming the comment or new issue is actually there. The GitHub change is the ground truth behind the safe-output record.
+Then verify the real output in your repository. For **Daily Report Status**, that usually means opening the issue the agent touched and confirming the comment or new issue is actually there. The GitHub change is the ground truth behind the [safe-output](https://github.github.com/gh-aw/reference/safe-outputs/) record.
 
 ![Workflow run summary panel](images/08-run-summary.svg)
 
@@ -58,3 +58,5 @@ For a deeper troubleshooting guide, see [Step 9: Reading Workflow Output](09-und
 
 - [Overview of GitHub Agentic Workflows](https://github.github.com/gh-aw/introduction/overview/)
 - [Safe Outputs reference](https://github.github.com/gh-aw/reference/safe-outputs/)
+- [Compilation Process](https://github.github.com/gh-aw/reference/compilation-process/)
+- [Auditing Workflows](https://github.github.com/gh-aw/reference/audit/)