[guidelines] fix obvious guideline violations in 10 file(s)

workshop/side-quest-11-03-better-prompts.md

@@ -147,7 +147,7 @@ posted to the Actions run summary.
 
 ---
 
-## ✅ Checkpoint
+## :white_check_mark: Checkpoint
 
 - [ ] You can name three techniques for improving a task brief
 - [ ] You have updated your daily status workflow with at least one improvement from this guide

workshop/side-quest-11-04-annotated-workflow.md

@@ -92,7 +92,7 @@ safe-outputs:
 
 ---
 
-## ✅ Checkpoint
+## :white_check_mark: Checkpoint
 
 - [ ] I changed `emoji:`, ran `gh aw list`, and saw the update reflected
 - [ ] I removed `safe-outputs:`, observed the compile error, then restored it and confirmed the error was gone

workshop/side-quest-11-05-event-triggers.md

@@ -136,7 +136,7 @@ The Daily Repo Status workflow in [Step 7](07-your-first-workflow.md) and the PR
 That is the core decision: pick the trigger that matches the moment you care about, then pick the write target that matches the object you want the workflow to answer.
 
 <!-- journey: all -->
-## ✅ Checkpoint
+## :white_check_mark: Checkpoint
 
 - [ ] I can explain the difference between a scheduled workflow and an event-driven workflow
 - [ ] I know starter trigger blocks for `pull_request`, `push`, `issues`, and `schedule`

workshop/side-quest-11-06-anthropic-key.md

@@ -106,7 +106,7 @@ You should see output confirming the file compiled without errors.
 
 ---
 
-## ✅ Checkpoint
+## :white_check_mark: Checkpoint
 
 - [ ] You have an Anthropic account and have generated an API key
 - [ ] `ANTHROPIC_API_KEY` is stored as a repository secret

workshop/side-quest-11-07-openai-key.md

@@ -123,7 +123,7 @@ You should see:
 
 ---
 
-## ✅ Checkpoint
+## :white_check_mark: Checkpoint
 
 - [ ] You have an OpenAI account and have generated an API key
 - [ ] My new key is listed at `platform.openai.com/api-keys`

workshop/side-quest-11-08-frontmatter-tools-outputs.md

@@ -113,7 +113,7 @@ Three conventions keep a task brief reliable:
 
 ---
 
-## ✅ Checkpoint
+## :white_check_mark: Checkpoint
 
 - [ ] You can explain what `mode: gh-proxy` does and why it matters for security
 - [ ] You understand that `safe-outputs` is the only source of write access — not the body text

workshop/side-quest-11-09-agent-session-phases.md

@@ -58,7 +58,7 @@ gh aw compile --watch
 
 Each save triggers another compile, so you get immediate feedback instead of discovering YAML mistakes later. See [Side Quest: Using `gh aw compile` to Catch Errors Early](side-quest-07-01-compile-workflow.md) for a full walkthrough.
 
-## ✅ Checkpoint
+## :white_check_mark: Checkpoint
 
 - [ ] I can name the five phases of an agent session in order
 - [ ] I know what a successful Compiling phase looks like (green success message, `.lock.yml` generated)

workshop/side-quest-12-01-iterate-agent-output.md

@@ -104,7 +104,7 @@ Quick run-log check:
 
 </details>
 
-## ✅ Checkpoint
+## :white_check_mark: Checkpoint
 
 - [ ] You triggered a fresh workflow run and captured one real output to review
 - [ ] You recorded a baseline score for accuracy, completeness, and tone

workshop/side-quest-13-01-pr-labeler-pattern.md

@@ -78,7 +78,7 @@ Compile, push, and test with a PR that changes a workflow file.
 
 </details>
 
-## ✅ Checkpoint
+## :white_check_mark: Checkpoint
 
 - [ ] I created `.github/workflows/pr-labeler.md` with a `pull_request` trigger
 - [ ] `gh aw compile` completed without errors and `.lock.yml` is committed and pushed

workshop/side-quest-13-01-schedule-expressions.md

@@ -78,7 +78,7 @@ If none of the fuzzy options match your exact timing need, choose the closest fu
 > ```
 
 <!-- journey: all -->
-## ✅ Checkpoint
+## :white_check_mark: Checkpoint
 
 - [ ] I can explain what a cron expression is at a high level
 - [ ] I know which fuzzy schedule expression best matches my workflow cadence