@bamdra/bamdra-user-bind 0.1.10 → 0.1.12

package/README.md

@@ -1,9 +1,22 @@
 # bamdra-user-bind
 
+![Bamdra Animated Logo](./docs/assets/bamdra-logo-animated.svg)
+
 The identity and living profile layer for the Bamdra suite.
 
 It can run independently, and it is also auto-provisioned by `bamdra-openclaw-memory`.
 
+Install directly:
+
+```bash
+openclaw plugins install @bamdra/bamdra-user-bind
+```
+
+Release package:
+
+- GitHub Releases: https://github.com/bamdra/bamdra-user-bind/releases
+- You can also build a local release bundle with `pnpm package:release`
+
 [中文文档](./README.zh-CN.md)
 
 ## What it does
@@ -12,12 +25,20 @@ It can run independently, and it is also auto-provisioned by `bamdra-openclaw-me
 
 It also becomes the user's evolving profile layer, including:
 
-- preferred address
+- `userId`-scoped preferred address
 - timezone
 - tone preferences
 - role
 - long-lived user notes
 
+## Profile Policy
+
+- `userId` is the primary key for personalization
+- preferred address should live in the bound profile, not in scattered workspace `USER.md` files
+- workspace `USER.md` should stay minimal and only keep environment facts
+- if the current turn explicitly asks for a different address, follow the current turn
+- admin tools are for repair, merge, audit, and sync, not for blind bulk rewriting
+
 ## Why it matters
 
 Without an identity layer:
@@ -51,6 +72,11 @@ The Markdown mirror is for humans, so profiles stay editable like a living per-u
 - keep profile mirrors private
 - let humans edit the mirror gradually
 - use admin tools only for audit, merge, repair, and maintenance
+- when updating how someone is addressed, update the bound profile for that `userId` first
+
+## Architecture
+
+![Bamdra Suite Architecture](./docs/assets/architecture-technical-en.svg)
 
 ## What it unlocks
 
@@ -66,3 +92,4 @@ With `bamdra-memory-vector`:
 
 - [GitHub organization](https://github.com/bamdra)
 - [Repository](https://github.com/bamdra/bamdra-user-bind)
+- [Releases](https://github.com/bamdra/bamdra-user-bind/releases)

package/README.zh-CN.md

@@ -1,9 +1,22 @@
 # bamdra-user-bind
 
+![Bamdra Animated Logo](./docs/assets/bamdra-logo-animated.svg)
+
 Bamdra 套件中的身份与“活画像”层。
 
 它可以独立运行，也会被 `bamdra-openclaw-memory` 自动补齐。
 
+单独安装：
+
+```bash
+openclaw plugins install @bamdra/bamdra-user-bind
+```
+
+发布包下载：
+
+- GitHub Releases: https://github.com/bamdra/bamdra-user-bind/releases
+- 本地也可以执行 `pnpm package:release` 生成独立发布包
+
 [English README](./README.md)
 
 ## 它做什么
@@ -12,12 +25,20 @@ Bamdra 套件中的身份与“活画像”层。
 
 同时，它也会逐渐成为用户持续演化的画像层，包括：
 
-- 应该怎么称呼
+- userid 级别的默认称呼
 - 时区
 - 语气偏好
 - 角色
 - 长期用户备注
 
+## 画像策略
+
+- `userId` 是画像的主键
+- 默认称呼应当写入该 `userId` 的画像，而不是散落在各个工作区 `USER.md`
+- `USER.md` 只保留运行环境事实，不负责称呼
+- 当当前会话显式要求不同称呼时，以当前会话为准
+- 管理员只做修复、合并、审计和同步，不做批量越权改写
+
 ## 为什么重要
 
 没有身份层时：
@@ -51,6 +72,11 @@ Markdown 镜像则是给人编辑的，让用户画像更像一份活的 per-use
 - 画像镜像保持私有
 - 让人逐步维护画像镜像
 - 管理员能力只用于审计、合并、修复和维护
+- 当你要改称呼时，优先改 `userId` 对应画像，不要去改 workspace 的 `USER.md`
+
+## 架构图
+
+![Bamdra 套件架构图](./docs/assets/architecture-technical-zh.svg)
 
 ## 它能解锁什么
 
@@ -66,3 +92,4 @@ Markdown 镜像则是给人编辑的，让用户画像更像一份活的 per-use
 
 - [GitHub 首页](https://github.com/bamdra)
 - [仓库地址](https://github.com/bamdra/bamdra-user-bind)
+- [Releases](https://github.com/bamdra/bamdra-user-bind/releases)

package/dist/openclaw.plugin.json

@@ -3,10 +3,13 @@
   "type": "tool",
   "name": "Bamdra User Bind",
   "description": "Identity resolution, user profile binding, and admin profile tools for OpenClaw channels.",
-  "version": "0.1.0",
+  "version": "0.1.12",
   "main": "./index.js",
+  "skills": [
+    "./skills"
+  ],
   "configSchema": {
     "type": "object",
     "additionalProperties": true
   }
-}
+}

package/dist/package.json

@@ -1,12 +1,41 @@
 {
   "name": "@bamdra/bamdra-user-bind",
-  "version": "0.1.0",
-  "private": true,
+  "version": "0.1.12",
+  "description": "Identity resolution, user profile binding, and admin-safe profile tools for OpenClaw channels.",
+  "license": "MIT",
+  "homepage": "https://www.bamdra.com",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/bamdra/bamdra-user-bind.git"
+  },
+  "bugs": {
+    "url": "https://github.com/bamdra/bamdra-user-bind/issues"
+  },
   "type": "commonjs",
   "main": "./index.js",
   "types": "./dist/index.d.ts",
+  "files": [
+    "dist",
+    "skills",
+    "openclaw.plugin.json",
+    "README.md",
+    "LICENSE"
+  ],
+  "keywords": [
+    "openclaw",
+    "openclaw-plugin",
+    "identity",
+    "user-profile",
+    "feishu",
+    "memory"
+  ],
+  "engines": {
+    "node": ">=22"
+  },
   "scripts": {
-    "bundle": "node ../../scripts/run-local-bin.mjs tsup && node ../../scripts/prepare-plugin-dist.mjs bamdra-user-bind"
+    "bundle": "node ../bamdra-openclaw-memory/scripts/run-local-bin.mjs tsup && node -e \"const fs=require('node:fs');const path='./dist/index.js';const text=fs.readFileSync(path,'utf8').replace(/require\\\\(\\\"sqlite\\\"\\\\)/g,'require(\\\"node:sqlite\\\")');fs.writeFileSync(path,text);\" && node ./scripts/prepare-plugin-dist.mjs",
+    "prepublishOnly": "pnpm run bundle",
+    "package:release": "node ./scripts/package-release.mjs"
   },
   "openclaw": {
     "id": "bamdra-user-bind",
@@ -22,8 +51,11 @@
       "default": "./dist/index.js"
     }
   },
+  "publishConfig": {
+    "access": "public"
+  },
   "dependencies": {},
   "devDependencies": {
     "@types/node": "^24.5.2"
   }
-}
+}

package/openclaw.plugin.json

@@ -3,7 +3,7 @@
   "type": "tool",
   "name": "Bamdra User Bind",
   "description": "Identity resolution, user profile binding, and admin profile tools for OpenClaw channels.",
-  "version": "0.1.10",
+  "version": "0.1.12",
   "main": "./dist/index.js",
   "skills": ["./skills"],
   "configSchema": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bamdra/bamdra-user-bind",
-  "version": "0.1.10",
+  "version": "0.1.12",
   "description": "Identity resolution, user profile binding, and admin-safe profile tools for OpenClaw channels.",
   "license": "MIT",
   "homepage": "https://www.bamdra.com",
@@ -33,8 +33,9 @@
     "node": ">=22"
   },
   "scripts": {
-    "bundle": "node ../bamdra-openclaw-memory/scripts/run-local-bin.mjs tsup && node -e \"const fs=require('node:fs');const path='./dist/index.js';const text=fs.readFileSync(path,'utf8').replace(/require\\\\(\\\"sqlite\\\"\\\\)/g,'require(\\\"node:sqlite\\\")');fs.writeFileSync(path,text);\"",
-    "prepublishOnly": "pnpm run bundle"
+    "bundle": "node ../bamdra-openclaw-memory/scripts/run-local-bin.mjs tsup && node -e \"const fs=require('node:fs');const path='./dist/index.js';const text=fs.readFileSync(path,'utf8').replace(/require\\\\(\\\"sqlite\\\"\\\\)/g,'require(\\\"node:sqlite\\\")');fs.writeFileSync(path,text);\" && node ./scripts/prepare-plugin-dist.mjs",
+    "prepublishOnly": "pnpm run bundle",
+    "package:release": "node ./scripts/package-release.mjs"
   },
   "openclaw": {
     "id": "bamdra-user-bind",

package/skills/bamdra-user-bind-admin/SKILL.md

@@ -12,7 +12,7 @@ Its purpose is operational: inspect user bindings, repair incorrect profile fiel
 ## Allowed Jobs
 
 - query a specific user profile or binding by `userId`
-- correct nickname, role, timezone, preferences, or personality fields
+- correct nickname, role, timezone, preferences, personality fields, or preferred address
 - merge duplicate user records
 - inspect sync failures and identity resolution issues
 - request a resync for a known user
@@ -31,6 +31,7 @@ Use the admin tools in natural language:
 
 - “查询 user:u_123 的画像和绑定关系”
 - “把 user:u_123 的称呼改成老板，时区改成 Asia/Shanghai”
+- “把 user:u_123 的默认称呼改成丰哥”
 - “合并 user:u_old 到 user:u_new”
 - “列出最近的绑定失败问题”
 

package/skills/bamdra-user-bind-profile/SKILL.md

@@ -24,12 +24,15 @@ The runtime profile comes from `bamdra-user-bind`.
 
 Humans can edit the Markdown mirror for the current user, and the plugin will sync that into the controlled store. Treat the bound profile as more authoritative than guesswork.
 
+Keep per-user address preferences in the bound profile instead of `USER.md`. `USER.md` should stay minimal and only carry environment facts that are not identity-specific.
+
 ## Behavior Rules
 
 - personalize naturally when the stored profile clearly helps
 - use the stored nickname if the user has not asked for a different form of address in the current turn
 - respect the stored timezone for scheduling, reminders, dates, and time-sensitive explanations
 - prefer the stored tone/style preferences when shaping responses
+- if the profile contains a preferred address, treat it as the default greeting and do not duplicate it in workspace-level `USER.md`
 - if the current turn conflicts with the stored profile, follow the current turn
 - do not invent profile traits that are not present