@visa/cli 5.0.0-rc.409 → 5.0.0-rc.412

package/package.json

@@ -1,11 +1,12 @@
 {
   "name": "@visa/cli",
-  "version": "5.0.0-rc.409",
+  "version": "5.0.0-rc.412",
   "description": "Visa CLI runtime for stable agent identity and separately authorized payment capabilities",
   "bin": {
     "visa-cli": "./bin/visa-cli.js",
     "visa": "./bin/visa-cli.js",
-    "visa-runtime-converge": "./dist/managed-runtime/resolve-and-update.mjs"
+    "visa-runtime-converge": "./dist/managed-runtime/resolve-and-update.mjs",
+    "visa-tool": "./bin/visa-tool.js"
   },
   "scripts": {
     "sync:server-json": "node scripts/sync-server-json.mjs",
@@ -27,7 +28,6 @@
     "test:smoke": "VISA_AUTH_URL=https://auth.visacli.sh jest --config jest.smoke.config.js",
     "test:packed": "node scripts/packed-cli-smoke.mjs",
     "test:e2e": "jest --config jest.e2e.config.js",
-    "coinbase:onramp": "pnpm exec tsx tests/e2e/coinbase-onramp-harness/run.ts",
     "test:all": "npm run test:unit && npm run test:e2e",
     "prepublishOnly": "npm run build && npm test",
     "lint": "eslint src/**/*.ts",
@@ -49,8 +49,7 @@
   "dependencies": {
     "@modelcontextprotocol/server": "2.0.0",
     "commander": "^12.1.0",
-    "punycode": "^2.3.1",
-    "zod": "^3.25.76"
+    "punycode": "^2.3.1"
   },
   "devDependencies": {
     "@types/express": "^5.0.0",
@@ -58,14 +57,12 @@
     "@types/node": "^22.20.5",
     "@typescript-eslint/eslint-plugin": "^8.68.0",
     "@typescript-eslint/parser": "^8.68.0",
-    "@visa/crypto": "workspace:*",
     "@visa/financial-core": "workspace:*",
     "@visa/identity": "workspace:*",
     "@visa/contracts": "workspace:*",
     "@visa/observability": "workspace:*",
     "@visa/shared": "workspace:*",
     "@visa/wallet": "workspace:*",
-    "@visa/wallet-tools": "workspace:*",
     "esbuild": "^0.28.1",
     "eslint": "^10.0.2",
     "express": "^4.21.0",
@@ -81,6 +78,7 @@
   "mcpName": "io.github.visa-crypto-labs/visa-cli",
   "files": [
     "bin/visa-cli.js",
+    "bin/visa-tool.js",
     "dist/",
     "install.ps1",
     "install.sh",

package/server.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.visa-crypto-labs/visa-cli",
-  "version": "5.0.0-rc.409",
+  "version": "5.0.0-rc.412",
   "title": "Visa CLI",
   "description": "Pair a human-approved agent identity, configure payment capabilities separately, and discover and pay x402 services from your AI coding assistant.",
   "websiteUrl": "https://github.com/Visa-Crypto-Labs/Visa-mono/tree/main/packages/cli#readme",
@@ -9,7 +9,7 @@
     {
       "registryType": "npm",
       "identifier": "@visa/cli",
-      "version": "5.0.0-rc.409",
+      "version": "5.0.0-rc.412",
       "transport": {
         "type": "stdio"
       },

package/dist/skills/pair-visa-agent/RUNTIMES.md

@@ -1,117 +0,0 @@
-# Running Visa agent setup in OpenClaw and Hermes
-
-`@visa/visa-cli-openclaw` is packaged for OpenClaw, but the skill is runtime-agnostic.
-OpenClaw, Hermes, and any runtime that can execute the `visa` CLI or mount its MCP server
-all drive the same setup operation: identity plus every requested rail, behind one owner
-approval.
-
-## Plugins are runtime-specific
-
-| Axis            | OpenClaw                                                  | Hermes                                                                                          |
-| --------------- | --------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
-| Language        | JavaScript/TypeScript                                     | Python                                                                                          |
-| Plugin manifest | `openclaw.plugin.json` + `definePluginEntry` (`index.ts`) | `~/.hermes/plugins/<name>/plugin.yaml` + `__init__.py`, `ctx.register_tool(...)`                |
-| Config file     | `~/.openclaw/openclaw.json`                               | `~/.hermes/config.yaml`                                                                         |
-| Skills          | Markdown `SKILL.md`                                       | Markdown under `~/.hermes/skills/<name>/`                                                       |
-| MCP             | `mcp.servers.*`                                           | `mcp_servers.*`                                                                                 |
-| Migration       | —                                                         | `hermes claw migrate` imports skills, allowlists, compatible MCP servers, memory, and `SOUL.md` |
-
-The OpenClaw JavaScript tools do not load as a Hermes plugin. Portability comes from the
-Markdown skill, CLI, and MCP protocol instead.
-
-## One ceremony, two surfaces
-
-Both supported surfaces run the same protected enrollment and share the same local
-pending record:
-
-1. Visa MCP server: `agent_enroll` once; after the owner approves, this computer
-   finishes in the background (`get_status` shows `pairing.setup.state` go
-   `finishing` → `connected`; do not call `agent_enroll` while it is `finishing`).
-2. Terminal: `visa connect` (add `--format json` for machine output).
-
-Each returns one link and a short code for the human. The browser receives only that
-link. The agent's keys are generated on this device and never leave it, and the
-approval page certifies only the keys this device named in the link. Calling it again
-resumes the same pending enrollment after an interruption.
-
-Use `agentId` as the stable identity. `identityKeyJkt` identifies the currently bound
-Ed25519 public key and can change after key rotation.
-
-The older plugin pairing tools and MCP enrollment tools are gone: they drove CLI
-commands that no longer exist. `agent_enroll` (MCP) and `visa connect` are the one door.
-
-## Install and mount
-
-Install the prerelease CLI, which provides both command names and the MCP server:
-
-```sh
-npm install -g @visa/cli@rc
-```
-
-There is no `visa mcp` subcommand. Run `visa-cli connect <runtime>` when supported, or
-configure `@visa/cli/dist/mcp-server/index.js` directly. Replace `<npm root -g>` below
-with the output of `npm root -g`.
-
-OpenClaw (`~/.openclaw/openclaw.json`):
-
-```json
-{
-  "mcp": {
-    "servers": {
-      "visa-cli": {
-        "command": "node",
-        "args": ["<npm root -g>/@visa/cli/dist/mcp-server/index.js"]
-      }
-    }
-  }
-}
-```
-
-Hermes (`~/.hermes/config.yaml`). Hermes passes a filtered platform-safe baseline
-(`PATH`, `HOME`, platform variables, and `XDG_*`) plus this server's `env:` map.
-Arbitrary gateway variables are excluded, so map `VISA_RC_CODE` explicitly. The
-placeholder keeps its value in `~/.hermes/.env` instead of `config.yaml`:
-
-```yaml
-mcp_servers:
-  visa-cli:
-    command: node
-    args: ['<npm root -g>/@visa/cli/dist/mcp-server/index.js']
-    env:
-      VISA_RC_CODE: ${VISA_RC_CODE}
-      # Optional overrides for a different state directory or toolchain:
-      # HOME: /home/<user>
-      # PATH: /usr/local/bin:/usr/bin:/bin
-```
-
-### Keep one local-state namespace
-
-The gateway shell and the Visa MCP subprocess must resolve the same `HOME` and
-`VISA_CLI_HOME`. Set that boundary before pairing and keep it stable. Changing
-`VISA_CLI_HOME` later also changes where paired identity and grant records are
-read; it is not a safe way to make an old contact file visible.
-
-For example, with `HOME=/opt/data/home` and no `VISA_CLI_HOME`, identity lives
-under `/opt/data/home/.visa-cli` and checkout contact under
-`/opt/data/home/.visa-mcp`. A profile at `/opt/data/.visa-mcp` belongs to a
-different state namespace. Do not scan, copy, or auto-adopt it: contact files
-contain owner PII. The host passes checkout details to `purchase_create` itself;
-no Visa tool writes the profile.
-
-## Runtime setup map
-
-| Runtime       | Setup surface                                                                                                                                                                                                                                                          |
-| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| OpenClaw      | Install `@visa/cli@rc` (`npm install -g @visa/cli@rc`) and run `visa connect openclaw`. It plants the skill under `~/.openclaw/skills/` and mounts the Visa MCP server into `~/.openclaw/openclaw.json`. (The `@visa/visa-cli-openclaw` plugin package is prerelease). |
-| Hermes        | Run `visa connect hermes`. It resolves the per-profile skills directory and refuses to guess when several profiles exist — set `HERMES_PROFILE` to choose one. `hermes claw migrate` can import an existing OpenClaw setup.                                            |
-| Codex         | Run `visa connect codex`. It plants the skill under `~/.codex/skills/` and mounts the Visa MCP server into `~/.codex/config.toml` in the same step.                                                                                                                    |
-| Other runtime | Put `visa` on `PATH` and mount the same MCP server by hand; `get_status` shows what is connected.                                                                                                                                                                      |
-
-The skill is planted by `visa connect <client>`, into that client's own skills
-directory. Reload the runtime afterwards.
-
-## Optional Hermes wrapper
-
-A Hermes Python plugin may wrap the canonical raw CLI commands and register tools with
-`ctx.register_tool(...)`. It is optional: the MCP server and skill already expose the
-same operation and persisted local state without a second implementation.