@evref-bl/pharo-mcp 1.4.1 → 1.5.0

package/README.md

@@ -15,7 +15,7 @@ files as plain text.
 
 ## Supported Versions
 
-Pharo 12, 13, and 14 are supported. Development targets Pharo 13 while CI
+Pharo 12, 13, and 14 are supported. Development targets Pharo 14 while CI
 checks the full matrix.
 
 ## Install And Start
@@ -74,7 +74,7 @@ installGuidance({ host: "codex", cwd: process.cwd() });
 
 ## Contributing
 
-Use Pharo 13 for normal development and preserve Pharo 12/14 compatibility.
+Use Pharo 14 for normal development and preserve Pharo 12/13 compatibility.
 Live behavior must be verified in an image; source inspection alone is not
 enough. Start with [AGENTS.md](AGENTS.md) and
 [MCP verification](docs/mcp-verification.md).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@evref-bl/pharo-mcp",
-  "version": "1.4.1",
+  "version": "1.5.0",
   "description": "Pharo MCP agent-host templates",
   "license": "MIT",
   "type": "module",

package/templates/pharo-references/safety-and-ecosystem.md

@@ -235,22 +235,21 @@ By default, JSON observability exports under the image-local
 `mcp observabilityExportDirectory: aDirectory` to override that export root for
 instance metadata, `logs.jsonl`, `metrics.json`, and `traces.jsonl`.
 
-OpenTelemetry support is optional. Load the `OpenTelemetry` group, then enable
+OpenTelemetry support is optional. Load the `Telemetry` group, then enable
 the OpenTelemetry backend for an MCP instance:
 
 ```smalltalk
 Metacello new
    baseline: 'MCP';
    repository: 'github://Evref-BL/MCP:main/src';
-   load: 'OpenTelemetry'.
+   load: 'Telemetry'.
 
 mcp useOpenTelemetryObservability
 ```
 
 ## Version Compatibility
 
-The core baseline loads PharoCompatibility, JRPC, and PCRE2.
-OpenTelemetry is loaded only by the optional `OpenTelemetry` group. CI covers
-Pharo 12, 13, and 14. Code that depends on version-sensitive Pharo APIs should
-go through PharoCompatibility rather than assuming the Pharo 13 API is present
-everywhere.
+The core baseline loads PharoBackwardCompatibility, JRPC, and PCRE2.
+OpenTelemetry is loaded only by the optional `Telemetry` group. CI covers
+Pharo 12, 13, and 14. Code should target the Pharo 14 API; PharoBackwardCompatibility
+backports supported APIs to older images.

package/templates/pharo-skills/pharo-ci-repro/SKILL.md

@@ -31,7 +31,7 @@ produces logs.
 ```sh
 skills/pharo-ci-repro/scripts/run-smalltalkci-docker.sh \
   --repo /path/to/repo \
-  --platform Pharo64-13 \
+  --platform Pharo64-14 \
   --attempts 3
 ```
 

package/templates/pharo-skills/pharo-ci-repro/scripts/run-smalltalkci-docker.sh

@@ -8,7 +8,7 @@ Usage:
 
 Options:
   --repo DIR          Source repository or working tree to test.
-  --platform NAME    smalltalkCI platform, default Pharo64-13.
+  --platform NAME    smalltalkCI platform, default Pharo64-14.
   --spec FILE        smalltalkCI spec file, default .smalltalk.ston.
   --attempts N       Number of attempts, default 1.
   --out DIR          Scratch/log directory, default /tmp/pharo-ci-repro-<timestamp>.
@@ -24,7 +24,7 @@ USAGE
 }
 
 repo=""
-platform="Pharo64-13"
+platform="Pharo64-14"
 spec=".smalltalk.ston"
 attempts="1"
 out=""

package/templates/pharo-skills/pharo-version-compat/SKILL.md

@@ -1,32 +1,29 @@
 ---
 name: pharo-version-compat
-description: Use PharoCompatibility to load and test a project across supported Pharo versions. Use for missing or renamed Pharo globals, classes, selectors, packages, notices, or semantics; baseline surface selection; and reusable cross-version shims.
+description: Use PharoBackwardCompatibility to load and test a project developed on a later Pharo across supported older versions. Use for missing APIs, selectors, packages, notices, or semantics and reusable upstream backports.
 ---
 
 # Pharo Version Compatibility
 
 ## Model
 
-`PharoCompatibility` handles Pharo-version differences, not library-specific
-workarounds. A project declares the Pharo API surface its source expects; the
-runtime loads the compatibility packages needed by the current image.
+`PharoBackwardCompatibility` backports later Pharo APIs to older supported
+images. Develop against the newest supported Pharo and let the dependency load
+the packages needed by the current image.
 
-Known source surfaces include `Pharo12Surface` and `Pharo13Surface`. Omit a
-surface only when the project needs the core helper API alone.
+It has no source-surface group: load its default baseline.
 
 ## Workflow
 
 1. Read the project baseline, supported-version policy, and CI matrix.
-2. Identify the source Pharo surface and target runtime versions.
-3. Load the matching surface from the project baseline:
+2. Identify the newest source Pharo version and target runtime versions.
+3. Load PBC from the project baseline:
 
 ```smalltalk
 spec
-  baseline: 'PharoCompatibility'
+  baseline: 'PharoBackwardCompatibility'
   with: [
-    spec
-      repository: 'github://Evref-BL/PharoCompatibility:main/src';
-      loads: #( 'Pharo13Surface' ) ]
+    spec repository: 'github://jecisc/PharoBackwardCompatibility:v1.x.x/src' ]
 ```
 
 4. Reproduce on every affected Pharo version and classify the failure: missing
@@ -34,19 +31,19 @@ spec
    native/tooling failure.
 5. Choose the narrowest owner:
    - transparent shim for equivalent APIs;
-   - explicit PharoCompatibility helper for reusable behavior;
+   - an upstream PharoBackwardCompatibility backport for general APIs;
    - project abstraction for irreducible semantic differences;
    - project-local fix for library-specific behavior.
-6. Verify both PharoCompatibility and the consuming project across the matrix.
+6. Verify both PharoBackwardCompatibility and the consuming project across the matrix.
 
-## Extending PharoCompatibility
+## Extending PharoBackwardCompatibility
 
-- Confirm the difference is general and assign it to a source surface and
-  runtime version.
+- Confirm the difference is general, originates in a newer Pharo API, and
+  affects an older supported runtime.
 - Put runtime code in the matching conditional package and baseline group.
 - Use late lookup for optional globals.
-- Keep shims additive when possible and test the compatibility contract, not
-  only package loading.
+- Keep backports additive when possible and test the compatibility contract,
+  not only package loading.
 
 Use `pharo-project-load` for load-path failures and `pharo-ci-repro` for
 smalltalkCI or runner-specific failures.

package/templates/pharo-skills/pharo-version-compat/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "Pharo Version Compatibility"
-  short_description: "Use PharoCompatibility surfaces"
-  default_prompt: "Use $pharo-version-compat to make this Pharo project compatible across supported Pharo versions with PharoCompatibility."
+  short_description: "Use PharoBackwardCompatibility backports"
+  default_prompt: "Use $pharo-version-compat to make this Pharo project compatible across supported Pharo versions with PharoBackwardCompatibility."