@evref-bl/pharo-agent 0.3.10 → 0.4.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "pharo-agent",
   "displayName": "Pharo Agent",
-  "version": "0.3.10",
+  "version": "0.4.0",
   "description": "Terminal-first Pharo image setup for coding agents.",
   "author": {
     "name": "Evref-BL",

package/README.md

@@ -26,27 +26,32 @@ pharo-agent image add dev --template 'Pharo 13.0 - 64bit (stable)'
 ```
 
 `image add` registers a template-created image with the pinned MCP load policy,
-and the first one registered becomes the default. `image list`,
-`image use <id>` (change the default) and `image remove <id>` cover the rest;
-an open image must be closed before its declaration is removed.
+and the first one registered becomes the default. Pass `--profile <id>` to put
+it under a particular launcher profile. `image list`, `image use <id>` (change
+the default) and `image remove <id>` cover the rest; an open image must be
+closed before its declaration is removed.
 
 `open` starts an image through PLexus, loads PIFS, and mounts its projection
 below `.pharo-agent/mounts`. `close` unmounts the projection and closes the
-PLexus image. `pharo` calls any exposed MCP tool through the same project
-route, while `mcp` exposes that tool surface as a command-scoped stdio MCP
+PLexus image. `pharo <tool> [arguments-json]` calls any exposed MCP tool
+through the same project route and `pharo list` names the tools an image
+offers, while `mcp` exposes that tool surface as a command-scoped stdio MCP
 server.
 
-Several images can be open at once. `open`, `close`, `status`, `pharo` and
-`mcp` all accept `--image <id>`; without it the default image answers, so a
-project with one image never mentions an image at all. `open --image <id>`
-adds an image without closing the others, and `close` without `--image` closes
-every image this project opened. Over `mcp`, each Pharo tool takes the same
-optional `image` argument.
+Several images can be open at once. `open`, `close`, `pharo` and `mcp` accept
+`--image <id>`; without it the default image answers, so a project with one
+image never mentions an image at all. `open --image <id>` adds an image
+without closing the others, and `close` without `--image` closes every image
+this project opened. `status` takes no `--image`, because it reports every
+open image and which one is the default. Over `mcp`, each Pharo tool takes the
+same optional `image` argument.
 
 Pass `--mount-root <path>` to `init` to use a different projection root.
 
 ## Requirements
 
+Node 22.12 or later.
+
 PIFS currently supports the macOS workflow and needs
 [fuse-t](https://www.fuse-t.org/). Its matching daemon is downloaded by PIFS;
 Go is not required at runtime.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@evref-bl/pharo-agent",
-  "version": "0.3.10",
+  "version": "0.4.0",
   "private": false,
   "description": "Terminal-first Pharo integration for coding agents.",
   "license": "Apache-2.0",
@@ -31,9 +31,9 @@
     "test": "node --test"
   },
   "dependencies": {
-    "@evref-bl/pharo-mcp": "1.5.1",
-    "@evref-bl/plexus": "0.4.8",
-    "@evref-bl/plexus-gateway": "0.4.8",
+    "@evref-bl/pharo-mcp": "2.0.0",
+    "@evref-bl/plexus": "0.5.1",
+    "@evref-bl/plexus-gateway": "0.5.1",
     "@modelcontextprotocol/sdk": "1.32.1"
   }
 }

package/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "pharo-agent",
-  "version": "0.3.10",
+  "version": "0.4.0",
   "description": "Terminal-first Pharo image setup for coding agents.",
   "author": {
     "name": "Evref-BL",

package/skills/pharo-setup/SKILL.md

@@ -8,7 +8,7 @@ Run this only when the user asks to enable Pharo tooling in this project.
 From the project root, run the released CLI that matches this plugin:
 
 ```sh
-npx --yes @evref-bl/pharo-agent@0.3.10 init --host codex
+npx --yes @evref-bl/pharo-agent@0.4.0 init --host codex
 ```
 
 Use `--host claude` in Claude Code and `--host opencode` in OpenCode.

package/src/cli.js

@@ -146,6 +146,9 @@ export async function main(args) {
   }
   if (command === "status") {
     requireNoArguments(command, commandArgs);
+    if (image) {
+      throw new Error("status reports every open image and does not accept --image");
+    }
     console.log(JSON.stringify({ ok: true, ...agentImageStatus(projectRoot) }, null, 2));
     return;
   }

package/src/live.js

@@ -21,7 +21,13 @@ import {
   writeOpenImages,
 } from "./runtime.js";
 
-export const pifsRelease = "v0.4.1";
+export const pifsRelease = "v0.6.0";
+
+// The class-side PIFSServer messages this plugin sends into the image. The
+// release automation checks that a published PIFS still implements them: a pin
+// bump that leaves a removed selector in place passes every test here, because
+// the tests read generated source, and fails only in a live image.
+export const pifsSelectors = ["startMountedAt:named:", "stopOn:"];
 
 export function pifsStartCode(mountPath, imageName) {
   return `Metacello new
@@ -29,11 +35,14 @@ export function pifsStartCode(mountPath, imageName) {
 	repository: 'github://Evref-BL/pharo-image-fs:${pifsRelease}/src';
 	load: 'Core'.
 ((Smalltalk globals at: #PIFSServer)
-	startOn: 0
-	mountAt: ${smalltalkString(mountPath)} asFileReference
+	startMountedAt: ${smalltalkString(mountPath)} asFileReference
 	named: ${smalltalkString(imageName)}) port`;
 }
 
+export function pifsStopCode(projectionPort) {
+  return `(Smalltalk globals at: #PIFSServer) stopOn: ${projectionPort}`;
+}
+
 export function resultPrintString(result) {
   // MCP tool results carry the image's answer as JSON inside a text content part.
   if (typeof result === "string") {
@@ -200,7 +209,7 @@ async function closeOneImage(projectRoot, openImages, imageId) {
   let projectionError;
   try {
     await callImageTool(projectRoot, open, "image_evaluate", {
-      code: `(Smalltalk globals at: #PIFSServer) stopOn: ${open.projectionPort}`,
+      code: pifsStopCode(open.projectionPort),
     });
   } catch (error) {
     projectionError = error;