gm-skill 2.0.2495 → 2.0.2497

package/bin/plugkit-slim.wasm.sha256

@@ -1 +1 @@
-34be2c21ecc4da19b821bc947b99c19a7ebb9219dd6509364f6005d55873f58c  plugkit-slim.wasm
+017303c78b6dbe30924660e5866f1c900566378e2e2a5ead26d71b93c270c22a  plugkit-slim.wasm

package/bin/plugkit.version

@@ -1 +1 @@
-0.1.1190
+0.1.1191

package/bin/plugkit.wasm.sha256

@@ -1 +1 @@
-fa876c06e0042d6bae16ef2c0396a95e2092226692d9bc7b9c7bced584d2fc90  plugkit.wasm
+643494c20d039446c588b35fc20aadc2d86fc3bf3735dfb5614ae270b255c086  plugkit.wasm

package/gm-plugkit/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-plugkit",
-  "version": "2.0.2495",
+  "version": "2.0.2497",
   "description": "Bootstrap and daemon-spawn tool for gm plugkit binary. Downloads the correct platform wasm, verifies SHA256, and launches agentplug-runner (the native wasm host) as the spool watcher daemon.",
   "main": "index.js",
   "bin": {

package/gm-plugkit/plugkit-slim.wasm.sha256

@@ -1 +1 @@
-34be2c21ecc4da19b821bc947b99c19a7ebb9219dd6509364f6005d55873f58c  plugkit-slim.wasm
+017303c78b6dbe30924660e5866f1c900566378e2e2a5ead26d71b93c270c22a  plugkit-slim.wasm

package/gm-plugkit/plugkit.version

@@ -1 +1 @@
-0.1.1190
+0.1.1191

package/gm.json

@@ -1,6 +1,6 @@
 {
   "name": "gm",
-  "version": "2.0.2495",
+  "version": "2.0.2497",
   "description": "Spool-dispatch orchestration engine with unified state machine, skills, and automated git enforcement",
   "author": "AnEntrypoint",
   "license": "MIT",
@@ -17,5 +17,5 @@
   "publishConfig": {
     "access": "public"
   },
-  "plugkitVersion": "0.1.1190"
+  "plugkitVersion": "0.1.1191"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-skill",
-  "version": "2.0.2495",
+  "version": "2.0.2497",
   "description": "Canonical universal harness — AI-native software engineering via skill-driven orchestration; bootstraps plugkit for task execution and session isolation. Install in any AI coding agent host.",
   "author": "AnEntrypoint",
   "license": "MIT",

package/skills/agent-memory/SKILL.md

@@ -62,6 +62,33 @@ Zero-config works for basic capability. Production tuning groups: `capture`, `ex
 
 Use the migration tool documented at `MemoryCore/scripts/migrate-v2-to-v3/README.md` in the repo. New installs skip this.
 
+### 4. Migrating gm's own memories into the `tencentdb_backend` store
+
+Distinct from #3 above (that's the standalone system's own internal format
+evolution). This is for a project that already has gm-native memories
+(`.gm/memories/*.md`, written by `memorize`/`memorize-fire` before
+`memory.tencentdb_backend` was enabled) and wants them carried over once a
+namespace opts into the Tencent-compatible backend, so recall doesn't go
+cold on the switch.
+
+Dispatch the `tencentdb-memory-import` verb: `{"source_namespace":
+"default", "dest_namespace": "<routed-namespace>", "kind": "l1"}`. It reads
+every `.md` doc in the source namespace, re-embeds through gm's own
+384-dim pipeline, and writes into the destination via
+`tencentdb_memory::write_cfg`. It refuses up front unless
+`dest_namespace`'s resolved `memory.tencentdb_backend.vectors_db_dims` is
+exactly `384` -- gm's embedder cannot produce vectors at any other width,
+and a namespace configured for externally-embedded 768-dim content (the
+default) cannot safely receive them (recall queries that namespace through
+the project-resolved dim, not a per-import override, so a dim mismatch
+there is a real defect, not a formality). A project wanting both kinds of
+content needs two separate `tencentdb_backend`-routed namespaces, each at
+its own dim.
+
+This is a one-way copy, not a move: the source `.md` files and their
+`rssearch_vectors` index rows are untouched, so the default backend keeps
+working for any namespace not also switched over.
+
 ## Verification (do this before declaring setup done)
 
 1. Confirm version prerequisites: `node -v` (`>=22.16`), and `openclaw --version` (`>=2026.3.13`) if using the OpenClaw plugin path.