@cello-protocol/cli 0.0.215 → 0.0.217

package/dist/hermes/assets.d.ts

@@ -31,5 +31,5 @@ export declare const HERMES_PLUGIN_YAML = "name: cello\nlabel: CELLO\nkind: plat
  */
 export declare const HERMES_PLUGIN_INIT_PY: string;
 /** The setup skill — `~/.hermes/skills/cello-bridge-setup/SKILL.md`. */
-export declare const HERMES_SKILL_MD = "---\nname: cello-bridge-setup\ndescription: \"Install and configure the CELLO agent-to-agent bridge for this Hermes instance.\"\nversion: 1.0.0\nplatforms: [linux, macos]\nmetadata:\n  hermes:\n    tags: [cello, messaging, integration, agent-to-agent]\n    related_skills: []\n---\n\n# CELLO Bridge Setup\n\nCELLO is a peer-to-peer identity and trust layer for agent-to-agent communication:\nsplit-key signing, tamper-evident hash chains, and content-free wake notifications.\nThis skill wires the local CELLO daemon into Hermes so this agent can talk to other\nCELLO agents anywhere.\n\nTrigger: /cello-bridge-setup, or \"install the CELLO bridge\".\n\n## Steps\n\n1. **Check CELLO is set up.** Run `cello status`. If the CLI is missing or the daemon\n   is not running, walk the user through CELLO onboarding first:\n   `npx --yes @cello-protocol/cli@latest login`, then `cello create-agent <name>`,\n   then `cello register-agent <name> <pre-auth-token>` (token from the CELLO Operations\n   Agent on Telegram). Confirm with `cello status`.\n2. **Pick the agent.** Ask the user which registered CELLO agent this Hermes instance\n   should bind to (the `cello status` output lists them).\n3. **Run the installer** \u2014 one command does all the work (plugin scaffold, env binding,\n   `hermes plugins enable cello`, `hermes mcp add cello`):\n\n       cello bridge hermes --agent <name>\n\n   Pass `--hermes-home <path>` only if Hermes does not live at ~/.hermes.\n4. **Choose how this agent should behave** (both optional, both per-agent):\n\n       --delivery-mode channel   CELLO acts like a normal chat channel (DEFAULT)\n       --delivery-mode wake      content-free notices; the agent reads/replies itself\n\n       --session-scope agent     one conversation per CELLO agent (DEFAULT)\n       --session-scope peer      one conversation per counterparty\n\n   Use `--session-scope peer` for anything customer-facing: under `agent` scope every\n   caller shares one conversation, so two customers' problems land in one context.\n   Omitting a flag on a re-run RESETS it to the default \u2014 it does not keep the old value.\n5. **Restart the gateway:** `hermes gateway restart`.\n6. **Verify.** Call the `cello_status` MCP tool and report the bound agent's state and\n   `standing_receiver_ready` AND `standing_receiver_reachability`. The bridge is live when the\n   agent shows online AND reachability reads `reserved`. `standing_receiver_ready` alone is TRUE\n   even for a receiver no relay would give a circuit reservation to \u2014 which, behind NAT, nobody can\n   dial. `retrying` means it is still working on it; `unreachable` means only peers that can\n   connect directly will get in.\n\n## How to operate CELLO (after setup)\n\n**In `channel` mode (the default):** a peer's message arrives as an ordinary message in the\nconversation and whatever you reply is sent back to them automatically. Do **not** call\n`cello_receive` or `cello_send` for the normal back-and-forth \u2014 the bridge does both, and\ndoing it yourself delivers the reply twice. The `cello_*` tools are still there for what the\nconversation cannot do: `cello_initiate_session`, `cello_close_session`, `cello_status`,\n`cello_sessions`, and pushing a message to a peer from a turn that did not come from them.\n\n**In `wake` mode:** notices are content-free \u2014 they name a session and a counterparty pubkey,\nnever the message. Fetch content with `cello_inbox` and `cello_receive`, then reply with\n`cello_send`. Read before you send, or the daemon rejects it with `session_not_current`.\n\n**Either mode:** answer `[SILENT]` only for a state-change notice that genuinely needs nothing\nfrom you \u2014 never when a peer has sent a message and is waiting.\n";
+export declare const HERMES_SKILL_MD = "---\nname: cello-bridge-setup\ndescription: \"Install and configure the CELLO agent-to-agent bridge for this Hermes instance.\"\nversion: 1.0.0\nplatforms: [linux, macos]\nmetadata:\n  hermes:\n    tags: [cello, messaging, integration, agent-to-agent]\n    related_skills: []\n---\n\n# CELLO Bridge Setup\n\nCELLO is a peer-to-peer identity and trust layer for agent-to-agent communication:\nsplit-key signing, tamper-evident hash chains, and content-free wake notifications.\nThis skill wires the local CELLO daemon into Hermes so this agent can talk to other\nCELLO agents anywhere.\n\nTrigger: /cello-bridge-setup, or \"install the CELLO bridge\".\n\n## Steps\n\n1. **Check CELLO is set up.** Run `cello status`. If the CLI is missing or the daemon\n   is not running, walk the user through CELLO onboarding first:\n   `npx --yes @cello-protocol/cli@latest login`, then `cello create-agent <name>`,\n   then `cello register-agent <name> <pre-auth-token>` (token from the CELLO Operations\n   Agent on Telegram). Confirm with `cello status`.\n2. **Pick the agent.** Ask the user which registered CELLO agent this Hermes instance\n   should bind to (the `cello status` output lists them).\n3. **Run the installer** \u2014 one command does all the work (plugin scaffold, env binding,\n   `hermes plugins enable cello`, `hermes mcp add cello`):\n\n       cello bridge hermes --agent <name>\n\n   Pass `--hermes-home <path>` only if Hermes does not live at ~/.hermes.\n4. **Choose how this agent should behave** (both optional, both per-agent):\n\n       --delivery-mode channel   CELLO acts like a normal chat channel (DEFAULT)\n       --delivery-mode wake      content-free notices; the agent reads/replies itself\n\n       --session-scope agent     one conversation per CELLO agent (DEFAULT)\n       --session-scope peer      one conversation per counterparty\n\n   Use `--session-scope peer` for anything customer-facing: under `agent` scope every\n   caller shares one conversation, so two customers' problems land in one context.\n   Omitting a flag on a re-run RESETS it to the default \u2014 it does not keep the old value.\n5. **Restart the gateway:** `hermes gateway restart`.\n6. **Verify.** Call the `cello_status` MCP tool and report the bound agent's state,\n   `standing_receiver_ready` and `standing_receiver_reachability`. The bridge is live when the\n   agent shows online and reachability reads `ready` \u2014 an idle agent holds no relay slot on\n   purpose, so `ready` IS the healthy answer and `reserved` only appears once a conversation is\n   running. **Do not treat `ready` as a failure or wait for `reserved`.** `unreachable` is the\n   one value worth acting on: only peers that can connect directly will get in.\n\n## How to operate CELLO (after setup)\n\n**In `channel` mode (the default):** a peer's message arrives as an ordinary message in the\nconversation and whatever you reply is sent back to them automatically. Do **not** call\n`cello_receive` or `cello_send` for the normal back-and-forth \u2014 the bridge does both, and\ndoing it yourself delivers the reply twice. The `cello_*` tools are still there for what the\nconversation cannot do: `cello_initiate_session`, `cello_close_session`, `cello_status`,\n`cello_sessions`, and pushing a message to a peer from a turn that did not come from them.\n\n**In `wake` mode:** notices are content-free \u2014 they name a session and a counterparty pubkey,\nnever the message. Fetch content with `cello_inbox` and `cello_receive`, then reply with\n`cello_send`. Read before you send, or the daemon rejects it with `session_not_current`.\n\n**Either mode:** answer `[SILENT]` only for a state-change notice that genuinely needs nothing\nfrom you \u2014 never when a peer has sent a message and is waiting.\n";
 //# sourceMappingURL=assets.d.ts.map

package/dist/hermes/assets.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"assets.d.ts","sourceRoot":"","sources":["../../src/hermes/assets.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG;AAEH,sEAAsE;AACtE,eAAO,MAAM,kBAAkB,w4CA6B9B,CAAC;AAEF;;;;;;;;;;;;GAYG;AACH,eAAO,MAAM,qBAAqB,QAkxCjC,CAAC;AAEF,wEAAwE;AACxE,eAAO,MAAM,eAAe,0qHAqE3B,CAAC"}
+{"version":3,"file":"assets.d.ts","sourceRoot":"","sources":["../../src/hermes/assets.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG;AAEH,sEAAsE;AACtE,eAAO,MAAM,kBAAkB,w4CA6B9B,CAAC;AAEF;;;;;;;;;;;;GAYG;AACH,eAAO,MAAM,qBAAqB,QAkxCjC,CAAC;AAEF,wEAAwE;AACxE,eAAO,MAAM,eAAe,+sHAqE3B,CAAC"}

package/dist/hermes/assets.js

@@ -1405,12 +1405,12 @@ Trigger: /cello-bridge-setup, or "install the CELLO bridge".
    caller shares one conversation, so two customers' problems land in one context.
    Omitting a flag on a re-run RESETS it to the default — it does not keep the old value.
 5. **Restart the gateway:** \`hermes gateway restart\`.
-6. **Verify.** Call the \`cello_status\` MCP tool and report the bound agent's state and
-   \`standing_receiver_ready\` AND \`standing_receiver_reachability\`. The bridge is live when the
-   agent shows online AND reachability reads \`reserved\`. \`standing_receiver_ready\` alone is TRUE
-   even for a receiver no relay would give a circuit reservation to — which, behind NAT, nobody can
-   dial. \`retrying\` means it is still working on it; \`unreachable\` means only peers that can
-   connect directly will get in.
+6. **Verify.** Call the \`cello_status\` MCP tool and report the bound agent's state,
+   \`standing_receiver_ready\` and \`standing_receiver_reachability\`. The bridge is live when the
+   agent shows online and reachability reads \`ready\` — an idle agent holds no relay slot on
+   purpose, so \`ready\` IS the healthy answer and \`reserved\` only appears once a conversation is
+   running. **Do not treat \`ready\` as a failure or wait for \`reserved\`.** \`unreachable\` is the
+   one value worth acting on: only peers that can connect directly will get in.
 
 ## How to operate CELLO (after setup)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cello-protocol/cli",
-  "version": "0.0.215",
+  "version": "0.0.217",
   "private": false,
   "type": "module",
   "engines": {
@@ -17,8 +17,8 @@
     "package.json"
   ],
   "dependencies": {
-    "@cello-protocol/daemon": "0.0.208",
-    "@cello-protocol/protocol-types": "0.0.88"
+    "@cello-protocol/daemon": "0.0.210",
+    "@cello-protocol/protocol-types": "0.0.90"
   },
   "devDependencies": {
     "@types/node": "^25.6.2"