@expert-council/pi-package 0.5.0 → 0.5.3

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.0) includes:
+The current release (0.5.3) 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.
@@ -29,7 +29,7 @@ The current release (0.5.0) includes:
 - Runtime availability markers: when a call fails with dead-model evidence, the model is recorded into the persisted assessment and hard-rejected by later council building, delegation, and escalation; markers expire and are retried automatically after 24 hours.
 - Provider session error surfacing: upstream denials such as `403 AccessDenied` are no longer swallowed; they return to the Main Agent with the real diagnostic and the correct failure class.
 - Cross-process shared model assessment: with multiple instances running in parallel, availability markers become visible to each other without a restart.
-- A Codex plugin with the shared Skill and a bundled stdio MCP Server, using Codex's host-owned `codex/sandbox-state-meta` capability for workspace discovery (no hooks).
+- A self-contained Codex plugin with the shared Skill, stdio MCP Server, and tested Pi SDK runtime, using Codex's host-owned `codex/sandbox-state-meta` capability for workspace discovery (no hooks or global SDK lookup).
 - Deterministic automated tests that never consume model quota.
 
 ## Architecture
@@ -97,7 +97,14 @@ pi update npm:@expert-council/pi-package
 
 ### Install the Codex plugin (optional)
 
-To run Codex as the Main Agent, build the repository and install the bundled plugin through a Codex plugin marketplace — see [Codex plugin](#codex-plugin) for the full walkthrough.
+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 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.
 
 ### Build from source (development)
 
@@ -478,16 +485,73 @@ packages/codex-integration/plugin/expert-council/
   skills/expert-council/SKILL.md
   dist/server.mjs
   dist/roles/*.md
+  THIRD_PARTY_NOTICES.md
 ```
 
 ### Installation
 
-1. Build from a repository checkout: `npm install && npm run build`.
-2. Expose the plugin directory through a personal or repository plugin marketplace as documented by the current [OpenAI plugin packaging guide](https://developers.openai.com/plugins/build/plugins). This repository does not write marketplace files automatically, because that would change user or team Codex configuration.
-3. Install the plugin from your marketplace in Codex. After every install or reinstall, fully quit Codex Desktop, wait for its backend process to exit, and reopen the app — merely opening a new task is not a reliable MCP reload boundary in every Desktop build.
-4. When upgrading, bump the marketplace cachebuster and remove obsolete test installations first; installing multiple copies that all declare the `expert_council` MCP server makes host diagnostics ambiguous.
+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 list --json
+codex plugin list --marketplace expert-council-router --available --json
+codex plugin add expert-council@expert-council-router --json
+codex plugin list --json
+```
+
+`marketplace add` is needed only once for this release. If the marketplace name is already registered from an older or local source, remove that source first or follow the upgrade procedure below. `plugin list --json` should show `expert-council` as installed from `expert-council-router`.
+
+Codex Desktop on Windows includes the CLI, but it may not be on `PATH`. In PowerShell, resolve the running Desktop binary and use it for the same remote installation:
+
+```powershell
+$ecCodex = (Get-Command codex.exe -ErrorAction SilentlyContinue).Source
+if (-not $ecCodex) {
+    $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/bin") `
+        -Filter codex.exe -File -Recurse -ErrorAction SilentlyContinue |
+        Sort-Object LastWriteTime -Descending |
+        Select-Object -First 1 -ExpandProperty FullName
+}
+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 list --json
+& $ecCodex plugin list --marketplace expert-council-router --available --json
+& $ecCodex plugin add "expert-council@expert-council-router" --json
+& $ecCodex plugin list --json
+```
+
+Fully quit Codex Desktop, wait for its backend process to exit, reopen it, and start a new task. Merely opening another task is not a reliable MCP reload boundary in every Desktop build.
 
-A correct load exposes the `expert-council` Skill and all nine `expert_*` MCP tools. If the Skill is present but the tools are absent, treat the installation as failed: restart or reinstall the plugin instead of launching `dist/server.mjs` manually or sending hand-written JSON-RPC.
+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.
+
+To verify the installed workflow, use a new Codex task and ask:
+
+```text
+Use Expert Council to inspect the currently available Pi models, providers, billing classification, and model-assessment status. Return only a compact summary; do not build a council or delegate experts.
+```
+
+The task should invoke `expert_inspect`. It should not ask for hook trust, manually launch the MCP server, or treat the plugin cache as the project workspace.
+
+### Upgrade
+
+A marketplace pinned with `--ref` intentionally stays on that release. To upgrade, remove the installed plugin and old marketplace registration, then add the new tag and reinstall:
+
+```bash
+codex plugin remove expert-council@expert-council-router --json
+codex plugin marketplace remove expert-council-router --json
+codex plugin marketplace add Labiey/expert-council-router --ref vX.Y.Z --json
+codex plugin add expert-council@expert-council-router --json
+```
+
+Replace `vX.Y.Z` with the intended release. Users who deliberately track the default branch can omit `--ref` and later run `codex plugin marketplace upgrade expert-council-router --json`, but pinned tags are safer for normal use. After reinstalling, fully restart Codex Desktop and test in a new task. Avoid installing multiple copies that all declare the `expert_council` MCP server.
 
 ### Behavior highlights
 
@@ -497,7 +561,16 @@ A correct load exposes the `expert-council` Skill and all nine `expert_*` MCP to
 
 ### Removal
 
-Remove the plugin from Codex's plugin settings, then fully quit Codex Desktop before starting new tasks.
+Remove the plugin and its marketplace registration:
+
+```bash
+codex plugin remove expert-council@expert-council-router --json
+codex plugin marketplace remove expert-council-router --json
+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.
 
 ## Testing
 

package/package.json

@@ -1,24 +1,45 @@
 {
   "name": "@expert-council/pi-package",
-  "version": "0.5.0",
+  "version": "0.5.3",
   "description": "Native Pi package exposing Expert Council tools and host guidance",
   "type": "module",
   "main": "./dist/extension.js",
   "types": "./dist/extension.d.ts",
-  "files": ["dist", "skills", "README.md", "LICENSE"],
+  "files": [
+    "dist",
+    "skills",
+    "README.md",
+    "LICENSE"
+  ],
   "license": "MIT",
-  "repository": { "type": "git", "url": "git+https://github.com/Labiey/expert-council-router.git", "directory": "packages/pi-package" },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Labiey/expert-council-router.git",
+    "directory": "packages/pi-package"
+  },
   "homepage": "https://github.com/Labiey/expert-council-router#readme",
-  "bugs": { "url": "https://github.com/Labiey/expert-council-router/issues" },
-  "keywords": ["pi-package", "multi-model", "orchestration"],
-  "publishConfig": { "access": "public" },
+  "bugs": {
+    "url": "https://github.com/Labiey/expert-council-router/issues"
+  },
+  "keywords": [
+    "pi-package",
+    "multi-model",
+    "orchestration"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
   "pi": {
-    "extensions": ["./dist/extension.js"],
-    "skills": ["./skills"]
+    "extensions": [
+      "./dist/extension.js"
+    ],
+    "skills": [
+      "./skills"
+    ]
   },
   "dependencies": {
-    "@expert-council/core": "0.5.0",
-    "@expert-council/pi-runtime": "0.5.0"
+    "@expert-council/core": "0.5.3",
+    "@expert-council/pi-runtime": "0.5.3"
   },
   "peerDependencies": {
     "@earendil-works/pi-coding-agent": ">=0.84.0 <1",