@karmaniverous/jeeves-meta-openclaw 0.14.0 → 0.15.0-1

package/README.md

@@ -1,16 +1,14 @@
 # @karmaniverous/jeeves-meta-openclaw
 
-OpenClaw plugin for [jeeves-meta](../service/). A thin HTTP client that registers interactive tools and uses [`@karmaniverous/jeeves`](https://github.com/karmaniverous/jeeves) core for managed TOOLS.md content writing and platform maintenance.
+OpenClaw plugin for [jeeves-meta](https://github.com/karmaniverous/jeeves-meta/tree/main/packages/service). A standard OpenClaw plugin and thin HTTP client that registers interactive tools on top of the [`@karmaniverous/jeeves`](https://github.com/karmaniverous/jeeves) core SDK. It writes no workspace files: static platform content is rendered by `jeeves install`, and live state is served by the tools.
 
 ## Features
 
 - **Twelve tools** — standard: `meta_status`, `meta_config`, `meta_config_apply`, `meta_service`; custom: `meta_list`, `meta_detail`, `meta_trigger`, `meta_preview`, `meta_seed`, `meta_unlock`, `meta_queue` (list/clear/abort), `meta_update`
 - **MetaServiceClient** — typed HTTP client delegating all operations to the running service
-- **TOOLS.md injection** — periodic refresh of entity stats, phase-state summary, failed-phase alerts, and next-phase indicator via `ComponentWriter` from `@karmaniverous/jeeves` (73-second prime interval)
 - **Phase-state awareness** — tools expose per-meta `_phaseState`, `owedPhase`, and phase-state summary from the service's phase-state machine
-- **Cleanup escalation** — passes `gatewayUrl` into `ComponentWriter` so managed-content cleanup can request a gateway session when needed
-- **Dependency health** — shows warnings when watcher/gateway are degraded
-- **Consumer skill** — `SKILL.md` for agent integration
+- **Lazy config** — registers with no config; `configRoot` is resolved when a tool needs it
+- **Consumer skill** — `jeeves-meta` skill shipped through the plugin manifest
 
 ## Plugin Lifecycle
 
@@ -18,24 +16,28 @@ OpenClaw plugin for [jeeves-meta](../service/). A thin HTTP client that register
 
 ## Install
 
+Install with the Jeeves CLI, which runs the OpenClaw install and writes the plugin config:
+
 ```bash
-npm install @karmaniverous/jeeves-meta-openclaw
+jeeves install meta --config-root j:/config
 ```
 
-Then run the CLI installer to register with the OpenClaw gateway:
+Or install it as a standard OpenClaw plugin and configure it yourself:
 
 ```bash
-npx @karmaniverous/jeeves-meta-openclaw install
+openclaw plugins install npm:@karmaniverous/jeeves-meta-openclaw@<version> --pin --accept-capabilities
 ```
 
+Restart the gateway afterwards. There is no plugin-specific installer (the `npx @karmaniverous/jeeves-meta-openclaw install` CLI was removed in favour of `jeeves install`).
+
 ## Configuration
 
-The plugin resolves settings via a three-step fallback chain: plugin config → environment variable → default.
+The plugin resolves settings via a fallback chain: plugin config → environment variable → default.
 
 | Setting | Plugin Config Key | Env Var | Default |
-|---------|-------------------|---------|---------|
+| --- | --- | --- | --- |
 | Service URL | `apiUrl` | `JEEVES_META_URL` | `http://127.0.0.1:1938` |
-| Config Root | `configRoot` | `JEEVES_CONFIG_ROOT` | `j:/config` |
+| Config Root | `configRoot` | `JEEVES_CONFIG_ROOT` | _none_ |
 
 ```json
 {
@@ -53,14 +55,21 @@ The plugin resolves settings via a three-step fallback chain: plugin config →
 }
 ```
 
-The `configRoot` setting tells `@karmaniverous/jeeves` core where to find the platform config directory. Core derives `{configRoot}/jeeves-meta/` for component-specific configuration.
+The `configRoot` setting tells `@karmaniverous/jeeves` core where to find the platform config directory. Core derives `{configRoot}/jeeves-meta/` for component-specific configuration. It has no default: `jeeves install --config-root <path>` writes it.
+
+`configRoot` is resolved **lazily**. Registration always succeeds without it (with a running gateway, `openclaw plugins install` activates the plugin before `jeeves install` writes its config), logging one warning:
+
+```text
+[jeeves-meta] configRoot not configured yet — meta_service install will be unavailable until it is set in plugin config or JEEVES_CONFIG_ROOT
+```
+
+Only `meta_service` with `action: "install"` reads it (core resolves the service config path from it); invoked without it, that call returns an error naming both ways to set it. Core `init()` runs the first time `configRoot` resolves. The other `meta_service` actions (`status`, `start`, `stop`, `restart`, `uninstall`) address the OS service by name, and every other tool only talks HTTP to the service at `apiUrl`, so all of them work without it.
 
 ## Documentation
 
 - **[Plugin Setup](guides/plugin-setup.md)** — installation, config, lifecycle
 - **[Tools Reference](guides/tools-reference.md)** — 12 tools: standard (meta_status, meta_config, meta_config_apply, meta_service) + custom (meta_list, meta_detail, meta_trigger, meta_preview, meta_seed, meta_unlock, meta_queue, meta_update)
 - **[Virtual Rules](guides/virtual-rules.md)** — watcher inference rules
-- **[TOOLS.md Injection](guides/tools-injection.md)** — dynamic prompt generation
 
 ## License