clawdentity 0.0.19 → 0.0.21

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "clawdentity",
3
- "version": "0.0.19",
3
+ "version": "0.0.21",
4
4
  "type": "module",
5
5
  "publishConfig": {
6
6
  "access": "public"
@@ -199,7 +199,8 @@ Note: Registry operators must run `admin bootstrap` before creating invites. See
199
199
  - setup checklist is healthy (fails fast when hook/device/runtime prerequisites drift)
200
200
 
201
201
  7. Validate readiness.
202
- - Run `clawdentity openclaw doctor`.
202
+ - `clawdentity openclaw setup` already runs an internal checklist and auto-recovers pending OpenClaw gateway device approvals when possible.
203
+ - Run `clawdentity openclaw doctor` only for diagnostics or CI reporting.
203
204
  - Use `--json` for machine-readable output.
204
205
  - Use `--peer <alias>` to validate a specific peer exists after pairing.
205
206
  - Doctor check IDs and remediation:
@@ -214,9 +215,11 @@ Note: Registry operators must run `admin bootstrap` before creating invites. See
214
215
  | `state.hookMapping` | `send-to-peer` hook mapping in OpenClaw config | `clawdentity openclaw setup <agent-name>` |
215
216
  | `state.hookToken` | Hooks enabled with token in OpenClaw config | `clawdentity openclaw setup <agent-name>` then restart OpenClaw |
216
217
  | `state.hookSessionRouting` | `hooks.defaultSessionKey`, `hooks.allowRequestSessionKey=false`, and required prefixes (`hook:`, default session key) | `clawdentity openclaw setup <agent-name>` then restart OpenClaw |
217
- | `state.gatewayDevicePairing` | Pending OpenClaw device approvals (prevents `pairing required` websocket errors) | `openclaw devices list` then `openclaw devices approve <requestId>` |
218
+ | `state.gatewayDevicePairing` | Pending OpenClaw device approvals (prevents `pairing required` websocket errors) | Re-run `clawdentity openclaw setup <agent-name>` so setup auto-recovers approvals |
218
219
  | `state.openclawBaseUrl` | OpenClaw base URL resolvable | `clawdentity openclaw setup <agent-name> --openclaw-base-url <url>` |
219
220
  | `state.connectorRuntime` | Local connector runtime reachable and websocket-connected | `clawdentity openclaw setup <agent-name>` |
221
+ | `state.connectorInboundInbox` | Connector local inbound inbox backlog and replay queue state (`/v1/status`) | Re-run `clawdentity openclaw setup <agent-name>` and verify connector runtime health |
222
+ | `state.openclawHookHealth` | Connector replay status for local OpenClaw hook delivery (`/v1/status`) | Re-run `clawdentity openclaw setup <agent-name>` and restart OpenClaw if hook replay stays failed |
220
223
 
221
224
  - At this point the agent is ready to start pairing or accept pairing.
222
225
 
@@ -327,7 +330,8 @@ Do not suggest switching endpoints unless user explicitly asks for endpoint chan
327
330
  - Report exact missing file/value.
328
331
  - Fix only failing input/config.
329
332
  - Prefer `openclaw setup` as the single runtime reconciliation command.
330
- - Re-run `openclaw doctor`, then `openclaw relay test`.
333
+ - Then run `openclaw relay test`.
334
+ - Use `openclaw doctor` only when you need a detailed diagnostic report.
331
335
 
332
336
  ## Bundled Resources
333
337