fix: complete Gandalf rename and fix stale autograder references (Issue #204)

Gandalf rename - remaining source files:
- REPOSITORY_SECURITY.md: 4 Aria references updated
- classroom/challenge-content-review.md: ~25 Aria refs + gender pronouns updated
- admin/qa-bundle/classroom/challenge-content-review.md: mirrored
- docs/images/learning-room-tree.svg: caption updated
- podcasts/build-challenge-bundles.js: template prompt updated
- podcasts/generate-draft-transcripts.js: proper noun regex updated
- podcasts/scripts/{cc-01,cc-03,cc-04,cc-05,ep00,ep04}: 43 bot name refs

Issue #204 - stale autograder language in podcast scripts:
- cc-07: autograded check replaced with Gandalf validation language
- cc-10: autograded check + raw YAML metadata removed
- cc-14: autograder check references updated to validation workflow
- cc-16: 8 autograder references replaced (Validation Report, no point values)
- cc-bonus-a: 7 autograder references replaced
- ep48-build-your-agent-capstone: 7 autograder references replaced

Removes: Classroom point-based scoring (10/10, 0/15), autograded section
labels, and listen-for-score instructions. Replaces with: Challenge 16
validation workflow checks, Gandalf PR Validation Report language.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: GitHub Workshop Bot

REPOSITORY_SECURITY.md

@@ -51,7 +51,7 @@ Student repos are created from the `learning-room-template`. Branch protection i
 - Students can create branches freely (required for challenges)
 - Students can merge their own PRs (required for the learning flow)
 - No force push protection (students are learning; mistakes are part of the process)
-- GitHub Actions workflows run with read/write permissions (required for Aria and the Progression Bot)
+- GitHub Actions workflows run with read/write permissions (required for Gandalf and the Progression Bot)
 
 ### What Students Cannot Do
 
@@ -113,7 +113,7 @@ The template repository includes these workflows, which are copied into every st
 
 | Workflow | Trigger | Permissions | What It Does |
 |---|---|---|---|
-| `pr-validation-bot.yml` | PR opened/updated | Read/Write | Aria validates PR structure and posts feedback |
+| `pr-validation-bot.yml` | PR opened/updated | Read/Write | Gandalf validates PR structure and posts feedback |
 | `student-progression.yml` | Issue closed | Read/Write | Creates the next challenge issue |
 | `autograder-conflicts.yml` | Push | Read | Checks for conflict markers |
 | `autograder-local-commit.yml` | Push | Read | Verifies local commit evidence |
@@ -181,7 +181,7 @@ See [teardown-checklist.md](classroom/teardown-checklist.md) for the complete po
 
 **Deployment verification:** Complete the verification checklist in the [Workshop Deployment Guide](classroom/README.md#step-6-verify-everything-works). This confirms:
 - Student repos are created correctly from the template
-- Aria responds to PRs within 60 seconds
+- Gandalf responds to PRs within 60 seconds
 - The Progression Bot creates challenge issues on issue close
 - Autograding runs and reports results
 - The feedback PR is created by Classroom
@@ -203,7 +203,7 @@ See [teardown-checklist.md](classroom/teardown-checklist.md) for the complete po
 | Incident | Response |
 |---|---|
 | GitHub is down | Continue teaching fundamentals offline; resume when GitHub is back |
-| Aria stops responding | Check Actions tab; facilitators post feedback manually until resolved |
+| Gandalf stops responding | Check Actions tab; facilitators post feedback manually until resolved |
 | Autograding fails | Check workflow logs; use it as a teaching moment about CI/CD |
 | Student cannot accept invite | Verify GitHub account exists and is signed in; check roster match |
 | Progression Bot skips a challenge | Check Actions tab for errors; manually create the missed issue |

admin/qa-bundle/classroom/challenge-content-review.md

@@ -86,7 +86,7 @@ Generate a short, conversational two-host teaching episode for this challenge.
 3. Teach the concept before the steps
 4. Walk the task in screen-reader-friendly language
 5. Explain the evidence the learner submits
-6. Explain what Aria or the autograder checks, if applicable
+6. Explain what Gandalf or the validation workflow checks, if applicable
 7. Name common mistakes and recovery paths
 8. Describe what success sounds or feels like
 9. Bridge to the next challenge

classroom/challenge-content-review.md

@@ -782,7 +782,7 @@ function buildClosingTeachingPoint(title) {
 }
 
 function lowerFirst(text) {
-  if (/^(I|GitHub|Git|VS Code|NVDA|JAWS|VoiceOver|Copilot|Aria|AI|URL)\b/.test(text)) return text;
+  if (/^(I|GitHub|Git|VS Code|NVDA|JAWS|VoiceOver|Copilot|Gandalf|AI|URL|ARIA)\b/.test(text)) return text;
   return text ? text.charAt(0).toLowerCase() + text.slice(1) : text;
 }
 

docs/images/learning-room-tree.svg

@@ -975,10 +975,10 @@ This part earns its place because when your Learning Room repo is ready, Challen
 The path is straightforward once it is named. Step one is from your repository page, navigate to the Issues tab. Keyboard shortcut: press G then I. Step two is you should see at least one open issue with a title like "Challenge 1: Find Your Way Around" authored by aria-bot (or github-actions[bot]). Step three is open Challenge 1. Read the issue body -- it tells you what to do, where to find evidence, and how to submit completion. That small check between steps is what makes the workflow reliable.
 
 [JAMIE]
-Let's pause on 6. Confirm Aria can talk to you. What should a learner take away from it?
+Let's pause on 6. Confirm Gandalf can talk to you. What should a learner take away from it?
 
 [ALEX]
-6. Confirm Aria can talk to you: The PR validation bot, Aria, posts educational feedback whenever you open a pull request. The next useful detail is concrete: To confirm Aria is wired up, open the Actions tab in your repo and look for a workflow named pr-validation-bot (or Aria PR Validation ).
+6. Confirm Gandalf can talk to you: The PR validation bot, Gandalf, posts educational feedback whenever you open a pull request. The next useful detail is concrete: To confirm Gandalf is wired up, open the Actions tab in your repo and look for a workflow named pr-validation-bot (or Gandalf PR Validation ).
 
 [PAUSE]
 
@@ -995,7 +995,7 @@ Let's pause on Readiness Checkpoint. What should a learner take away from it?
 Readiness Checkpoint has three jobs: name the idea, give the learner a move, and show what counts as evidence.
 
 [ALEX]
-Walk it in order: Find docs/CHALLENGES.md in your Learning Room repository; Explain the flow: issue - branch - pull request - review - merge; and Identify where Aria bot feedback appears on a PR (the Conversation tab). Pause after each step and listen for the confirmation before moving on.
+Walk it in order: Find docs/CHALLENGES.md in your Learning Room repository; Explain the flow: issue - branch - pull request - review - merge; and Identify where Gandalf bot feedback appears on a PR (the Conversation tab). Pause after each step and listen for the confirmation before moving on.
 
 [ALEX]
 Keep the teaching thread moving. Anchor this part on Two Tracks That Reinforce Each Other. Throughout Day 1 you work on two parallel learning tracks, both in your own account. The durable skill is not memorizing one screen. It is knowing how to find your footing when the screen changes.
@@ -1032,7 +1032,7 @@ Use the comparison to make a decision, not to recite a table. The main contrasts
 Keep the teaching thread moving. Learning Cards: Two Tracks, One Account has three jobs: name the idea, give the learner a move, and show what counts as evidence.
 
 [ALEX]
-Here is the part to remember. GitHub Skills modules run in your personal account; press G I from any Skills repo to see the issue thread where Mona posts instructions. Your Learning Room repository lives at a different URL inside the workshop organization; bookmark it and use Alt+D (address bar) to confirm which repo you are in. Aria's bot comments on your PRs appear as PR conversation comments; press 3 on the PR page to jump between them. GitHub Skills repos have a distinct green banner at the top of the README that says "Start course"; your Learning Room repo has no such banner. Check the repository name in the top-left header to confirm which track you are working in (Skills repo vs. your Learning Room). Aria's avatar appears next to bot comments; your human reviewer's avatar appears next to peer review comments.
+Here is the part to remember. GitHub Skills modules run in your personal account; press G I from any Skills repo to see the issue thread where Mona posts instructions. Your Learning Room repository lives at a different URL inside the workshop organization; bookmark it and use Alt+D (address bar) to confirm which repo you are in. Gandalf's bot comments on your PRs appear as PR conversation comments; press 3 on the PR page to jump between them. GitHub Skills repos have a distinct green banner at the top of the README that says "Start course"; your Learning Room repo has no such banner. Check the repository name in the top-left header to confirm which track you are working in (Skills repo vs. your Learning Room). Gandalf's avatar appears next to bot comments; your human reviewer's avatar appears next to peer review comments.
 
 [JAMIE]
 Let's pause on Your Learning Room Folder Structure. What should a learner take away from it?
@@ -1058,7 +1058,7 @@ Let's pause on Why you create a separate branch. What should a learner take away
 Why you create a separate branch has three jobs: name the idea, give the learner a move, and show what counts as evidence.
 
 [ALEX]
-Here is the part to remember. Protected main branch - The main branch in your Learning Room is protected; changes have to land via pull request even though you own the repo. This mirrors how mature open source projects work. Your workspace - Your learn/ branch is where you commit and push changes before opening a PR. Clean history - Keeping experiments off main until they are reviewed (by you, by Aria, or by a peer) keeps your project history easy to read. Realistic workflow - Contributors to real open source projects always create feature branches before opening a PR. You are practicing exactly that pattern.
+Here is the part to remember. Protected main branch - The main branch in your Learning Room is protected; changes have to land via pull request even though you own the repo. This mirrors how mature open source projects work. Your workspace - Your learn/ branch is where you commit and push changes before opening a PR. Clean history - Keeping experiments off main until they are reviewed (by you, by Gandalf, or by a peer) keeps your project history easy to read. Realistic workflow - Contributors to real open source projects always create feature branches before opening a PR. You are practicing exactly that pattern.
 
 [JAMIE]
 Let's pause on How to use your branch. What should a learner take away from it?
@@ -1209,7 +1209,7 @@ Let's pause on Your assigned peer reviewer (when one is paired with you). What s
 Your assigned peer reviewer (when one is paired with you) has three jobs: name the idea, give the learner a move, and show what counts as evidence.
 
 [ALEX]
-Here is the part to remember. PR title: "Complete [TODO] sections in welcome.md". PR description: lists which sections were completed. Aria's feedback: checks that all [TODO] markers are removed, heading hierarchy is valid. The actual file changes (Files Changed tab): sees the diff showing old [TODO] markers replaced with new content. Inline comment on the "Who Can Contribute?" paragraph: "Great addition - I especially like the point about AT users bringing valuable perspective.". Overall comment: "The content reads well and all TODOs are resolved. One suggestion: the 'Finding Something to Work On' section could mention checking if an issue already has an assignee.".
+Here is the part to remember. PR title: "Complete [TODO] sections in welcome.md". PR description: lists which sections were completed. Gandalf's feedback: checks that all [TODO] markers are removed, heading hierarchy is valid. The actual file changes (Files Changed tab): sees the diff showing old [TODO] markers replaced with new content. Inline comment on the "Who Can Contribute?" paragraph: "Great addition - I especially like the point about AT users bringing valuable perspective.". Overall comment: "The content reads well and all TODOs are resolved. One suggestion: the 'Finding Something to Work On' section could mention checking if an issue already has an assignee.".
 
 [ALEX]
 Walk it in order: Receives notification: "PR review requested"; Navigates to the PR in your Learning Room repo (they have collaborator access); Leaves review comments; and Submits review: Approve (or Request Changes if a [TODO] marker was missed). The point is not speed; the point is never losing your place.
@@ -1229,7 +1229,7 @@ Let's pause on You (PR author). What should a learner take away from it?
 You (PR author) has three jobs: name the idea, give the learner a move, and show what counts as evidence.
 
 [ALEX]
-The path is straightforward once it is named. Step one is read Aria's feedback and any human review. Step two is talks to the reviewer if something is unclear. Step three is makes changes based on feedback. Step four is pushes new commits to the same branch. If one step does not match what you hear, stop there and re-orient.
+The path is straightforward once it is named. Step one is read Gandalf's feedback and any human review. Step two is talks to the reviewer if something is unclear. Step three is makes changes based on feedback. Step four is pushes new commits to the same branch. If one step does not match what you hear, stop there and re-orient.
 
 [JAMIE]
 Before we leave You (PR author), what is the practical point?
@@ -1241,7 +1241,7 @@ First, re-addresses the feedback. That is the rhythm: orient, act, verify, conti
 What is the teaching move inside Visibility?
 
 [ALEX]
-Here is the part to remember. Aria re-validates on each new commit and updates its comment. Your reviewer sees the updated activity in the PR. The PR timeline shows iteration happening.
+Here is the part to remember. Gandalf re-validates on each new commit and updates its comment. Your reviewer sees the updated activity in the PR. The PR timeline shows iteration happening.
 
 [PAUSE]
 
@@ -1324,7 +1324,7 @@ Can you translate that into plain choices?
 Key Differences: Skills Module vs. Your Learning Room has three jobs: name the idea, give the learner a move, and show what counts as evidence.
 
 [ALEX]
-Use the comparison to make a decision, not to recite a table. The main contrasts are: GitHub Skills (Your Account) means Your Learning Room (Classroom). Your personal copy of a Skills repo means Your private copy of learning-room-template. Mona (GitHub) means Aria (PR validation) and the Student Progression bot.
+Use the comparison to make a decision, not to recite a table. The main contrasts are: GitHub Skills (Your Account) means Your Learning Room (Classroom). Your personal copy of a Skills repo means Your private copy of learning-room-template. Mona (GitHub) means Gandalf (PR validation) and the Student Progression bot.
 
 [ALEX]
 Keep the teaching thread moving. Here is the learner-facing version. When the facilitators pair you with another participant for Challenge 3 or Challenge 8, you will be added as a collaborator on their Learning Room repo. Put another way, here is how to find the PRs they want you to look at.
@@ -1411,7 +1411,7 @@ The teaching point here is not the label; it is the move. When the facilitators
 [PAUSE]
 
 [ALEX]
-Keep the teaching thread moving. This part earns its place because your repo is your own; you only see your own PRs. That gives the learner a foothold: Aria's feedback is on your PR alone, and any peer reviewer is specifically assigned to you.
+Keep the teaching thread moving. This part earns its place because your repo is your own; you only see your own PRs. That gives the learner a foothold: Gandalf's feedback is on your PR alone, and any peer reviewer is specifically assigned to you.
 
 [JAMIE]
 Let's pause on "Can I comment on someone else's PR?". What should a learner take away from it?
@@ -1437,7 +1437,7 @@ Keep the teaching thread moving. Anchor this part on "How long does review take?
 Let's pause on "What if bot feedback is wrong?". What should a learner take away from it?
 
 [ALEX]
-The reason this matters is simple: Aria is intentionally educational, not punitive -- if you disagree with a check, the facilitators can override it. The listener should be able to check this: Aria is not perfect, which is exactly why human review still matters.
+The reason this matters is simple: Gandalf is intentionally educational, not punitive -- if you disagree with a check, the facilitators can override it. The listener should be able to check this: Gandalf is not perfect, which is exactly why human review still matters.
 
 [PAUSE]
 

podcasts/build-challenge-bundles.js

@@ -33,7 +33,7 @@ Instructions has three jobs: name the idea, give the learner a move, and show wh
 Here are the anchors worth keeping. Confirm you can reproduce the problem they described. Suggest an approach to fix it. Ask a clarifying question.
 
 [ALEX]
-Start here: Open the Peer Simulation: Welcome Link Needs Context issue in this repository. If your facilitator gave you access to a real buddy repository, you may use your buddy's Challenge 2 issue instead. Then: Leave a meaningful comment on their issue. Ideas. Next: Use an @mention in your comment. For the simulation, mention @aria-bot. For a real buddy repository, mention your buddy's username. Last: Add a reaction to the original issue. The point is not speed; the point is never losing your place.
+Start here: Open the Peer Simulation: Welcome Link Needs Context issue in this repository. If your facilitator gave you access to a real buddy repository, you may use your buddy's Challenge 2 issue instead. Then: Leave a meaningful comment on their issue. Ideas. Next: Use an @mention in your comment. For the simulation, mention @gandalf-bot. For a real buddy repository, mention your buddy's username. Last: Add a reaction to the original issue. The point is not speed; the point is never losing your place.
 
 [JAMIE]
 What is the one idea that makes the next few steps less mysterious?
@@ -53,7 +53,7 @@ Right. The magic is not speed. The magic is knowing what changed and why it matt
 [PAUSE]
 
 [ALEX]
-Now bring the learner back to the room. Anchor this part on Peer simulation check. If your facilitator gave you a real buddy, check whether they commented on your issue and reply. This is the part to say slowly: Otherwise, reply to Aria or to your own peer-simulation comment with one follow-up thought.
+Now bring the learner back to the room. Anchor this part on Peer simulation check. If your facilitator gave you a real buddy, check whether they commented on your issue and reply. This is the part to say slowly: Otherwise, reply to Gandalf or to your own peer-simulation comment with one follow-up thought.
 
 [JAMIE]
 What would you say to someone who is already bracing for this to be too much?