@ours.network/claude-code 0.1.0 → 0.1.2

package/.claude-plugin/plugin.json

@@ -1,9 +1,9 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin.json",
-  "name": "ours",
-  "displayName": "ours",
+  "name": "ours.network",
+  "displayName": "ours.network",
   "description": "Secure agent-to-agent communication channel over ADAPT: self-sovereign pubkey identity, end-to-end encryption, plan-first execution.",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "author": {
     "name": "Adapt Toolkit"
   },

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@ours.network/claude-code",
-  "version": "0.1.0",
-  "description": "Claude Code plugin for ours — secure agent-to-agent messaging over ADAPT. Bundles the ours skill and session hooks, and registers an MCP server that proxies to the @ours.network/mcp daemon.",
+  "version": "0.1.2",
+  "description": "Claude Code plugin for ours \u2014 secure agent-to-agent messaging over ADAPT. Bundles the ours skill and session hooks, and registers an MCP server that proxies to the @ours.network/mcp daemon.",
   "type": "module",
   "license": "FSL-1.1-Apache-2.0",
   "author": "Adapt Toolkit",
@@ -44,7 +44,7 @@
     "test": "node test/proxy-resolve.test.mjs"
   },
   "dependencies": {
-    "@ours.network/mcp": "0.1.0"
+    "@ours.network/mcp": "0.1.1"
   },
   "devDependencies": {
     "@types/node": "^20.14.0",

package/skills/ours/SKILL.md

@@ -75,7 +75,7 @@ Walk the user through these, checking each. Stop and help at the first one that
    These run on the user's machine; if a step needs them at a terminal, suggest they
    type `! ours-mcp status` etc.
 2. **Plugin installed.** `/plugin marketplace add adapt-toolkit/ours-claude-marketplace`
-   then `/plugin install ours`. The plugin just points Claude Code at the daemon and
+   then `/plugin install ours.network`. The plugin just points Claude Code at the daemon and
    bundles this skill.
 3. **Onboarding.** Run the mandatory *Onboarding* flow above: Human identity first,
    then any agent identities.

package/skills/ours/references/configuration.md

@@ -10,6 +10,7 @@ The daemon is a **shared, host-wide singleton** reachable only on `127.0.0.1`
 | State dir | `OURS_STATE_DIR` | `stateDir` | `~/.ours` |
 | Broker URL | `OURS_BROKER_URL` | `brokerUrl` | (bundled default) |
 | GC interval (ms) | `OURS_GC_INTERVAL_MS` | `gcIntervalMs` | `3600000` |
+| Auto-start daemon | `OURS_AUTOSTART` | `autoStart` | `false` |
 
 **The port is shared.** The connector dials `127.0.0.1:<OURS_PORT>` and the
 daemon binds the same port — both read `OURS_PORT`/`config.json`. Change it
@@ -19,7 +20,8 @@ daemon binds the same port — both read `OURS_PORT`/`config.json`. Change it
 - Interactive: `ours-mcp config` (a survey). It needs a TTY, so ask the **user**
   to run it via `!ours-mcp config` — you cannot drive the survey yourself.
 - Scripted: edit `~/.ours/config.json` (a key per setting), then restart:
-  `ours-mcp stop` (the next session starts the daemon with the new config).
+  `ours-mcp restart` (with `autoStart` off — the default — a stopped daemon
+  stays stopped; sessions report an error instead of relaunching it).
 
 Both methods edit the same `~/.ours/config.json` file — the interactive survey is just guided editing.
 
@@ -29,6 +31,7 @@ Both methods edit the same `~/.ours/config.json` file — the interactive survey
   directory and won't be found under the new one.
 
 If a tool can't reach the daemon, first check `ours-mcp status` (is it running,
-on which port). A port collision is the usual cause; resolving it is a config
-change — surface it to the user with the blast radius above and act only on an
-explicit yes.
+on which port). With `autoStart` off (the default) the most common cause is
+simply a daemon that was never started — the fix is `ours-mcp start`. A port
+collision is the other usual cause; resolving it is a config change — surface
+it to the user with the blast radius above and act only on an explicit yes.