memory-eternal 0.10.33 → 0.10.34

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "memory-eternal",
-  "version": "0.10.33",
+  "version": "0.10.34",
   "description": "记忆核心（Memory Eternal）：对话结束后自动沉淀知识卡到本地记忆库（~/.dsh/memory-vault），支持检索 / 召回 / 审核中心。",
   "author": {
     "name": "EternalNight996",

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "memory-eternal",
-  "version": "0.10.33",
+  "version": "0.10.34",
   "description": "记忆核心（Memory Eternal）：对话结束后自动沉淀知识卡到本地记忆库（~/.dsh/memory-vault），支持检索 / 召回 / 审核中心。",
   "author": {
     "name": "EternalNight996",

package/.cursor-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "memory-eternal",
-  "version": "0.10.33",
+  "version": "0.10.34",
   "description": "记忆核心（Memory Eternal）：对话结束后自动沉淀知识卡到本地记忆库（~/.dsh/memory-vault），支持检索 / 召回 / 审核中心。",
   "author": {
     "name": "EternalNight996",

package/README.en.md

@@ -361,14 +361,15 @@ curl http://127.0.0.1:7999/memory-eternal/api/web-info    # is the standalone we
 
 | Version | Date | Highlights |
 |---|---|---|
+| **v0.10.34** | 2026-10-16 | **Root fix: when the lock is unwritable the HOST manages the resident instance itself (adopting the reporter's fourth point in issue #30)**. Their diagnosis: on that machine the "registration" happens to live in the only process that cannot write the lock, so automatic replacement is permanently refused. Fixes: ① the host's `autoWebMode=interval` keep-alive loop now probes **the version served on the port**, not just liveness — if it lags and the lock is writable the watchdog/drift path still handles it (the host does not compete); if it lags and the **lock is unwritable** the **host takes over**: `ensureWebServer({forceTakeover:true})` stops only **our own** web, starts a new instance on the **same port** and keeps it alive; ② a testable `takeoverOwnWeb()` with a safety gate that only acts on occupants where `looksLikeOurWeb` is true (foreign processes are never touched); ③ "host-managed" is recorded as state (`recordHostManaged`) so `/version-check` reports `resident.managedBy='host'` and the panel says "**host-managed**" instead of "unmanaged / orphan"; the state clears itself once a watchdog registers again. `npm test` now runs **366 checks** |
 | **v0.10.33** | 2026-10-15 | **Distillation provider: dynamic dropdowns, best-effort follow-session, first-candidate-only and a test button (first slice of issue #42)**. ① **Dynamic dropdowns**: a new read-only `/llm-routes` endpoint (backed by the host's listProviders/listModels) turns the "distill provider / model" fields from hand-typed IDs into selects (falling back to text inputs when unavailable); ② **Follow the current session** (their top priority): the new `captureFollowSession` config makes host distillation **try** the session's provider/model first (`sessionRouteFrom()` sniffs `agent / session / session.route / session.options`), and **falls back to the explicit config with a log line** when nothing is exposed (DSH does not guarantee a route on the session object — that log is the basis for a future adapter rather than a guess); background/no-session tasks (CLI, watchdog, hooks) can only use the explicit config; ③ **First-candidate-only + test button**: `captureFirstOnly` makes routing take just the first candidate and stop on failure (no more "hit the official provider first, burn a call, then rotate"); `POST /llm-test` makes one small real call and echoes **provider / model / latency / candidate count / error code**, which also verifies ① and ②; ④ also fixes **probe jitter**: `probeServedVersion()` now retries with backoff three times (the reporter measured "version-check 200 at one moment, then status says no service 2s later"), so single-shot probes are no longer fooled by restart windows or transient refusals. `npm test` now runs **363 checks** |
-| **v0.10.32** | 2026-10-15 | **"The resident instance cannot be replaced" becomes a long-lived state instead of a retry on every boot (issue #30, fifth retest round: the steady state on the A: drive machine)**. The reporter measured 44 "version drift" events over five days, with a mechanism where **every step works as designed yet the instance can never be replaced**: upgrade → the port still serves the previous generation → the host detects drift → it spawns a `--replace` helper → the helper pre-flights and finds `lock.writable=false` → it **correctly refuses** (the 0.10.29 design, zero damage) → the old instance survives → the next boot reports it again. Fixes: ① new `lib/resident-state.js` **records "cannot replace (environment limit)" as state** (cause / lock path / port / versions / count, valid for 7 days); ② the host now **probes lock writability before restarting** and, when unwritable, **stops retrying a doomed replacement**, recording just one line — `warn` the first time, then downgraded to a `boot`-level "known state" on later boots (the reporter's words: they do not want a warn on every boot forever); ③ the wording is explicitly split from "drift": **"the resident instance cannot be replaced (environment limit)"** plus the way out (fix permissions then restart, or run `dsh-memory watchdog --port N` in the foreground); ④ the panel, `/version-check` and `align` all surface the state (`resident.replaceBlocked`; in `align` it is a `warn` finding that clears itself once the environment is fixed). `npm test` now runs **359 checks** |
 
 <details>
-<summary>Older release notes (v0.10.31 and earlier · 58 releases, click to expand)</summary>
+<summary>Older release notes (v0.10.32 and earlier · 59 releases, click to expand)</summary>
 
 | Version | Date | Highlights |
 |---|---|---|
+| **v0.10.32** | 2026-10-15 | **"The resident instance cannot be replaced" becomes a long-lived state instead of a retry on every boot (issue #30, fifth retest round: the steady state on the A: drive machine)**. The reporter measured 44 "version drift" events over five days, with a mechanism where **every step works as designed yet the instance can never be replaced**: upgrade → the port still serves the previous generation → the host detects drift → it spawns a `--replace` helper → the helper pre-flights and finds `lock.writable=false` → it **correctly refuses** (the 0.10.29 design, zero damage) → the old instance survives → the next boot reports it again. Fixes: ① new `lib/resident-state.js` **records "cannot replace (environment limit)" as state** (cause / lock path / port / versions / count, valid for 7 days); ② the host now **probes lock writability before restarting** and, when unwritable, **stops retrying a doomed replacement**, recording just one line — `warn` the first time, then downgraded to a `boot`-level "known state" on later boots (the reporter's words: they do not want a warn on every boot forever); ③ the wording is explicitly split from "drift": **"the resident instance cannot be replaced (environment limit)"** plus the way out (fix permissions then restart, or run `dsh-memory watchdog --port N` in the foreground); ④ the panel, `/version-check` and `align` all surface the state (`resident.replaceBlocked`; in `align` it is a `warn` finding that clears itself once the environment is fixed). `npm test` now runs **359 checks** |
 | **v0.10.31** | 2026-10-15 | **Root fix for `restart` failing 100% of the time on machines with slow port enumeration (issue #30, third/fourth retest rounds — the reporter traced it to the line)**. Mechanism: the `--replace` helper ran "clear the scene → only then write the lock if the port is free → start the watchdog", while `Get-NetTCPConnection` inside the clear step measured **4–13.6 seconds** and was **not bounded by the 8-second budget** → the helper **never reached the lock write** → the lock stayed empty → `waitForTakeover` (which requires a fresh live watchdog in the lock) **was guaranteed to time out** → on such machines both the CLI and the panel button report "(no response)" **100% of the time, regardless of version**. Fixes: ① **a failed clear step still leaves a registration** (`acquireWatchdogLock({force:true})`), so "a web on the port with an empty lock" can no longer happen; ② **`acquireWatchdogLock` gains `force`** (the whole point of `--replace` is to replace that same-port instance, so it must not yield — otherwise the helper exits before the clear step finishes); ③ 0.10.30 already bounded the enumerator (`defaultExec` kills the child on timeout, `findPortListener({timeoutMs})` threads it through, the clear step uses ≤2.5s); ④ the CLI's `restart` result is now **actually written to the auto-capture log** (the hint always claimed so, but the CLI path never did). They also measured "two competing takeover helpers" (the host tick and the CLI each spawning one) — with registration plus force, that race is far less harmful (the later one takes over the registration instead of both leaving nothing). `npm test` now runs **355 checks** |
 | **v0.10.30** | 2026-10-15 | **Two fixes for "the whole page is unusable": malformed tags causing a black screen (#41) plus two real defects in the takeover path (issue #30, third/fourth retest rounds)**. ① **#41**: a string `tags` value sent to `/write` (e.g. `"[\"a\",\"b\"]"`) was passed straight into `writeCard`'s `JSON.stringify` → **double-encoded** in the database → read back as a string → the client's `card.tags.slice(...).map` threw → **the React root failed to mount and the whole page went black** (restarting DSH, the plugin or the resident instance changed nothing, because the bad data lives in the DB). `normalizeTags()` is now the **single entry point**: arrays, JSON strings, comma strings and **legacy double-encoded rows** all collapse to arrays, used by the write path **and every read path** (existing bad data needs no manual repair); the render layer also guards itself (bad tags cost a few chips, never the tree). ② **#30**: the reporter found two more issues inside my 0.10.29 — `restoreWatchdogLock`'s "live registration" test **missed `!w.endedAt`** (so with a reused pid the write-back was abandoned), and **Windows port enumeration had no timeout** (`Get-NetTCPConnection` measured at 4–7.5s, once 13.6s, while the takeover's 8s budget could not bound it → decisions were made on stale data). `defaultExec` now supports a timeout and actually kills the child, `findPortListener({timeoutMs})` threads it through, and the takeover passes a bounded value (≤2.5s). Adds `tests/tags-normalize.test.mjs` (4 checks) and 2 regressions in `watchdog-restart`. `npm test` now runs **354 checks** |
 | **v0.10.29** | 2026-10-14 | **A failed takeover no longer wrecks the crime scene (key finding from the issue #30 retest)**. The reporter measured on 0.10.26 that after a failed `restart` the **lock file was deleted** while the same web kept listening — the scene then looked as if a resident had never existed, leaving only an orphan. Four fixes: ① **releasing the lock no longer deletes the file** (`releaseWatchdogLock` leaves an "ended" record with `endedAt`; `status` shows "exited (stale record)", and such slots **never block** a new instance, even with pid reuse); ② **a failed restart writes the pre-replacement registration back** (`restoreWatchdogLock`, only when no live registration exists for that port); ③ **failing to enumerate the occupant no longer counts as "port free"** — `clearResidentForTakeover` now **double-checks with TCP** (in restricted environments the process query returns nothing, and the old code concluded the port was free, so the new web could not bind, the self-check reported "(no response)" and the lock was wiped); if something is still listening the takeover aborts and **touches no registration at all**; ④ **refuse to take over when the lock file is unwritable** (an unregisterable instance would only become another orphan — it now errors out and points at running the watchdog in the foreground). The restart failure message also names **who is on the port now** and whether the lock was written back, and `status` now **labels the port probe and the lock registration as separate sections** (the reporter pointed out the old output mixed the two and misled readers). `npm test` now runs **348 checks** |

package/README.md

@@ -393,14 +393,15 @@ curl http://127.0.0.1:7999/memory-eternal/api/web-info    # 独立 web 是否活
 
 | 版本 | 日期 | 关键改动 |
 |---|---|---|
+| **v0.10.34** | 2026-10-16 | **治本：锁不可写时由「宿主」自己托管常驻实例（采纳 #30 报告者第四点建议）**。他的诊断：那台机器上「登记」恰好落在**唯一写不了锁的那个进程**上 → 自动替换被永久拒绝。修法：① 宿主的 `autoWebMode=interval` 保活循环**不再只探存活**，还探**端口上服务的版本** —— 落后且锁可写 → 仍交给看门狗 / 漂移路径（宿主不抢）；落后且**锁不可写** → **宿主自己接管**（`ensureWebServer({forceTakeover:true})`：只收掉**自家** web、在**同端口**起新实例、由宿主保活）；② 新增可测试的 `takeoverOwnWeb()`（安全闸门：只对 `looksLikeOurWeb` 为真的占用者下手，别人的进程一个都不动）；③ 「宿主托管」记成状态（`recordHostManaged`）→ `/version-check` 报 `resident.managedBy='host'`，面板显示「**宿主托管**」而不是「未托管 / 孤儿」；看门狗重新登记后自动清除。`npm test` 共 **366 项** |
 | **v0.10.33** | 2026-10-15 | **蒸馏供应商：动态下拉 + 跟随当前会话（尽力）+ 仅试首选 + 测试按钮（issue #42 第一刀）**。① **动态下拉**：新增只读接口 `/llm-routes`（宿主侧的 listProviders/listModels），配置页的「蒸馏 provider / model」从**手填编号**变成**下拉选择**（取不到时自动回退成文本输入）；② **跟随当前会话**（他的最高优先级）：新增配置 `captureFollowSession`，开启后宿主蒸馏**先尝试**用这一轮会话的 provider/model（`sessionRouteFrom()` 按 `agent / session / session.route / session.options` 逐个嗅探），**读不到就回退显式配置并记一条日志**（DSH 未保证会话对象暴露 route —— 这条日志就是以后补适配的依据，不猜）；后台 / 无会话任务（CLI、watchdog、hooks）天然只能回退配置；③ **仅试首选 + 测试按钮**：`captureFirstOnly` 让选路只取第一个候选、失败即停（避免「先打官方 → 白烧一次调用 → 再轮换」）；`POST /llm-test` 用真实调用路径打一次小请求，回显 **provider / model / 耗时 / 候选数 / 错误码**，也是 ①② 的验证手段。④ 顺带修一处**探测抖动**：`probeServedVersion()` 现在退避重试 3 次（报告者实测「同一时刻 version-check 200、2 秒后 status 说没有服务」），单发探测不再被重启窗口/瞬时拒绝骗到。`npm test` 共 **363 项** |
-| **v0.10.32** | 2026-10-15 | **「常驻实例不可替换」变成长期状态，而不是每次开机重试（#30 第五轮复测：A: 盘的稳态）**。报告者实测 5 天 44 次「版本漂移」，机制是**每一步都按设计工作、合起来永远换不掉**：升级 → 端口上仍是上一代 → 宿主探测漂移 → 拉起 `--replace` 助手 → 助手前置探到 `lock.writable=false` → **正确地拒绝**（0.10.29 的设计，零破坏）→ 旧实例继续存活 → 下次开机再报一次。修法：① 新增 `lib/resident-state.js`：把「不可替换（环境限制）」**记成状态**（原因 / 锁路径 / 端口 / 版本 / 次数，7 天有效）；② 宿主在重启前**先探锁可写性**，不可写就**不再重试注定失败的替换**，只记一条 —— **首次 `warn`**、之后每次开机降级为 `boot` 级「已知状态」（报告者原话：不想每次开机都看到一条 warn 永久持续）；③ 措辞与「漂移」显式分开：**「常驻实例不可替换（环境限制）」** + 出路（修权限后 restart，或 `dsh-memory watchdog --port N` 前台观察）；④ 面板 / `/version-check` / `align` 都能看到这个状态（`resident.replaceBlocked`；`align` 里是一条 `warn` 级结论，环境修好后自动清除）。`npm test` 共 **359 项** |
 
 <details>
-<summary>更早的更新日志（v0.10.31 及以前 · 共 58 版，点开查看）</summary>
+<summary>更早的更新日志（v0.10.32 及以前 · 共 59 版，点开查看）</summary>
 
 | 版本 | 日期 | 关键改动 |
 |---|---|---|
+| **v0.10.32** | 2026-10-15 | **「常驻实例不可替换」变成长期状态，而不是每次开机重试（#30 第五轮复测：A: 盘的稳态）**。报告者实测 5 天 44 次「版本漂移」，机制是**每一步都按设计工作、合起来永远换不掉**：升级 → 端口上仍是上一代 → 宿主探测漂移 → 拉起 `--replace` 助手 → 助手前置探到 `lock.writable=false` → **正确地拒绝**（0.10.29 的设计，零破坏）→ 旧实例继续存活 → 下次开机再报一次。修法：① 新增 `lib/resident-state.js`：把「不可替换（环境限制）」**记成状态**（原因 / 锁路径 / 端口 / 版本 / 次数，7 天有效）；② 宿主在重启前**先探锁可写性**，不可写就**不再重试注定失败的替换**，只记一条 —— **首次 `warn`**、之后每次开机降级为 `boot` 级「已知状态」（报告者原话：不想每次开机都看到一条 warn 永久持续）；③ 措辞与「漂移」显式分开：**「常驻实例不可替换（环境限制）」** + 出路（修权限后 restart，或 `dsh-memory watchdog --port N` 前台观察）；④ 面板 / `/version-check` / `align` 都能看到这个状态（`resident.replaceBlocked`；`align` 里是一条 `warn` 级结论，环境修好后自动清除）。`npm test` 共 **359 项** |
 | **v0.10.31** | 2026-10-15 | **`restart` 在「端口枚举很慢」的机器上 100% 失败的根因修复（#30 第三/四轮复测，报告者定位到行）**。机制：`--replace` 助手的顺序是「清场 → 端口空了才写锁 → 启动看门狗」，而清场里 `Get-NetTCPConnection` 实测要 **4–13.6 秒**且不受 8 秒预算约束 → 助手**永远走不到写锁那一步** → 锁里什么都没有 → `waitForTakeover`（要求「锁里出现新的活看门狗」）**必然超时** → CLI 与面板按钮在这类机器上 100% 报「（无响应）」，**与版本号无关**。修法：① **清场失败也必须留下登记**（`acquireWatchdogLock({force:true})`），现场不再出现「端口有 web、锁里空白」；② **`acquireWatchdogLock` 支持 `force`**（`--replace` 的语义就是替换同端口那个，不许让位 —— 否则助手在清场没跑完时先退出）；③ 0.10.30 已给枚举执行器加超时（`defaultExec` 真掐断子进程、`findPortListener({timeoutMs})` 逐层传递、清场给 ≤2.5s 有界值）；④ CLI 的 `restart` 结果**真的写进自动沉淀日志**（提示里一直这么说，但 CLI 路径过去不写）。他还实测到「两个接管助手互相赛跑」（宿主 tick + CLI 各拉一个）—— 登记 + force 之后这种赛跑的危害大幅降低（后到者接管登记，而不是双双留空）。`npm test` 共 **355 项** |
 | **v0.10.30** | 2026-10-15 | **两处「让整页不可用」的修复：畸形 tags 黑屏（#41）+ 接管链路的两个真病灶（#30 第三/四轮复测）**。① **#41**：`/write` 传字符串 `tags`（如 `"[\"a\",\"b\"]"`）被 `writeCard` 直接 `JSON.stringify` → **双重编码**落库 → 读出来仍是字符串 → 前端 `card.tags.slice(...).map` 抛错 → **React 根组件挂载失败、整页黑屏**（重启 DSH / 插件 / 常驻实例都无效，因为坏数据一直在库里）。现在 `normalizeTags()` 是**唯一入口**：数组 / JSON 字符串 / 逗号串 / **双重编码的旧数据**都收敛成数组，写路径与**所有读路径**都走它（既有坏数据不必用户手工修）；渲染层再加兜底（坏 tags 最多少显示几个标签，不许把整棵树带走）。② **#30**：报告者在我 0.10.29 里又抓出两处 —— `restoreWatchdogLock` 的「活登记」判定**少了 `!w.endedAt`**（PID 复用/正在退出时，写回会被放弃）；**Windows 端口枚举没有超时**（实测 `Get-NetTCPConnection` 无条件要 4–7.5 秒、一次 13.6 秒，而接管清场的 8 秒预算根本管不住它 → 决策基于过期数据）。现在 `defaultExec` 支持超时并真的掐断子进程、`findPortListener({timeoutMs})` 逐层传下去、接管清场给有界值（≤2.5s）。新增 `tests/tags-normalize.test.mjs`（4 项）+ `watchdog-restart` 2 项回归。`npm test` 共 **354 项** |
 | **v0.10.29** | 2026-10-14 | **失败的接管不再破坏现场（issue #30 复测的关键发现）**。报告者在 0.10.26 上实测：`restart` 失败后**锁文件被删除**、端口上还是同一个 web —— 现场从此看起来像「从来没有过常驻实例」，只剩一个孤儿。四处修复：① **释放锁不再删文件**（`releaseWatchdogLock` 留一条带 `endedAt` 的「已结束」记录，`status` 会显示「已退出（陈旧记录）」；这种槽**永不阻挡**新实例，pid 复用也不怕）；② **失败的 restart 把替换前的登记写回去**（`restoreWatchdogLock`，只在本端口没有活着的登记时才写）；③ **枚举不到占用者时不再误判「端口已空」**——`clearResidentForTakeover` 用 **TCP 复核**（受限环境里进程查询被拒会返回空，旧实现据此认为端口空出 → 新 web 绑不上 → 自检「（无响应）」+ 锁被清空），还在监听就中止接管且**一个登记都不动**；④ **锁写不进去时前置拒绝接管**（写不进锁 → 新实例无法登记 → 只会留孤儿；直接报错并给前台观察的出路）。另外 `restart` 失败信息补上「**端口上现在是谁**」+「锁有没有写回」，`status` 把「端口探测」与「锁登记」**分段标注**（报告者指出旧输出两者并列会误导）。`npm test` 共 **348 项** |

package/index.js

@@ -1309,8 +1309,9 @@ export function apply(ctx, config) {
     const mode = cfg0.autoWebMode || 'init'
     const port = Number(cfg0.webPort) || 7999
     const ensureOpts = { port, vaultRoot: vaultDir() }
-    const ensureWeb = () => import('./lib/web.js')
-      .then((m) => m.ensureWebServer(ensureOpts))
+    let hostTakeoverAt = 0   // 宿主接管的防抖（issue #30 ④）
+    const ensureWeb = (extra = {}) => import('./lib/web.js')
+      .then((m) => m.ensureWebServer({ ...ensureOpts, ...extra }))
       .then((info) => { refreshWebInfo(info); return info })
       .catch((error) => console.error('[memory-eternal] web server failed:', error?.message || error))
 
@@ -1345,6 +1346,30 @@ export function apply(ctx, config) {
             restartCount = 0
             // 活着也要回写记录：首轮 ensure 可能漂到过别的端口，此后没有任何校正点 → web-info 悬空（issue #29）
             refreshWebInfo({ url: `http://127.0.0.1:${port}`, port, spawned: false })
+            // issue #30 ④（治本）：只探「活着」不够 —— 端口上可能是**升级前的旧实例**，而看门狗路径在
+            // 锁不可写时被永久拒绝。锁可写 → 交给看门狗/漂移路径（宿主不抢）；锁不可写 → 宿主自己接管。
+            try {
+              const wd = await import('./lib/watchdog.js')
+              const served = await wd.probeServedVersion(port)
+              const cur = wd.currentPkgVersion()
+              const lockOk = Boolean(wd.probeLockWritable().writable)
+              const locked = wd.readWatchdogLock(process.env).watchdogs.some((w) => Number(w.port) === port && !w.endedAt && wd.isPidAlive(w.pid))
+              if (locked) { try { const st = await import('./lib/resident-state.js'); st.clearHostManaged(process.env) } catch { /* 无妨 */ } }
+              if (!locked && served && cur && served !== cur && !lockOk) {
+                if (!hostTakeoverAt || Date.now() - hostTakeoverAt > 60000) {
+                  hostTakeoverAt = Date.now()
+                  logCapture('system', 'warn', `常驻实例落后（端口 ${port} 服务 v${served} ≠ 本机 v${cur}）且看门狗锁不可写 → 宿主自己接管：停掉旧实例并在同端口拉起新实例`)
+                  await ensureWeb({ forceTakeover: true })
+                  const after = await wd.probeServedVersion(port)
+                  if (after && after === cur) {
+                    try { const st = await import('./lib/resident-state.js'); st.recordHostManaged(process.env, { port, version: cur, served: after, reason: 'lock-unwritable' }) } catch { /* 无妨 */ }
+                    logCapture('system', 'boot', `宿主接管完成：端口 ${port} 现在服务 v${after}（锁不可写，故由宿主保活）`)
+                  } else {
+                    logCapture('system', 'warn', `宿主接管后端口 ${port} 仍服务 v${after || '（无响应）'}（本机 v${cur}）`)
+                  }
+                }
+              }
+            } catch { /* 探测失败不影响保活 */ }
           }
         }
         // 立即跑一次（首启 + 间隔循环）

package/lib/api.js

@@ -328,6 +328,11 @@ export function createApi(deps = {}) {
         // 用户会以为实例坏了、反复重启。这里把「判不出来」单独标出来，并解释原因。
         const lockInfo = probeLockWritable(process.env)
         const managedKnown = residentManaged || lockInfo.writable
+        // 「宿主托管」（issue #30 ④）：锁不可写的机器上，宿主自己停旧实例、起新实例并保活 ——
+        // 锁里当然没有登记，但不等于「未托管 / 孤儿」。
+        let hostManaged = null
+        try { const st = await import('./resident-state.js'); hostManaged = st.hostManagedInfo(process.env) } catch { hostManaged = null }
+        const managedBy = residentManaged ? 'watchdog' : ((hostManaged && hostManaged.fresh) ? 'host' : '')
         // 「不可替换（环境限制）」的长期状态（issue #30 第五轮复测）：面板据此显示成**环境限制**，
         // 而不是每次开机都当成「漂移 → 替换失败」。
         let replaceBlocked = null
@@ -343,6 +348,8 @@ export function createApi(deps = {}) {
             served: residentServed,
             managed: residentManaged,
             managedKnown,
+            managedBy,
+            hostManaged,
             pid: process.pid,
             lock: lockInfo,
             replaceBlocked,