Merge remote-tracking branch 'origin/dev'

Author: localpibox

.env.example

@@ -70,15 +70,16 @@ LPB_AGENT_BROWSER_IDLE_TIMEOUT_MS=300000
 # Response ceilings are per-model now — the `maxTokens` field in the
 # lemonade-pi-plugin model catalog (~/.pi/agent/model-params.json). The old
 # global LPB_MAX_TOKENS_CONTEXT_RATIO was retired 2026-09-02 (exact values
-# per model, no formula — see lemonade-pi-plugin/docs/qwen-thinking-
-# mainstream-pi.md §5.0).
+# per model, no formula — see the lemonade-pi-plugin README, "Model
+# parameters").
 
 # Capture outgoing provider payloads (lemonade-pi-plugin) — ALL models.
 # 1 = the plugin logs one JSON line per request (tuned view for catalogued
 # models, raw view otherwise) to /tmp/pi-payload-capture.jsonl inside the
 # container. Used to verify exactly what goes over the wire.
-# See lemonade-pi-plugin/docs/qwen-thinking-mainstream-pi.md §5.0/§7.
-# LPB_PAYLOAD_DEBUG=1
+# Bare name on purpose: the plugin reads LEMONADE_PAYLOAD_DEBUG (the
+# LPB_→bare bridge would only produce PAYLOAD_DEBUG, which nothing reads).
+# LEMONADE_PAYLOAD_DEBUG=1
 
 # SSH port for `lpb --ssh` (default: 2222)
 # LPB_SSH_PORT=2222

.githooks/pre-commit

@@ -13,6 +13,13 @@
 #   SKIP_TESTS=1 git commit ...   — skip unit tests (~4s)
 #   git commit --no-verify ...    — skip everything
 
+# In a linked worktree GIT_DIR is an ABSOLUTE path into the main repo's
+# .git/worktrees/<name> — it would leak into every `git -C` subprocess the
+# validate runs and poison the workspace checks (all repos would report
+# the worktree's HEAD). Re-derive from CWD instead. GIT_INDEX_FILE stays:
+# the staged-check below needs the commit's temporary index.
+unset GIT_DIR GIT_WORK_TREE
+
 # Devstack's own tree: tracked changes must be STAGED — unstaged edits
 # would silently be missing from the commit being made right now.
 # (Untracked files are fine: new work-in-progress.)

.github/workflows/build-and-publish.yml

@@ -304,14 +304,12 @@ jobs:
           # dev pipeline: dev branches; main pipeline: stable branches
           if [ "${GITHUB_REF_NAME}" = "main" ]; then
             declare -A REPO_BRANCHS=(
-              ["lpb-stack/pi-subagents"]="lpb"
               ["lpb-stack/lemonade-pi-plugin"]="lpb"
               ["lpb-stack/config"]="main"
               ["lpb-stack/lpb-memory"]="main"
             )
           else
             declare -A REPO_BRANCHS=(
-              ["lpb-stack/pi-subagents"]="lpb-dev"
               ["lpb-stack/lemonade-pi-plugin"]="lpb-dev"
               ["lpb-stack/config"]="dev"
               ["lpb-stack/lpb-memory"]="dev"
@@ -398,10 +396,10 @@ jobs:
           VERSION=$(git show origin/main:VERSION | tr -d '[:space:]')
           mkdir -p ws/git
           git clone --quiet https://github.com/lpb-stack/config.git ws/config
-          for r in lpb-memory pi-subagents lemonade-pi-plugin; do
+          for r in lpb-memory lemonade-pi-plugin; do
             git clone --quiet "https://github.com/lpb-stack/$r.git" "ws/git/$r"
           done
-          for d in ws/config ws/git/lpb-memory ws/git/pi-subagents \
+          for d in ws/config ws/git/lpb-memory \
                    ws/git/lemonade-pi-plugin; do
             git -C "$d" fetch --quiet --depth 1 origin tag "$VERSION"
             git -C "$d" checkout -q "$VERSION"

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

@@ -33,7 +33,7 @@ from `gh-pages` at `https://lpb-stack.github.io/devstack/<version>/`).
 
 **Branch facts** (for "branch off X / PR to X" lines in CONTRIBUTING files):
 default branch is `dev` for devstack/config/lpb-memory, `lpb-dev` for the
-forks (pi, pi-subagents, lemonade-pi-plugin). `main`/`lpb` are stable
+lemonade-pi-plugin fork. `main`/`lpb` are stable
 branches written by `lpb-devstack release promote` — not PR targets.
 
 ## GitHub-Compatible Mermaid

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

@@ -1,6 +1,6 @@
 ---
 name: lpb-stack-repo-workflow
-description: Manage the 6 LocalPibox repos — manual versioning (lpb-devstack bump), stable releases, image builds, lpb.py.
+description: Manage the LocalPibox stack repos — manual versioning (lpb-devstack bump), stable releases, image builds, lpb.py.
 ---
 # LocalPibox Repository Workflow
 
@@ -39,9 +39,10 @@ CI: VERSION changed in pushed commit → tests → build + publish → tag 4 rep
 - **devstack/VERSION** — the only VERSION file in the stack (e.g. `0.0.N-lpb-dev`)
 - **Format:** dev pipeline `0.x.y-lpb-dev`, main pipeline `0.x.y-lpb`
 - **`lpb-devstack bump`** is the **dev release trigger**: before committing a
-  VERSION change it gates on all 5 stack repos being on their dev branch,
-  fully pushed, and committed (CI tags the *remote* dev heads — unpushed or
-  uncommitted local work would ship invisibly). `bump --force` bypasses.
+  VERSION change it gates on every tagged stack repo (all except devstack)
+  being on its dev branch, fully pushed, and committed (CI tags the *remote*
+  dev heads — unpushed or uncommitted local work would ship invisibly).
+  `bump --force` bypasses.
   The docs gate is main-pipeline only (`release promote`).
 - **`lpb-devstack bump`** preserves major.minor, increments patch (or
   `--minor` / `--major` / `--set`), keeps the current suffix, and commits
@@ -67,7 +68,7 @@ CI: VERSION changed in pushed commit → tests → build + publish → tag 4 rep
 | **config** | workspace (agent preset) | `dev` | `main` |
 | **lpb-memory** | workspace + extension | `dev` | `main` |
 | **pi** | reference clone (de-forked — image installs pi from npm at `LPB_PI_VERSION`) | — | — |
-| **pi-subagents** | extension | `lpb-dev` | `lpb` |
+| **pi-subagents** | extension (upstream npm — de-forked 2026-09-10, not a git repo) | — | — |
 | **lemonade-pi-plugin** | extension | `lpb-dev` | `lpb` |
 
 Org: all repos live under **`github.com/lpb-stack`** (migrated from
@@ -81,7 +82,6 @@ the GitHub org and GHCR paths use `lpb-stack`.
 Workspace:
   /home/lpb/workspace/devstack            (real clone, single source)
   /home/lpb/workspace/pi                  (reference clone of the retired fork)
-  /home/lpb/workspace/pi-subagents        (symlink → agent git clone)
   /home/lpb/workspace/lemonade-pi-plugin  (symlink → agent git clone)
   /home/lpb/workspace/lpb-memory          (symlink → agent git clone)
 
@@ -90,7 +90,10 @@ Agent config (cloned from lpb-stack/config by start.sh at container start):
 
 Extension clones (pi loads these per settings.json pins):
   /home/lpb/.pi/agent/git/github.com/lpb-stack/
-      lemonade-pi-plugin, lpb-memory, pi-subagents
+      lemonade-pi-plugin, lpb-memory
+
+  pi-subagents is NOT a git clone — it installs from the upstream npm
+  package (@tintinweb/pi-subagents) per the settings.json pin.
 
 ⚠️ Extensions update at runtime via `pi update --extensions`.
    They are NOT baked into Docker images.
@@ -102,9 +105,9 @@ Extension clones (pi loads these per settings.json pins):
 
 - **`dev`** (devstack, config, lpb-memory): primary development. Default on GitHub.
 - **`main`** (devstack, config, lpb-memory): stable release branch.
-- **`lpb-dev`** (pi-subagents, lemonade-pi-plugin): active development from
+- **`lpb-dev`** (lemonade-pi-plugin): active development from
   upstream + LPB patches. Default on GitHub.
-- **`lpb`** (pi-subagents, lemonade-pi-plugin): stable branch — receives
+- **`lpb`** (lemonade-pi-plugin): stable branch — receives
   clean merges from `lpb-dev` via the release procedure. Divergence from
   `lpb-dev` is normal during active development.
 
@@ -138,7 +141,7 @@ docs sync + review happens at release time via `docs-ready`.
 #    commits DOCS_READY=<stable-version> on the docs branch + pushes)
 lpb-devstack release docs-ready
 
-# 1. Readiness check (all 5 repos + docs verdict, non-destructive, fetches first)
+# 1. Readiness check (all tagged repos + docs verdict, non-destructive, fetches first)
 lpb-devstack release status
 
 # 2. Inspect the exact plan without changing anything
@@ -262,8 +265,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
 

CONTRIBUTING.md

@@ -20,7 +20,7 @@ has its own scope:
 | [config](https://github.com/lpb-stack/config) | Pi settings, MCP servers, custom skills, subagents presets |
 | [pi](https://github.com/earendil-works/pi) | Upstream of the coding agent core — installed from npm at `LPB_PI_VERSION`, not a stack repo since the 2026-08-31 de-fork; patches go upstream |
 | [lemonade-pi-plugin](https://github.com/lpb-stack/lemonade-pi-plugin) | Qwen thinking + vision support (fork) |
-| [pi-subagents](https://github.com/lpb-stack/pi-subagents) | Centralized subagent model registry (fork) |
+| [pi-subagents](https://github.com/tintinweb/pi-subagents) | Upstream of the subagent model registry — installed from npm, not a stack repo since the 2026-09-10 de-fork |
 | [lpb-memory](https://github.com/lpb-stack/lpb-memory) | Persistent memory / session search extension |
 
 ### Process

Dockerfile

@@ -29,7 +29,7 @@
 # NOTE: Docker ARG values can't reference source'd shell variables.
 ARG NODE_VERSION=24
 ARG VSCODIUM_VERSION=1.126.04524
-ARG PI_VERSION=0.84.4
+ARG PI_VERSION=0.85.1
 ARG PI_HEAD_SHA=unknown
 
 # Config preset repo — baked so start.sh clones the fork's config at boot.
@@ -51,7 +51,7 @@ FROM ubuntu:26.04 AS base
 
 ARG NODE_VERSION
 ARG VSCODIUM_VERSION
-ARG PI_VERSION=0.84.4
+ARG PI_VERSION=0.85.1
 ARG PI_HEAD_SHA
 ARG CONFIG_FORK
 ARG CONFIG_REF

README.md

@@ -6,6 +6,26 @@ optimized for Qwen models served locally through **Lemonade**, targeting
 AMD Strix Halo hardware. No cloud LLM required; your code and data stay
 on your machine.
 
+## What You Get
+
+Everything below ships in the base image — no extra setup beyond the
+[Quick Start](#quick-start).
+
+| Capability | What it means in practice |
+|---|---|
+| **Local inference, zero cloud** | All model calls go to the local Lemonade server (GGUF models, AMD Strix Halo optimized). Your code, data, and prompts never leave the machine. |
+| **Full coding agent** | Pi — foreground CLI, interactive shell, SSH login, or web; sessions, session tree, skills, prompt templates, themes. |
+| **Controlled thinking depth** | `/thinking` levels (off → high) with per-level budgets and per-model effort mapping; per-model parameters tunable live via `/lemonade tune` — [Thinking Support](doc/thinking-support.md) |
+| **Vision** | Screenshots and visual page analysis by the local vision model — the agent can see webpages, UIs, and render output. |
+| **Persistent memory** | `lpb-memory` — durable memory plus cross-session conversation search; subagent and review results land back into it. |
+| **Subagents & orchestration** | Local-first subagent registry (subagents inherit your session model — no cloud defaults), parallel delegation, and workflow scripting. |
+| **Browser automation** | agent-browser + Chrome for Testing — navigation, form interaction, screenshots, vitals, accessibility checks, structured validation reports. |
+| **Web research** | Exa MCP (search + content fetch) and Context7 (version-specific library docs) as on-demand tools for the agent. |
+| **Web editor** | VSCodium over the OpenVSCode protocol — edit in any browser, token printed per launch (or pinned via `.env`). |
+| **Guided setup & health** | Interactive setup wizard on first run (server, key, model, MCP, memory) and `lpb doctor` / `lpb-config check` read-only validation, any time. |
+| **Multi-project & persistent** | One container per project; agent state, sessions, and memory survive image rebuilds; `lpb --update` self-updates launcher + image. |
+| **Reproducible releases** | Manual versioning, stable tags, a versioned docs site — every capability above is documented at its release version. |
+
 ## Quick Start
 
 ### 1. Install the launcher (once)
@@ -73,7 +93,7 @@ lpb --help       # full usage
 | **VSCodium** | Web-based editor (`:web` image), connects over the OpenVSCode protocol |
 | **lemonade-pi-plugin** (forked) | Model provider for the local **Lemonade** server — Qwen thinking + vision support |
 | **lpb-memory** | Persistent memory + session search for the agent |
-| **pi-subagents** (forked) | Local-first subagent model registry (no hardcoded cloud models) |
+| **pi-subagents** | Subagent model registry — upstream `tintinweb/pi-subagents` installed via npm (no hardcoded cloud models) |
 | **agent-browser** + Chrome | Browser automation tools for the agent |
 | **MCP servers** | Exa (web search), Context7 (library docs), agent-browser |
 | **Lemonade** (host prerequisite) | Local model server — AMD/Strix Halo-optimized, serves GGUF models; on this host or any reachable host; model chosen by the user at setup (no default) |
@@ -199,9 +219,10 @@ flowchart TB
 
 ## Forked Repos & Upstream Policy
 
-Pi itself is no longer a fork: the image installs mainstream pi from the
-npm registry at `LPB_PI_VERSION` (the `lpb-stack/pi` fork is retired — see
-[Fork improvements](doc/fork-improvements.md) for the retirement note).
+Pi itself is not a repo: the image installs mainstream pi from the npm
+registry at `LPB_PI_VERSION`. The only fork is `lemonade-pi-plugin`; retired
+forks and the full repo map are in
+[Repositories & Customizations](doc/fork-improvements.md).
 
 The remaining fork URLs and branches are tracked in `lpb.stack.env` at the
 repo root. Each fork keeps its LocalPibox work as clean commits on top of
@@ -211,7 +232,7 @@ patch.
 | Repo | Upstream | LocalPibox work | Update policy |
 |---|---|---|---|
 | **lemonade-pi-plugin** | `lemonade-sdk/lemonade-pi-plugin` (no stable release) | Qwen thinking + vision support | follow upstream `main`, check periodically |
-| **pi-subagents** | `tintinweb/pi-subagents` (v0.16.1) | centralized local-first subagent model registry | follow upstream; merge + repair as needed |
+| **pi-subagents** | `tintinweb/pi-subagents` (upstream, npm) | installed from upstream npm — no local fork; subagent model registry | track upstream releases |
 | **lpb-memory** | *(independent project)* | Pi memory extension (subprocess reviews) | no upstream to track |
 | **config** / **devstack** | — | own | own |
 
@@ -238,7 +259,7 @@ GitHub Actions (`.github/workflows/build-and-publish.yml`) runs on:
 Versioning is **manual**: `lpb-devstack bump` commits a new `VERSION`, and CI
 builds + tags only when VERSION changed in the pushed commit. Pipeline jobs:
 **VERSION check** → **test** (always) → **build & publish images** →
-**tag repos** (CI tags the other 4 stack repos on their pipeline branches) →
+**tag repos** (CI tags the other 3 stack repos on their pipeline branches) →
 **docs publish** (main pipeline only — publishes the stable docs version,
 gated on the docs being flagged ready via `lpb-devstack release docs-ready`
 before promotion) → **status**. Devstack itself is tracked by its `VERSION`
@@ -315,5 +336,5 @@ devstack/
 - [lpb-stack/pi](https://github.com/lpb-stack/pi) — retired pi fork (reference only; last state `pre-defork-0.0.71`)
 - [lpb-stack/config](https://github.com/lpb-stack/config) — agent config preset
 - [lpb-stack/lemonade-pi-plugin](https://github.com/lpb-stack/lemonade-pi-plugin) — Lemonade provider plugin
-- [lpb-stack/pi-subagents](https://github.com/lpb-stack/pi-subagents) — subagent model registry
+- [tintinweb/pi-subagents](https://github.com/tintinweb/pi-subagents) — subagent model registry (upstream, installed via npm; the `lpb-stack/pi-subagents` fork is retired)
 - [lpb-stack/lpb-memory](https://github.com/lpb-stack/lpb-memory) — persistent memory extension

VERSION

@@ -1 +1 @@
-0.0.77-lpb
+0.0.83-lpb-dev

doc/config-repo.md

@@ -58,16 +58,18 @@ The settings file is **template-driven**, not git-tracked:
 
 ### Example pin format
 
-Extensions are pinned in the `packages` array of `settings.json` as
-`git:<owner>/<repo>@<stack-tag>` strings:
+Extensions are pinned in the `packages` array of `settings.json`. Git forks
+use `git:<owner>/<repo>@<stack-tag>` (version-tracked by the stack); npm
+packages use a bare `npm:<pkg>` specifier with **no version** so pi can
+update them via `pi update --extensions`:
 
 ```json
 {
   "packages": [
     "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",
     "npm:pi-powerline-footer",
     "@upstash/context7-mcp"
   ]
@@ -104,9 +106,11 @@ runtime via `pi update --extensions`.
 | Directory | Repo | Role |
 |---|---|---|
 | `lpb-memory/` | `lpb-stack/lpb-memory` | Persistent memory extension |
-| `pi-subagents/` | `lpb-stack/pi-subagents` | Subagent model registry |
 | `lemonade-pi-plugin/` | `lpb-stack/lemonade-pi-plugin` | Lemonade provider plugin |
 
+`pi-subagents` is not here — it de-forked to the upstream npm package
+(installed by pi from the npm registry, not a git clone under `git/`).
+
 ## Runtime State: lpb-memory Dir
 
 The directory `~/.pi/agent/lpb-memory/` holds **runtime state** for the