shroud-privacy 2.2.18 → 2.2.20

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
@@ -85,7 +85,7 @@ Shroud does not guarantee compliance — regex-based detection has limitations (
85
85
  - **Formal minimum supported version:** `2026.3.24` (from `openclaw.plugin.json` `minOpenClawVersion`).
86
86
  - **Release validation matrix (this release):**
87
87
  - **Baseline:** `2026.3.28` (includes WhatsApp E2E path)
88
- - **Latest-at-release:** `2026.4.5` (Slack E2E path)
88
+ - **Latest-at-release:** `2026.4.9` (full 192-scenario E2E pass)
89
89
  - **Latest caveat:** on OpenClaw builds where WhatsApp provisioning via `channels add` is unsupported, latest-focused compat runs skip WhatsApp E2E and validate Slack E2E.
90
90
  - **Source of truth for current matrix:** `docs/ci-current-state.md` and `CHANGELOG.md`.
91
91
 
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "id": "shroud-privacy",
3
3
  "name": "Shroud",
4
- "version": "2.2.17",
4
+ "version": "2.2.20",
5
5
  "description": "Privacy obfuscation with deterministic fake values and deobfuscation — PII never reaches the LLM, tool calls still work",
6
6
  "configSchema": {
7
7
  "type": "object",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "shroud-privacy",
3
- "version": "2.2.18",
3
+ "version": "2.2.20",
4
4
  "description": "Privacy and infrastructure protection for AI agents — detects sensitive data (PII, network topology, credentials, OT/SCADA) and replaces with deterministic fakes before anything reaches the LLM.",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",