README: FAQ update steps — add /reload-plugins and lazarus-forge (#22)

The 'How do updates work?' answer predated forge and omitted the
reload step the install section calls mandatory — a real user hit
exactly this gap. Now: update all installed plugins, then
/reload-plugins; plus a /plugin list pointer to verify.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Author: CognitiveCodeAI

README.md

@@ -278,7 +278,7 @@ Use <b>WSL</b>. The guard is a bash hook (<code>scripts/check-destructive.sh</co
 <details>
 <summary><b>How do updates work?</b></summary>
 <br/>
-Run <code>/plugin update lazarus@cognitivecode</code> (and <code>lazarus-github</code> if you installed it). The plugin is git-SHA-versioned, so <code>/plugin update</code> always pulls the latest <code>main</code> — there's no version number you have to match. Tagged releases like <code>v0.2.1</code> are human-readable changelog markers (see <b>Releases</b>), not something you pin to.
+Two steps. <b>1)</b> Run <code>/plugin update lazarus@cognitivecode</code> (and the same for <code>lazarus-github</code> / <code>lazarus-forge</code> if you installed them). <b>2)</b> Run <code>/reload-plugins</code> (or restart <code>claude</code>) — same rule as installing: the updated skills, hooks, and guard don't go live in your session until you reload. The plugin is git-SHA-versioned, so <code>/plugin update</code> always pulls the latest <code>main</code> — there's no version number you have to match. Tagged releases like <code>v0.5.0</code> are human-readable changelog markers (see <b>Releases</b>), not something you pin to. Check what you're on with <code>/plugin list</code>.
 </details>
 
 <details>