@xdxer/dingtalk-agent 0.1.5-beta.4 → 0.1.5-beta.5

package/CHANGELOG.md

@@ -2,6 +2,26 @@
 
 All notable changes to `@xdxer/dingtalk-agent` are documented here. The project follows semantic versioning; prerelease entries describe release candidates and do not imply that Live canaries or registry publication have completed.
 
+## 0.1.5-beta.5 - 2026-07-23
+
+Long-term memory becomes a bundled standard capability: any DingTalk Agent can maintain living profiles for the **people** and **conversations (groups/DMs)** it works with over time, storage-decoupled behind a port so the model layer never touches a specific medium (PR #13). Ships on the `beta` dist-tag; `latest` stays at 0.1.4.
+
+### Added
+
+- `dingtalk-people-group-memory` joins the default bundle (`BUNDLED_SKILL_NAMES`). It is fully inert until storage is bound — zero writes, zero probes, and it must not claim "I remembered" — so bundling it by default has no side effect; binding is deferred to when the user actually asks. The skill is a three-layer design: `model.md` (Person/Conversation/Fact/Watermark, medium-agnostic — verifiably zero DingTalk vocabulary), `event-ingest.md` (message/todo/doc events → Facts, `evidenceId`-keyed idempotency), and `storage-port.md` (10 operations + 8 capability bits) with adapters for `dingtalk-doc` (narrative) and `aitable` (registry), plus a `local-md` contract.
+- Section `kind` split (`narrative` vs `registry`): prose profiles live in DingTalk docs (read-whole, human-readable), while indexes/watermarks/tombstones live in AI Tables (query-by-key, real pagination, no 340-line truncation wall). The same model-layer operations route to either medium purely by capability bits — swapping the registry medium collapses a whole class of doc-only pathologies.
+- `consolidation.md`: the one-year answer for append-only raw — monthly digests, a bounded O(1) working set, `working-on` decay, derived-section curation, and count-based completeness (write-side row counts reconciled on read, since the production medium truncates silently).
+- `config-binding.md` + `guided-setup.md`: the user-configured storage address lives in `agent.bindings.json#memory` (`dingtalk-doc:<adoc-node>`) or `DTA_MEMORY_STORAGE`, resolved by the existing bootstrap `select()` chain — never hardcoded in the skill. A seven-step guided-creation flow walks a user from nothing to a valid, parse-verified adoc binding record. `COMPLETENESS.md` states honestly what is delivered (guided single-agent read/write, proven on real dws) versus contract-only (full autonomy, multi-agent, one-year compaction).
+- The compose Skill gains a "long-term memory" section: bundled, no assembly-time action beyond writing a seed into the body if already bound; binding must happen under the runtime identity, not the developer identity.
+
+### Changed
+
+- `dta --help` merges the `info` / `workspace doctor` / `schedule show` read-only-diagnostics into one line, keeping the default help at ≤20 lines after the driving layer (beta.4) added its `schedule` entry.
+
+### Fixed
+
+- `package.json#files`, the release-readiness required-skill list, and the `#20`/`#28` contract fixtures are updated for the four-skill default bundle; `package-lock.json` is realigned to the package version (beta.4 had bumped the manifest but not the lock).
+
 ## 0.1.5-beta.4 - 2026-07-23
 
 Driving layer: the recurring drives that wake a digital employee become a version-controlled, provider-mapped declaration instead of imperative platform state, plus a smoke-whitelist bare-filename fix that had blocked live deployment (PR #16). Ships on the `beta` dist-tag; `latest` stays at 0.1.4.

package/dist/bin/dingtalk-agent.js

@@ -65,8 +65,7 @@ dta —— 给 Agent 安装钉钉员工的基础行为和工作环境
   dta setup             首次配置 CLI、DWS 和内置 Skill（基础行为 + Agent 装配 + 交付后评测）
   dta bootstrap --json  为当前 Agent 会话加载工作区
   dta agent enhance / audit  安全增强已有仓库，再审计定义、存储与 Skill 真加载
-  dta info / dta workspace doctor <name>  查看 Project 并只读诊断 Workspace
-  dta schedule show / plan --workspace <name>  查看声明的常驻节律并生成 provider 部署计划
+  dta info / workspace doctor / schedule show <name>  只读诊断 Project、Workspace 与声明的常驻节律
   dta agent-platform use <platform> → dta deploy / dta promote  声明平台归属并装平台技能包，再受控部署与晋级
 
 维护环境：