@karmaniverous/jeeves-watcher-openclaw 0.3.8 → 0.3.10

package/dist/index.js

@@ -265,7 +265,7 @@ function createMemoryTools(api, baseUrl) {
             });
             const minScore = typeof params.minScore === 'number' ? params.minScore : 0;
             const filtered = results.filter((r) => typeof r.score === 'number' && r.score >= minScore);
-            return ok(filtered);
+            return ok({ provider: 'jeeves-watcher', results: filtered });
         }
         catch (error) {
             state.initialized = false;
@@ -289,9 +289,9 @@ function createMemoryTools(api, baseUrl) {
                     ? Number(params.lines)
                     : lines.length - startIdx;
                 const sliced = lines.slice(startIdx, startIdx + count);
-                return ok(sliced.join('\n'));
+                return ok({ provider: 'jeeves-watcher', content: sliced.join('\n') });
             }
-            return ok(content);
+            return ok({ provider: 'jeeves-watcher', content });
         }
         catch (error) {
             return fail(error);

package/dist/skills/jeeves-watcher/SKILL.md

@@ -84,6 +84,54 @@ You don't need to know the rules in advance. The config is introspectable at run
 2. **Search** — use `watcher_search` with a natural language query and optional metadata filters
 3. **Read source** — use `read` (standard file read) with `file_path` from search results for full document content
 
+## Bootstrap (First Session)
+
+The first time the watcher plugin loads in a new deployment, orient yourself proactively. Don't wait for the user to ask a question — understand what you have access to.
+
+**Automatic bootstrap sequence:**
+
+1. **Health check** — call `watcher_status`. Confirm the service is running, note point count and collection dimensions.
+2. **Discover the deployment** — run the Orientation Pattern (see below): query `$.['description','search']` for organizational strategy and score thresholds, then `$.inferenceRules[*].['name','description']` for available record types.
+3. **Cache context** — store the orientation results mentally for the session. You now know what domains exist, what record types are searchable, and how to interpret scores.
+4. **Report readiness** — briefly tell the user what you found: how many points, which domains, any issues. One or two sentences, not a wall of text.
+
+**On subsequent sessions:** Repeat steps 1-3 silently. Only report if something changed (service down, point count dropped significantly, new domains appeared).
+
+**Key principle:** The agent drives discovery. The user shouldn't have to explain their archive to you — the archive explains itself through its config.
+
+## Install Modes
+
+The plugin supports two install modes, controlled by the `--memory` flag during installation:
+
+**Standard mode** (`npx @karmaniverous/jeeves-watcher-openclaw install`):
+- Registers `watcher_*` tools only (search, enrich, status, query, validate, config_apply, reindex, issues)
+- OpenClaw's built-in `memory-core` remains the memory provider
+- Use when the watcher is a supplementary search tool alongside native memory
+
+**Memory mode** (`npx @karmaniverous/jeeves-watcher-openclaw install --memory`):
+- Registers all tools: `watcher_*` plus `memory_search` and `memory_get`
+- Claims the OpenClaw memory slot — the watcher becomes the memory provider
+- MEMORY.md and memory/*.md files are indexed and searched via the watcher's vector store
+- Use when the watcher should be the single source of truth for both archive search and agent memory
+
+**How to tell which mode you're in:** Check the response from `memory_search` or `memory_get`. In memory mode (watcher-backed), responses include `"provider": "jeeves-watcher"`. In standard mode (memory-core), responses are bare arrays/strings with no `provider` field.
+
+## Proactive Posture
+
+**On your first `memory_search` or `memory_get` call each session, check the response for the `provider` field.**
+
+- **If the response is `{ provider: "jeeves-watcher", ... }`:** You're in memory mode. The watcher is serving memory. No action needed.
+- **If the response has any other shape** (bare array, bare string, different provider, no `provider` field): The watcher is NOT serving memory. Another provider is active. Check whether an upgrade is warranted.
+
+**When to suggest upgrading to memory mode:**
+Call `watcher_status` to check the archive size. If the watcher has >10K points, the deployment has a substantial archive and would benefit from semantic memory. Offer to run the upgrade yourself:
+
+> "I notice memory queries are running on flat file search, but the watcher has [N] points with semantic embeddings. I can upgrade to memory mode now — this runs `npx @karmaniverous/jeeves-watcher-openclaw install --memory` and restarts the gateway. Shall I go ahead?"
+
+If the user agrees, execute the install and gateway restart. Don't hand them a CLI command when you can do it yourself.
+
+**Don't nag.** Suggest once per session at most. If the user declines, drop it.
+
 ## Tools
 
 ### `memory_search`
@@ -92,7 +140,8 @@ Semantically search MEMORY.md and memory/*.md files. Powered by the watcher's ve
 - `maxResults` (number, optional) — maximum results to return
 - `minScore` (number, optional) — minimum similarity score threshold
 
-Returns: `[{ path, from, to, snippet, score }]` where `from`/`to` are 1-indexed line numbers.
+**Response (memory mode):** `{ provider: "jeeves-watcher", results: [{ path, from, to, snippet, score }] }` where `from`/`to` are 1-indexed line numbers.
+**Response (standard mode / memory-core):** `[{ path, from, to, snippet, score }]` — bare array, no `provider` field.
 
 ### `memory_get`
 Read content from MEMORY.md or memory/*.md files with optional line range.
@@ -100,6 +149,9 @@ Read content from MEMORY.md or memory/*.md files with optional line range.
 - `from` (number, optional) — line number to start reading from (1-indexed)
 - `lines` (number, optional) — number of lines to read
 
+**Response (memory mode):** `{ provider: "jeeves-watcher", content: "file content..." }`
+**Response (standard mode / memory-core):** `"file content..."` — bare string, no `provider` field.
+
 Path validation: only files within the workspace's MEMORY.md and memory/**/*.md are accessible.
 
 ### `watcher_search`

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "jeeves-watcher-openclaw",
   "name": "Jeeves Watcher",
   "description": "Semantic search, metadata enrichment, and instance administration for a jeeves-watcher deployment.",
-  "version": "0.3.8",
+  "version": "0.3.10",
   "skills": [
     "dist/skills/jeeves-watcher"
   ],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@karmaniverous/jeeves-watcher-openclaw",
-  "version": "0.3.8",
+  "version": "0.3.10",
   "author": "Jason Williscroft",
   "description": "OpenClaw plugin for jeeves-watcher — semantic search and metadata enrichment tools",
   "license": "BSD-3-Clause",