clawdentity 0.0.7 → 0.0.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clawdentity",
-  "version": "0.0.7",
+  "version": "0.0.9",
   "type": "module",
   "publishConfig": {
     "access": "public"

package/skill-bundle/openclaw-skill/skill/SKILL.md

@@ -10,7 +10,7 @@ This skill prepares a local OpenClaw agent in a strict sequence:
 1. finish registry onboarding and generate/store API key
 2. create local agent identity
 3. configure relay runtime
-4. become ready to start or accept pairing
+4. become ready to start or accept QR pairing
 
 Relay invite codes are not part of this flow.
 
@@ -46,21 +46,14 @@ Required for onboarding:
 - Registry onboarding invite code: `clw_inv_...` (or existing local API key)
 - Local agent name
 
-Required for relay setup (after onboarding + agent create):
-- Peer alias
-- Peer DID
-- Peer proxy URL (`.../hooks/agent`)
-- Optional peer display name
-
 Required for pairing phase (after setup):
-- Initiator proxy URL
-- Responder proxy URL
+- Pairing QR from the other side (`clwpair1_...` inside QR image)
 
 ## Tool Execution Contract (Agent)
 
 - Execute side effects directly with tools/CLI.
 - Do not ask humans to run commands that the agent can run.
-- Ask humans only for missing secrets or missing peer/proxy inputs.
+- Ask humans only for missing secrets or missing required command inputs.
 - Keep status output concrete: created agent DID, generated API key status, written files.
 
 ## Command Utilization (required)
@@ -73,18 +66,23 @@ Required for pairing phase (after setup):
 - `clawdentity config set apiKey <api-key>` (fallback only when invite is unavailable)
 - `clawdentity agent create <agent-name> --framework openclaw`
 - `clawdentity agent inspect <agent-name>`
-- `clawdentity openclaw setup <agent-name> --peer-alias <alias> --peer-did <did> --peer-proxy-url <url>`
+- `clawdentity openclaw setup <agent-name>`
 - `clawdentity connector start <agent-name>`
 - `clawdentity connector service install <agent-name>` (optional)
 - `clawdentity openclaw doctor`
-- `clawdentity openclaw relay test --peer <alias>`
-- `clawdentity pair start <agent-name> --proxy-url <initiator-proxy-url> --qr`
-- `clawdentity pair confirm <agent-name> --qr-file <path> --proxy-url <responder-proxy-url>`
+- `clawdentity openclaw relay test` (auto-selects when one peer exists)
+- `clawdentity pair start <agent-name> --qr`
+- `clawdentity pair confirm <agent-name> --qr-file <path>`
 
 ## Journey (strict order)
 
 1. Validate prerequisites.
 - Confirm CLI is installed.
+- Confirm CLI setup command is self-setup only:
+  - `clawdentity openclaw setup --help` must not include peer routing flags.
+  - it must **not** include `--invite-code`.
+- If `--invite-code` appears, treat CLI as outdated and upgrade before continuing:
+  - `npm install -g clawdentity@latest`
 - Confirm local agent name.
 - Confirm either existing API key or `clw_inv_...`.
 - Confirm OpenClaw path/base URL only if non-default.
@@ -113,12 +111,11 @@ Required for pairing phase (after setup):
 
 6. Configure relay setup.
 - Run:
-  `clawdentity openclaw setup <agent-name> --peer-alias <alias> --peer-did <did> --peer-proxy-url <url>`
+  `clawdentity openclaw setup <agent-name>`
 - Add optional:
-  - `--peer-name <displayName>`
   - `--openclaw-dir <path>`
   - `--openclaw-base-url <url>`
-- Verify output contains peer alias, peer DID, peer proxy URL, OpenClaw config path, and relay runtime path.
+- Verify output contains self-setup completion, OpenClaw config path, and relay runtime path.
 
 7. Start connector runtime.
 - Run `clawdentity connector start <agent-name>`.
@@ -126,24 +123,24 @@ Required for pairing phase (after setup):
 
 8. Validate readiness.
 - Run `clawdentity openclaw doctor`.
-- Run `clawdentity openclaw relay test --peer <alias>`.
 - At this point the agent is ready to start pairing or accept pairing.
 
 9. Pairing phase (separate from onboarding).
-- Initiator: `clawdentity pair start <agent-name> --proxy-url <initiator-proxy-url> --qr`
-- Responder: `clawdentity pair confirm <agent-name> --qr-file <path> --proxy-url <responder-proxy-url>`
-- Confirm pairing success before first real peer message.
+- Initiator: `clawdentity pair start <agent-name> --qr`
+- Responder: `clawdentity pair confirm <agent-name> --qr-file <path>`
+- Pair confirm auto-saves peer DID/proxy mapping locally from QR ticket metadata.
+- Confirm pairing success, then run `clawdentity openclaw relay test`.
 
 ## Required Question Policy
 
 Ask only when missing:
 - local agent name
 - onboarding invite (`clw_inv_...`) when API key is absent
-- peer alias/DID/proxy URL for setup
-- initiator/responder proxy URLs for pairing
 - non-default OpenClaw path/base URL
+- pairing QR image path for confirm
 
 Do not ask for relay invite codes.
+Do not ask for `clawd1_...` values.
 
 ## Failure Handling
 

package/skill-bundle/openclaw-skill/skill/references/clawdentity-protocol.md

@@ -28,17 +28,11 @@ Define the exact runtime contract used by `relay-to-peer.mjs`.
 
 ## Setup Input Contract
 
-`clawdentity openclaw setup` is configured with explicit peer routing fields:
-
-- `--peer-alias <alias>`
-- `--peer-did <did:claw:agent:...>`
-- `--peer-proxy-url <http(s)://.../hooks/agent>`
-- optional `--peer-name <display-name>`
+`clawdentity openclaw setup` is self-setup only. It does not accept peer routing fields.
 
 Rules:
-- peer alias uses `[a-zA-Z0-9._-]`
-- peer DID must be a valid agent DID
-- peer proxy URL must be absolute `http` or `https`
+- setup must succeed without any peer metadata
+- peers config snapshot still exists and may be empty until pairing is completed
 
 ## Peer Map Schema
 
@@ -69,7 +63,7 @@ Relay delivery policy is trust-pair based on proxy side. Pairing must be complet
 Current pairing contract is ticket-based with CLI support:
 
 1. Initiator owner starts pairing:
-   - CLI: `clawdentity pair start <agent-name> --proxy-url <url> --qr`
+   - CLI: `clawdentity pair start <agent-name> --qr`
    - proxy route: `POST /pair/start`
    - headers:
      - `Authorization: Claw <AIT>`
@@ -83,7 +77,7 @@ Current pairing contract is ticket-based with CLI support:
 ```
 
 2. Responder confirms pairing:
-   - CLI: `clawdentity pair confirm <agent-name> --qr-file <path> --proxy-url <url>`
+   - CLI: `clawdentity pair confirm <agent-name> --qr-file <path>`
    - proxy route: `POST /pair/confirm`
    - headers:
      - `Authorization: Claw <AIT>`
@@ -98,6 +92,7 @@ Current pairing contract is ticket-based with CLI support:
 Rules:
 - `ticket` is one-time and expires (default 5 minutes, max 15 minutes).
 - Confirm establishes mutual trust for the initiator/responder pair.
+- Confirm auto-persists peer DID/proxy mapping locally in `~/.clawdentity/peers.json` using ticket issuer metadata.
 - Same-agent sender/recipient is allowed by policy without explicit pair entry.
 
 ## Relay Input Contract