@visa/cli 4.1.0-rc.170 → 4.1.0-rc.172

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

@@ -217,12 +217,11 @@ It returns `browserUrl`, `pairingId`, stable `agentId`, the full public
 `requestKeyFingerprint`, and — on newer builds — `confirmationCode` **immediately**. It
 starts a detached activation process only after the pending identity and private key are
 durable. Present the link, returned confirmation code, and fingerprint for browser
-comparison; omit only a confirmation code the result did not provide. When `claiming` is `background`,
+comparison; omit only a confirmation code the result did not provide. When driving `visa agent pair --format json` and `claiming` is `background`,
 activation completes after approval without another command; if it is `manual`, run the
 returned `recoveryCommand` after approval. Use the step-by-step flow
-below when `pair` is unavailable or when driving the plugin/MCP tools — `enroll_agent`
-action `start` reports the same `claiming` / `recoveryCommand` fields and starts the same
-detached poller.
+below when `pair` is unavailable or when driving the plugin/MCP tools — `enroll_agent` and `visa agent enroll`
+are explicit two-step flows (`start` returns `state: "needs_owner"` and `nextAction: {tool: "enroll_agent", action: "claim"}`; `claim` completes activation after human approval). There is no detached background poller for `enroll_agent` or `visa agent enroll`.
 
 ## Returning & already-connected — do NOT re-pair
 
@@ -416,10 +415,9 @@ state. Asking the human to report back is what strands a pairing: they approve i
 browser, the server records it, and nothing ever writes the local record — so the ceremony
 expires while both sides believe the other is acting.
 
-When the start result reports `claiming: "background"`, a detached poller is already
+When driving `visa agent pair --format json` and the start result reports `claiming: "background"`, a detached poller is already
 finishing activation and it will complete even if this turn ends; poll anyway so you can
-confirm the outcome. When it reports `claiming: "manual"`, that poller could NOT start and
-polling in this turn is the ONLY thing that will complete the pairing.
+confirm the outcome. When driving `enroll_agent` or `visa agent enroll`, there is no detached poller: calling `enroll_agent` with `{"action":"claim"}` (or `visa agent enroll-claim`) is required to complete the pairing and write the local credential.
 
 ### 2. Poll
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@visa/cli",
-  "version": "4.1.0-rc.170",
+  "version": "4.1.0-rc.172",
   "description": "Visa CLI runtime for stable agent identity and separately authorized payment capabilities",
   "bin": {
     "visa-cli": "./bin/visa-cli.js",

package/server.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
   "name": "io.github.visa-crypto-labs/visa-cli",
-  "version": "4.1.0-rc.170",
+  "version": "4.1.0-rc.172",
   "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": "4.1.0-rc.170",
+      "version": "4.1.0-rc.172",
       "transport": {
         "type": "stdio"
       },