@evref-bl/pharo-mcp 3.5.0 → 3.7.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +3 -3
  2. package/package.json +1 -1
  3. package/templates/.opencode/opencode.json +2 -1
  4. package/templates/pharo-references/tool-reference.md +3 -1
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # MCP for Pharo
2
2
 
3
- [![Pharo version](https://img.shields.io/badge/Pharo-12%20%7C%2013%20%7C%2014%20%7C%2015-%23aac9ff.svg)](https://github.com/pharo-project/Pharo)
3
+ [![Pharo version](https://img.shields.io/badge/Pharo-10%20%7C%2011%20%7C%2012%20%7C%2013%20%7C%2014%20%7C%2015-%23aac9ff.svg)](https://github.com/pharo-project/Pharo)
4
4
  [![CI](https://github.com/Evref-BL/MCP/actions/workflows/ci.yml/badge.svg?branch=main&event=push)](https://github.com/Evref-BL/MCP/actions/workflows/ci.yml?query=branch%3Amain+event%3Apush)
5
5
  [![Coverage Status](https://coveralls.io/repos/github/Evref-BL/MCP/badge.svg?branch=main)](https://coveralls.io/github/Evref-BL/MCP?branch=main)
6
6
 
@@ -15,7 +15,7 @@ files as plain text.
15
15
 
16
16
  ## Supported Versions
17
17
 
18
- Pharo 12, 13, 14, and 15 are supported.
18
+ Pharo 10, 11, 12, 13, 14, and 15 are supported.
19
19
 
20
20
  Protocol revisions `2025-03-26`, `2025-06-18`, `2025-11-25` and `2026-07-28`
21
21
  are supported, each answered in its own shape.
@@ -94,7 +94,7 @@ installGuidance({ host: "codex", cwd: process.cwd() });
94
94
 
95
95
  ## Contributing
96
96
 
97
- Use Pharo 14 for normal development and preserve Pharo 12, 13 and 15
97
+ Use Pharo 14 for normal development and preserve Pharo 10, 11, 12, 13 and 15
98
98
  compatibility. Live behavior must be verified in an image; source inspection
99
99
  alone is not enough. Start with [AGENTS.md](AGENTS.md) and
100
100
  [MCP verification](docs/mcp-verification.md).
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@evref-bl/pharo-mcp",
3
- "version": "3.5.0",
3
+ "version": "3.7.0",
4
4
  "description": "Pharo MCP agent-host templates",
5
5
  "license": "MIT",
6
6
  "type": "module",
package/templates/.opencode/opencode.json CHANGED
@@ -4,7 +4,8 @@
4
4
  "pharo": {
5
5
  "type": "remote",
6
6
  "url": "http://127.0.0.1:4000",
7
- "enabled": true
7
+ "enabled": true,
8
+ "codemode": false
8
9
  }
9
10
  }
10
11
  }
package/templates/pharo-references/tool-reference.md CHANGED
@@ -119,7 +119,9 @@ the running image; both preview, and perform with `confirm=true`.
119
119
  `image_evaluate` runs arbitrary Smalltalk. Prefer a dedicated tool when one
120
120
  exists: it validates its input and answers structured data. A warning raised
121
121
  while the code runs is printed after the value, so a deprecated method's answer
122
- arrives with the deprecation that qualifies it.
122
+ arrives with the deprecation that qualifies it, and so is what the code wrote to
123
+ the Transcript. As in a Playground, a lowercase name the code assigns without
124
+ declaring is a variable of that one call; a name it only reads stays undeclared.
123
125
 
124
126
  Compiling is the case that bites. Method source separates lines with CR, and
125
127
  `method_compile` normalizes what it is given, while a bare `compile:` from