jaspervault_cli 1.0.2 → 1.0.3

package/dist/src/templates/skill-body.js

@@ -23,28 +23,28 @@ export const BANNER = `
 `.trim();
 /** Skill body content (shared across platforms, after the main heading) */
 const SKILL_BODY_CONTENT = `
-Interact with JasperVault's perpetual contract platform. You can create market/limit orders, set take-profit and stop-loss, create hedging options, manage limit orders, and query positions — all via the \`jv\` CLI.
+Interact with JasperVault's perpetual contract platform. You can create market/limit orders, set take-profit and stop-loss, create hedging options, manage limit orders, and query positions — all via the \`jv\` CLI. No private key is ever required.
 
 ## Prerequisites
 
 - \`jv\` CLI installed and available in PATH
-- For first-time setup: run \`jv vault init\` (requires \`PRIVATE_KEY\` env var)
-- API URL defaults to \`https://trading-api-test.jaspervault.pro\`; set \`JV_API_URL\` only when debugging locally
+- **First-time setup**: use \`jv vault init-wc\` to initialize via WalletConnect (scan QR on phone, sign delegation — no private key needed)
+- API URL defaults to the JasperVault trading endpoint; no environment variables needed for normal use
 
-## Setup Flow (First Time)
+## Setup Flow (First Time — WalletConnect)
 
 \`\`\`bash
-# 1. Set your EOA private key (required only for vault init and deposit)
-export PRIVATE_KEY=0x...
+# Initialize vault and delegation wallet via WalletConnect (one-time, no private key required)
+jv vault init-wc --network jaspervault --timeout 120
+\`\`\`
 
-# 2. Initialize vault and delegation wallet (one-time)
-jv vault init --network jaspervault --vault-types 33,37 --pretty
+CRITICAL EXECUTION NOTE: This command runs for up to 2 minutes. Do NOT interrupt or kill the process after the first JSON line. Wait for the process to exit naturally (second JSON output = success or failure).
 
-# 3. (Optional) Deposit tokens from Base via Hyperlane
-jv deposit --token jusdc --amount 100 --pretty
-\`\`\`
+The command outputs two JSON lines:
+1. \`{"status":"awaiting_connection", "uri":"wc:...", "qrCodeUrl":"https://api.qrserver.com/...", ...}\` — Send the \`qrCodeUrl\` as a plain text URL to the user so their chat platform renders a link preview. Also provide the \`uri\` as a fallback for manual paste.
+2. \`{"success":true, "message":"Vault initialized successfully", ...}\` — Init complete. The delegation wallet is saved to \`~/.jaspervault/keys.json\` and vault addresses to \`~/.jaspervault/profile.json\`. Subsequent commands use these automatically — no wallet interaction needed.
 
-After init, the delegation wallet is saved to \`~/.jaspervault/keys.json\` and vault addresses to \`~/.jaspervault/profile.json\`. Subsequent commands use these automatically — no \`PRIVATE_KEY\` needed.
+Do NOT ask the user to set \`PRIVATE_KEY\`. Do NOT suggest \`jv vault init\` unless the user explicitly requests private-key mode.
 
 ## Intent Mapping
 
@@ -182,7 +182,7 @@ Tell the user: "Order executed successfully. Tx: {transactionHash}."
 
 ## Error Handling
 
-- **Exit code 1**: Configuration error (e.g. delegation key not found — run \`jv vault init\` first; or invalid parameters). Tell the user to check setup.
+- **Exit code 1**: Configuration error (e.g. delegation key not found — run \`jv vault init-wc\` first; or invalid parameters). Tell the user to check setup.
 - **Exit code 2**: Network/HTTP error. Tell the user the service may be unreachable.
 - **Exit code 3**: Business error (duplicate order, invalid params, etc.). Read stderr for details and relay the message without exposing raw technical data.
 
@@ -191,8 +191,8 @@ When an error occurs, stderr contains the error message. Never expose raw stack
 ## Security Notes
 
 - Never log or display private keys, signatures, or API keys in responses to the user.
-- The CLI signs orders internally via the delegation wallet stored in \`~/.jaspervault/keys.json\`.
-- \`PRIVATE_KEY\` is only needed for \`jv vault init\` and \`jv deposit\`; it is not stored by the CLI.
+- The CLI signs orders internally via the delegation wallet stored in \`~/.jaspervault/keys.json\`. No private key is ever required from the user.
+- Do NOT ask the user to set \`PRIVATE_KEY\` — vault initialization is done via WalletConnect (\`jv vault init-wc\`).
 - \`JV_API_KEY\` (optional Bearer token) should be injected via environment variables or secrets manager, never hardcoded.
 `.trim();
 function getOpenClawFrontmatter() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jaspervault_cli",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "JasperVault CLI for interacting with the JasperVault Manager API",
   "type": "module",
   "bin": {