Hide non-active challenge templates from issue picker (#215)

- Add hidden: true to all challenge/bonus templates except current active one (Challenge 2)
- Students now only see Challenge 2 template when creating issues
- Reduces template picker UX friction during learning

Co-authored-by: GitHub Workshop Bot <workshop@example.com>

Author: accesswatch

admin/qa-bundle/learning-room/.github/ISSUE_TEMPLATE/bonus-a-improve-agent.yml

@@ -1,5 +1,6 @@
 name: "Bonus A: Improve an Existing Agent"
 description: Fork an agent, make a meaningful improvement, and open a PR.
+hidden: true
 title: "Bonus: Improve an Existing Agent (@{username})"
 labels: ["challenge", "bonus"]
 body:
@@ -36,6 +37,7 @@ body:
     attributes:
       label: "Your evidence"
       description: "Describe the agent you improved, what you changed, and link your PR."
+hidden: true
       placeholder: |
         Agent I improved: ...
         What I changed: ...

admin/qa-bundle/learning-room/.github/ISSUE_TEMPLATE/bonus-b-document-journey.yml

@@ -1,5 +1,6 @@
 name: "Bonus B: Document Your Journey"
 description: Write a reflection document about your workshop experience.
+hidden: true
 title: "Bonus: Document Your Journey (@{username})"
 labels: ["challenge", "bonus"]
 body:
@@ -43,6 +44,7 @@ body:
     attributes:
       label: "Your evidence"
       description: "Share the link to your reflection file or PR."
+hidden: true
       placeholder: |
         Reflection URL: https://github.com/...
         My biggest takeaway: ...

admin/qa-bundle/learning-room/.github/ISSUE_TEMPLATE/bonus-c-group-challenge.yml

@@ -1,5 +1,6 @@
 name: "Bonus C: Create a Group Challenge"
 description: Design a collaborative challenge for future workshop cohorts.
+hidden: true
 title: "Bonus: Create a Group Challenge (@{username})"
 labels: ["challenge", "bonus"]
 body:
@@ -39,6 +40,7 @@ body:
     attributes:
       label: "Your evidence"
       description: "Describe your group challenge and link to the file."
+hidden: true
       placeholder: |
         Challenge name: ...
         What teams would do: ...

admin/qa-bundle/learning-room/.github/ISSUE_TEMPLATE/bonus-d-notifications.yml

@@ -1,5 +1,6 @@
 name: "Bonus D: Notification Mastery"
 description: Configure GitHub notifications for productive inbox management.
+hidden: true
 title: "Bonus: Notification Mastery (@{username})"
 labels: ["challenge", "bonus"]
 body:
@@ -36,6 +37,7 @@ body:
     attributes:
       label: "Your evidence"
       description: "Describe your notification configuration and strategy."
+hidden: true
       placeholder: |
         My notification strategy: ...
         I configured email for: ...

admin/qa-bundle/learning-room/.github/ISSUE_TEMPLATE/bonus-e-git-history.yml

@@ -1,5 +1,6 @@
 name: "Bonus E: Explore Git History Visually"
 description: Use GitHub Desktop to explore repository history as a visual timeline.
+hidden: true
 title: "Bonus: Explore Git History Visually (@{username})"
 labels: ["challenge", "bonus"]
 body:
@@ -41,6 +42,7 @@ body:
     attributes:
       label: "Your evidence"
       description: "Describe what you discovered by exploring the Git history visually."
+hidden: true
       placeholder: |
         Tool I used: GitHub Desktop / GitHub.com
         Number of branches I found: ...

admin/qa-bundle/learning-room/.github/ISSUE_TEMPLATE/challenge-01-find-your-way.yml

@@ -1,5 +1,6 @@
 name: "Challenge 1: Find Your Way Around"
 description: Navigate the learning-room repository and find key landmarks.
+hidden: true
 title: "Challenge 1: Find Your Way Around (@{username})"
 labels: ["challenge", "day-1"]
 body:
@@ -28,6 +29,7 @@ body:
     attributes:
       label: "Your evidence"
       description: "Paste your scavenger hunt findings below. For each item, write a short sentence about what you found."
+hidden: true
       placeholder: |
         1. I found ___ files in the root of the repository.
         2. The open issue I found was titled "___".

admin/qa-bundle/learning-room/.github/ISSUE_TEMPLATE/challenge-03-conversation.yml

@@ -1,5 +1,6 @@
 name: "Challenge 3: Join the Conversation"
 description: Comment on a peer-simulation issue using @mentions and reactions.
+hidden: true
 title: "Challenge 3: Join the Conversation (@{username})"
 labels: ["challenge", "day-1"]
 body:
@@ -33,6 +34,7 @@ body:
     attributes:
       label: "Your evidence"
       description: "Paste the URL of the comment you left on the peer-simulation issue or buddy issue."
+hidden: true
       placeholder: |
         Comment URL: https://github.com/...
         I commented on the peer-simulation issue about...

admin/qa-bundle/learning-room/.github/ISSUE_TEMPLATE/challenge-04-branch-out.yml

@@ -1,5 +1,6 @@
 name: "Challenge 4: Branch Out"
 description: Create your personal branch for Day 1 work.
+hidden: true
 title: "Challenge 4: Branch Out (@{username})"
 labels: ["challenge", "day-1"]
 body:
@@ -34,6 +35,7 @@ body:
     attributes:
       label: "Your evidence"
       description: "Confirm your branch name and describe how you created it."
+hidden: true
       placeholder: |
         My branch name: learn/myusername
         I created it by...

admin/qa-bundle/learning-room/.github/ISSUE_TEMPLATE/challenge-05-make-your-mark.yml

@@ -1,5 +1,6 @@
 name: "Challenge 5: Make Your Mark"
 description: Edit welcome.md to fix a TODO and commit with a meaningful message.
+hidden: true
 title: "Challenge 5: Make Your Mark (@{username})"
 labels: ["challenge", "day-1"]
 body:
@@ -36,6 +37,7 @@ body:
     attributes:
       label: "Your evidence"
       description: "Paste the URL of your commit and share your commit message."
+hidden: true
       placeholder: |
         Commit URL: https://github.com/...
         My commit message was: "..."

admin/qa-bundle/learning-room/.github/ISSUE_TEMPLATE/challenge-06-first-pr.yml

@@ -1,5 +1,6 @@
 name: "Challenge 6: Open Your First Pull Request"
 description: Open a PR from your branch to main, linking it to your issue.
+hidden: true
 title: "Challenge 6: Open Your First PR (@{username})"
 labels: ["challenge", "day-1"]
 body:
@@ -24,6 +25,7 @@ body:
         ### PR description template
 
         Use this structure for your PR description:
+hidden: true
 
         ```
         ## What this PR does
@@ -48,6 +50,7 @@ body:
     attributes:
       label: "Your evidence"
       description: "Paste the URL of your pull request."
+hidden: true
       placeholder: |
         PR URL: https://github.com/...
         My PR links to issue #...