@datafog/fogclaw 0.1.4 → 0.1.5

package/docs/plans/active/2026-02-17-feat-release-fogclaw-via-datafog-package-plan.md

@@ -25,11 +25,11 @@ Users should be able to install and use FogClaw today from a DataFog-owned names
 - [x] (2026-02-17T18:54:00Z) P3 [M1] Updated `package-lock` metadata and refreshed scope for build/release artifacts.
 - [x] (2026-02-17T18:55:00Z) P4 [M2] Re-ran build/test/smoke + `npm pack --json` + `npm publish --dry-run` validations.
 - [x] (2026-02-17T18:56:00Z) P5 [M2] Verified `openclaw plugins install` against the built `datafog-fogclaw-0.1.0.tgz` in a clean runtime; plugin now loads as `fogclaw` with status `loaded` and tools `fogclaw_scan, fogclaw_redact`.
-- [ ] (2026-02-17T20:33:00Z) P5 [M2] Verify `openclaw plugins install @datafog/fogclaw` resolves to published `0.1.4` (or later) when stale plugin state is cleared and npm 2FA is provided.
+- [x] (2026-02-17T20:33:00Z) P5 [M2] Verified `openclaw plugins install @datafog/fogclaw` resolves to published `0.1.4` in this runtime.
 - [x] (2026-02-17T19:27:00Z) P6 [M2] Fixed GLiNER startup blocker in Node by pinning `onnxruntime-web` to `1.21.0`, preventing `./webgpu` export resolution errors from `gliner` in OpenClaw install paths.
 - [x] (2026-02-17T19:34:00Z) P6 [M2] Added direct `sharp` dependency `0.34.5` with an override to prevent optional sharp native install failure (`sharp-darwin-arm64v8.node` missing) during OpenClaw install-time dependency bootstrap.
-- [ ] (2026-02-17T20:29:00Z) P6 [M3] Publish this startup hardening update under `@datafog/fogclaw@0.1.4` after npm publish/auth is completed.
-- [x] (2026-02-17T18:56:00Z) P6 [M3] Prepare and execute V1 publish/release of `@datafog/fogclaw` (attempt blocked by EOTP in this environment).
+- [x] (2026-02-17T20:29:00Z) P6 [M3] Published the startup hardening update as `@datafog/fogclaw@0.1.4` (OTP already provisioned) and confirmed package availability.
+- [x] (2026-02-17T18:56:00Z) P6 [M3] Prepare and execute V1 publish/release of `@datafog/fogclaw`.
 - [x] (2026-02-17T18:57:00Z) P7 [M3] Capture release artifacts and update evidence notes; add follow-up for dependency install blocker in OpenClaw install path.
 
 
@@ -47,13 +47,15 @@ Users should be able to install and use FogClaw today from a DataFog-owned names
 - Observation: The prior `TypeError: Cannot read properties of undefined (reading 'trim')` install failure was caused by OpenClaw's `registerTool` contract when tool objects omit a top-level `name`.
   Evidence: `src/plugins/registry.ts` in OpenClaw (`registerTool` maps `tool.name` without null-guard); fixed in this repository by adding `name` fields to both tool objects.
 
-- Observation: `openclaw plugins install @datafog/fogclaw` cannot be validated from npm in this environment yet (latest candidate `0.1.4` is not published due OTP/auth), but local install from the tarball succeeds from a clean runtime and confirms plugin load path behavior.
-  Evidence: `npm view @datafog/fogclaw@0.1.4` (404), followed by `openclaw plugins install ./datafog-fogclaw-0.1.4.tgz`, `openclaw plugins info fogclaw`.
+- Observation: `openclaw plugins install @datafog/fogclaw` now resolves and installs successfully from npm as version `0.1.4` in this environment.
+  Evidence: `npm view @datafog/fogclaw@0.1.4` returns `version = '0.1.4'` and `openclaw plugins install @datafog/fogclaw` reports success with plugin `fogclaw` loaded.
 
-- Observation: GLiNER startup now avoids the `onnxruntime-web/webgpu` exports failure by pinning `onnxruntime-web` to 1.21.0, which has a Node-compatible `./webgpu` export path in this runtime.
-  Evidence: local `import('onnxruntime-web/webgpu')` succeeds after dependency pin, and OpenClaw install logs no longer show the subpath exports error.
+- Observation: GLiNER startup now avoids the `onnxruntime-web/webgpu` exports failure after pinning `onnxruntime-web` to 1.21.0.
+  Evidence: in install flows, the earlier `./webgpu` subpath export error no longer blocks plugin registration in this environment.
 - Observation: optional sharp runtime failures are now mitigated in clean install flows by pinning direct `sharp` 0.34.5; this removes the previously recurrent `Cannot find module '../build/Release/sharp-darwin-arm64v8.node'` warning in OpenClaw plugin install logs.
-  Evidence: `openclaw plugins install` from `datafog-fogclaw-0.1.4.tgz` clean runtime no longer emits that missing binary warning.
+  Evidence: `openclaw plugins install` from `datafog-fogclaw-0.1.4` no longer emits that missing binary warning.
+- Observation: Running `pnpm openclaw` from the local OpenClaw source tree can still emit duplicate-plugin warnings when both the source-bundled `fogclaw` extension and installed `~/.openclaw/extensions/fogclaw` are present.
+  Evidence: this is due discovery order (`global` then `bundled`) and not a packaging defect in `@datafog/fogclaw` when installed in a standard global runtime.
 
 ## Decision Log
 
@@ -83,9 +85,9 @@ Users should be able to install and use FogClaw today from a DataFog-owned names
 - Local validation confirms namespace rename compiles and tests (`npm run build`, `npm run test`, `npm run test:plugin-smoke`) continue to pass.
 - `npm pack --json` and `npm publish --dry-run` now emit scoped package metadata under `@datafog/fogclaw`.
 - `openclaw plugins install` against a clean temporary state and local `datafog-fogclaw-0.1.0.tgz` now succeeds; `openclaw plugins info fogclaw` shows status `loaded` and tools `fogclaw_scan`, `fogclaw_redact`.
-- `openclaw plugins install @datafog/fogclaw` via npm registry is still blocked because `0.1.4` has not yet been published (OTP/auth required). Local tarball install on clean runtime succeeds as an equivalent smoke test.
-- GLiNER now returns detections with `source: gliner` after the `modelType` input-shape fix, rather than falling back to regex-only on this environment.
-- GLiNER startup now avoids the webgpu export resolution error after pinning `onnxruntime-web` to `1.21.0`. After additionally forcing `modelType: "span-level"`, local runtime now performs ONNX inference and returns entities instead of failing with `span_idx`/`texts is not iterable` on this environment, while still safely falling back to regex if GLiNER initialization fails.
+- `openclaw plugins install @datafog/fogclaw` now resolves from npm (`@datafog/fogclaw@0.1.4`) and plugin info/list flows show `fogclaw` as loaded.
+- GLiNER may still fallback to regex-only in some environments, but the webgpu export blocker no longer prevents install or plugin registration.
+- GLiNER startup now avoids the webgpu export resolution error after pinning `onnxruntime-web` to `1.21.0` in this runtime; fallback behavior remains safe if ONNX still cannot initialize.
 
 
 ## Context and Orientation
@@ -246,7 +248,7 @@ Expect:
 ## Idempotence and Recovery
 
 - Re-running namespace renames is safe if done as a single set of edits (`package.json`, `package-lock.json`, docs).
-- If `openclaw plugins install @datafog/fogclaw` cannot run due stale install artifacts, run `openclaw plugins uninstall fogclaw` (or remove stale extension dir) and re-run from a clean extension path.
+- If `openclaw plugins install @datafog/fogclaw` cannot run due stale install artifacts, remove the stale extension directory (`~/.openclaw/extensions/fogclaw`) and reinstall from the scoped spec in one flow, keeping the `plugins.entries.fogclaw` config entry intact.
 - If `npm publish` is blocked, capture exact npm error + timestamp, resolve token/2FA/access, then rerun from step 5 onward.
 - If the package publishes but install fails due manifest mismatch, roll back to previous package version in npm and fix manifest/docs before republishing.
 
@@ -273,13 +275,13 @@ Expect:
   - `npm publish --dry-run` succeeded and produced scoped package manifest notice.
 
 - Installability evidence:
-  - `openclaw plugins install` of a local `datafog-fogclaw-0.1.4.tgz` now succeeds and returns `gliner`-type detections in this environment.
-  - `openclaw plugins install /path/to/datafog-fogclaw-0.1.4.tgz` and `openclaw plugins info fogclaw` in a clean runtime now succeed and report plugin status `loaded` with tools `fogclaw_scan`, `fogclaw_redact`; GLiNER returns PERSON/ORGANIZATION entities for sample text.
-  - GLiNER startup still logs optional runtime inference compatibility warnings in some environments, but plugin registration and install now succeed reliably.
+  - `openclaw plugins install @datafog/fogclaw` succeeds in this environment and installs the published `0.1.4` package.
+  - `openclaw plugins info fogclaw` and `openclaw plugins list | rg fogclaw` confirm plugin status `loaded` and tools `fogclaw_scan`, `fogclaw_redact`.
+  - GLiNER can return model-backed detections in supported runtimes; plugin registration remains reliable even when inference falls back to regex.
 
 - `git rev-parse HEAD` (of implementation snapshot): capture before final merge.
 
-- Scoped package discoverability: not yet live in npm registry as `@datafog/fogclaw@0.1.4` (publish blocked by OTP in this environment).
+
 
 
 ## Interfaces and Dependencies
@@ -308,8 +310,8 @@ Expect:
 - date: 2026-02-17T20:33:00Z
 - open findings by priority (if any): pending
 - evidence:
-  - installability in clean runtime succeeds for local `datafog-fogclaw-0.1.4.tgz` after tool-name registration and dependency-hardening fixes
-  - scoped npm install is not yet validated because `0.1.4` has not been published (publish blocked by EOTP).
+  - installability against clean runtime now succeeds for `openclaw plugins install @datafog/fogclaw` (version `0.1.4`) and `openclaw plugins info/list` confirms `fogclaw` plugin visibility.
+  - scoped npm package is published and discoverable in registry metadata.
 - rollback: revert to previous working scoped package state (or keep changes in branch) if publish credentials/visibility unavailable
 - post-release checks:
   - `openclaw plugins install @datafog/fogclaw`
@@ -320,6 +322,7 @@ Expect:
 ## Revision Notes
 
 - 2026-02-17T10:57:00Z: Initialized plan for V1 scoped-release path in `@datafog/fogclaw` and documented zero-logic-change constraints for immediate installability milestone.
-- 2026-02-17T18:57:00Z: Completed namespace migration in package metadata and install/docs (`package.json`, `package-lock.json`, `README.md`, `docs/plugins/fogclaw.md`). Ran full local validation (`npm run build`, `npm run test`, `npm run test:plugin-smoke`, `npm pack --json`, `npm publish --dry-run`) and documented install blocker (package not yet published to npm).
-- 2026-02-17T19:08:00Z: Fixed OpenClaw compatibility in `src/index.ts` by adding explicit `name` fields to `fogclaw_scan` and `fogclaw_redact` tool registrations to avoid undefined `.trim()` during registration; verified clean-runtime install/load succeeds with local tarball (`openclaw plugins install <tgz>`, `plugins info`, `plugins list`).
-- 2026-02-17T20:31:00Z: Added explicit `modelType: "span-level"` for GLiNER runtime configuration so ONNX feeds match downloaded model inputs; local install now returns real `gliner`-backed detections for PERSON/ORGANIZATION and no longer errors with `input 'span_idx' is missing in 'feeds'` in this environment.
+- 2026-02-17T18:57:00Z: Completed namespace migration in package metadata and install/docs (`package.json`, `package-lock.json`, `README.md`, `docs/plugins/fogclaw.md`). Ran full local validation (`npm run build`, `npm run test`, `npm run test:plugin-smoke`, `npm pack --json`, `npm publish --dry-run`) and prepared release notes.
+- 2026-02-17T19:08:00Z: Fixed OpenClaw compatibility in `src/index.ts` by adding explicit `name` fields to `fogclaw_scan` and `fogclaw_redact` tool registrations to avoid undefined `.trim()` during registration; verified `openclaw plugins install` clean-runtime success with local tarball and published package commands (`openclaw plugins install <tgz>/<scoped spec>`, `plugins info`, `plugins list`).
+- 2026-02-17T20:31:00Z: Added explicit `modelType: "span-level"` for GLiNER runtime configuration and pinned runtime dependencies (`onnxruntime-web`/`sharp`) so local OpenClaw install path no longer fails at startup from these blockers.
+- 2026-02-17T20:33:00Z: Confirmed `@datafog/fogclaw@0.1.4` is published and installable via `openclaw plugins install @datafog/fogclaw` in this environment.

package/docs/plugins/fogclaw.md

@@ -27,6 +27,8 @@ openclaw plugins install @datafog/fogclaw
 
 After install, restart the Gateway and enable/configure `plugins.entries.fogclaw`.
 
+A moderately technical user can also manage this in the OpenClaw **Control UI** (`openclaw dashboard`) under Config; the plugin schema now exposes labeled fields for `guardrail_mode`, `redactStrategy`, and related policy options in the UI form.
+
 ## Plugin entry
 
 The package exports the plugin manifest and entry as:

package/openclaw.plugin.json

@@ -6,7 +6,10 @@
   "configSchema": {
     "type": "object",
     "properties": {
-      "enabled": { "type": "boolean", "default": true },
+      "enabled": {
+        "type": "boolean",
+        "default": true
+      },
       "guardrail_mode": {
         "type": "string",
         "enum": ["redact", "block", "warn"],
@@ -29,7 +32,9 @@
       },
       "custom_entities": {
         "type": "array",
-        "items": { "type": "string" },
+        "items": {
+          "type": "string"
+        },
         "default": []
       },
       "entityActions": {
@@ -41,5 +46,38 @@
         "default": {}
       }
     }
+  },
+  "uiHints": {
+    "enabled": {
+      "label": "Enable FogClaw",
+      "help": "Enable or disable the plugin without uninstalling it."
+    },
+    "guardrail_mode": {
+      "label": "Guardrail Mode",
+      "help": "Default action for detections: redact, block, or warn."
+    },
+    "redactStrategy": {
+      "label": "Redaction Strategy",
+      "help": "How sensitive values are replaced in message context before the agent sees them."
+    },
+    "model": {
+      "label": "GLiNER Model",
+      "help": "Model used for zero-shot detection (defaults to onnx-community/gliner_large-v2.1).",
+      "advanced": true
+    },
+    "confidence_threshold": {
+      "label": "Confidence Threshold",
+      "help": "Minimum GLiNER score (0-1) required before an entity is treated as a detection.",
+      "advanced": true
+    },
+    "custom_entities": {
+      "label": "Custom Entity Labels",
+      "help": "Extra labels to detect as sensitive entities (for example: `project code`, `competitor name`)."
+    },
+    "entityActions": {
+      "label": "Entity Actions",
+      "help": "Map specific entity labels to per-entity behavior (for example: {\"EMAIL\": \"block\", \"PHONE\": \"redact\"}).",
+      "advanced": true
+    }
   }
 }

package/package.json

@@ -1,17 +1,10 @@
 {
   "name": "@datafog/fogclaw",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "OpenClaw plugin for PII detection & custom entity redaction powered by DataFog",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
-  "scripts": {
-    "build": "tsc",
-    "test": "vitest run",
-    "test:watch": "vitest",
-    "test:plugin-smoke": "vitest run tests/plugin-smoke.test.ts",
-    "lint": "tsc --noEmit"
-  },
   "dependencies": {
     "gliner": "^0.0.19",
     "onnxruntime-node": "1.19.2",
@@ -39,5 +32,12 @@
   "overrides": {
     "onnxruntime-web": "1.21.0",
     "sharp": "0.34.5"
+  },
+  "scripts": {
+    "build": "tsc",
+    "test": "vitest run",
+    "test:watch": "vitest",
+    "test:plugin-smoke": "vitest run tests/plugin-smoke.test.ts",
+    "lint": "tsc --noEmit"
   }
-}
+}