docs(enrollment): explain instant access for existing org members

Learners who are already Community-Access org members (prior cohort,
facilitator role, etc.) get instant repo access with no invitation
email, so the standard "watch for an invitation" guidance leaves them
stuck. Add the same clarification to the enrollment success comment
and the Get Going guide. Surfaced by support#62.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Author: GitHub Workshop Bot

.github/workflows/registration.yml

@@ -400,6 +400,8 @@ jobs:
               'Please reply `ack` on this issue after you receive your learning room invitation.',
               'Then close this enrollment issue as Challenge 0.',
               '',
+              'If you are already a member of the Community-Access GitHub organization for any other reason, you will not get an invitation email - GitHub grants existing org members instant access instead. If an hour has passed, check your repository list directly for `learning-room-self-paced-2026-<your-username>` before filing a support issue.',
+              '',
               'If you do not receive an invitation within an hour, or you get stuck at any step, open support:',
               '- https://github.com/Community-Access/support/issues',
               '',

docs/get-going.md

@@ -48,6 +48,8 @@ At the start of the workshop, the facilitator shares an enrollment link. Complet
 
 Your repository name usually looks like `learning-room-your-username`. This is your personal practice space for the workshop.
 
+> **No invitation arrived?** If you are already a member of the Community-Access GitHub organization for any other reason (a prior cohort, a facilitator role, and so on), GitHub grants you instant access to your new Learning Room instead of sending an invitation - there is nothing to accept and no notification. Check your repository list or search github.com directly for your repository name before filing a support issue.
+
 ## Step 3 - Understand the Learning Room
 
 The Learning Room is a private repository created from a template. Everyone starts from the same materials, but your work belongs to you.

html/admin/PODCASTS.html

@@ -4665,8 +4665,8 @@ <h4 id="transcript">Transcript</h4>
 </p>
 <hr />
 <p><strong>Alex:</strong> In the chapter practice, the first mini challenge is intentionally small: create one
-  branch change. You open your assigned Chapter 6.1 issue in the Learning Room, go to the
-  file it names, and make only the requested edit.
+  branch change. This is prep work for Challenge 6, not a separate issue - you just pick one
+  of the three practice files in the Learning Room and make one focused edit.
 </p>
 <p><strong>Jamie:</strong> Those files are things like the welcome document, the keyboard shortcuts reference, and
   the setup guide, right?
@@ -5749,9 +5749,9 @@ <h4 id="transcript">Transcript</h4>
 <p><strong>Jamie:</strong> I like that it is controlled. You are not being dropped into a huge open source conflict
   with ten files and a blinking cursor.
 </p>
-<p><strong>Alex:</strong> Exactly. You open your assigned Chapter 7 challenge issue, the one titled something like
-  &quot;Chapter 7.1: Resolve Conflict Markers (@yourname).&quot; The issue tells you which
-  practice file contains the markers.
+<p><strong>Alex:</strong> Exactly. You open your Challenge 7 issue - titled &quot;Challenge 7: Survive a Merge
+  Conflict&quot; - and opening it automatically opens a practice pull request in your repository
+  with a real conflict already showing in docs/welcome.md.
 </p>
 <p><strong>Jamie:</strong> Then the first practical move is to search for &lt;&lt;&lt;&lt;&lt;&lt;&lt;, right?
 </p>

html/docs/get-going.html

@@ -283,6 +283,9 @@ <h2 id="step-2---complete-your-enrollment">Step 2 - Complete Your Enrollment</h2
 <li>Wait for the invitation email from GitHub, then open and bookmark your repository.</li>
 </ol>
 <p>Your repository name usually looks like <code>learning-room-your-username</code>. This is your personal practice space for the workshop.</p>
+<blockquote>
+<p><strong>No invitation arrived?</strong> If you are already a member of the Community-Access GitHub organization for any other reason (a prior cohort, a facilitator role, and so on), GitHub grants you instant access to your new Learning Room instead of sending an invitation - there is nothing to accept and no notification. Check your repository list or search github.com directly for your repository name before filing a support issue.</p>
+</blockquote>
 <h2 id="step-3---understand-the-learning-room">Step 3 - Understand the Learning Room</h2>
 <p>The Learning Room is a private repository created from a template. Everyone starts from the same materials, but your work belongs to you.</p>
 <p>You can safely practice there because:</p>