fix(challenges): point Challenges 10-11 at the student's own Learning Room repo (#239)

Challenge 10 told students to clone vscode-sci-fi-themes (no student
write access, so the push step fails) and its CLI option cloned
Community-Access/learning-room.git, which does not exist. Challenge 11
sent students to the sci-fi themes repository to open their Day 2 PR,
but the Day 2 autograders (local-commit, day2-pr) only run on pull
requests inside the student's own learning room.

Both challenges and the CHALLENGES.md hub now use the student's own
Learning Room repository, matching the canonical practice flow in
Chapter 14 (which already said to clone your own room and explicitly
warned against cloning anything else). Chapter 14's read-only sci-fi
clone examples are unchanged. Legacy .github/ISSUE_TEMPLATE copies kept
in sync; work.md and html/ regenerated.

Co-authored-by: GitHub Workshop Bot <workshop@example.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Author: 3 people

.github/ISSUE_TEMPLATE/challenge-10-go-local.yml

@@ -10,7 +10,9 @@ body:
 
         **Chapters:** [Ch11: VS Code Interface](https://github.com/Community-Access/git-going-with-github/blob/main/docs/11-vscode-interface.md) | [Ch13: How Git Works](https://github.com/Community-Access/git-going-with-github/blob/main/docs/13-how-git-works.md) | [Ch14: Git in Practice](https://github.com/Community-Access/git-going-with-github/blob/main/docs/14-git-in-practice.md)
 
-        **What you will do:** Clone the sci-fi themes repo to your computer, create a feature branch, make an edit to the README.md file, commit locally, and push to GitHub.
+        **What you will do:** Clone your own Learning Room repository (this repo) to your computer, create a feature branch, make an edit to the README.md file, commit locally, and push to GitHub.
+
+        **Your repository URL:** On this repository's main page, select the green **Code** button and copy the HTTPS URL. It looks like `https://github.com/Community-Access/learning-room-...-YOUR-USERNAME.git`. You already have write access to this repo, so your push will work without any extra setup.
 
         ### The local workflow
 
@@ -30,7 +32,7 @@ body:
         1. Open VS Code
         2. Press Ctrl+Shift+P (or Cmd+Shift+P on Mac) to open the Command Palette
         3. Type `Git: Clone`
-        4. Paste this repository URL: `https://github.com/Community-Access/vscode-sci-fi-themes.git`
+        4. Paste your Learning Room repository URL (copied from the green **Code** button on this repo)
         5. Choose a folder on your computer where you want to save it
         6. Wait for it to clone (you should see it in the file explorer)
 
@@ -67,7 +69,7 @@ body:
         **Step 1: Clone the repository**
         1. Open GitHub Desktop
         2. Choose File > Clone Repository
-        3. Paste the URL: `https://github.com/Community-Access/vscode-sci-fi-themes.git`
+        3. Paste your Learning Room repository URL (copied from the green **Code** button on this repo)
         4. Choose a folder location
         5. Select Clone
 
@@ -98,19 +100,19 @@ body:
         **Option C: Command Line (CLI)**
 
         ```bash
-        # Step 1: Clone
-        git clone https://github.com/Community-Access/learning-room.git
-        cd learning-room
+        # Step 1: Clone (paste your Learning Room URL from the green Code button)
+        git clone https://github.com/Community-Access/learning-room-...-YOUR-USERNAME.git
+        cd learning-room-...-YOUR-USERNAME
 
         # Step 2: Create your branch
         git checkout -b fix/YOUR-USERNAME
 
         # Step 3: Edit a file (use your preferred editor)
-        # Open docs/chapter-XX.md and make a change
+        # Open README.md and improve a sentence or fix a typo
 
         # Step 4: Stage and commit
         git add .
-        git commit -m "fix: correct typo in chapter 5"
+        git commit -m "docs: improve README wording"
 
         # Step 5: Push
         git push -u origin fix/YOUR-USERNAME
@@ -143,7 +145,7 @@ body:
         | Symptom | Try this |
         |---|---|
         | Clone fails with authentication error | See [Appendix D: Git Authentication](https://github.com/Community-Access/git-going-with-github/blob/main/docs/appendix-d-git-authentication.md) for setup help. |
-        | Push fails with permission denied | Make sure you have write access to the repository. Ask your facilitator. |
+        | Push fails with permission denied | Make sure you cloned your own Learning Room repository (this repo), not another repository. If it still fails, ask your facilitator. |
         | I am not sure what to edit | Fix any typo, improve any sentence, or add a helpful comment. The content of the change matters less than the workflow. |
         | VS Code does not show the Source Control panel | Press Ctrl+Shift+G (Cmd+Shift+G on Mac). Make sure you opened the cloned folder as a workspace. |
         | I finished but want to check my work | [View the reference solution](https://github.com/Community-Access/git-going-with-github/blob/main/docs/solutions/solution-10-go-local.md) |

.github/ISSUE_TEMPLATE/challenge-11-day2-pr.yml

@@ -23,7 +23,7 @@ body:
         ### Step-by-step instructions
 
         **Step 1: Check for a notification banner**
-        1. Go to the sci-fi themes repository on GitHub.com
+        1. Go to your Learning Room repository (this repo) on GitHub.com
         2. You may see a notification banner at the top saying "Your branch had recent pushes"
         3. If so, select **Compare & pull request** - this is a shortcut
         4. Skip to Step 3

docs/CHALLENGES.md

@@ -188,7 +188,7 @@ Before moving on, scan the [Challenge 9 solution reference](https://github.com/C
 
 **Chapters:** Ch11-14 | **Evidence:** Comment | **Autograded**
 
-Day 2 moves the same contribution workflow onto your computer. You clone the sci-fi themes repository, create a branch locally, edit `README.md`, commit, and push the branch back to GitHub.
+Day 2 moves the same contribution workflow onto your computer. You clone your own Learning Room repository, create a branch locally, edit `README.md`, commit, and push the branch back to GitHub.
 
 **CLI best practices for this challenge:**
 
@@ -199,7 +199,7 @@ Day 2 moves the same contribution workflow onto your computer. You clone the sci
 
 **What to do:**
 
-- Clone `https://github.com/Community-Access/vscode-sci-fi-themes.git` to your computer with VS Code, GitHub Desktop, or the command line
+- Clone your own Learning Room repository (copy the HTTPS URL from the green **Code** button on its main page) with VS Code, GitHub Desktop, or the command line
 - Create a branch named `fix/YOUR-USERNAME`
 - Edit `README.md`
 - Commit and push the branch to GitHub
@@ -214,7 +214,7 @@ The [Challenge 10 solution reference](https://github.com/Community-Access/git-go
 
 **Chapters:** Ch14-15 | **Evidence:** Comment
 
-This challenge proves that the pull request pattern is the same whether the edit started in the browser or on your computer. You push a local branch to the sci-fi themes repository, open a PR, and explain the change for reviewers.
+This challenge proves that the pull request pattern is the same whether the edit started in the browser or on your computer. You push a local branch to your Learning Room repository, open a PR, and explain the change for reviewers.
 
 **CLI best practices for this challenge:**
 

html/docs/CHALLENGES.html

@@ -374,7 +374,7 @@ <h2 id="day-2-you-can-build-this-challenges-10-16">Day 2: You Can Build This (Ch
 <summary>Challenge 10: Go Local</summary>
 
 <p><strong>Chapters:</strong> Ch11-14 | <strong>Evidence:</strong> Comment | <strong>Autograded</strong></p>
-<p>Day 2 moves the same contribution workflow onto your computer. You clone the sci-fi themes repository, create a branch locally, edit <code>README.md</code>, commit, and push the branch back to GitHub.</p>
+<p>Day 2 moves the same contribution workflow onto your computer. You clone your own Learning Room repository, create a branch locally, edit <code>README.md</code>, commit, and push the branch back to GitHub.</p>
 <p><strong>CLI best practices for this challenge:</strong></p>
 <ul>
 <li>Run <code>git status</code> before and after each step.</li>
@@ -384,7 +384,7 @@ <h2 id="day-2-you-can-build-this-challenges-10-16">Day 2: You Can Build This (Ch
 </ul>
 <p><strong>What to do:</strong></p>
 <ul>
-<li>Clone <code>https://github.com/Community-Access/vscode-sci-fi-themes.git</code> to your computer with VS Code, GitHub Desktop, or the command line</li>
+<li>Clone your own Learning Room repository (copy the HTTPS URL from the green <strong>Code</strong> button on its main page) with VS Code, GitHub Desktop, or the command line</li>
 <li>Create a branch named <code>fix/YOUR-USERNAME</code></li>
 <li>Edit <code>README.md</code></li>
 <li>Commit and push the branch to GitHub</li>
@@ -397,7 +397,7 @@ <h2 id="day-2-you-can-build-this-challenges-10-16">Day 2: You Can Build This (Ch
 <summary>Challenge 11: Open a Day 2 PR</summary>
 
 <p><strong>Chapters:</strong> Ch14-15 | <strong>Evidence:</strong> Comment</p>
-<p>This challenge proves that the pull request pattern is the same whether the edit started in the browser or on your computer. You push a local branch to the sci-fi themes repository, open a PR, and explain the change for reviewers.</p>
+<p>This challenge proves that the pull request pattern is the same whether the edit started in the browser or on your computer. You push a local branch to your Learning Room repository, open a PR, and explain the change for reviewers.</p>
 <p><strong>CLI best practices for this challenge:</strong></p>
 <ul>
 <li>Build the PR body in clear plain text first, including <code>Closes #XX</code>.</li>