docs(troubleshooting): explain disabled Commit and Push in github.dev after room updates (#244)

A learner with confirmed write access hit a disabled Commit and Push in
github.dev because the editor's copy of her Learning Room went stale
after maintenance commits were pushed to the room
(Community-Access/support#59). Copilot then misreported it as a
permissions problem.

- Add a Common Issues entry to Appendix J with reload-and-recover steps
- Add a matching troubleshooting row to the Challenge 5 issue template
- Regenerate html/ and work.md

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

Author: 3 people

docs/appendix-j-cloud-editors.md

@@ -348,6 +348,18 @@ If the branch exists on GitHub, you can create a new Codespace from it. Uncommit
 
 You may have committed but not pushed. In the Source Control panel, look for the **Sync Changes** or **Push** button. Run `git push` in the terminal if needed.
 
+### Commit and Push is disabled in github.dev even though I have write access
+
+In github.dev, your edits are saved in the browser's local storage until you commit them. If the repository receives new commits after you opened the editor (for example, workshop maintenance updates pushed to your Learning Room), the editor's copy of the repository goes stale and **Commit & Push** can become disabled - pressing `Ctrl+Enter` in the commit message field does nothing, and the Accessible View reports that commit and push are disabled. AI assistants sometimes misreport this as a permissions problem; if you could open the private repository in github.dev, you are signed in and your access is fine.
+
+To fix it:
+
+1. Reload the browser tab (`F5`), or go back to the repository page on GitHub.com and press `.` to reopen github.dev. Your uncommitted edits are restored from browser storage after the reload.
+2. Confirm you are signed in: the **Accounts** button in the Activity Bar should announce your GitHub username.
+3. Return to the Source Control panel (`Ctrl+Shift+G`), enter your commit message, and press `Ctrl+Enter`.
+
+If it is still disabled after a reload, copy your edited text to the clipboard as a backup, then use the **Edit this file** (pencil) editor on GitHub.com instead - it commits directly and does not depend on browser state.
+
 ---
 
 *Next: [Appendix K: Copilot Reference](appendix-k-copilot-reference.md)*  

html/docs/appendix-j-cloud-editors.html

@@ -267,6 +267,7 @@ <h2 class="onpage-title">On This Page</h2>
 <li class="onpage-item onpage-sub"><a href="#extensions-i-rely-on-locally-are-not-available">Extensions I rely on locally are not available</a></li>
 <li class="onpage-item onpage-sub"><a href="#i-accidentally-deleted-my-codespace-before-pushing">I accidentally deleted my Codespace before pushing</a></li>
 <li class="onpage-item onpage-sub"><a href="#my-changes-are-not-showing-in-github-after-committing">My changes are not showing in GitHub after committing</a></li>
+<li class="onpage-item onpage-sub"><a href="#commit-and-push-is-disabled-in-githubdev-even-though-i-have-write-access">Commit and Push is disabled in github.dev even though I have write access</a></li>
 <li class="onpage-item"><a href="#authoritative-sources">Authoritative Sources</a></li>
 <li class="onpage-item onpage-sub"><a href="#section-level-source-map">Section-Level Source Map</a></li>
     </ul>
@@ -723,6 +724,15 @@ <h3 id="i-accidentally-deleted-my-codespace-before-pushing">I accidentally delet
 <p>If the branch exists on GitHub, you can create a new Codespace from it. Uncommitted changes in a deleted Codespace cannot be recovered.</p>
 <h3 id="my-changes-are-not-showing-in-github-after-committing">My changes are not showing in GitHub after committing</h3>
 <p>You may have committed but not pushed. In the Source Control panel, look for the <strong>Sync Changes</strong> or <strong>Push</strong> button. Run <code>git push</code> in the terminal if needed.</p>
+<h3 id="commit-and-push-is-disabled-in-githubdev-even-though-i-have-write-access">Commit and Push is disabled in github.dev even though I have write access</h3>
+<p>In github.dev, your edits are saved in the browser&#39;s local storage until you commit them. If the repository receives new commits after you opened the editor (for example, workshop maintenance updates pushed to your Learning Room), the editor&#39;s copy of the repository goes stale and <strong>Commit &amp; Push</strong> can become disabled - pressing <code>Ctrl+Enter</code> in the commit message field does nothing, and the Accessible View reports that commit and push are disabled. AI assistants sometimes misreport this as a permissions problem; if you could open the private repository in github.dev, you are signed in and your access is fine.</p>
+<p>To fix it:</p>
+<ol>
+<li>Reload the browser tab (<code>F5</code>), or go back to the repository page on GitHub.com and press <code>.</code> to reopen github.dev. Your uncommitted edits are restored from browser storage after the reload.</li>
+<li>Confirm you are signed in: the <strong>Accounts</strong> button in the Activity Bar should announce your GitHub username.</li>
+<li>Return to the Source Control panel (<code>Ctrl+Shift+G</code>), enter your commit message, and press <code>Ctrl+Enter</code>.</li>
+</ol>
+<p>If it is still disabled after a reload, copy your edited text to the clipboard as a backup, then use the <strong>Edit this file</strong> (pencil) editor on GitHub.com instead - it commits directly and does not depend on browser state.</p>
 <hr>
 <p><em>Next: <a href="appendix-k-copilot-reference.html">Appendix K: Copilot Reference</a></em><br><em>Back: <a href="appendix-i-github-cli.html">Appendix I: GitHub CLI Reference</a></em><br><em>Teaching chapter: <a href="01-choose-your-tools.html">Chapter 01: Choose Your Tools</a></em></p>
 <h2 id="authoritative-sources">Authoritative Sources</h2>