@expert-council/pi-package 0.5.3 → 0.5.4

package/README.md

@@ -17,7 +17,7 @@ In practice, the theoretically strongest model is not automatically the best exe
 
 ## Current status
 
-The current release (0.5.3) includes:
+The current release (0.5.4) includes:
 
 - A host-independent Core: configuration validation, model normalization, billing policy, profile layering, role scoring, task classification, dynamic team sizing, retry/escalation, and telemetry aggregation.
 - An execution runtime built on Pi's current `ModelRuntime` and `createAgentSession` APIs.
@@ -100,11 +100,11 @@ pi update npm:@expert-council/pi-package
 To run Codex as the Main Agent, install the pinned prebuilt plugin directly from its Git marketplace; no repository clone or local build is required:
 
 ```bash
-codex plugin marketplace add Labiey/expert-council-router --ref v0.5.3 --json
+codex plugin marketplace add Labiey/expert-council-router --ref v0.5.4 --json
 codex plugin add expert-council@expert-council-router --json
 ```
 
-Fully restart Codex Desktop after installation. See [Codex plugin](#codex-plugin) for Windows CLI discovery, verification, upgrade, and removal instructions.
+Fully restart Codex Desktop after installation. The plugin ships its own tested Pi SDK runtime, so the globally installed `pi` package is not used at runtime; Pi still must have been installed and configured once — or provider credentials placed manually under `~/.pi` — so the account and model catalog are available. See [Codex plugin](#codex-plugin) for Windows CLI discovery, verification, upgrade, and removal instructions.
 
 ### Build from source (development)
 
@@ -493,7 +493,7 @@ packages/codex-integration/plugin/expert-council/
 Release `v0.5.2` includes both the prebuilt MCP server and its tested Pi SDK runtime, so Codex can install the plugin directly from the repository as a pinned Git marketplace. Node.js 22.19 or newer and an already configured Pi account/model catalog are required; cloning this repository, running `npm install`, or resolving a global `@earendil-works/pi-coding-agent` module is not required.
 
 ```bash
-codex plugin marketplace add Labiey/expert-council-router --ref v0.5.3 --json
+codex plugin marketplace add Labiey/expert-council-router --ref v0.5.4 --json
 codex plugin marketplace list --json
 codex plugin list --marketplace expert-council-router --available --json
 codex plugin add expert-council@expert-council-router --json
@@ -519,7 +519,7 @@ if (-not $ecCodex) {
 }
 if (-not $ecCodex) { throw "Codex Desktop CLI was not found." }
 
-& $ecCodex plugin marketplace add Labiey/expert-council-router --ref v0.5.3 --json
+& $ecCodex plugin marketplace add Labiey/expert-council-router --ref v0.5.4 --json
 & $ecCodex plugin marketplace list --json
 & $ecCodex plugin list --marketplace expert-council-router --available --json
 & $ecCodex plugin add "expert-council@expert-council-router" --json
@@ -530,7 +530,7 @@ Fully quit Codex Desktop, wait for its backend process to exit, reopen it, and s
 
 For local plugin development, clone the repository, run `npm ci && npm run build`, and pass its absolute root to `codex plugin marketplace add` instead of the GitHub repository name. The pinned remote release is recommended for normal use.
 
-A correct load exposes the `expert-council` Skill and all nine `expert_*` MCP tools. `expert_inspect` must return a real inventory rather than a "No compatible Pi SDK is installed" diagnostic. If the Skill is present but the tools are absent, or inspection reports that diagnostic, verify that the marketplace is pinned to `v0.5.3` or newer, then restart or reinstall the plugin instead of launching `dist/server.mjs` manually or sending hand-written JSON-RPC.
+A correct load exposes the `expert-council` Skill and all nine `expert_*` MCP tools. `expert_inspect` must return a real inventory rather than a "No compatible Pi SDK is installed" diagnostic. If the Skill is present but the tools are absent, or inspection reports that diagnostic, verify that the marketplace is pinned to `v0.5.4` or newer, then restart or reinstall the plugin instead of launching `dist/server.mjs` manually or sending hand-written JSON-RPC.
 
 To verify the installed workflow, use a new Codex task and ask:
 
@@ -570,7 +570,64 @@ codex plugin list --json
 codex plugin marketplace list --json
 ```
 
-On Windows, replace `codex` with `& $ecCodex` when using the PowerShell variable above. Fully quit Codex Desktop before starting new tasks.
+If PowerShell cannot find `codex`, locate the Codex Desktop CLI first (while Codex Desktop is running its path can be taken from the process; otherwise fall back to the install directory):
+
+```powershell
+$ecCodex = Get-Process codex -ErrorAction SilentlyContinue |
+    Where-Object Path |
+    Select-Object -First 1 -ExpandProperty Path
+
+if (-not $ecCodex) {
+    $ecCodex = Get-ChildItem (Join-Path $env:LOCALAPPDATA "OpenAI\Codex") `
+        -Filter codex.exe -File -Recurse -ErrorAction SilentlyContinue |
+        Sort-Object LastWriteTime -Descending |
+        Select-Object -First 1 -ExpandProperty FullName
+}
+
+if (-not $ecCodex) {
+    throw "Codex Desktop's codex.exe was not found."
+}
+```
+
+Then uninstall through the located CLI:
+
+```powershell
+& $ecCodex plugin remove "expert-council@expert-council-router" --json
+& $ecCodex plugin marketplace remove "expert-council-router" --json
+
+& $ecCodex plugin list --json
+& $ecCodex plugin marketplace list --json
+```
+
+If the plugin still shows after reopening Codex Desktop, close Codex and safely remove the stale Expert Council caches (only `%USERPROFILE%\.codex\plugins\cache\expert-council-*` is touched):
+
+```powershell
+$ecCacheRoot = [IO.Path]::GetFullPath(
+    (Join-Path $env:USERPROFILE ".codex\plugins\cache")
+)
+$ecCachePrefix = $ecCacheRoot.TrimEnd("\") + "\"
+
+$ecTargets = Get-ChildItem -LiteralPath $ecCacheRoot `
+    -Directory -ErrorAction SilentlyContinue |
+    Where-Object Name -Like "expert-council-*"
+
+foreach ($ecTarget in $ecTargets) {
+    $ecResolved = [IO.Path]::GetFullPath($ecTarget.FullName)
+
+    if (
+        $ecResolved.StartsWith(
+            $ecCachePrefix,
+            [StringComparison]::OrdinalIgnoreCase
+        ) -and
+        (Split-Path $ecResolved -Leaf) -like "expert-council-*"
+    ) {
+        Write-Host "Removing cache: $ecResolved"
+        Remove-Item -LiteralPath $ecResolved -Recurse -Force
+    }
+}
+```
+
+Fully quit Codex Desktop before starting new tasks.
 
 ## Testing
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@expert-council/pi-package",
-  "version": "0.5.3",
-  "description": "Native Pi package exposing Expert Council tools and host guidance",
+  "version": "0.5.4",
+  "description": "Expert Council: cost-aware multi-model expert orchestration for Pi — assemble a council of scout, oracle, implementation-worker, and reviewer experts and delegate bounded tasks",
   "type": "module",
   "main": "./dist/extension.js",
   "types": "./dist/extension.d.ts",
@@ -23,8 +23,14 @@
   },
   "keywords": [
     "pi-package",
+    "pi-extension",
+    "expert-council",
+    "council",
+    "multi-agent",
+    "agent-orchestration",
     "multi-model",
-    "orchestration"
+    "codex",
+    "mcp"
   ],
   "publishConfig": {
     "access": "public"
@@ -38,8 +44,8 @@
     ]
   },
   "dependencies": {
-    "@expert-council/core": "0.5.3",
-    "@expert-council/pi-runtime": "0.5.3"
+    "@expert-council/core": "0.5.4",
+    "@expert-council/pi-runtime": "0.5.4"
   },
   "peerDependencies": {
     "@earendil-works/pi-coding-agent": ">=0.84.0 <1",