procesio-cli 0.1.1__tar.gz → 0.1.2__tar.gz

{procesio_cli-0.1.1 → procesio_cli-0.1.2}/.github/workflows/ci.yml

@@ -51,13 +51,14 @@ jobs:
         if: runner.os == 'Linux'
         run: |
           python - <<'PY'
-          import json, pathlib, subprocess
+          import json, os, pathlib, subprocess
 
           # The plugin pins the PyPI release ("procesio-cli==<version>"), which does not
           # exist yet while its pull request is open, so the checkout stands in for it.
           # Everything else in the command (pins, interpreter choice) runs as shipped.
           cfg = json.loads(pathlib.Path("plugin/.mcp.json").read_text())["mcpServers"]["procesio"]
-          args = [a.replace("${CLAUDE_PLUGIN_ROOT}", "plugin") for a in cfg["args"]]
+          args = list(cfg["args"])
+          plugin_env = {**os.environ, **cfg.get("env", {})}
           release = args[args.index("--from") + 1]
           if not release.startswith("procesio-cli=="):
               raise SystemExit(f"plugin/.mcp.json must pin an exact release, got {release!r}")
@@ -65,16 +66,16 @@ jobs:
           plugin_argv = [cfg["command"]] + args
           request = '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}\n'
 
-          for label, argv in (
-              ("plugin, per plugin/.mcp.json", plugin_argv),
+          for label, argv, env in (
+              ("plugin, per plugin/.mcp.json", plugin_argv, plugin_env),
               ("full registry surface", ["uvx", "--python-preference", "system",
                                          "--python", ">=3.11",
                                          "--from", ".", "--constraints", "constraints.txt",
                                          "--build-constraints", "build-constraints.txt",
-                                         "procesio-mcp"]),
+                                         "procesio-mcp"], None),
           ):
               proc = subprocess.run(argv, input=request, capture_output=True,
-                                    text=True, timeout=600)
+                                    text=True, timeout=600, env=env)
               if proc.returncode != 0:
                   raise SystemExit(f"{label}: exited {proc.returncode}\n{proc.stderr[-2000:]}")
               tools = json.loads(proc.stdout.splitlines()[0])["result"]["tools"]

{procesio_cli-0.1.1 → procesio_cli-0.1.2}/CHANGELOG.md

@@ -9,11 +9,19 @@ there, not here.
 
 ## [Unreleased]
 
+## [0.1.2] - 2026-10-27
+
+### Changed
+- The plugin's launcher is now just `uvx --from procesio-cli==0.1.2 procesio-mcp-chat`.
+  The interpreter preference moved to `UV_PYTHON_PREFERENCE` and `UV_PYTHON` in its
+  environment, and the pin files are no longer passed from the plugin folder: a plugin
+  directory could not verify the version pin through them.
+
 ## [0.1.1] - 2026-10-27
 
 ### Changed
 - The Claude Code plugin moved to `plugin/`. It now installs the exact PyPI release
-  (`uvx --from procesio-cli==0.1.1`) instead of building the repository, ships four
+  (`uvx --from procesio-cli==0.1.2`) instead of building the repository, ships four
   skills and a listing icon, and no longer picks up the repository's agent docs as
   subagents. The marketplace entry points at `./plugin`.
 - First release published to PyPI, so `pip install procesio-cli` and `uvx` work without a

{procesio_cli-0.1.1 → procesio_cli-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: procesio-cli
-Version: 0.1.1
+Version: 0.1.2
 Summary: Command-line tooling and an AI agent for the PROCESIO automation platform: drive processes, forms, documents and custom actions from a terminal or from an AI coding assistant.
 Project-URL: Homepage, https://procesio.com
 Project-URL: Documentation, https://docs.procesio.com
@@ -180,17 +180,19 @@ icon. It launches the exact PyPI release of this package through `uvx`, so
 itself on first run. Authenticate with `add-credential` below, run as
 `uvx --from procesio-cli procesio add-credential ...` when there is no clone.
 
-**What gets installed is pinned.** The plugin names one exact release and passes
-`constraints.txt` and `build-constraints.txt` to `uvx`, so a fresh launch installs exactly the versions that
-were resolved and checked for this release, not whatever is newest on PyPI that day. The
-pins are checked to have prebuilt wheels for Python 3.11 to 3.14 on Windows, Linux
-(x86-64 and ARM) and Apple Silicon. Intel Macs are not covered: `cryptography` no longer
-publishes wheels for them, so installing there needs a Rust toolchain.
+**What gets installed is pinned.** The plugin installs one exact release of `procesio-cli`
+from PyPI, the version this repository was tagged with, and its dependencies resolve
+within the ranges `pyproject.toml` allows. For an install where every package is pinned,
+run from a clone and pass `constraints.txt` and `build-constraints.txt` to `uvx`, as the
+CI does: they hold the versions checked for this release, with prebuilt wheels for
+Python 3.11 to 3.14 on Windows, Linux (x86-64 and ARM) and Apple Silicon. Intel Macs are
+not covered: `cryptography` no longer publishes wheels for them, so installing there
+needs a Rust toolchain.
 
 **On Windows with Smart App Control.** Windows 11 can refuse to load a Python file
 whose publisher it cannot confirm, and shows "Part of this app has been blocked" for
 each one. The Python builds uv downloads for itself are not signed, so the plugin asks
-uv for a Python that is already installed first (`--python-preference system`, never
+uv for a Python that is already installed first (`UV_PYTHON_PREFERENCE=system` in its environment, never
 older than 3.11) and uses uv's own build only when there is none. If
 you see those notifications, install Python 3.11 or newer from
 [python.org](https://www.python.org/downloads/windows/) (for example

{procesio_cli-0.1.1 → procesio_cli-0.1.2}/README.md

@@ -136,17 +136,19 @@ icon. It launches the exact PyPI release of this package through `uvx`, so
 itself on first run. Authenticate with `add-credential` below, run as
 `uvx --from procesio-cli procesio add-credential ...` when there is no clone.
 
-**What gets installed is pinned.** The plugin names one exact release and passes
-`constraints.txt` and `build-constraints.txt` to `uvx`, so a fresh launch installs exactly the versions that
-were resolved and checked for this release, not whatever is newest on PyPI that day. The
-pins are checked to have prebuilt wheels for Python 3.11 to 3.14 on Windows, Linux
-(x86-64 and ARM) and Apple Silicon. Intel Macs are not covered: `cryptography` no longer
-publishes wheels for them, so installing there needs a Rust toolchain.
+**What gets installed is pinned.** The plugin installs one exact release of `procesio-cli`
+from PyPI, the version this repository was tagged with, and its dependencies resolve
+within the ranges `pyproject.toml` allows. For an install where every package is pinned,
+run from a clone and pass `constraints.txt` and `build-constraints.txt` to `uvx`, as the
+CI does: they hold the versions checked for this release, with prebuilt wheels for
+Python 3.11 to 3.14 on Windows, Linux (x86-64 and ARM) and Apple Silicon. Intel Macs are
+not covered: `cryptography` no longer publishes wheels for them, so installing there
+needs a Rust toolchain.
 
 **On Windows with Smart App Control.** Windows 11 can refuse to load a Python file
 whose publisher it cannot confirm, and shows "Part of this app has been blocked" for
 each one. The Python builds uv downloads for itself are not signed, so the plugin asks
-uv for a Python that is already installed first (`--python-preference system`, never
+uv for a Python that is already installed first (`UV_PYTHON_PREFERENCE=system` in its environment, never
 older than 3.11) and uses uv's own build only when there is none. If
 you see those notifications, install Python 3.11 or newer from
 [python.org](https://www.python.org/downloads/windows/) (for example

{procesio_cli-0.1.1 → procesio_cli-0.1.2}/mcpb/manifest.json

@@ -2,7 +2,7 @@
   "manifest_version": "0.4",
   "name": "procesio",
   "display_name": "PROCESIO",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Lets your own AI assistant build, run, validate and audit PROCESIO processes, forms and documents.",
   "long_description": "procesio-cli is a command-line tool and MCP server for the PROCESIO automation platform. With it, your own AI assistant can build, run, validate and audit PROCESIO processes, forms and documents, from a terminal or over MCP. Open source, Apache-2.0 licence. Source: https://github.com/Procesio-Externals/procesio-cli. Docs: https://docs.procesio.com",
   "author": {

{procesio_cli-0.1.1 → procesio_cli-0.1.2}/plugin/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "procesio",
   "displayName": "PROCESIO",
   "description": "Lets your own AI assistant build, run, validate and audit PROCESIO processes, forms and documents.",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "author": {
     "name": "Ringhel TEAM SRL (PROCESIO)",
     "url": "https://procesio.com"

procesio_cli-0.1.2/plugin/.mcp.json

@@ -0,0 +1,16 @@
+{
+  "mcpServers": {
+    "procesio": {
+      "command": "uvx",
+      "args": [
+        "--from",
+        "procesio-cli==0.1.2",
+        "procesio-mcp-chat"
+      ],
+      "env": {
+        "UV_PYTHON_PREFERENCE": "system",
+        "UV_PYTHON": ">=3.11"
+      }
+    }
+  }
+}

{procesio_cli-0.1.1 → procesio_cli-0.1.2}/plugin/README.md

@@ -3,9 +3,8 @@
 Lets your own AI assistant build, run, validate and audit PROCESIO processes, forms and documents.
 
 This folder is the plugin: the MCP server configuration, four Agent Skills and the
-listing icon. The code is the `procesio-cli` package on PyPI. `.mcp.json` pins it to
-version 0.1.1, together with the dependency pins in `constraints.txt` and
-`build-constraints.txt`, and uv installs it the first time Claude Code starts the server.
+listing icon. The code is the `procesio-cli` package on PyPI. `.mcp.json` pins it to exactly
+version 0.1.2, and uv installs it the first time Claude Code starts the server.
 
 ## Install
 

{procesio_cli-0.1.1 → procesio_cli-0.1.2}/procesio_cli/__init__.py

@@ -11,7 +11,7 @@ Running from a clone is unchanged and still documented:
 """
 from pathlib import Path
 
-__version__ = "0.1.1"
+__version__ = "0.1.2"
 
 #: The bundled repository root. In a wheel this directory holds tools/, agents/,
 #: scripts/, skills/ and registry.py; in a clone it is the package beside them.

{procesio_cli-0.1.1 → procesio_cli-0.1.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "procesio-cli"
-version = "0.1.1"
+version = "0.1.2"
 description = "Command-line tooling and an AI agent for the PROCESIO automation platform: drive processes, forms, documents and custom actions from a terminal or from an AI coding assistant."
 requires-python = ">=3.11"
 license = { text = "Apache-2.0" }

{procesio_cli-0.1.1 → procesio_cli-0.1.2}/server.json

@@ -3,7 +3,7 @@
   "name": "io.github.Procesio-Externals/procesio-cli",
   "title": "PROCESIO",
   "description": "Lets your own AI assistant build, run, validate and audit PROCESIO processes, forms and documents.",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "repository": {
     "url": "https://github.com/Procesio-Externals/procesio-cli",
     "source": "github"
@@ -19,8 +19,8 @@
   "packages": [
     {
       "registryType": "mcpb",
-      "identifier": "https://github.com/Procesio-Externals/procesio-cli/releases/download/v0.1.1/procesio-mcp-0.1.1.mcpb",
-      "version": "0.1.1",
+      "identifier": "https://github.com/Procesio-Externals/procesio-cli/releases/download/v0.1.2/procesio-mcp-0.1.2.mcpb",
+      "version": "0.1.2",
       "fileSha256": "FILLED-IN-BY-THE-RELEASE-WORKFLOW",
       "transport": {
         "type": "stdio"
@@ -30,13 +30,13 @@
       "registryType": "pypi",
       "registryBaseUrl": "https://pypi.org",
       "identifier": "procesio-cli",
-      "version": "0.1.1",
+      "version": "0.1.2",
       "runtimeHint": "uvx",
       "runtimeArguments": [
         {
           "type": "named",
           "name": "--from",
-          "value": "procesio-cli==0.1.1"
+          "value": "procesio-cli==0.1.2"
         }
       ],
       "packageArguments": [

{procesio_cli-0.1.1 → procesio_cli-0.1.2}/tools/procesio/PROCESIO-API-NOTES.md

@@ -865,7 +865,16 @@ output by field: `attribute.attributeId` must be a **GUID**, and a field NAME fa
 - **Type the Node's output variable to the target store's backing data model** — builder
   `{"name":"rec","model":"<store dataTypeId>","direction":"output"}` (the `model` escape hatch;
   the store's `dataTypeId` comes from `datastore-get`). Return a plain object from the Node whose
-  KEYS match the model's attribute names; the platform populates the typed attributes by name.
+  KEYS match each attribute's **`jsonProperty`** (from `datastore-get-data-model`), which is the
+  camelCased name, e.g. `invoiceNumber`, and `pONumber` for a column `PONumber`. ⚠ Returning the
+  PascalCase attribute NAMES (`InvoiceNumber`) is silent: the run finishes with status 50 and every
+  attribute of the typed variable is null, so downstream Where/Decisional/Set Values see nulls
+  (measured 2026-10-27). The same variable injected into a later Node arrives with the
+  `jsonProperty` keys too. Builder paths (`{"var": x, "path": ["PONumber"]}`) still use the
+  attribute NAME; the builder resolves it to the attribute GUID.
+  A plain `json` variable cannot be bound by field anywhere the attribute is parsed as a GUID
+  (a rule Decisional rejects it at validate with `Error converting value "<field>" to type
+  'System.Guid'`), so route a field of a json input through a Node into a model-typed variable.
   Then each mapper row binds `attribute:{attributeId:<data-model attr GUID>, nextAttribute:null}`,
   `column:"<store column name>"`.
 - ⚠ **The store's COLUMN ids (`datastore-get` `columns[].id`) are NOT the data-model ATTRIBUTE ids

procesio_cli-0.1.1/plugin/.mcp.json

@@ -1,20 +0,0 @@
-{
-  "mcpServers": {
-    "procesio": {
-      "command": "uvx",
-      "args": [
-        "--python-preference",
-        "system",
-        "--python",
-        ">=3.11",
-        "--from",
-        "procesio-cli==0.1.1",
-        "--constraints",
-        "${CLAUDE_PLUGIN_ROOT}/constraints.txt",
-        "--build-constraints",
-        "${CLAUDE_PLUGIN_ROOT}/build-constraints.txt",
-        "procesio-mcp-chat"
-      ]
-    }
-  }
-}

procesio_cli-0.1.1/plugin/build-constraints.txt

@@ -1,14 +0,0 @@
-# This file was autogenerated by uv via the following command:
-#    python scripts/run-tool.py procesio-oss pin-dependencies
-hatchling==1.32.4
-    # via -r requirements.in
-packaging==26.3
-    # via hatchling
-pathspec==1.1.1
-    # via hatchling
-pluggy==1.7.0
-    # via hatchling
-tomlkit==0.15.2
-    # via hatchling
-trove-classifiers==2026.9.21.13
-    # via hatchling

procesio_cli-0.1.1/plugin/constraints.txt

@@ -1,78 +0,0 @@
-# This file was autogenerated by uv via the following command:
-#    python scripts/run-tool.py procesio-oss pin-dependencies
-annotated-types==0.8.0
-    # via pydantic
-attrs==26.1.0
-    # via
-    #   jsonschema
-    #   referencing
-backports-tarfile==1.2.0 ; python_full_version < '3.12'
-    # via jaraco-context
-certifi==2026.10.23
-    # via requests
-cffi==2.1.1 ; platform_python_implementation != 'PyPy'
-    # via cryptography
-charset-normalizer==3.5.2
-    # via requests
-cryptography==50.0.2
-    # via
-    #   -r requirements.in
-    #   secretstorage
-idna==3.20
-    # via requests
-importlib-metadata==10.1.0 ; python_full_version < '3.12'
-    # via keyring
-jaraco-classes==3.4.0
-    # via keyring
-jaraco-context==6.1.2
-    # via keyring
-jaraco-functools==4.6.0
-    # via keyring
-jeepney==0.9.0 ; sys_platform == 'linux'
-    # via
-    #   keyring
-    #   secretstorage
-jsonschema==4.26.0
-    # via -r requirements.in
-jsonschema-specifications==2025.9.1
-    # via jsonschema
-keyring==25.7.0
-    # via -r requirements.in
-more-itertools==11.2.1
-    # via
-    #   jaraco-classes
-    #   jaraco-functools
-pycparser==3.12 ; implementation_name != 'PyPy' and platform_python_implementation != 'PyPy'
-    # via cffi
-pydantic==2.14.1
-    # via -r requirements.in
-pydantic-core==2.50.1
-    # via pydantic
-pywin32-ctypes==0.2.3 ; sys_platform == 'win32'
-    # via keyring
-pyyaml==6.0.3
-    # via -r requirements.in
-referencing==0.37.0
-    # via
-    #   jsonschema
-    #   jsonschema-specifications
-requests==2.34.2
-    # via -r requirements.in
-rpds-py==2026.9.1
-    # via
-    #   jsonschema
-    #   referencing
-secretstorage==3.5.0 ; sys_platform == 'linux'
-    # via keyring
-typing-extensions==4.16.0
-    # via
-    #   pydantic
-    #   pydantic-core
-    #   referencing
-    #   typing-inspection
-typing-inspection==0.4.4
-    # via pydantic
-urllib3==2.8.0
-    # via requests
-zipp==4.1.2 ; python_full_version < '3.12'
-    # via importlib-metadata