workshop docs: add gh-aw doc links (round 5) (#2468)

Author: github-actions[bot]

workshop/side-quest-08-01-codespaces-actions-write.md

@@ -17,7 +17,7 @@ If you are not in a Codespace or you do not see the 403 error, return to [Run an
 
 ## :dart: What You'll Do
 
-You'll identify the Codespaces token error that blocks `gh aw run` and use the fastest recovery path. Optionally, you can re-create your Codespace with the extra permissions needed for terminal-based workflow triggers.
+You'll identify the Codespaces token error that blocks `gh aw run` and use the fastest recovery path. Optionally, you can re-create your Codespace with the extra [permissions](https://github.github.com/gh-aw/reference/permissions/) needed for terminal-based workflow triggers.
 
 ---
 

workshop/side-quest-09-01b-pattern-empty-results.md

@@ -34,7 +34,7 @@ Identify the pattern before opening the answer.
 <details>
 <summary>Show answer</summary>
 
-Pattern: **`[tool]` call returns empty results**. Check required read permissions and broaden filters to confirm data availability.
+Pattern: **`[tool]` call returns empty results**. Check required read [permissions](https://github.github.com/gh-aw/reference/permissions/) and broaden filters to confirm data availability.
 
 </details>
 

workshop/side-quest-09-01e-pattern-done-no-write.md

@@ -15,7 +15,7 @@ A run can finish with `:white_check_mark: [done]` and still create no comment or
 Start with three checks:
 
 1. Confirm whether your condition was actually true at runtime.
-2. Confirm a matching write action exists in `safe-outputs:`.
+2. Confirm a matching write action exists in [`safe-outputs:`](https://github.github.com/gh-aw/reference/safe-outputs/).
 3. Confirm your instructions define what to do when no condition matches.
 
 To avoid silent no-write outcomes, include explicit fallback behavior such as: "If no incidents are found, post one status comment saying no action is required." This still gives users a visible status indicator and proves the workflow ran.

workshop/side-quest-10-01-agent-brief.md

@@ -65,7 +65,7 @@ Before moving on, confirm you have at least three inputs, each linked to a field
 <details>
 <summary>Why this works</summary>
 
-Inputs turn "summarize the repo" into a concrete data request. They also make it easier to spot missing [permissions](https://github.github.com/gh-aw/reference/permissions/) or tools when you build the workflow.
+Inputs turn "summarize the repo" into a concrete data request. They also make it easier to spot missing [permissions](https://github.github.com/gh-aw/reference/permissions/) or [tools](https://github.github.com/gh-aw/reference/tools/) when you build the workflow.
 
 </details>