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

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

@@ -50,7 +50,7 @@ If you see `401 Unauthorized` in the run log, see [Method 1: Copilot Requests Pe
 Use this path for a personal repository, or when the owning organization does not provide centralized Copilot billing.
 
 > [!IMPORTANT]
-> When `copilot-requests: write` is present, the workflow ignores `COPILOT_GITHUB_TOKEN`. Remove that permission line before adding the secret.
+> When `copilot-requests: write` is present, the workflow ignores `COPILOT_GITHUB_TOKEN`. Remove that [permission](https://github.github.com/gh-aw/reference/permissions/#special-permission-copilot-requests-write) 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).

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

@@ -9,7 +9,7 @@
 This side quest applies to you if **both** of the following are true:
 
 - You are running `gh aw run` inside a GitHub Codespace (not a local environment).
-- You see an `actions:write` permission error (HTTP 403) in your terminal run log.
+- You see an `actions:write` [permission](https://github.github.com/gh-aw/reference/permissions/) error (HTTP 403) in your terminal run log.
 
 If you are not in a Codespace or you do not see the 403 error, return to [Run and Watch Your Workflow](08-run-your-workflow.md) and use the GitHub Actions UI path instead.
 

workshop/side-quest-09-01-debug-output.md

@@ -16,8 +16,8 @@ You will diagnose five common output patterns one at a time. Each micro-step inc
 
 | Pattern | What you learn | Micro-step |
 |---|---|---|
-| Long `[plan]` chain | How to turn planning loops into concrete tool calls | [09-01a](side-quest-09-01a-pattern-long-plan-chain.md) |
-| Empty tool results | How to separate permission issues from filter issues | [09-01b](side-quest-09-01b-pattern-empty-results.md) |
+| Long `[plan]` chain | How to turn planning loops into concrete [tool](https://github.github.com/gh-aw/reference/tools/) calls | [09-01a](side-quest-09-01a-pattern-long-plan-chain.md) |
+| Empty tool results | How to separate [permission](https://github.github.com/gh-aw/reference/permissions/) issues from filter issues | [09-01b](side-quest-09-01b-pattern-empty-results.md) |
 | [Safe-output](https://github.github.com/gh-aw/reference/safe-outputs/) `limit reached` | How to decide between raising `max` and tightening guidance | [09-01c](side-quest-09-01c-pattern-safe-output-blocked.md) |
 | `permission denied` | How to map failures to [`permissions`](https://github.github.com/gh-aw/reference/permissions/) vs [`safe-outputs`](https://github.github.com/gh-aw/reference/safe-outputs/) | [09-01d](side-quest-09-01d-pattern-permission-denied.md) |
 | "Done" with no write | How to clarify write conditions and fallback behavior | [09-01e](side-quest-09-01e-pattern-done-no-write.md) |

workshop/side-quest-09-01a-pattern-long-plan-chain.md

@@ -4,7 +4,7 @@
 
 ## :dart: What You'll Do
 
-You will learn how to spot a planning loop and rewrite your workflow brief so the agent starts with an explicit first tool call.
+You will learn how to spot a planning loop and rewrite your workflow brief so the agent starts with an explicit first [tool](https://github.github.com/gh-aw/reference/tools/) call.
 
 ## :clipboard: Before You Start
 

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

@@ -4,7 +4,7 @@
 
 ## :dart: What You'll Do
 
-You will diagnose empty tool responses and decide whether the root cause is missing read scope, over-filtering, or truly empty repository data.
+You will diagnose empty [tool](https://github.github.com/gh-aw/reference/tools/) responses and decide whether the root cause is missing read scope, over-filtering, or truly empty repository data.
 
 ## :clipboard: Before You Start
 

workshop/side-quest-09-01c-pattern-safe-output-blocked.md

@@ -17,7 +17,7 @@ A safe-output error such as `E002: add-comment limit reached — 1 of 1 already
 
 Treat `max` as a safety boundary, not a convenience setting. A low limit reduces accidental spam if instructions are interpreted too broadly.
 
-When changing behavior, prefer precise workflow guidance like "Post one comment per run. If a comment already exists today, update context in memory and skip writing."
+When changing behavior, prefer precise workflow guidance like "Post one comment per run. If a comment already exists today, update context in [memory](https://github.github.com/gh-aw/patterns/memory-ops/) and skip writing."
 
 If you need help with wording, ask the `agentic-workflows` skill or iterate quickly with [`gh aw compile --watch`](https://github.github.com/gh-aw/setup/cli/#compile).
 

workshop/side-quest-09-01d-pattern-permission-denied.md

@@ -4,7 +4,7 @@
 
 ## :dart: What You'll Do
 
-You will map permission failures to the correct control: read access in `permissions:` and write allowlisting in `safe-outputs:`.
+You will map [permission](https://github.github.com/gh-aw/reference/permissions/) failures to the correct control: read access in `permissions:` and write allowlisting in `safe-outputs:`.
 
 ## :clipboard: Before You Start
 

workshop/side-quest-09-01f-debugging-checklist.md

@@ -13,7 +13,7 @@ You will apply a repeatable seven-step triage flow whenever a run produces unexp
 ## Checklist
 
 1. Open the live log in **Actions** and scan for `[error]` lines first.
-2. Check `[plan]` density. More than four consecutive plan lines without a tool call usually means your brief is underspecified.
+2. Check `[plan]` density. More than four consecutive plan lines without a [tool](https://github.github.com/gh-aw/reference/tools/) call usually means your brief is underspecified.
 3. Inspect `[tool]` and `[result]` lines to confirm expected data is returned.
 4. Look for `limit reached` [safe-output](https://github.github.com/gh-aw/reference/safe-outputs/) errors, such as `E002: add-comment limit reached — 1 of 1 already used this run`, and decide whether to increase `max` or tighten "post once" guidance.
 5. Read the run summary and compare it to your expected write behavior.