@nowledge/openclaw-nowledge-mem 0.8.34 → 0.8.35

package/CHANGELOG.md

@@ -4,6 +4,11 @@ All notable changes to the Nowledge Mem OpenClaw plugin will be documented in th
 
 ## Unreleased
 
+## [0.8.35] - 2026-10-08
+
+- Align ClawHub-first code-plugin install metadata with the supported host baseline.
+- Publish the scoped code plugin and npm package through GitHub OIDC with independent artifact receipts. Memory and capture behavior are unchanged.
+
 ## [0.8.34] - 2026-08-31
 
 - Fixed automatic capture for agent-scoped OpenClaw 2.0 Incognito session keys.

package/README.md

@@ -19,7 +19,7 @@ the user intentionally asks Mem to keep.
 ## Installation
 
 ```bash
-openclaw plugins install clawhub:nowledge-mem
+openclaw plugins install clawhub:@nowledge/openclaw-nowledge-mem
 ```
 
 OpenClaw's installer writes the install record, enables the plugin, and switches the `memory` slot to `openclaw-nowledge-mem`. On current OpenClaw builds, that same install flow may also set `plugins.slots.contextEngine` to `openclaw-nowledge-mem`. Plugin `0.8.18+` accepts that automatically as a compatibility alias.
@@ -35,7 +35,7 @@ If `openclaw config get tools` shows a restrictive profile such as `coding`, pre
 To update the plugin, re-run the ClawHub install with `--force`:
 
 ```bash
-openclaw plugins install clawhub:nowledge-mem --force
+openclaw plugins install clawhub:@nowledge/openclaw-nowledge-mem --force
 ```
 
 Use this instead of `openclaw plugins update openclaw-nowledge-mem` when an old install record is pinned to a specific version.
@@ -543,7 +543,7 @@ If you also use linked or workspace copies, review `plugins.load.paths` before r
 The memory slot is probably still set to the built-in `memory-core`. OpenClaw 3.22+ defaults to `memory-core` when no explicit slot is configured. Reinstall to reset the slot automatically:
 
 ```bash
-openclaw plugins install clawhub:nowledge-mem
+openclaw plugins install clawhub:@nowledge/openclaw-nowledge-mem
 ```
 
 Or set the slot manually in `~/.openclaw/openclaw.json`:

package/SKILL.md

@@ -105,7 +105,7 @@ Success means the backend responds correctly through `nmem`. Do not skip this st
 Default install:
 
 ```bash
-openclaw plugins install clawhub:nowledge-mem
+openclaw plugins install clawhub:@nowledge/openclaw-nowledge-mem
 ```
 
 If this fails with `archive integrity mismatch`, update OpenClaw first, then
@@ -114,7 +114,7 @@ retry. Current ClawHub packages require OpenClaw 2026.5.3 or later.
 To update an existing install:
 
 ```bash
-openclaw plugins install clawhub:nowledge-mem --force
+openclaw plugins install clawhub:@nowledge/openclaw-nowledge-mem --force
 ```
 
 Alternatively, if the user is installing from OpenClaw's default registry rather than ClawHub, this also works:
@@ -232,7 +232,7 @@ If only `memory_search` and `memory_get` tools are available (other Nowledge Mem
 }
 ```
 
-If missing, reinstall (`openclaw plugins install clawhub:nowledge-mem`) which sets the slot automatically. This is common after upgrading OpenClaw to 3.22+ where the default memory slot changed.
+If missing, reinstall (`openclaw plugins install clawhub:@nowledge/openclaw-nowledge-mem`) which sets the slot automatically. This is common after upgrading OpenClaw to 3.22+ where the default memory slot changed.
 
 Then verify in chat.
 
@@ -282,7 +282,7 @@ What to expect:
 | `nmem --json status` fails in local mode | Start Nowledge Mem locally first |
 | Remote mode fails | Re-run `nmem --json --api-url ... status` with the exact URL and auth you plan to use |
 | `openclaw nowledge-mem status` fails after install | Restart OpenClaw and confirm the plugin was installed successfully |
-| ClawHub reports `archive integrity mismatch` | Update OpenClaw to 2026.5.3+ or latest, then reinstall with `openclaw plugins install clawhub:nowledge-mem --force` |
+| ClawHub reports `archive integrity mismatch` | Update OpenClaw to 2026.5.3+ or latest, then reinstall with `openclaw plugins install clawhub:@nowledge/openclaw-nowledge-mem --force` |
 | `plugins.allow is empty` warning | Add `openclaw-nowledge-mem` to `plugins.allow` if the user wants explicit trust |
 | Remote config seems ignored | Check whether `~/.nowledge-mem/openclaw.json` is overriding plugin settings |
 | Local mode unexpectedly talks to a remote server | Check for stale `NMEM_API_URL` / `NMEM_API_KEY` in the environment or an overriding `~/.nowledge-mem/openclaw.json` |

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
 	"id": "openclaw-nowledge-mem",
 	"name": "Nowledge Mem",
 	"description": "Cross-tool knowledge graph memory for OpenClaw with startup context, graph search, and session distillation.",
-	"version": "0.8.34",
+	"version": "0.8.35",
 	"kind": ["memory", "context-engine"],
 	"contracts": {
 		"tools": [

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@nowledge/openclaw-nowledge-mem",
 	"displayName": "Nowledge Mem for OpenClaw",
-	"version": "0.8.34",
+	"version": "0.8.35",
 	"type": "module",
 	"description": "Nowledge Mem memory plugin for OpenClaw, local-first personal knowledge base",
 	"author": {
@@ -29,7 +29,7 @@
 			"./src/index.js"
 		],
 		"install": {
-			"clawhubSpec": "clawhub:nowledge-mem",
+			"clawhubSpec": "clawhub:@nowledge/openclaw-nowledge-mem",
 			"npmSpec": "@nowledge/openclaw-nowledge-mem",
 			"defaultChoice": "clawhub"
 		},