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

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

@@ -53,16 +53,12 @@ jobs:
           python - <<'PY'
           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.
+          # The plugin runs `uv run --locked` against plugin/uv.lock, which names a release
+          # already on PyPI, so it launches here exactly as it ships. A lock that no longer
+          # matches plugin/pyproject.toml fails right here, as it would for every user.
           cfg = json.loads(pathlib.Path("plugin/.mcp.json").read_text())["mcpServers"]["procesio"]
-          args = list(cfg["args"])
+          args = [a.replace("${CLAUDE_PLUGIN_ROOT}", "plugin") for a in 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}")
-          args[args.index("--from") + 1] = "."
           plugin_argv = [cfg["command"]] + args
           request = '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}\n'
 

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

@@ -9,10 +9,22 @@ there, not here.
 
 ## [Unreleased]
 
+## [0.1.3] - 2026-10-27
+
+### Added
+- A `procesio-cli` command, the package's own name, that starts the chat MCP server, so
+  `uvx procesio-cli==<version>` runs it with no extra arguments. The registry entry for
+  PyPI uses that form.
+
+### Changed
+- The plugin starts its server with `uv run --locked` against `plugin/uv.lock`, which
+  pins the runtime release and every dependency with hashes, instead of `uvx` with only
+  the top-level version pinned.
+
 ## [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 plugin's launcher is now just `uvx --from procesio-cli==0.1.3 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.
@@ -21,7 +33,7 @@ there, not here.
 
 ### Changed
 - The Claude Code plugin moved to `plugin/`. It now installs the exact PyPI release
-  (`uvx --from procesio-cli==0.1.2`) instead of building the repository, ships four
+  (`uvx --from procesio-cli==0.1.3`) 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.2 → procesio_cli-0.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: procesio-cli
-Version: 0.1.2
+Version: 0.1.3
 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,11 +180,12 @@ 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 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
+**What gets installed is pinned.** The plugin carries a small runtime project in
+`plugin/`: `pyproject.toml` names one release of `procesio-cli` and `uv.lock` pins it and
+every dependency to exact versions with hashes. It starts the server with `uv run
+--locked`, so a fresh launch installs exactly what was locked for this release, not
+whatever is newest on PyPI that day. A clone can do the same with `constraints.txt` and
+`build-constraints.txt`, which pin every package to versions 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.

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

@@ -136,11 +136,12 @@ 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 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
+**What gets installed is pinned.** The plugin carries a small runtime project in
+`plugin/`: `pyproject.toml` names one release of `procesio-cli` and `uv.lock` pins it and
+every dependency to exact versions with hashes. It starts the server with `uv run
+--locked`, so a fresh launch installs exactly what was locked for this release, not
+whatever is newest on PyPI that day. A clone can do the same with `constraints.txt` and
+`build-constraints.txt`, which pin every package to versions 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.

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

@@ -2,7 +2,7 @@
   "manifest_version": "0.4",
   "name": "procesio",
   "display_name": "PROCESIO",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "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.2 → procesio_cli-0.1.3}/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.2",
+  "version": "0.1.3",
   "author": {
     "name": "Ringhel TEAM SRL (PROCESIO)",
     "url": "https://procesio.com"

{procesio_cli-0.1.2 → procesio_cli-0.1.3}/plugin/.mcp.json

@@ -1,10 +1,12 @@
 {
   "mcpServers": {
     "procesio": {
-      "command": "uvx",
+      "command": "uv",
       "args": [
-        "--from",
-        "procesio-cli==0.1.2",
+        "run",
+        "--locked",
+        "--project",
+        "${CLAUDE_PLUGIN_ROOT}",
         "procesio-mcp-chat"
       ],
       "env": {

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

@@ -3,8 +3,10 @@
 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 exactly
-version 0.1.2, and uv installs it the first time Claude Code starts the server.
+listing icon. The code is the `procesio-cli` package on PyPI. `pyproject.toml` names
+release 0.1.2, and `uv.lock` pins it and every dependency to exact
+versions with their hashes. Claude Code starts the server with `uv run --locked`, so the
+first launch installs exactly those files and nothing newer.
 
 ## Install
 

procesio_cli-0.1.3/plugin/pyproject.toml

@@ -0,0 +1,17 @@
+# The Claude plugin's runtime: one dependency, the procesio-cli release the plugin runs,
+# locked with exact versions and hashes in uv.lock beside this file. .mcp.json starts the
+# server with `uv run --locked`, so what installs is exactly what was locked and reviewed.
+# Regenerate both with `procesio-oss lock-plugin` in the upstream repo, never by hand.
+[project]
+name = "procesio-plugin-runtime"
+version = "0.1.2"
+description = "Locked runtime for the PROCESIO Claude plugin"
+requires-python = ">=3.11"
+dependencies = ["procesio-cli==0.1.2"]
+
+[tool.uv]
+package = false
+# Written by lock-plugin: third-party releases newer than the cutoff are never locked,
+# and the runtime release itself is exempt. Change them only by re-running lock-plugin.
+exclude-newer = "2026-10-20T15:46:56Z"
+exclude-newer-package = { procesio-cli = "2026-10-27T15:46:56Z" }