@visa/cli 4.1.0-rc.74 → 4.1.0-rc.76

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

@@ -153,7 +153,8 @@ after the pending identity and private key are durable. Present the link and fin
 for exact browser comparison. When `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.
+the plugin/MCP tools — `enroll_agent` action `start` reports the same `claiming` /
+`recoveryCommand` fields and starts the same detached poller.
 
 ## Returning & already-connected — do NOT re-pair
 
@@ -269,6 +270,22 @@ dangerous). All spending is gated by the owner-approved local policy caps.
       `visa agent enroll-claim --format json`.
 - [ ] Report the stable `agentId` and that the identity is paired on this runtime.
 
+### Completion is `activated` — nothing else
+
+Only a poll result of `activated` means this runtime is paired. Until you have one, do not
+tell the human the agent is connected, paired, enrolled, set up, ready, or good to go, and
+do not move on to spending, mail, or mesh steps that assume an identity.
+
+`start` returning successfully is not completion. It returns a stable `agentId` and a
+`requestKeyFingerprint` **before any human has approved anything** — those are review
+values for the browser comparison, not evidence of pairing. Reporting an `agentId` as
+though it were a finished pairing is the most likely way to mislead the human here, because
+the number looks like a result.
+
+If you cannot reach `activated`, say plainly what state you did reach and what the human
+should do next. An honest "approved but not yet activated — I'm still polling" is correct;
+"you're all set" without an `activated` result is not.
+
 ### 1. Start
 
 Start once. If there is already a pending pairing, poll it before creating another.
@@ -290,12 +307,23 @@ Use this concise shape:
 > Public request-key fingerprint — compare every character in the browser:
 > <requestKeyFingerprint, complete and untruncated>
 >
-> Approve only if the fingerprint matches, then tell me when it is finished. The link
-> expires shortly.
+> Approve only if the fingerprint matches. The link expires shortly — I'll keep watching
+> and confirm here the moment it activates.
 
 Do not ask the human for a code, secret, private key, token, or signed message. The URL,
 stable agent ID, and public fingerprint are review values, not claim credentials.
 
+**Do not end your turn here waiting to be told the human is done.** Presenting the link is
+not the end of the ceremony; go straight to the poll in §2 and drive it to a terminal
+state. Asking the human to report back is what strands a pairing: they approve in the
+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
+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.
+
 ### 2. Poll
 
 Poll the same pending pairing. Interpret results as follows:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@visa/cli",
-  "version": "4.1.0-rc.74",
+  "version": "4.1.0-rc.76",
   "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.74",
+  "version": "4.1.0-rc.76",
   "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.74",
+      "version": "4.1.0-rc.76",
       "transport": {
         "type": "stdio"
       },