clawdentity 0.0.17 → 0.0.19

package/package.json

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

package/skill-bundle/openclaw-skill/dist/relay-to-peer.mjs

@@ -56,11 +56,11 @@ function parseProxyUrl(value) {
     throw new Error("proxyUrl must be a valid URL");
   }
 }
-function parsePeerName(value) {
+function parseProfileName(value, label) {
   if (value === void 0) {
     return void 0;
   }
-  return parseNonEmptyString(value, "name");
+  return parseNonEmptyString(value, label);
 }
 function parsePeerEntry(value) {
   if (!isRecord(value)) {
@@ -68,11 +68,12 @@ function parsePeerEntry(value) {
   }
   const did = parseDid(value.did);
   const proxyUrl = parseProxyUrl(value.proxyUrl);
-  const name = parsePeerName(value.name);
-  if (name === void 0) {
+  const agentName = parseProfileName(value.agentName, "agentName");
+  const humanName = parseProfileName(value.humanName, "humanName");
+  if (agentName === void 0 && humanName === void 0) {
     return { did, proxyUrl };
   }
-  return { did, proxyUrl, name };
+  return { did, proxyUrl, agentName, humanName };
 }
 function parsePeersConfig(value, source) {
   if (!isRecord(value)) {

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

@@ -57,6 +57,7 @@ Relay invite codes are not part of this flow.
 Required for onboarding:
 - Registry onboarding invite code: `clw_inv_...` (default onboarding path)
 - Local agent name
+- Human display name (used by invite redeem and pairing profile metadata)
 
 Optional only for recovery/advanced operator flows:
 - Existing API key (only when user explicitly says no invite is available)
@@ -84,8 +85,8 @@ Note: Registry operators must run `admin bootstrap` before creating invites. See
 - `clawdentity config show`
 
 ### Invite management
-- `clawdentity invite redeem <registry-invite-code>`
-- `clawdentity invite redeem <registry-invite-code> --registry-url <registry-url>`
+- `clawdentity invite redeem <registry-invite-code> --display-name <human-name>`
+- `clawdentity invite redeem <registry-invite-code> --display-name <human-name> --registry-url <registry-url>`
 - `clawdentity invite create` (admin only, see registry reference)
 - `clawdentity invite create --expires-at <iso-8601>` (admin only)
 
@@ -152,6 +153,7 @@ Note: Registry operators must run `admin bootstrap` before creating invites. See
 - If `--invite-code` appears, treat CLI as outdated and upgrade before continuing:
   - `npm install -g clawdentity@latest`
 - Confirm local agent name.
+- Confirm local human display name for onboarding.
 - Check local API key status with `clawdentity config get apiKey`.
 - If API key is missing, ask for onboarding invite `clw_inv_...` and continue with invite redeem.
 - Do not ask for raw API key unless the user explicitly says invite is unavailable.
@@ -167,13 +169,14 @@ Note: Registry operators must run `admin bootstrap` before creating invites. See
 - If needed, run with `--registry-url`.
 
 4. Finish onboarding and generate API key.
-- Preferred path: run `clawdentity invite redeem <clw_inv_...>`.
+- Preferred path: run `clawdentity invite redeem <clw_inv_...> --display-name <human-name>`.
 - If local API key already exists and user explicitly wants to reuse it, continue without redeem.
 - Use `config set apiKey` only as a manual recovery path when user cannot provide invite.
 - Confirm output shows:
   - `Invite redeemed`
   - API key token printed once
   - `API key saved to local config`
+  - `Human name: <human-name>`
 - Stop and fix if this step fails. Do not proceed to pairing.
 
 5. Create local OpenClaw agent identity.
@@ -193,6 +196,7 @@ Note: Registry operators must run `admin bootstrap` before creating invites. See
   - OpenClaw config path and relay runtime path
   - runtime mode/status
   - websocket status `connected`
+  - setup checklist is healthy (fails fast when hook/device/runtime prerequisites drift)
 
 7. Validate readiness.
 - Run `clawdentity openclaw doctor`.
@@ -209,6 +213,8 @@ Note: Registry operators must run `admin bootstrap` before creating invites. See
 | `state.transform` | Relay transform artifacts in OpenClaw hooks dir | Reinstall skill package or `openclaw setup <agent-name>` |
 | `state.hookMapping` | `send-to-peer` hook mapping in OpenClaw config | `clawdentity openclaw setup <agent-name>` |
 | `state.hookToken` | Hooks enabled with token in OpenClaw config | `clawdentity openclaw setup <agent-name>` then restart OpenClaw |
+| `state.hookSessionRouting` | `hooks.defaultSessionKey`, `hooks.allowRequestSessionKey=false`, and required prefixes (`hook:`, default session key) | `clawdentity openclaw setup <agent-name>` then restart OpenClaw |
+| `state.gatewayDevicePairing` | Pending OpenClaw device approvals (prevents `pairing required` websocket errors) | `openclaw devices list` then `openclaw devices approve <requestId>` |
 | `state.openclawBaseUrl` | OpenClaw base URL resolvable | `clawdentity openclaw setup <agent-name> --openclaw-base-url <url>` |
 | `state.connectorRuntime` | Local connector runtime reachable and websocket-connected | `clawdentity openclaw setup <agent-name>` |
 
@@ -226,6 +232,14 @@ Note: Registry operators must run `admin bootstrap` before creating invites. See
   - Inline ticket path: `clawdentity pair confirm <agent-name> --ticket <clwpair1_...>`
   - Cannot provide both `--qr-file` and `--ticket` simultaneously.
 - Pair confirm auto-saves peer DID/proxy mapping locally from QR ticket metadata.
+- Pair start/confirm/status exchange profile metadata:
+  - `initiatorProfile = { agentName, humanName }`
+  - `responderProfile = { agentName, humanName }`
+- Local peer entries in `~/.clawdentity/peers.json` should include:
+  - `did`
+  - `proxyUrl`
+  - `agentName`
+  - `humanName`
 - If initiator started without `--wait`, initiator must run:
   - `clawdentity pair status <agent-name> --ticket <clwpair1_...> --wait`
   - This persists the peer on initiator after responder confirmation.
@@ -236,6 +250,8 @@ Note: Registry operators must run `admin bootstrap` before creating invites. See
 - Verify output shows token status, expiry, and no revocation.
 - Run `clawdentity openclaw doctor --peer <alias>` to confirm the new peer is visible.
 - Run `clawdentity openclaw relay test` to confirm end-to-end message delivery.
+- Relay delivery is asynchronous: proxy accepts deliveries with `202`, and `state=queued` is expected when the recipient connector is temporarily offline.
+- `state=queued` is not a pairing failure. The proxy retries delivery automatically while the message is within queue TTL/retry limits.
 - Note: `relay test` runs preflight doctor checks before sending the probe.
 
 ## Lifecycle Management

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

@@ -51,7 +51,8 @@ Rules:
     "beta": {
       "did": "did:claw:agent:01H...",
       "proxyUrl": "https://beta-proxy.example.com/hooks/agent",
-      "name": "Beta Agent"
+      "agentName": "beta",
+      "humanName": "Ira"
     }
   }
 }
@@ -61,7 +62,8 @@ Rules:
 - peer alias key uses `[a-zA-Z0-9._-]`
 - `did` required and must begin with `did:`
 - `proxyUrl` required and must be a valid absolute URL
-- `name` optional
+- `agentName` optional
+- `humanName` optional
 
 ## Proxy Pairing Prerequisite
 
@@ -75,11 +77,15 @@ Current pairing contract is ticket-based with CLI support:
    - headers:
      - `Authorization: Claw <AIT>`
      - ownership validation is handled internally by proxy-to-registry service auth
-   - body (optional):
+   - body:
 
 ```json
 {
-  "ttlSeconds": 300
+  "ttlSeconds": 300,
+  "initiatorProfile": {
+    "agentName": "alpha",
+    "humanName": "Ravi"
+  }
 }
 ```
 
@@ -92,7 +98,11 @@ Current pairing contract is ticket-based with CLI support:
 
 ```json
 {
-  "ticket": "clwpair1_..."
+  "ticket": "clwpair1_...",
+  "responderProfile": {
+    "agentName": "beta",
+    "humanName": "Ira"
+  }
 }
 ```
 
@@ -202,7 +212,7 @@ Known defaults:
 | `https://registry.clawdentity.com` | `https://proxy.clawdentity.com` |
 | `https://dev.registry.clawdentity.com` | `https://dev.proxy.clawdentity.com` |
 
-Recovery: rerun onboarding (`clawdentity invite redeem <clw_inv_...>`) so local config aligns to registry metadata.
+Recovery: rerun onboarding (`clawdentity invite redeem <clw_inv_...> --display-name <human-name>`) so local config aligns to registry metadata.
 
 ## Pairing Error Codes
 
@@ -213,6 +223,7 @@ Recovery: rerun onboarding (`clawdentity invite redeem <clw_inv_...>`) so local
 | 403 | `PROXY_PAIR_OWNERSHIP_FORBIDDEN` | Initiator ownership check failed |
 | 503 | `PROXY_PAIR_OWNERSHIP_UNAVAILABLE` | Registry ownership lookup unavailable |
 | — | `CLI_PAIR_AGENT_NOT_FOUND` | Agent ait.jwt or secret.key missing/empty |
+| — | `CLI_PAIR_HUMAN_NAME_MISSING` | Local config is missing `humanName`; set via invite redeem or config |
 | — | `CLI_PAIR_PROXY_URL_REQUIRED` | Proxy URL could not be resolved |
 | — | `CLI_PAIR_START_INVALID_TTL` | ttlSeconds must be a positive integer |
 | — | `CLI_PAIR_INVALID_PROXY_URL` | Proxy URL is invalid |