From bdbec224372b37b15280f13a4a69265edfebf69d Mon Sep 17 00:00:00 2001 From: Larry Stewart Date: Wed, 10 Jun 2026 16:50:19 -0400 Subject: [PATCH] =?UTF-8?q?README:=20FAQ=20update=20steps=20=E2=80=94=20ad?= =?UTF-8?q?d=20/reload-plugins=20and=20lazarus-forge?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 227c8f3..990d0de 100644 --- a/README.md +++ b/README.md @@ -278,7 +278,7 @@ Use WSL. The guard is a bash hook (scripts/check-destructive.sh How do updates work?
-Run /plugin update lazarus@cognitivecode (and lazarus-github if you installed it). The plugin is git-SHA-versioned, so /plugin update always pulls the latest main — there's no version number you have to match. Tagged releases like v0.2.1 are human-readable changelog markers (see Releases), not something you pin to. +Two steps. 1) Run /plugin update lazarus@cognitivecode (and the same for lazarus-github / lazarus-forge if you installed them). 2) Run /reload-plugins (or restart claude) — 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 /plugin update always pulls the latest main — there's no version number you have to match. Tagged releases like v0.5.0 are human-readable changelog markers (see Releases), not something you pin to. Check what you're on with /plugin list.