docs: update all documentation for Hybrid provisioning with GitHub App

Author: GitHub Workshop Bot

docs/00-pre-workshop-setup.md

@@ -16,9 +16,9 @@
 >
 > **Please complete this guide at least one day before the workshop.** If you run into any issues, use the support hub at [Community-Access/support](https://github.com/Community-Access/support) so we can help - we want Day 1 to start with everyone ready to go, not troubleshooting.
 
-If you want the most guided starting path, begin with [Get Going with GitHub](get-going.md). It explains how GitHub Classroom, your Learning Room repository, Challenge 1, evidence prompts, and tool choice all fit together before you start setup.
+If you want the most guided starting path, begin with [Get Going with GitHub](get-going.md). It explains how your Learning Room repository, Challenge 1, evidence prompts, and tool choice all fit together before you start setup.
 
-> **Expect change across tools.** GitHub.com, GitHub Classroom, VS Code, GitHub Copilot, github.dev, browsers, extensions, and agent tools change regularly. The setup steps below are maintained against official sources, but exact labels, order, prompts, and availability can vary by account, organization policy, browser, operating system, and rollout. If something differs, pause, use headings/landmarks/labels or the VS Code Command Palette to explore, and ask for help with the exact page or prompt where you got stuck.
+> **Expect change across tools.** GitHub.com, VS Code, GitHub Copilot, github.dev, browsers, extensions, and agent tools change regularly. The setup steps below are maintained against official sources, but exact labels, order, prompts, and availability can vary by account, organization policy, browser, operating system, and rollout. If something differs, pause, use headings/landmarks/labels or the VS Code Command Palette to explore, and ask for help with the exact page or prompt where you got stuck.
 
 ## Table of Contents
 
@@ -910,9 +910,9 @@ GIT & VS CODE (required before the workshop)
 
 ### What Happens at the Start of Day 1
 
-You do **not** need to claim a workshop repository before Day 1 -- that is the very first hands-on step we do together in Block 0. When the workshop opens, the facilitator will paste a **GitHub Classroom assignment link** in the chat. Accepting that link creates your own private Learning Room repository in the workshop organization and seeds it with Challenge 1.
+You do **not** need to claim a workshop repository before Day 1 -- that is the very first hands-on step we do together in Block 0. When the workshop opens, the facilitator will share an **enrollment link** in the chat. Completing enrollment creates your own private Learning Room repository in the workshop organization and seeds it with Challenge 1.
 
-The full guided walkthrough lives in [Chapter 4: Step-by-Step: Accept Your Classroom Assignment and Open Your Repo](04-the-learning-room.md#step-by-step-accept-your-classroom-assignment-and-open-your-repo). Skim it the night before if you want to know what to expect; we will walk through it live in Block 0.
+The full guided walkthrough lives in [Chapter 4: Step-by-Step: Get Your Learning Room Repository and Open Your Repo](04-the-learning-room.md#step-by-step-get-your-learning-room-and-open-your-repo). Skim it the night before if you want to know what to expect; we will walk through it live in Block 0.
 
 ## Other GitHub Access Methods (Reference Only)
 

docs/04-the-learning-room.md

@@ -7,56 +7,41 @@
 
 ## What Is the Learning Room?
 
-The **Learning Room** is your **own private GitHub repository** for the workshop. When you accept the GitHub Classroom assignment in Block 0, GitHub copies the [`Community-Access/learning-room-template`](https://github.com/Community-Access/learning-room-template) repository into the workshop classroom organization as `<workshop-org>/learning-room-<your-username>`. That copy is yours to use for the workshop - you have write access, your own branches, your own pull requests, and your own automated feedback from Gandalf the PR validation bot.
+The **Learning Room** is your **own private GitHub repository** for the workshop. When you enroll in Block 0, the provisioning system creates a copy of the [`Community-Access/learning-room-template`](https://github.com/Community-Access/learning-room-template) repository in the workshop organization as `<workshop-org>/learning-room-<your-username>`. That copy is yours to use for the workshop - you have write access, your own branches, your own pull requests, and your own automated feedback from Gandalf the PR validation bot.
 
-You do **not** work directly in `Community-Access/learning-room-template`. Think of the template as the clean master copy facilitators maintain. Your work happens in the private Learning Room repository created for you by GitHub Classroom.
+You do **not** work directly in `Community-Access/learning-room-template`. Think of the template as the clean master copy facilitators maintain. Your work happens in the private Learning Room repository created for you during enrollment.
 
 Throughout this chapter and the rest of Day 1, "your Learning Room repository" or "your Learning Room repo" refers to this private copy. Every student gets one, and every copy starts from the same template files. You will not see other students' work in your repo, and they will not see yours - but everyone is doing the same challenges in parallel. Peer-simulation issues and pull requests inside your repo provide realistic collaboration practice, and facilitators may also pair students for real peer review when access is intentionally provided.
 
-You do **not** need to create a GitHub organization or change repository permission settings. The workshop organization, template repository, Classroom assignment, and GitHub Actions permissions are managed by the facilitators.
+You do **not** need to create a GitHub organization or change repository permission settings. The workshop organization, template repository, provisioning system, and GitHub Actions permissions are managed by the facilitators.
 
 ## Why a Per-Student Repo?
 
-GitHub Classroom gives each participant their own repository for three reasons:
+Each participant gets their own repository for three reasons:
 
 - **Safety** -- you can experiment, break things, and recover without affecting anyone else
 - **Authenticity** -- you practice real repository work: issues, branches, pull requests, checks, reviews, and merging
 - **Pace** -- you progress through the 9 Day 1 challenges as fast or as slow as you need; nobody is waiting on you and you are not blocking anybody else
 
 Real open source projects are shared spaces, and you will absolutely contribute to one on Day 2 (`accessibility-agents`) and through the Bonus C challenge. The Learning Room exists so you can build the muscle memory for issue, branch, PR, review, merge in a space where every mistake is a learning opportunity, not a public problem.
 
-## Step-by-Step: Accept Your Classroom Assignment and Open Your Repo
+## Step-by-Step: Get Your Learning Room and Open Your Repo
 
 This is the very first hands-on step of Day 1. By the end of this walkthrough you will have your own Learning Room repository on GitHub and your first challenge issue waiting for you. The whole flow takes about five minutes.
 
 > **What you need before you start:**
 >
 > - A GitHub account you are signed into in your browser ([Pre-Workshop Setup, Step 1](00-pre-workshop-setup.md#step-1---create-your-github-account))
-> - The **Classroom assignment link** -- the facilitator pastes this link in the workshop chat at the start of Block 0. It looks like `https://classroom.github.com/a/<random-id>`. If you do not have it, ask in chat or DM the facilitator.
+> - The **enrollment link** -- the facilitator shares this link in the workshop chat at the start of Block 0. If you do not have it, ask in chat or DM the facilitator.
 
-### 1. Open the assignment link
+### 1. Complete enrollment
 
-1. In the same browser where you are signed into GitHub, open the Classroom assignment link the facilitator shared.
-2. The page that loads is hosted on `classroom.github.com`. Your screen reader announces a heading with the assignment name (for example, "Git Going with GitHub").
-3. If the page asks you to authorize **GitHub Classroom** to access your GitHub account, activate **Authorize GitHub Classroom**. This is a one-time step.
-
-### 2. Identify yourself (if asked)
-
-GitHub Classroom may ask you to pick your name from a roster so the facilitators can match your GitHub username to the registration list.
-
-1. If a roster page appears, navigate the list with arrow keys or use Find-in-Page (`Ctrl+F` / `Cmd+F`) to search for your name.
-2. Activate the link or button next to your name.
-3. If you do not see your name on the roster, activate the **Skip to the next step** link and tell the facilitator in chat. They will reconcile the roster after your repo is created.
-
-### 3. Accept the assignment
-
-1. You now see a screen with a button that says **Accept this assignment** (or just **Accept the assignment**). Activate it.
-2. The page changes to a status screen that says something like "You are ready to go!" with a refresh option. GitHub Classroom is now copying the `learning-room-template` repository into the workshop classroom organization and granting you access to your private copy. This usually takes 10-30 seconds.
-3. Activate the **Refresh** link (or reload the page with `F5`) every 15 seconds or so until you see a link to your new repository. The link looks like `https://github.com/<workshop-org>/learning-room-<your-username>`.
-
-> **Screen reader tip:** The status page does not auto-announce when the repo is ready. Use Browse mode and press `K` to step through links until you hear your repository link, or refresh the page until it appears.
-
-### 4. Open your new repository
+1. Open the enrollment link the facilitator shared in your browser (where you are signed into GitHub).
+2. Fill in your profile information (name, email, GitHub experience level).
+3. Submit the form to file an enrollment issue.
+4. On the issue page, reply `ack` in a comment, then close the issue.
+5. The automation will process your enrollment and create your Learning Room repository. This usually takes 30-60 seconds.
+6. Once ready, you will receive a GitHub notification with a link to your new repository, or you can navigate to it directly at `https://github.com/<workshop-org>/learning-room-<your-username>`.
 
 1. Activate the link to your repository. You land on the standard GitHub repo page for `<workshop-org>/learning-room-<your-username>`.
 2. Verify three things on this page:
@@ -65,7 +50,7 @@ GitHub Classroom may ask you to pick your name from a roster so the facilitators
    - You see folders like `docs/`, `.github/`, and files like `README.md`. These came from the template.
 3. Bookmark this page. You will return here for every Day 1 challenge.
 
-### 5. Find your first challenge issue
+### 3. Find your first challenge issue
 
 When your Learning Room repo is ready, **Challenge 1** appears as a GitHub issue in your repo. The facilitators prepare this by running the Student Progression Bot after students accept the Classroom assignment. The next challenges unlock one at a time as you close the previous ones.
 
@@ -78,7 +63,7 @@ When your Learning Room repo is ready, **Challenge 1** appears as a GitHub issue
 > 1. Open the **Actions** tab and check whether the **Student Progression Bot** workflow ran successfully.
 > 2. If it failed or never ran, post a message in the workshop chat with the link to your repo. The facilitator can trigger `student-progression.yml` or create Challenge 1 from the issue template.
 
-### 6. Confirm Gandalf can talk to you
+### 4. Confirm Gandalf can talk to you
 
 The PR validation bot, **Gandalf**, posts educational feedback whenever you open a pull request. 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**). The workflow should appear in the list even before you have opened a PR. You do not need to run anything yet -- you just want to confirm it exists.
 

docs/TOOLING-INVENTORY.md

@@ -22,7 +22,7 @@ Out of scope (excluded as noise):
 - `podcasts/logs/`, `tmp-*` files.
 - `podcasts/chapters/`, `podcasts/transcripts/`, `podcasts/bundles/`, `podcasts/challenge-bundles/` (regenerable build outputs).
 - `podcasts/llm-podcast-generator-review/generated/` (regression run outputs).
-- `node_modules/`, `.git/`, `epub/`, `learning-room/`, `classroom/` (out of reorg scope).
+- `node_modules/`, `.git/`, `epub/`, `learning-room/` (out of reorg scope).
 
 Counts shown below are raw hits from ripgrep against the patterns `\bep[0-9]{2}\b`, `appendix-[a-z]+`, and `cc-bonus-[a-e]`.
 

docs/course-guide.md

@@ -8,7 +8,7 @@
 >
 > **Note:** Workshop content is being actively refined for the May 2026 cohort. Students should expect updates to materials leading up to and during the course.
 
-> **Important: tools and websites change.** GitHub.com, GitHub Classroom, VS Code, GitHub Copilot, github.dev, browser extensions, and agent experiences are living products. We do our best to keep this curriculum current and source-backed, but labels, page order, shortcuts, preview features, model availability, and account-policy behavior can shift. If the documentation and your screen differ, use the exploration pattern taught in Chapters 2 and 3: orient by URL, page title, H1, landmarks, tab names, button labels, keyboard help, and the VS Code Command Palette. Then report the mismatch so the documentation can be corrected.
+> **Important: tools and websites change.** GitHub.com, VS Code, GitHub Copilot, github.dev, browser extensions, and agent experiences are living products. We do our best to keep this curriculum current and source-backed, but labels, page order, shortcuts, preview features, model availability, and account-policy behavior can shift. If the documentation and your screen differ, use the exploration pattern taught in Chapters 2 and 3: orient by URL, page title, H1, landmarks, tab names, button labels, keyboard help, and the VS Code Command Palette. Then report the mismatch so the documentation can be corrected.
 
 ## How This Course Works
 

docs/get-going.md

@@ -6,7 +6,7 @@
 
 This workshop is designed so you are never left guessing what comes next. You will have:
 
-- A GitHub Classroom assignment link from the facilitator
+- An enrollment link from the facilitator to create your Learning Room
 - Your own private Learning Room repository
 - Challenge issues that tell you exactly what to do
 - Evidence prompts that tell you what to post when you finish
@@ -18,7 +18,7 @@ The goal is not to rush. The goal is to build confidence one checkable step at a
 
 ## When Tools or Pages Change
 
-GitHub.com, GitHub Classroom, VS Code, GitHub Copilot, github.dev, browser extensions, and agent tools change often. This course is actively maintained, and we use official sources and live checks wherever possible, but your screen may not always match the exact wording in a step.
+GitHub.com, VS Code, GitHub Copilot, github.dev, browser extensions, and agent tools change often. This course is actively maintained, and we use official sources and live checks wherever possible, but your screen may not always match the exact wording in a step.
 
 When that happens, do not assume you are failing. Use the same exploration skills the workshop teaches:
 
@@ -36,17 +36,15 @@ Before Day 1 starts, complete [Chapter 00: Pre-Workshop Setup](00-pre-workshop-s
 
 If you cannot finish every setup step before the workshop, tell a facilitator early. Setup problems are normal, and the workshop is designed with time and support for recovery.
 
-## Step 2 - Accept the GitHub Classroom Assignment
+## Step 2 - Complete Your Enrollment
 
-At the start of the workshop, the facilitator gives you a GitHub Classroom assignment link. It usually starts with `https://classroom.github.com/a/`. This single assignment covers both Day 1 and Day 2 content -- Day 2 challenges automatically unlock after you complete Day 1.
+At the start of the workshop, the facilitator shares an enrollment link. Complete the form to create your private Learning Room repository. Day 2 challenges automatically unlock after you complete Day 1.
 
-1. Open the assignment link in the browser where you are signed in to GitHub.
-2. If GitHub asks you to authorize GitHub Classroom, activate **Authorize GitHub Classroom**.
-3. If you are asked to choose your name from a roster, find your name and select it. If your name is missing, use the skip option and tell the facilitator.
-4. Activate **Accept this assignment**.
-5. Wait while GitHub Classroom creates your private repository.
-6. Refresh the page until the repository link appears.
-7. Open the repository link and bookmark it.
+1. Open the enrollment link in the browser where you are signed in to GitHub.
+2. Complete the enrollment form with your details.
+3. An issue will be created in your account. Reply with acknowledgement (`ack`).
+4. Automation will provision your private Learning Room repository.
+5. Wait for the invitation email from GitHub, then open and bookmark your repository.
 
 Your repository name usually looks like `learning-room-your-username`. This is your personal practice space for the workshop.
 

docs/student-onboarding.md

@@ -30,15 +30,15 @@ If any step blocks you, tell us before the workshop. Setup problems are normal,
 
 You do **not** need to accept a GitHub Classroom assignment before Day 1.
 
-At the beginning of the workshop, the facilitator will share a GitHub Classroom assignment link in the meeting chat. That link creates your private Learning Room repository. We will walk through the process together.
+At the beginning of the workshop, the facilitator will share an enrollment link in the meeting chat. Completing enrollment creates your private Learning Room repository. We will walk through the process together.
 
-Preview the steps in [The Learning Room: Accept Your Classroom Assignment and Open Your Repo](04-the-learning-room.md#step-by-step-accept-your-classroom-assignment-and-open-your-repo).
+Preview the steps in [The Learning Room: Get Your Learning Room and Open Your Repo](04-the-learning-room.md#step-by-step-get-your-learning-room-and-open-your-repo).
 
 ## What Your Learning Room Is
 
 Your Learning Room is a private GitHub repository created from the `Community-Access/learning-room-template` template. It is your practice space for the workshop.
 
-You do **not** clone or work directly in the template repository. GitHub Classroom makes a private copy for you, and that private copy is the repository you use during the workshop.
+You do **not** clone or work directly in the template repository. The provisioning system makes a private copy for you, and that private copy is the repository you use during the workshop.
 
 Inside that repository you will find:
 
@@ -48,7 +48,7 @@ Inside that repository you will find:
 - Gandalf, the workshop bot that gives feedback on pull requests
 - Reference files for branches, pull requests, merge conflicts, Copilot, and agents
 
-Other students cannot see your private Learning Room repository. Facilitators can see it through GitHub Classroom so they can help when you get stuck.
+Other students cannot see your private Learning Room repository. Facilitators can see it so they can help when you get stuck.
 
 You do **not** need a GitHub organization, owner access, or repository settings access. The facilitators configure the template, Classroom assignment, and GitHub Actions permissions before the workshop. Your job is to accept the assignment link, work in the repository it creates for you, and ask for help if a permission prompt appears.
 

learning-room/.github/FACILITATOR_GUIDE.md

@@ -241,8 +241,8 @@ Remember: **The bot enables human connection, not replaces it.**
 - [Automation Setup and Maintenance](./SETUP_AND_MAINTENANCE.md)
 - [Learning Room README](../README.md)
 - [Challenge Hub](../../docs/CHALLENGES.md)
-- [Grading Guide](../../classroom/grading-guide.md)
 - [Solutions Directory](../../docs/solutions/)
+- [Hybrid Provisioning Guide](../../admin/HYBRID_DEPLOYMENT_GUIDE.md)
 
 **Questions?** Check the setup guide or reach out in your facilitator channel.