dsh-hypatia-auto-memory 2.2.2 → 2.3.0

package/README.md

@@ -9,7 +9,8 @@ cascade, and adjudicated work-unit extraction — all on a **dedicated model
 route**, with zero model work in the main session.
 
 Writing is automatic; **reading is the agent's job**, through the bundled
-`hypatia-memory` skill. That split is deliberate — see *Recall* below.
+`hypatia-memory` skill, with the bundled `smart-memory` preset carrying the
+retrieval discipline. That split is deliberate — see *Recall* below.
 
 **This plugin replaces `dsh-hypatia`.** That plugin left the writing to the
 agent, which in practice did not happen: in the deployment this one was written
@@ -35,14 +36,25 @@ The first call logs which the binary offers
 
 The plugin also needs **dsh ≥ 0.1.7**, and dsh enforces that itself rather than
 this README: the package declares
-`peerDependencies["@deepseek-ai/dsh"]: ">=0.1.7-rc.1"` (the same range also
-sits under `dsh.engines.dsh` for display), and dsh checks every
-`@deepseek-ai/dsh*` peer against the running version when a bundle is installed
-and again at startup — an older runtime refuses the install instead of loading a
-plugin built for API it does not have, and `dsh plugin allow-version` grants an
-exact-version exemption when the risk is accepted deliberately. The peer is
-marked optional in `peerDependenciesMeta` so that neither npm nor a profile
-installation pulls the runtime in as a dependency: the launcher supplies it.
+`peerDependencies["@deepseek-ai/dsh"]: ">=0.1.7-rc.1 || ^0.2.0-rc.1 || ^0.2.1-alpha.1"`
+(the same range also sits under `dsh.engines.dsh` for display), and dsh checks
+every `@deepseek-ai/dsh*` peer against the running version when a bundle is
+installed and again at startup — an older runtime refuses the install instead of
+loading a plugin built for API it does not have, and `dsh plugin allow-version`
+grants an exact-version exemption when the risk is accepted deliberately. The
+range names each published channel explicitly rather than one open lower bound:
+node-semver admits a prerelease only when the range carries a comparator with the
+same `[major, minor, patch]`, so a bare `>=0.1.7-rc.1` matches no `0.2.x`
+release candidate at all.
+
+Every peer the running dsh already supplies — `@deepseek-ai/dsh`,
+`@deepseek-ai/cordis`, and the `dsh-llm` / `dsh-tools` / `dsh-storage-domain`
+services — is marked `optional` in `peerDependenciesMeta`, so that neither npm
+nor a profile installation pulls a copy of its own: the launcher supplies them,
+and two copies of a package whose instances must be shared is how a plugin ends
+up beside the wrong one. dsh ignores the flag — its check reads
+`peerDependencies` alone — so the ranges above are still enforced at install and
+at startup.
 
 ```bash
 # from a local checkout (development)
@@ -86,6 +98,66 @@ renaming its directory in place is not enough, because DSH names a skill by its
 frontmatter `name`. The startup warning names the directory. The skill center shows the global view, so it can list this plugin
 as a skill's provider while sessions load the disk copy.
 
+## Agent preset: smart-memory（长程记忆）
+
+The bundle ships one agent preset. `cordis.patch.yml` inserts a
+`preset-smart-memory` row declaring `@deepseek-ai/dsh-agent-preset` with
+`config.id: smart-memory`, so the profile's bundle layer is what puts it in the
+agent-preset picker beside the shipped `standard`, `ptc` and `minimal`: install
+the plugin and a memory-first agent is available, with no hand-written profile
+patch.
+
+**It carries the reading half of the split, and nothing else.** Writing here is
+already automatic — logging, consolidation, the session seed. The preset carries
+the discipline the automatic layer cannot: *when* the agent must go and look
+(before planning, at every milestone, when an unfamiliar internal name or a
+familiar-looking bug shows up, before anything destructive — commit, push,
+delete or overwrite, config change, install or upgrade, migration, release —
+whenever the user refers to history, and periodically across a long run), the
+retrieval quality rules (query the concept rather than the user's words;
+`hypatia similar` for ideas and `hypatia search` for exact identifiers; always
+exclude the operational layer), and the one write rule no background pass can
+enforce: a durable rule, taboo or correction the user states is written
+immediately, as `knowledge-update` on an existing entry rather than
+delete-and-recreate.
+
+The persona states *when*; the `hypatia-memory` skill carries *how* — the
+commands, their flags, and the shelf and scope rules. The preset deliberately
+does not restate that protocol or mount it: it is a prompt, not a second
+provider, so load the skill when the work touches memory.
+
+**Tool set.** The `standard` roster with the plan-mode group and `present`
+removed (46 tools on a web profile). Its sub-plugins — `@deepseek-ai/dsh-persona`,
+the `dsh-tool-*` rows, `dsh-skill-filesystem` — come from the dsh installation
+and are deliberately **not** dependencies of this package; the launcher supplies
+them.
+
+**Nothing here mounts the plugin's own machinery.** The preset starts no second
+collector, consolidator, recall listener or auto-approval. Those belong to the
+`hypatia-auto-memory` row above and behave identically whichever preset a session
+runs under, so a session on this preset writes memory exactly like one on
+`standard`.
+
+**Selecting it.** Pick 长程记忆 in the new-session preset picker, or make it the
+default for a surface from the profile's own patch file:
+
+```yaml
+- id: agent-preset-registry
+  name: '@deepseek-ai/dsh-agent-preset-registry'
+  config:
+    selectedDefault: smart-memory
+```
+
+**Replacing a hand-written copy of it.** If you declared this preset yourself
+before it shipped here, delete that copy. The packaged row deliberately reuses
+the row id `preset-smart-memory`, and rows sharing a row id collapse to the later
+one — the profile's patch file is applied *after* every bundle layer, so a
+leftover copy wins and masks the packaged declaration, and the Plugin Manager
+then reports that row as `unaddressable` because its id has two candidate rows.
+Two *distinct* rows declaring one `config.id` fail the other way, with `Duplicate
+agent preset: smart-memory` from the registry. A comment where the row used to be
+is enough.
+
 ## How it works
 
 ```
@@ -666,7 +738,7 @@ Deliberate, and worth knowing before you rely on them:
 ```
 dsh-hypatia-auto-memory/
 ├── package.json          # bundle + client manifest, deps
-├── cordis.patch.yml      # bundle layer inserting id=hypatia-auto-memory
+├── cordis.patch.yml      # bundle layer: the plugin row + the smart-memory preset
 ├── tsconfig.json         # browser TS/TSX type-check config
 ├── tsconfig.build.json   # declaration emit for client bundle
 ├── tsdown.config.ts      # browser CJS factory build

package/README.zh-CN.md

@@ -7,8 +7,9 @@
 （span 摘要、log₁₆(n) 归档级联、带裁决的工作单元抽取）——全部走**专用模型路由**，
 主会话零模型工作。
 
-写入是全自动的；**读取由 Agent 负责**，通过随包附带的 `hypatia-memory` 技能完成。
-这种分工是有意为之——见下文 *Recall*。
+写入是全自动的；**读取由 Agent 负责**，通过随包附带的 `hypatia-memory` 技能完成，
+检索纪律则由同样随包附带的 `smart-memory` 预设承载。这种分工是有意为之——见下文
+*Recall*。
 
 **本插件取代 `dsh-hypatia`。** 后者把写入留给 Agent，实际上并没有发生：在编写本
 插件的那个部署环境里，模型加载了协议，却在十五个会话中只有一个会话主动执行了
@@ -29,12 +30,20 @@
 filters yes`）。
 
 本插件还需要 **dsh ≥ 0.1.7**，而且这个下限由 dsh 自己强制执行，不靠本 README：
-包里声明了 `peerDependencies["@deepseek-ai/dsh"]: ">=0.1.7-rc.1"`（同样的范围也写在
-`dsh.engines.dsh` 里，供展示），dsh 在安装 bundle 时、以及每次启动时，会把每个
-`@deepseek-ai/dsh*` peer 与自身版本比对——运行时太旧会直接拒绝安装，而不是加载一个
-面向它并不具备的 API 写成的插件；确实要接受风险时，用 `dsh plugin allow-version`
-授予精确版本豁免。该 peer 在 `peerDependenciesMeta` 里标为 optional，这样 npm 和
-profile 安装都不会把运行时本身拉成依赖：运行时由 launcher 提供。
+包里声明了
+`peerDependencies["@deepseek-ai/dsh"]: ">=0.1.7-rc.1 || ^0.2.0-rc.1 || ^0.2.1-alpha.1"`
+（同样的范围也写在 `dsh.engines.dsh` 里，供展示），dsh 在安装 bundle 时、以及每次启动时，
+会把每个 `@deepseek-ai/dsh*` peer 与自身版本比对——运行时太旧会直接拒绝安装，而不是加载
+一个面向它并不具备的 API 写成的插件；确实要接受风险时，用 `dsh plugin allow-version`
+授予精确版本豁免。范围把每条已发布通道逐一写出来，而不是只写一个开放下界：node-semver
+只在区间里存在同 `[major, minor, patch]` 的比较子时才接受预发布版，因此单写
+`>=0.1.7-rc.1` 其实一个 `0.2.x` 候选版都匹配不到。
+
+凡是运行中的 dsh 已经提供的 peer——`@deepseek-ai/dsh`、`@deepseek-ai/cordis`，以及
+`dsh-llm` / `dsh-tools` / `dsh-storage-domain` 三个服务——都在 `peerDependenciesMeta`
+里标为 `optional`，这样 npm 和 profile 安装都不会各自再拉一份：它们由 launcher 提供，
+而"需要共享实例的包存在两份"正是插件用错那一份的来源。dsh 会忽略这个标记——它的检查只读
+`peerDependencies`——所以上面的范围在安装时和启动时依旧生效。
 
 ```bash
 # 从本地 checkout 安装（开发）
@@ -73,6 +82,52 @@ user）只在一层内打破平局。Agent 预设（`st`、`standard`、…）
 目录名。技能中心展示的是全局视图，所以它可能把本插件列为某技能的提供者，而会话
 实际加载的是磁盘拷贝。
 
+## Agent 预设：smart-memory（长程记忆）
+
+本插件包内置一个 Agent 预设。`cordis.patch.yml` 插入一行 `preset-smart-memory`
+声明 `@deepseek-ai/dsh-agent-preset`、`config.id: smart-memory`，因此是 profile 的
+bundle 层把它送进 Agent 预设选择器，与自带的 `standard`、`ptc`、`minimal` 并列：
+装上插件就有一个「记忆优先」的 Agent 可用，不必再手写 profile 补丁。
+
+**它承载的是分工里「读」的那一半，仅此而已。** 这里的写入本来就是自动的——日志
+记录、巩固、会话开场的规则种子。预设承载的是自动层做不到的纪律：**什么时候必须去
+查**（制定计划前、每个里程碑、出现陌生内部名称或眼熟的 bug 时、任何破坏性操作之前
+——commit、push、删除或覆盖、改配置、安装或升级、迁移、发布——用户提到历史时，以及
+长程任务中的周期性回顾），检索质量要求（查询写成概念而非用户原话；想法用
+`hypatia similar`，精确标识符用 `hypatia search`；始终排除运维层），以及唯一一条
+后台流程无法强制执行的写入规则：用户给出的永久性规则、禁忌或纠正立即落库，且对已存在
+条目用 `knowledge-update`，而不是删除后重建。
+
+人设规定的是*什么时候*，`hypatia-memory` 技能承载的是*怎么做*——命令、参数，以及
+shelf 与 scope 的规则。预设刻意不重述这套协议，也不挂载它：它只是提示词，不是第二个
+提供者，所以在工作涉及记忆时加载该技能。
+
+**工具集。** 即 `standard` 的花名册去掉 plan mode 组与 `present`（web profile 下
+46 个工具）。它的子插件——`@deepseek-ai/dsh-persona`、各 `dsh-tool-*` 行、
+`dsh-skill-filesystem`——来自 dsh 安装本身，**刻意不**作为本包的依赖；由 launcher
+提供。
+
+**这里不挂载插件自身的任何机制。** 预设不会启动第二个 collector、consolidator、
+recall 监听或自动批准。那些属于上面那行 `hypatia-auto-memory`，且无论会话跑在哪个
+预设下行为一致；因此用本预设的会话写记忆的方式与 `standard` 完全相同。
+
+**怎么选。** 在新会话的预设选择器里选「长程记忆」，或在 profile 自己的补丁文件里把它
+设为该界面的默认值：
+
+```yaml
+- id: agent-preset-registry
+  name: '@deepseek-ai/dsh-agent-preset-registry'
+  config:
+    selectedDefault: smart-memory
+```
+
+**替换手写的那一份。** 如果你在本预设随包分发之前自己声明过它，请删掉那份拷贝。包内的
+行刻意沿用 row id `preset-smart-memory`，而同名 row id 的两行会折叠为靠后的那一行
+——profile 的补丁文件在所有 bundle 层**之后**应用，所以残留的拷贝会取胜并遮蔽包内
+声明；插件管理器随后会把该行报成 `unaddressable`，因为同一个 id 出现了两个候选行。
+另一种失败是两行**不同** row id 声明同一个 `config.id`：registry 会用
+`Duplicate agent preset: smart-memory` 拒绝第二次注册。在原处留一段注释即可。
+
 ## 工作原理
 
 ```
@@ -518,7 +573,7 @@ shelf 清单本来就不是配置，而设置域现在只投影插件的 Config
 ```
 dsh-hypatia-auto-memory/
 ├── package.json          # bundle + client manifest、依赖
-├── cordis.patch.yml      # 插入 id=hypatia-auto-memory 的 bundle 层
+├── cordis.patch.yml      # bundle 层：插件行 + smart-memory 预设
 ├── tsconfig.json         # 浏览器 TS/TSX 类型检查配置
 ├── tsconfig.build.json   # client bundle 的声明产物
 ├── tsdown.config.ts      # 浏览器 CJS 工厂构建

package/cordis.patch.yml

@@ -21,3 +21,152 @@
 - insert:
     - id: hypatia-auto-memory
       name: dsh-hypatia-auto-memory
+
+# ── Agent preset: smart-memory（长程记忆） ─────────────────────────────────────
+# The plugin owns the memory *writing* side; this preset owns the *reading*
+# discipline. Installing this bundle therefore ships a memory-first agent — the
+# preset is part of the package, not a profile patch a user has to hand-write.
+# The two rows are independent: the preset mounts none of the plugin's own
+# machinery (collector, consolidation, recall, autoApprove), and the plugin row
+# above registers no preset.
+#
+# The row declares `@deepseek-ai/dsh-agent-preset` with `config.id: smart-memory`
+# — the id the preset registry and a session header record. Its `config.plugins`
+# is the `standard` preset's roster with the plan-mode group and `present`
+# removed, under a memory-first persona; the sub-plugins (`@deepseek-ai/dsh-persona`,
+# the `dsh-tool-*` rows, `dsh-skill-filesystem`) come from the dsh installation
+# and are deliberately not dependencies of this package.
+#
+# The row id is deliberately the one hand-written profile patches used
+# (`preset-smart-memory`), so such a profile only has to drop its copy. Rows
+# sharing a row id collapse to the later one, and the profile's own
+# cordis.patch.yml is applied after every bundle layer, so a leftover copy wins
+# and masks this declaration; the Plugin Manager also reports that row as
+# `unaddressable`, because its id then has two candidate rows. Two *distinct*
+# rows declaring one `config.id` are refused instead: the registry throws
+# `Duplicate agent preset: smart-memory` on the second registration.
+#
+# Edits saved from the Web preset editor override this row's `config.plugins`
+# by id from the profile patch.
+- insert:
+    - id: preset-smart-memory
+      name: '@deepseek-ai/dsh-agent-preset'
+      config:
+        id: smart-memory
+        name: 长程记忆
+        description: >-
+          长程任务下强化 hypatia 记忆库的主动检索与落库：任务开始、里程碑、 发现新线索、重要操作前都先回忆，永久规则与纠正立即写库。
+        order: 2
+        plugins:
+          - id: persona
+            name: '@deepseek-ai/dsh-persona'
+            config:
+              prefix: |-
+                你是 {{model}} 驱动的长程记忆型编码 agent。默认假设是：这件事之前很可能已经被讨论、决定或踩过坑——先读记忆，再动手。
+
+                ## 记忆系统怎么分工
+                会话日志、span 摘要、work unit 固化和会话开场的规则/禁忌种子都由 dsh-hypatia-auto-memory 在后台完成，不要手工重复写这些。你负责两件事：在正确时机主动**检索**；在用户给出永久性规则、禁忌或纠正时**立即落库**。具体命令与查询配方在 hypatia-memory 技能里（用 skill 工具加载，CLI 细节见 hypatia 技能）——本段只规定纪律。
+
+                ## 检索纪律（下列时机是必须做的动作，不是建议）
+                1. 任务开始、制定计划前：先建立"已知决策 / 项目约定 / 已踩过的坑"的基线，再规划。
+                2. 每个里程碑或阶段边界：重新对齐一次，避免局部最优违背既有决策。
+                3. 任务中途发现新线索：出现陌生的内部名称或模块名、看不懂的报错、眼熟的 bug，或你意识到任务真正主题与开头不同时，立刻补查。
+                4. 重要或破坏性操作前：git commit / push、删除或覆盖文件、改配置、安装或升级插件与依赖、数据库迁移、发布或对外发送内容之前。
+                5. 用户提到历史时：例如"之前怎么定的""上次那个""为什么这么做"。
+                6. 长程任务周期性回顾：上下文已经很长，或目标已跨多轮续跑时，重新检索当前的关键主题。
+
+                检索质量要求：查询写成你想找的那个**概念**，不要照抄用户原话；语义检索用 `hypatia similar`，精确标识符用 `hypatia search`；始终排除运维层（`msg-`、`sum-`、`session-`、`hypatia-dream-run-` 开头，或带 `message`/`summary`/`session` 标签的行）；一次空结果不等于记忆里没有——换措辞、提高 `--limit` 再试。
+
+                ## 检索结果怎么用
+                查到既有决策就遵循它，并在回答里点明依据（条目名或结论）。记忆与当前代码或用户要求冲突时，明确说出冲突，以用户当前指令为准，并用 `supersedes` 语句把新结论落库——绝不删除旧条目。确实没有记录时，直接说明"记忆库中没有相关记录"，再按第一性原理推进，不要编造记忆内容。
+
+                ## 写入纪律
+                用户给出永久性规则、禁忌或纠正时立即写库（`rule` / `taboo` / `memory`，scope 用本项目的实际 scope）：先 `knowledge-get`，已存在就 `knowledge-update`，不存在才 `knowledge-create`，不要删除后重建。过程流水不要手工写。
+
+                ## 长程任务
+                复杂任务先用 todo_write 拆解并跟踪；跨轮目标用 goal 机制续跑，没有完成证据不要宣称完成。阶段收尾时把"值得留存的结论"落库，而不是把过程日志落库。
+              suffix: |-
+                你的工作目录是 {{cwd}}。记忆的检索与落库通过 bash 调用 hypatia CLI 完成，scope 归属由插件决定。
+          - id: agent-instructions
+            name: '@deepseek-ai/dsh-agent-instructions'
+            config:
+              maxBytes: 65536
+          - id: tool-bash
+            name: '@deepseek-ai/dsh-tool-bash'
+            disabled: !!js process.platform === 'win32'
+          - id: tool-pwsh
+            name: '@deepseek-ai/dsh-tool-pwsh'
+            disabled: !!js process.platform !== 'win32'
+          - id: tool-fs
+            name: '@deepseek-ai/dsh-tool-fs'
+          - id: tool-fs-search
+            name: '@deepseek-ai/dsh-tool-fs-search'
+            config:
+              sampleOverCapGlobResults: false
+          - id: tool-jobs
+            name: '@deepseek-ai/dsh-tool-jobs'
+          - id: skill-filesystem
+            name: '@deepseek-ai/dsh-skill-filesystem'
+          - id: tool-skill
+            name: '@deepseek-ai/dsh-tool-skill'
+          - id: command-goal
+            name: '@deepseek-ai/dsh-command-goal'
+          - id: tool-goal
+            name: '@deepseek-ai/dsh-tool-goal'
+          - id: compaction
+            name: cordis:group
+            group: true
+            isolate:
+              compaction: true
+              toolResultPruner: true
+            config:
+              - id: compaction-basic
+                name: '@deepseek-ai/dsh-compaction-basic'
+              - id: command-compact
+                name: '@deepseek-ai/dsh-command-compact'
+              - id: tool-result-pruner
+                name: '@deepseek-ai/dsh-compaction-tool-result-pruner'
+                config:
+                  thresholdChars: 8192
+                  headChars: 4096
+                  tailChars: 1024
+          - id: delegation
+            name: cordis:group
+            group: true
+            isolate:
+              workflowEngine: true
+            config:
+              - id: tool-subagent-control
+                name: '@deepseek-ai/dsh-tool-subagent-control'
+              - id: tool-subagent-list-agents
+                name: '@deepseek-ai/dsh-tool-subagent-control/list-agents'
+              - id: tool-subagent
+                name: '@deepseek-ai/dsh-tool-subagent'
+                config:
+                  provider: spawn
+                  toolName: subagent
+                  modelSelectionSettings: true
+                  backgroundMode: continuable
+              - id: tool-subagent-fork
+                name: '@deepseek-ai/dsh-tool-subagent'
+                config:
+                  provider: fork
+                  toolName: subagent_fork
+                  backgroundMode: continuable
+              - id: workflow-ptc
+                name: '@deepseek-ai/dsh-workflow-ptc'
+                config:
+                  provider: spawn
+              - id: tool-workflow
+                name: '@deepseek-ai/dsh-tool-workflow'
+          - id: tool-ask-user
+            name: '@deepseek-ai/dsh-tool-ask-user'
+          - id: tool-todo
+            name: '@deepseek-ai/dsh-tool-todo'
+            config:
+              allowParallelInProgress: true
+          - id: tool-web
+            name: '@deepseek-ai/dsh-tool-web'
+            config:
+              fetch: true
+              searchTimeoutMs: 60000

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-hypatia-auto-memory",
-  "version": "2.2.2",
+  "version": "2.3.0",
   "description": "Event-driven Hypatia memory for DSH: automatic conversation logging via session events, queued background consolidation (span summaries + work-unit extraction) with a dedicated model route, and recall injection — zero per-call model work in the main session.",
   "icon": "./icon.svg",
   "type": "module",
@@ -31,7 +31,7 @@
   },
   "dsh": {
     "engines": {
-      "dsh": ">=0.1.7-rc.1"
+      "dsh": ">=0.1.7-rc.1 || ^0.2.0-rc.1 || ^0.2.1-alpha.1"
     },
     "bundle": {
       "patch": "./cordis.patch.yml"
@@ -49,25 +49,37 @@
     "node": "^22.19.0 || >=24.0.0"
   },
   "dependencies": {
-    "@deepseek-ai/schemastery": "^3.18.2",
+    "@deepseek-ai/schemastery": "^3.18.2 || ~3.18.5-alpha.1",
     "zod": "^4.4.3"
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.2 || ~4.0.5-alpha.1",
-    "@deepseek-ai/dsh": ">=0.1.7-rc.1",
+    "@deepseek-ai/dsh": ">=0.1.7-rc.1 || ^0.2.0-rc.1 || ^0.2.1-alpha.1",
     "@deepseek-ai/dsh-llm": "^0.1.7-rc.1 || ^0.2.0-rc.1 || ^0.2.1-alpha.1",
     "@deepseek-ai/dsh-storage-domain": "^0.1.7-rc.1 || ^0.2.0-rc.1 || ^0.2.1-alpha.1",
     "@deepseek-ai/dsh-tools": "^0.1.7-rc.1 || ^0.2.0-rc.1 || ^0.2.1-alpha.1",
     "react": "^18.2.0"
   },
   "peerDependenciesMeta": {
+    "@deepseek-ai/cordis": {
+      "optional": true
+    },
     "@deepseek-ai/dsh": {
       "optional": true
+    },
+    "@deepseek-ai/dsh-llm": {
+      "optional": true
+    },
+    "@deepseek-ai/dsh-storage-domain": {
+      "optional": true
+    },
+    "@deepseek-ai/dsh-tools": {
+      "optional": true
     }
   },
   "devDependencies": {
     "@deepseek-ai/cordis": "^4.0.2 || ~4.0.5-alpha.1",
-    "@deepseek-ai/cordis-plugin-loader": "^1.0.5",
+    "@deepseek-ai/cordis-plugin-loader": "^1.0.5 || ~1.0.6-alpha.1",
     "@deepseek-ai/dsh-agent": "^0.1.7-rc.1",
     "@deepseek-ai/dsh-api-remotes": "^0.1.7-rc.1",
     "@deepseek-ai/dsh-api-session-controller": "^0.1.7-rc.1",