@darkelogix/openclaw-trusted-mode 1.0.6 → 1.0.7
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/CHANGELOG.md +4 -0
- package/openclaw.plugin.json +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -12,6 +12,10 @@ Terminology and acronyms: [`GLOSSARY.md`](./GLOSSARY.md).
|
|
|
12
12
|
## Unreleased
|
|
13
13
|
- No unreleased changes recorded.
|
|
14
14
|
|
|
15
|
+
## v1.0.7
|
|
16
|
+
- Replace the raw `LOCKDOWN_ONLY` / `UNSUPPORTED` certification block text with a clearer user-facing explanation that readonly governed validation is working and high-risk shell/write/delete actions remain intentionally disabled.
|
|
17
|
+
- Keep the policy behavior unchanged while improving what the OpenClaw UI shows after a blocked high-risk request.
|
|
18
|
+
|
|
15
19
|
## v1.0.6
|
|
16
20
|
- Add a runtime fallback that reads `plugins.entries.openclaw-trusted-mode.config` from `OPENCLAW_CONFIG_PATH` or `~/.openclaw/openclaw.json` when OpenClaw does not populate `api.config` on the hook-only plugin path.
|
|
17
21
|
- Preserve governed-mode settings written by `openclaw-trusted-mode-configure` even on OpenClaw builds that load the plugin with incomplete in-memory config injection.
|
package/openclaw.plugin.json
CHANGED
package/package.json
CHANGED