docs: pi-subagents pin examples — upstream npm package (fork retired)

Author: localpibox

.pi/skills/localpibox-repo-workflow/SKILL.md

@@ -262,8 +262,13 @@ Both tools are thin CLIs over the shared `scripts/localpibox/stack/` library
 6. `lpb-devstack validate` checks pins match the current stack version
 7. Persistent on the host volume — survives container rebuilds
 
-Pins look like: `git:github.com/lpb-stack/pi-subagents@<VERSION>`
-(e.g. `...pi-subagents@0.0.N-lpb-dev`)
+Pins look like:
+- `git:github.com/lpb-stack/<repo>@<VERSION>` — stack-versioned fork
+  extensions (lemonade-pi-plugin, lpb-memory), e.g. `...lpb-memory@0.0.N-lpb-dev`
+- `npm:@tintinweb/pi-subagents@<upstream-version>` — pi-subagents is pinned
+  to the **upstream npm package** (fork retired); its version follows
+  upstream releases, NOT the stack VERSION. Pin sync leaves it alone;
+  `lpb-devstack validate` treats it as a presence-only check.
 
 ## lpb-memory Config Lifecycle
 

doc/config-repo.md

@@ -67,7 +67,7 @@ Extensions are pinned in the `packages` array of `settings.json` as
     "git:github.com/lpb-stack/lemonade-pi-plugin@0.0.N-lpb-dev",
     "git:github.com/lpb-stack/lpb-memory@0.0.N-lpb-dev",
     "npm:pi-mcp-adapter",
-    "git:github.com/lpb-stack/pi-subagents@0.0.N-lpb-dev",
+    "npm:@tintinweb/pi-subagents@0.19.0",
     "npm:pi-powerline-footer",
     "@upstash/context7-mcp"
   ]

doc/lpb-config.md

@@ -79,7 +79,9 @@ Settings.json is **template-driven**, not git-tracked:
 5. `lpb-devstack validate` checks pins match the current stack version
 6. Settings.json persists on the host volume — survives container rebuilds
 
-Example pin: `git:github.com/lpb-stack/pi-subagents@0.0.N-lpb-dev`
+Example pins:
+- Fork extension (stack-versioned): `git:github.com/lpb-stack/lpb-memory@0.0.N-lpb-dev`
+- Upstream npm (fork retired, version follows upstream releases): `npm:@tintinweb/pi-subagents@0.19.0`
 
 ## lpb-memory Config Lifecycle