@martian-engineering/lossless-claw 0.9.0 → 0.9.2

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/README.md CHANGED
@@ -79,14 +79,19 @@ If you're running from a local OpenClaw checkout, use:
79
79
  pnpm openclaw plugins install @martian-engineering/lossless-claw
80
80
  ```
81
81
 
82
- For local plugin development, link your working copy instead of copying files:
82
+ For local plugin development, build your working copy first, then link it instead of copying files:
83
83
 
84
84
  ```bash
85
+ cd /path/to/lossless-claw
86
+ pnpm build
87
+
85
88
  openclaw plugins install --link /path/to/lossless-claw
86
89
  # or from a local OpenClaw checkout:
87
90
  # pnpm openclaw plugins install --link /path/to/lossless-claw
88
91
  ```
89
92
 
93
+ Re-run `pnpm build` after local source changes so the linked plugin's `dist/` output stays current.
94
+
90
95
  The install command records the plugin, enables it, and applies compatible slot selection (including `contextEngine` when applicable).
91
96
 
92
97
  > **Note:** If your OpenClaw config uses `plugins.allow`, allowlist the plugin id `lossless-claw` plus any other active plugins you rely on. Do not add command tokens or aliases like `lossless` or `/lcm` to `plugins.allow`; that setting only accepts plugin ids. In some setups, narrowing the allowlist can prevent plugin-backed integrations from loading, even if `lossless-claw` itself is installed correctly. Restart the gateway after plugin config changes.
@@ -426,7 +431,7 @@ For most long-lived LCM setups, a good starting point is:
426
431
 
427
432
  ```bash
428
433
  # Build (bundles TypeScript to dist/index.js)
429
- npm run build
434
+ pnpm build
430
435
 
431
436
  # Run tests
432
437
  npx vitest