@evref-bl/pharo-agent 0.14.0 → 0.15.0

package/.claude-plugin/plugin.json

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

package/README.md

@@ -87,6 +87,12 @@ Pharo work only, so Pharo instructions stay out of unrelated chats. The guide
 and what it refers to are maintained by the MCP project and copied from the
 release this plugin pins. [Hosts](docs/hosts.md) lists the paths it owns.
 
+**A way to report what got in its way.** The plugin's feedback skill has the
+agent look back over the conversation for tool calls that failed, misled it or
+needed a workaround, and draft issues for the tools' maintainers. It offers
+itself at the end of Pharo work where that happened, searches for existing
+issues first, and files only the drafts you approve.
+
 ## Refreshing after an upgrade
 
 Upgrade the plugin the way you installed it, then run the setup command again

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@evref-bl/pharo-agent",
-  "version": "0.14.0",
+  "version": "0.15.0",
   "private": false,
   "description": "Terminal-first Pharo integration for coding agents.",
   "license": "Apache-2.0",
@@ -32,8 +32,8 @@
     "test": "node --test"
   },
   "dependencies": {
-    "@evref-bl/pharo-mcp": "3.4.0",
-    "@evref-bl/plexus": "0.13.0",
+    "@evref-bl/pharo-mcp": "3.4.1",
+    "@evref-bl/plexus": "0.14.1",
     "@modelcontextprotocol/sdk": "1.32.2"
   },
   "devDependencies": {

package/plugin.json

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

package/skills/pharo-feedback/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: pharo-feedback
+description: Look back on how the Pharo tools served this conversation and propose GitHub issues for what failed, misled you or was missing. Use when the user asks for feedback on the Pharo tools or wants to report a problem with them. At the end of Pharo work in which a tool failed, misled you or needed a workaround, offer it once; never file anything unasked.
+---
+
+# Pharo tool feedback
+
+The Pharo tools improve from what their users run into, and you saw this
+conversation's tool calls more closely than anyone. Turn what got in your way
+into issues the maintainers can act on. Issues are public: file only what the
+user approves.
+
+## Look back
+
+Go over this conversation's calls to the Pharo tools, whether through this
+plugin's MCP tools or the `pharo-agent` command, and keep what the tools did
+wrong:
+
+- a call failed with an error you could not have avoided: an internal error, a
+  Smalltalk exception, a timeout;
+- a call failed on your input, and its description, schema or error message
+  led you there or did not say what was wrong;
+- a search missed a tool that existed, or found it only after several tries;
+- an answer was wrong, partial, too large to use, or said less than you needed;
+- a warning or the Pharo guidance sent you the wrong way;
+- you fell back to `image_evaluate`, a shell or the files because no tool did
+  what you needed;
+- one step took several attempts.
+
+Leave out your own slips that a clear error caught, bugs in the user's project,
+and passing trouble such as a network outage, unless the tool handled it badly.
+If the conversation was summarized, say what you can no longer see rather than
+reconstruct it.
+
+Then ask the user whether a tool got in their way in a way you did not notice.
+
+## Where each one goes
+
+- The image's own tools, from classes, methods and tests to repositories,
+  search and evaluation, and the Pharo guidance copied into the project
+  (`pharo.AGENTS.md`, the `pharo-*` skills and references): `Evref-BL/MCP`.
+- Everything else this plugin brings, such as the `image_*` tools, the source
+  projection, setup, the `pharo-agent` command and the passing of calls between
+  the host and an image: `Evref-BL/pharo-agent-plugin`. Its maintainers move an
+  issue to the component that owns it.
+
+When the project loads an MCP of its own into the image, that project answers
+for the image's tools.
+
+## Before proposing
+
+Look for the same problem among each repository's issues, open and closed:
+
+```sh
+gh issue list --repo Evref-BL/MCP --state all --search "<words>"
+```
+
+Where one exists, propose a comment adding what this conversation showed
+instead of a new issue.
+
+## Drafting
+
+One issue per problem; findings that share a cause make one issue. Title it
+with what goes wrong, in the tool's own terms. Keep the body short:
+
+- **Tool:** its name; `pharo-agent 0.15.0`; the image's Pharo version, which
+  `image_list` gives; the host you run in.
+- **What happened:** what you asked for and what came back, the error quoted
+  and trimmed.
+- **Expected:** what would have served.
+- **Workaround:** what worked instead, or none.
+- **To reproduce:** the smallest call that shows it.
+
+End with: "Reported through the pharo-agent feedback skill."
+
+Issues are public. Leave out the project's code, class and package names,
+paths, URLs, and anything that identifies the user or their organization.
+Reproduce on Pharo's own classes, such as `Object` or `OrderedCollection`, or
+describe the shape of what you had. When a problem cannot be shown without the
+project's material, say so and let the user decide.
+
+## Propose, then file
+
+Show every draft in full, with its repository, and ask which to file. File only
+those the user names:
+
+```sh
+gh issue create --repo Evref-BL/MCP --title "<title>" --body-file <draft>
+```
+
+Without `gh` or its login, give each draft as a link that opens the form
+already filled, `https://github.com/<owner>/<repo>/issues/new?title=…&body=…`
+with both values URL-encoded, and let the user submit it. A comment on an
+existing issue goes the same way.
+
+Report what was filed, with its link.

package/skills/pharo-setup/SKILL.md

@@ -8,7 +8,7 @@ Run this only when the user asks to enable or refresh Pharo tooling in this proj
 From the project root, run the released CLI that matches this plugin:
 
 ```sh
-npx --yes @evref-bl/pharo-agent@0.14.0 init --host claude
+npx --yes @evref-bl/pharo-agent@0.15.0 init --host claude
 ```
 
 Name the host this chat runs in: `--host claude` in Claude Code,

package/src/live.js

@@ -22,7 +22,7 @@ import {
   writeRunningImages,
 } from "./runtime.js";
 
-export const pifsRelease = "v0.10.1";
+export const pifsRelease = "v0.10.2";
 
 // fuse-t ships as a macOS installer package, so it lands in /usr/local
 // whatever Homebrew's prefix is. The unversioned symlink is what the daemon

package/src/runtime.js

@@ -166,8 +166,21 @@ export function selectRunningImage(state, imageId) {
 // is a supported way to run — it is what the policy is for — but nothing said
 // so, and the image's tools then quietly differ from the ones the project was
 // written against. PLexus records it; this says it.
+//
+// An image copied from a home image cache base is another matter: PLexus keys
+// a base on what preparing it loaded and says whether that is still what the
+// project loads. A `current` base holds the project's own MCP, and warning
+// about it told every new image the opposite of what happened; an `outdated`
+// one certainly holds another. Only an image nobody can vouch for gets the
+// hedged warning.
 export function unappliedPharoMcpPin(image) {
-  if (image?.pharoMcpLoad?.state !== "provided") return undefined;
+  const load = image?.pharoMcpLoad;
+  if (load?.state !== "provided" || load.preparedBase === "current") return undefined;
+  if (load.preparedBase === "outdated") {
+    return `Image ${image.id} kept the Pharo MCP it was prepared with, which is not the one this project`
+      + " loads now, so its tools may differ from the ones this project expects."
+      + " Recreate the image, or set mcp.loadPolicy to always.";
+  }
   return `Image ${image.id} started with the Pharo MCP it already had, so the version this project pins`
     + " was not loaded and its tools may differ from the ones this project expects."
     + " Recreate the image, or set mcp.loadPolicy to always.";