@khorsheed/dsh-ankh-guard 0.2.0 → 0.3.1

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # 变更记录
 
+## 0.3.1（2026-09-26）
+
+适配宿主 rc.1 线并实证 0.1.5/0.1.7 双线可用（0.1.5-rc.1 全量 boot 实证，2026-09-25；0.1.7-rc.1 为 3080 生产验证线）。
+
+- **修复 0.1.5 上 boot 即死**：preset 派生对宿主 preset-registry 包的导入从顶层静态导入改为运行期双名探测（0.1.7-rc.1 把官方包从 `dsh-agent-presets` 改名为 `dsh-agent-preset-registry`，0.1.5 宿主只装旧名，静态导入在模块解析期就炸穿整个 loader 树）；两个名字都装不上时按既定「无 preset 回落部署默认预设」降级，不再抛错
+- rc.1 适配波：中断续跑消息的 source 改为 V4 生产者归属 kind（退役的 `plugin` 外壳在 rc.1 持久层写入即抛）；preflight 执行器按宿主代际探测组合解析面（三代际→四代际）；`agent/created` 监听在 0.1.6 串行模式下保持 fire-and-forget
+- 插件清单展示元数据（`locale/*.json`）：rc.1 宿主插件页的卡面标题/描述中文化
+- 修复 boot 代际刷新过早：代际通道此前只凭「boot id 变了」就回 `ready/reload`，而 Web-server 座位与兄弟行共用——端口刚监听时 `/api` 路由 owner 可能还没挂上，被刷新的页面于是向半挂载的宿主发出第一次、也是唯一一次会话列表拉取，左侧列表只剩重启时被召回的那个会话（重新手动刷新才恢复）。现在代际回答先等新进程的 Loader 树结算（与 web-app 放行浏览器用的是同一信号）；就绪前的 poll 回 `waiting` 且**不下发 boot id**，标签页保持陈旧 id 持续重询，就绪即刷；无 Loader 的裸组合仍视为就绪。宿主侧新增「就绪前不回 reload、就绪后仍一次性刷新」单测，客户端侧新增「held 响应不消费代际判定」单测
+
+## 0.3.0（2026-09-11）
+
+适配宿主 0.1.5 线。
+
+- **BREAKING**：minHost 前移至 `0.1.5-rc.1`；宿主 `0.1.2-rc.1` ~ `0.1.4.x` 的用户请停留在 0.2.x 线（末版 `0.2.0`）
+- 冷读（用户输入停靠探测与 resume preset 推导）改走 0.1.5 的 handle 制 `sessionPersistence`（`open(id, 'read')` → `read` → `close`，与其他宿主面一样按调用探测）；0.1.5 已移除的一次性 `inspect` 会让重启 resume 静默降级
+- 生命周期漂移 lane 的通过计数改为环境感知：缺少部署 profile / 工具链缓存时合理跳过的绊线测试不再被硬编码期望数误伤（修 CI 红）
+- 开发基线随仓内 pin 对齐官方 `0.1.5-rc.1` / cordis `4.0.2`（单实例 cordis 终结 4.0.1/4.0.2 图分裂）；peer 范围保持宽松
+
 ## 0.2.0（2026-09-10）
 
 - **BREAKING**：minHost 前移至 `0.1.2-rc.1`；宿主 `0.1.0-rc.6` ~ `0.1.1-rc.2` 的用户请停留在 0.1.x 线（末版 `0.1.1`）

package/README.en.md

@@ -184,7 +184,7 @@ dsh-ankh-guard restart \
 
 Mounted as a cordis plugin (base bundle), the same surface is available as the `selfRestartGuard` service for in-app gates. Config: `maxAgeMinutes` (default 10), `stateDir`, `repoDir`, `reportRestartContext` (default `followup`), `fallbackGraceMs` (default 300000).
 
-Beyond the verify/record/canary gates, the service exposes `requestRestart({ start, profile, initiator })` — the in-process restart trigger for UI-grade callers (e.g. the mode switcher): `initiator` is required (the requesting session's real id) and the port comes from the launch record. With no live watchdog it drives `restart`; supervised instances drive the `reconfigure` transactional cutover (the only safe way to change the launch command under a watchdog). The credential/preflight/marker/lock gate chain is the CLI's own, refusals return a structured `{ accepted, stage, reason }` and never stop the instance. On the browser side, beside the cutover receipt channel there is a boot-generation channel: after an ordinary restart or a crash respawn, open tabs notice the process's boot id changed over the handoff long-poll and reload once to pick up the new bundle; a sustained disconnection (~5 s) raises a neutral overlay that never promises auto-recovery, and transient blips stay silent.
+Beyond the verify/record/canary gates, the service exposes `requestRestart({ start, profile, initiator })` — the in-process restart trigger for UI-grade callers (e.g. the mode switcher): `initiator` is required (the requesting session's real id) and the port comes from the launch record. With no live watchdog it drives `restart`; supervised instances drive the `reconfigure` transactional cutover (the only safe way to change the launch command under a watchdog). The credential/preflight/marker/lock gate chain is the CLI's own, refusals return a structured `{ accepted, stage, reason }` and never stop the instance. On the browser side, beside the cutover receipt channel there is a boot-generation channel: after an ordinary restart or a crash respawn, open tabs notice the process's boot id changed over the handoff long-poll and reload once to pick up the new bundle — before reloading it waits for the successor's composition to settle (the Web-server seat is shared, so `/api`'s route owner can still be mounting while the port already answers; until the Loader settles the poll is answered `waiting` with no boot id, the tab keeps asking with its stale id and reloads the moment the tree is up); visible sustained failures (~5 s) show a non-blocking connection banner with Retry; only confirmed cutovers use the restart overlay. Background/offline time does not count as failure. Returning to the foreground or online immediately resets backoff and restarts polling; stalled requests time out after 35 s and stale responses cannot trigger a reload.
 
 ## Model Experience
 
@@ -196,11 +196,12 @@ None.
 
 ## Compatibility
 
-- npm release line (`@deepseek-ai/dsh@0.1.2-rc.1`): ⚠️ degraded — everything works; the composition-preflight gate runs through the standalone `preflight-runner` (composing through the published `@deepseek-ai/dsh-app-boot` primitives with a drift tripwire, since 0.1.2-rc.1 still does not export `composeProfile`) wherever a dsh app layout resolves — `--harness-root`, the durable launch spec, `DSH_HARNESS`, or the default checkout. On a pure npm deployment with no harness checkout the gate reports a notice and proceeds instead. The original-tab bridge feature-probes the optional WebServer/connection authentication seams; hosts without token auth naturally take the existing-cookie path. Every other capability is intact on the npm line. minHost moves up to 0.1.2-rc.1 — older hosts stay on the previous release line.
+- npm release line (`@deepseek-ai/dsh@0.1.5-rc.1`): supported — 0.1.5-rc.1 full-line boot-verified (42 packages including capture, 2026-09-25) — with two designed degrades. The composition-preflight gate runs through the standalone `preflight-runner` (composing through the published `@deepseek-ai/dsh-app-boot` primitives with a drift tripwire, since 0.1.5-rc.1 still does not export `composeProfile`) wherever a dsh app layout resolves — `--harness-root`, the durable launch spec, `DSH_HARNESS`, or the default checkout. On a pure npm deployment with no harness checkout the gate reports a notice and proceeds instead. The original-tab bridge feature-probes the optional WebServer/connection authentication seams; hosts without token auth naturally take the existing-cookie path. Cold reads (the parked probe and the preset derivation) ride the 0.1.5 handle-based sessionPersistence (`open(id, 'read')` → `read` → `close`; the one-shot `inspect` is gone). Every other capability is intact on the npm line. minHost stays 0.1.5-rc.1 — older hosts stay on the previous release line.
 - Historical verification: a live npm-host 0.1.1-rc.2 → 0.1.2-alpha.4 isolated cutover passed (transition preflight removed a v3 whole-unit projection cache with an old-schema record from a home copy, live apply quarantined the old file, and target completed Token URL → 303 → cookie 200, the ownership stability window, and canary at zero retries; the old file remained byte-exact in the cutover directory. An untransitioned control over the same home failed on the missing Alpha.4 record fields, demonstrating that acceptance covered the real schema break).
-- source line (deepseek-harness master, fork or upstream): ✅ (verifiedHost: 0.1.2-rc.1) — the gate runs through the standalone `preflight-runner` (resolves the published `@deepseek-ai/dsh-app-boot` etc. from the live checkout), so no fork patch is required.
+- source line (deepseek-harness master, fork or upstream): ✅ (verifiedHost: 0.1.7-rc.1) — the gate runs through the standalone `preflight-runner` (resolves the published `@deepseek-ai/dsh-app-boot` etc. from the live checkout), so no fork patch is required.
+- Dual-line evidence: the 0.1.5 boot passes end-to-end through three compat layers — the [preset-registry dual-name probe](../../.agents/notes/implemented/bug-fix/2026-09-25-preset-registry-dual-name-probe.md), [dual-shape typert codecs](../../.agents/notes/implemented/bug-fix/2026-09-25-typert-codec-dual-shape.md), and [typert faces carrying zod@4](../../.agents/notes/implemented/bug-fix/2026-09-25-typert-faces-carry-zod-v4.md).
 
-**Version line mapping**: 0.2.0 and up support host `0.1.2-rc.1` and later; hosts on `0.1.0-rc.6` ~ `0.1.1-rc.2` stay on the 0.1.x release line (last release `0.1.1`).
+**Version line mapping**: the first release after 0.2.0 supports host `0.1.5-rc.1` and later; hosts on `0.1.2-rc.1` stay on `0.2.0`, hosts on `0.1.0-rc.6` ~ `0.1.1-rc.2` stay on the 0.1.x release line (last release `0.1.1`).
 
 ## Known Limitations and Deferred Work
 
@@ -214,6 +215,10 @@ None.
 - **`restart`/`supervise` discover the listener via `lsof`** (macOS/Linux with lsof); the guard prefers absolute system paths, while other platforms need `--pid`.
 - **Kills are per-pid identity with a descendant sweep, never per process group** — the instance is not setsid'd, so `restart`, `schedule-exit`'s exit agent, and watchdog cleanup target recorded child/listener identities. Cutover forced paths `SIGSTOP` first, then revalidate a Linux boot/start-tick token or macOS `proc_pidinfo` microsecond start time; a mismatch is only resumed and refused. Descendants are likewise frozen and their parentage rechecked while walking `pgrep -P`. Ordinary non-cutover port recovery retains a bounded listener-cleanup escape hatch; cutovers never select or kill a process by port.
 
+## Test concurrency
+
+Process integration tests run up to 4 shards concurrently by default; the unit lane caps at 2. On constrained machines, use `DSH_TEST_MAX_WORKERS=1 pnpm --filter @khorsheed/dsh-ankh-guard test` to schedule every shard serially. The same variable applies to the repository-wide `pnpm gate`. This only reduces scheduling concurrency: it does not omit tests, extend assertion deadlines, or change production restart behavior. Invalid values retain the defaults.
+
 ## Changelog
 
 See [CHANGELOG.md](CHANGELOG.md).

package/README.i18n.yaml

@@ -2,5 +2,5 @@
 # last confirmed-consistent state. Both languages carry equal authority; after
 # editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write packages/ankh-guard/README.en.md
-packages/ankh-guard/README.en.md: 941f3ceb4d5738244b46f4492eb8fc6c823fd967
-packages/ankh-guard/README.md: ab62e07753b0e0e24ff833aae5aafd600e184e95
+packages/ankh-guard/README.en.md: 551302cb33397c2c0e363d86de2a9fd66d52185a
+packages/ankh-guard/README.md: 7bd89a16642978a8ded951d2248b2a51887c294c

package/README.md

@@ -183,7 +183,7 @@ dsh-ankh-guard restart \
 
 以 cordis 插件挂载（base bundle）后，同一套能力以 `selfRestartGuard` 服务的形式供应用内闸门使用。配置：`maxAgeMinutes`（默认 10）、`stateDir`、`repoDir`、`reportRestartContext`（默认 `followup`）、`fallbackGraceMs`（默认 300000）。
 
-除 verify/record/canary 等闸门外，服务还暴露 `requestRestart({ start, profile, initiator })`——UI 级调用方（如 mode-switcher）的进程内重启触发缝：`initiator` 必填（发起会话的真实 id），端口从 launch 记录自知；无活 watchdog 走 `restart`，受监督走 `reconfigure` 事务 cutover（受监督下唯一安全的换命令通道），凭证/preflight/marker/lock 全套闸门与 CLI 同源，拒绝返回结构化 `{ accepted, stage, reason }` 且绝不停机。浏览器侧，除 cutover receipt 通道外还有 boot 代际通道：普通重启或崩溃救回后，打开的标签页经 handoff 长轮询发现进程 boot id 已变，自动全页刷新一次拿到新 bundle；持续断连约 5 秒挂中性遮罩（不承诺自动恢复），瞬时抖动不闪屏。
+除 verify/record/canary 等闸门外，服务还暴露 `requestRestart({ start, profile, initiator })`——UI 级调用方（如 mode-switcher）的进程内重启触发缝：`initiator` 必填（发起会话的真实 id），端口从 launch 记录自知；无活 watchdog 走 `restart`，受监督走 `reconfigure` 事务 cutover（受监督下唯一安全的换命令通道），凭证/preflight/marker/lock 全套闸门与 CLI 同源，拒绝返回结构化 `{ accepted, stage, reason }` 且绝不停机。浏览器侧，除 cutover receipt 通道外还有 boot 代际通道：普通重启或崩溃救回后，打开的标签页经 handoff 长轮询发现进程 boot id 已变，自动全页刷新一次拿到新 bundle；刷新前会等新进程的组合挂载完成（Web-server 座位与兄弟行共用，端口刚应答时 `/api` 路由 owner 可能还没挂上；Loader 结算前一律回 `waiting` 且不下发 boot id，标签页保持陈旧 id 继续问，就绪即刷）；仅前台持续失败约 5 秒后显示带重试按钮的轻量连接提示；只有确认的 cutover 使用重启遮罩。后台或离线时间不计入失败时长；回前台或恢复联网立即清除退避并重新轮询；挂起的请求在 35 秒后超时，过期响应不能触发刷新。
 
 ## Model Experience
 
@@ -195,11 +195,12 @@ dsh-ankh-guard restart \
 
 ## Compatibility
 
-- npm 发布线（`@deepseek-ai/dsh@0.1.2-rc.1`）：⚠️ 降级——一切可用；composition-preflight 门禁通过独立的 `preflight-runner` 运行（0.1.2-rc.1 仍未导出 `composeProfile`，runner 改经已发布的 `@deepseek-ai/dsh-app-boot` 原语组装，带漂移绊线测试），只要能解析到 dsh app 布局——`--harness-root`、耐久 launch spec、`DSH_HARNESS` 或默认检出路径——就完整运行。没有 harness 检出的纯 npm 部署下门禁退化为提示后放行。原标签页桥会探测可选 WebServer/connection 认证 seam，不使用 token 认证的宿主自然走现有 Cookie 路径；其余能力在 npm 线上完整。minHost 前移至 0.1.2-rc.1，旧宿主请停留在旧发布线。
+- npm 发布线（`@deepseek-ai/dsh@0.1.5-rc.1`）：支持——0.1.5-rc.1 全量 boot 实证通过（42 包含 capture，2026-09-25）——带两处设计内降级。composition-preflight 门禁通过独立的 `preflight-runner` 运行（0.1.5-rc.1 仍未导出 `composeProfile`，runner 改经已发布的 `@deepseek-ai/dsh-app-boot` 原语组装，带漂移绊线测试），只要能解析到 dsh app 布局——`--harness-root`、耐久 launch spec、`DSH_HARNESS` 或默认检出路径——就完整运行。没有 harness 检出的纯 npm 部署下门禁退化为提示后放行。原标签页桥会探测可选 WebServer/connection 认证 seam，不使用 token 认证的宿主自然走现有 Cookie 路径；冷读（停靠探测与 preset 推导）走 0.1.5 的 handle 制 sessionPersistence（`open(id, 'read')` → `read` → `close`，一次性 `inspect` 已移除）。其余能力在 npm 线上完整。minHost 保持 0.1.5-rc.1，旧宿主请停留在旧发布线。
 - 历史验证：npm host 的 0.1.1-rc.2 → 0.1.2-alpha.4 隔离切换已通过（transition preflight 在 home 副本上移开带旧 schema record 的 v3 whole-unit projection cache，live apply 隔离旧文件，target 以零重试完成 Token URL → 303 → Cookie 200、ownership 稳定窗口与 canary；旧文件逐字节保留在 cutover 目录。相同 home 的无 transition 对照因缺少 Alpha.4 record 字段而拒绝，证明验收覆盖了真实 schema 断裂面）。
-- 源码线（deepseek-harness master，fork 或上游）：✅（verifiedHost: 0.1.2-rc.1）——门禁通过独立的 `preflight-runner` 运行（从在线 checkout 解析已发布的 `@deepseek-ai/dsh-app-boot` 等），不再需要 fork 补丁。
+- 源码线（deepseek-harness master，fork 或上游）：✅（verifiedHost: 0.1.7-rc.1）——门禁通过独立的 `preflight-runner` 运行（从在线 checkout 解析已发布的 `@deepseek-ai/dsh-app-boot` 等），不再需要 fork 补丁。
+- 双线证据：0.1.5 的 boot 经三层兼容修复端到端通过——[preset-registry 双名探测](../../.agents/notes/implemented/bug-fix/2026-09-25-preset-registry-dual-name-probe.md)、[typert codec 双形状](../../.agents/notes/implemented/bug-fix/2026-09-25-typert-codec-dual-shape.md)、[face 自带 zod@4](../../.agents/notes/implemented/bug-fix/2026-09-25-typert-faces-carry-zod-v4.md)。
 
-**版本线对照**：0.2.0 起支持宿主 `0.1.2-rc.1` 及以后；宿主 `0.1.0-rc.6` ~ `0.1.1-rc.2` 的用户请停留在 0.1.x 发布线（末版 `0.1.1`）。
+**版本线对照**：0.2.0 之后的首个发布起支持宿主 `0.1.5-rc.1` 及以后；宿主 `0.1.2-rc.1` 请停留在 `0.2.0`，宿主 `0.1.0-rc.6` ~ `0.1.1-rc.2` 请停留在 0.1.x 发布线（末版 `0.1.1`）。
 
 ## Known Limitations and Deferred Work
 
@@ -213,6 +214,10 @@ dsh-ankh-guard restart \
 - **`restart`/`supervise` 通过 `lsof` 发现监听者**（macOS / 带 lsof 的 Linux）；guard 优先使用系统绝对路径，其他平台需用 `--pid`。
 - **杀进程一律按单 pid identity + 后代回收，从不按进程组**——实例不是 setsid 的，所以 `restart`、`schedule-exit` 的退出代理和 watchdog 清理都针对已记录的 child/listener；cutover 强制路径先 `SIGSTOP`，再用 Linux boot/start-tick 或 macOS `proc_pidinfo` 微秒启动时间复核 identity，不匹配就只 `SIGCONT` 并拒绝，然后才沿 `pgrep -P` 冻结、复核亲缘并回收后代。普通非 cutover 端口恢复仍有受限的 listener 清理兜底；cutover 禁止凭端口选择或杀进程。
 
+## 测试并发
+
+进程集成测试默认并行运行 4 个分片，unit lane 上限为 2。资源紧张时可用 `DSH_TEST_MAX_WORKERS=1 pnpm --filter @khorsheed/dsh-ankh-guard test` 串行调度全部分片；全仓 `pnpm gate` 也可使用这个环境变量。只降低调度并发，不减少测试、延长断言期限或改变生产重启行为；无效值保留默认值。
+
 ## 变更记录
 
 见 [CHANGELOG.md](CHANGELOG.md)。

package/lib/cli.js

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 import { i as resolveStateDir, n as isDirectInvocation, r as resolveRepoDir, t as SRC_ARTIFACT_PATTERN } from "./defaults-CduvOcGq.js";
-import { A as writeStableLaunchSpec, C as prepareLaunchCutover, D as selectedLaunchSpec, E as recordCutoverEvent, F as workingTreeChanges, M as currentHead, N as isWorkingTreeClean, O as summarizeLaunchState, P as resetToCheckpoint, T as readLaunchState, _ as writeRestartOutcome, b as activeCutover, c as readInstanceLaunch, f as writeAdoptionRecord, h as writeInstanceLaunchAsSupervisor, j as commitCheckpoint, k as writeCutoverControl, p as writeCompositionRecovery, u as readSkillRegistration, w as readCutoverReceipt, x as commandSha256, y as writeUnexpectedExitRecord } from "./restart-context-DUyExi9O.js";
+import { A as writeStableLaunchSpec, C as prepareLaunchCutover, D as selectedLaunchSpec, E as recordCutoverEvent, F as workingTreeChanges, M as currentHead, N as isWorkingTreeClean, O as summarizeLaunchState, P as resetToCheckpoint, T as readLaunchState, _ as writeRestartOutcome, b as activeCutover, c as readInstanceLaunch, f as writeAdoptionRecord, h as writeInstanceLaunchAsSupervisor, j as commitCheckpoint, k as writeCutoverControl, p as writeCompositionRecovery, u as readSkillRegistration, w as readCutoverReceipt, x as commandSha256, y as writeUnexpectedExitRecord } from "./restart-context-DlaDZWKq.js";
 import { _ as processIdentity, c as appendTestLifecycleEvent, d as registerTestProcess, f as discoverLaunchCommand, h as killPidTree, l as appendTestLifecycleEventForProcess, m as findPidOnPort, n as TEST_PROCESS_ROLE_ENV, p as findOwnedListener, r as TEST_PROCESS_TEMP_ROOT_ENV, t as TEST_PROCESS_PORT_ENV, u as registerCurrentTestProcess, v as processIdentityMatches } from "./test-seam-dwvaKjRp.js";
 import { a as setProvenDeployment, c as lastGoodBootRevision, d as pidAlive, f as stateFile, i as setCheckpoint, l as livePidIn, n as loadState, r as recordCredential, s as verifyCredential, t as clearCredential, u as liveWatchdogPid } from "./state-CZMypGkB.js";
 import { execFileSync, spawn } from "node:child_process";

package/lib/client.js

@@ -13,8 +13,9 @@ window.__ModuleLoader__.load({
 		const ACTIVE_RETRY_MS = 250;
 		const ERROR_RETRY_MIN_MS = 1e3;
 		const ERROR_RETRY_MAX_MS = 3e4;
-		/** Sustained-failure threshold for the disconnected overlay; transient blips never show it. */
-		const DISCONNECTED_OVERLAY_MS = 5e3;
+		/** Sustained-failure threshold for the connection notice; transient blips never show it. */
+		const DISCONNECTED_NOTICE_MS = 5e3;
+		const REQUEST_TIMEOUT_MS = 35e3;
 		/** No Cordis services are needed; this is a same-origin browser lifecycle observer. */
 		const inject = [];
 		function encodeBase64Url(bytes) {
@@ -80,16 +81,17 @@ window.__ModuleLoader__.load({
 			writePending(pending);
 			return pending;
 		}
-		function waitingOverlay(kind = "restarting") {
+		function waitingOverlay(kind = "restarting", retry) {
 			const existing = document.getElementById("ankh-guard-browser-handoff");
-			if (existing !== null) return existing;
+			if (existing?.dataset.kind === "restarting" && kind === "disconnected") return existing;
+			const element = existing ?? document.createElement("div");
 			const zh = navigator.language.toLowerCase().startsWith("zh");
-			const element = document.createElement("div");
 			element.id = "ankh-guard-browser-handoff";
+			element.dataset.kind = kind;
 			element.setAttribute("role", "status");
 			element.setAttribute("aria-live", "polite");
-			element.textContent = kind === "disconnected" ? zh ? "连接已断开,等待服务恢复。" : "Connection lost; waiting for the service to recover." : zh ? "dsh 正在重启；此标签页会自动恢复。" : "dsh is restarting; this tab will recover automatically.";
-			element.style.cssText = [
+			element.textContent = kind === "disconnected" ? zh ? "连接暂时中断，正在重试…" : "Connection interrupted; retrying…" : zh ? "dsh 正在重启；此标签页会自动恢复。" : "dsh is restarting; this tab will recover automatically.";
+			element.style.cssText = kind === "restarting" ? [
 				"position:fixed",
 				"inset:0",
 				"z-index:2147483647",
@@ -100,20 +102,48 @@ window.__ModuleLoader__.load({
 				"color:#fff",
 				"font:500 16px/1.5 system-ui,sans-serif",
 				"text-align:center"
+			].join(";") : [
+				"position:fixed",
+				"top:calc(env(safe-area-inset-top,0px) + 12px)",
+				"left:12px",
+				"right:12px",
+				"max-width:520px",
+				"margin:0 auto",
+				"box-sizing:border-box",
+				"z-index:2147483647",
+				"display:flex",
+				"align-items:center",
+				"justify-content:space-between",
+				"gap:12px",
+				"padding:12px 16px",
+				"border:1px solid var(--dsw-alias-border-l2,#8885)",
+				"border-radius:16px",
+				"background:var(--dsw-alias-bg-base,#fff)",
+				"color:var(--dsw-alias-label-primary,#181a20)",
+				"box-shadow:0 4px 24px #0002",
+				"font:400 15px/1.5 system-ui,sans-serif"
 			].join(";");
-			document.documentElement.append(element);
+			if (kind === "disconnected" && retry) {
+				const button = document.createElement("button");
+				button.textContent = zh ? "重试" : "Retry";
+				button.style.cssText = "flex:none;border:0;background:transparent;color:var(--dsw-alias-state-business-primary,#4d6bfe);font:inherit;min-height:36px;cursor:pointer";
+				button.onclick = retry;
+				element.append(button);
+			}
+			if (!existing) (document.body ?? document.documentElement).append(element);
 			return element;
 		}
-		async function post(body) {
+		async function post(body, signal) {
 			return fetch(ROUTE, {
 				method: "POST",
+				signal,
 				credentials: "same-origin",
 				cache: "no-store",
 				headers: { "content-type": "application/json" },
 				body: JSON.stringify(body)
 			});
 		}
-		async function acknowledge(pending) {
+		async function acknowledge(pending, signal) {
 			return (await post({
 				version: 1,
 				operation: "ack",
@@ -121,7 +151,7 @@ window.__ModuleLoader__.load({
 				channel: pending.channel,
 				authentication: pending.authentication,
 				...pending.capability !== void 0 ? { capability: pending.capability } : {}
-			})).status === 204;
+			}, signal)).status === 204;
 		}
 		/** Install the polling/reload loop for this tab's lifetime. */
 		function apply(_ctx) {
@@ -131,21 +161,61 @@ window.__ModuleLoader__.load({
 			let cap;
 			let errorRetryMs = ERROR_RETRY_MIN_MS;
 			let firstFailureAt;
+			let request;
+			let lastWakeAt = -Infinity;
+			const foreground = () => document.visibilityState !== "hidden" && navigator.onLine !== false;
+			const clearConnectionNotice = () => {
+				const notice = document.getElementById("ankh-guard-browser-handoff");
+				if (notice?.dataset.kind === "disconnected") notice.remove();
+			};
+			const pause = () => {
+				if (timer !== void 0) clearTimeout(timer);
+				timer = void 0;
+				const previous = request;
+				request = void 0;
+				previous?.abort();
+				firstFailureAt = void 0;
+				errorRetryMs = ERROR_RETRY_MIN_MS;
+				clearConnectionNotice();
+			};
+			const wake = () => {
+				if (disposed || !foreground() || Date.now() - lastWakeAt < 500) return;
+				lastWakeAt = Date.now();
+				pause();
+				schedule();
+			};
+			const visibility = () => {
+				if (!foreground()) {
+					lastWakeAt = -Infinity;
+					pause();
+				} else wake();
+			};
+			const page = (event) => {
+				if (event.persisted) wake();
+			};
 			const noteDisconnected = () => {
 				firstFailureAt ??= Date.now();
-				if (Date.now() - firstFailureAt >= DISCONNECTED_OVERLAY_MS) waitingOverlay("disconnected");
+				if (Date.now() - firstFailureAt >= DISCONNECTED_NOTICE_MS) waitingOverlay("disconnected", wake);
 			};
 			const schedule = (delayMs = 0) => {
-				if (!disposed) timer = setTimeout(() => {
+				if (timer !== void 0) clearTimeout(timer);
+				if (!disposed && foreground()) timer = setTimeout(() => {
+					timer = void 0;
 					tick();
 				}, delayMs);
 			};
 			const tick = async () => {
-				if (disposed) return;
+				if (disposed || !foreground() || request) return;
+				const current = new AbortController();
+				request = current;
+				const stale = () => disposed || request !== current || !foreground();
+				const deadline = setTimeout(() => current.abort(), REQUEST_TIMEOUT_MS);
 				try {
 					if (pending !== null) {
 						waitingOverlay();
-						if (await acknowledge(pending)) {
+						const acknowledged = await acknowledge(pending, current.signal);
+						if (stale()) return;
+						if (acknowledged) {
 							const returnPath = pending.returnPath;
 							const originalTab = pending.channel === "original-tab";
 							sessionStorage.removeItem(PENDING_KEY);
@@ -169,7 +239,8 @@ window.__ModuleLoader__.load({
 						operation: "poll",
 						capability: tabCapability,
 						...knownBootId === null ? {} : { knownBootId }
-					});
+					}, current.signal);
+					if (stale()) return;
 					if (!response.ok) {
 						noteDisconnected();
 						schedule(errorRetryMs);
@@ -179,6 +250,7 @@ window.__ModuleLoader__.load({
 					errorRetryMs = ERROR_RETRY_MIN_MS;
 					firstFailureAt = void 0;
 					const result = await response.json();
+					if (stale()) return;
 					if (typeof result.bootId === "string") sessionStorage.setItem(BOOT_ID_KEY, result.bootId);
 					if (result.state === "idle") {
 						document.getElementById("ankh-guard-browser-handoff")?.remove();
@@ -232,17 +304,32 @@ window.__ModuleLoader__.load({
 						return;
 					}
 				} catch {
+					if (stale()) return;
 					noteDisconnected();
 					schedule(errorRetryMs);
 					errorRetryMs = Math.min(errorRetryMs * 2, ERROR_RETRY_MAX_MS);
 					return;
+				} finally {
+					clearTimeout(deadline);
+					if (request === current) request = void 0;
 				}
 				schedule(ACTIVE_RETRY_MS);
 			};
+			document.addEventListener("visibilitychange", visibility);
+			window.addEventListener("online", wake);
+			window.addEventListener("offline", visibility);
+			window.addEventListener("pageshow", page);
+			window.addEventListener("dsh-mobile-foreground", wake);
 			tick();
 			return () => {
 				disposed = true;
-				if (timer !== void 0) clearTimeout(timer);
+				pause();
+				document.removeEventListener("visibilitychange", visibility);
+				window.removeEventListener("online", wake);
+				window.removeEventListener("offline", visibility);
+				window.removeEventListener("pageshow", page);
+				window.removeEventListener("dsh-mobile-foreground", wake);
+				document.getElementById("ankh-guard-browser-handoff")?.remove();
 			};
 		}
 		//#endregion

package/lib/index.js

@@ -1,5 +1,5 @@
 import { i as resolveStateDir, r as resolveRepoDir, t as SRC_ARTIFACT_PATTERN } from "./defaults-CduvOcGq.js";
-import { M as currentHead, N as isWorkingTreeClean, P as resetToCheckpoint, S as cutoverBlocksWake, a as interruptedSnapshotFile, b as activeCutover, c as readInstanceLaunch, d as restartContextText, g as writeInterruptedSnapshot, i as continueInterruptedText, j as commitCheckpoint, l as readInterruptedSnapshot, m as writeInstanceLaunch, n as buildLaunchCommand, o as isParkedOnUserInput, r as continueAndReportText, s as pendingRestartRecord, t as acknowledgeRestartRecord, v as writeSkillRegistration, w as readCutoverReceipt } from "./restart-context-DUyExi9O.js";
+import { M as currentHead, N as isWorkingTreeClean, P as resetToCheckpoint, S as cutoverBlocksWake, a as interruptedSnapshotFile, b as activeCutover, c as readInstanceLaunch, d as restartContextText, g as writeInterruptedSnapshot, i as continueInterruptedText, j as commitCheckpoint, l as readInterruptedSnapshot, m as writeInstanceLaunch, n as buildLaunchCommand, o as isParkedOnUserInput, r as continueAndReportText, s as pendingRestartRecord, t as acknowledgeRestartRecord, v as writeSkillRegistration, w as readCutoverReceipt } from "./restart-context-DlaDZWKq.js";
 import { _ as processIdentity, g as listeningPortsForPid, v as processIdentityMatches } from "./test-seam-dwvaKjRp.js";
 import { f as stateFile, i as setCheckpoint, n as loadState, r as recordCredential, s as verifyCredential, t as clearCredential, u as liveWatchdogPid } from "./state-CZMypGkB.js";
 import { spawn } from "node:child_process";
@@ -11,7 +11,6 @@ import { dirname, join, resolve, sep } from "node:path";
 import { fileURLToPath } from "node:url";
 import z from "@deepseek-ai/schemastery";
 import { createUserMessage } from "@deepseek-ai/dsh-llm";
-import * as agentPresetsHost from "@deepseek-ai/dsh-agent-presets";
 //#region lib/types/browser-handoff.js
 /**
 * Browser handoff bridge for launch cutovers.
@@ -31,6 +30,14 @@ import * as agentPresetsHost from "@deepseek-ai/dsh-agent-presets";
 * means the process it knew is gone — answer ready/reload. A cutover receipt
 * always wins over the generation check: during a cutover the old tab's known
 * id is already stale, and the receipt protocol owns the pacing.
+*
+* The generation answer waits for the successor's composition to settle. The
+* shared Web-server seat answers as soon as it listens — well before sibling
+* rows mount — and a page that loads then calls into a half-mounted /api
+* surface (the Web app gates its own browser handoff on the same Loader
+* settlement for that reason). Until then the poll is answered `waiting`
+* WITHOUT the boot id: teaching the tab the successor's id would consume its
+* one-shot generation check and strand it on an unusable page.
 */
 const BROWSER_HANDOFF_ROUTE = "/_ankh-guard/browser-handoff";
 const CAPABILITY_PATTERN = /^[A-Za-z0-9_-]{43}$/;
@@ -278,6 +285,10 @@ function createBrowserHandoffHandler(dependencies) {
 				});
 			};
 			if (bootId !== void 0 && message.knownBootId !== void 0 && message.knownBootId !== bootId && activeCutover(dependencies.stateDir) === null) {
+				if (dependencies.applicationReady?.() === false) {
+					json(res, 200, { state: "waiting" });
+					return;
+				}
 				respond(200, {
 					state: "ready",
 					action: "reload",
@@ -448,7 +459,8 @@ function registerBrowserHandoff(ctx, stateDir) {
 		if (webServer === void 0) return;
 		const handler = createBrowserHandoffHandler({
 			stateDir,
-			connectionProvider: () => webCtx.get("connection")
+			connectionProvider: () => webCtx.get("connection"),
+			applicationReady: applicationReadyProbe(webCtx)
 		});
 		webCtx.effect(() => webServer.register({
 			kind: "exact",
@@ -457,6 +469,30 @@ function registerBrowserHandoff(ctx, stateDir) {
 		}), "ankh-guard: browser handoff route");
 	});
 }
+/**
+* Build the generation channel's readiness probe from the Loader tree.
+*
+* The Web-server seat is shared: it answers as soon as it listens, while
+* sibling rows — including the /api route owner a reloaded page immediately
+* calls into — are still mounting. The Web app gates its own URL line and
+* browser handoff on this exact settlement, so the guard's automatic reload
+* must wait for it too. A composition without a Loader is already complete.
+*
+* Only settlement counts as ready: a failed tree leaves the tab on its old
+* page (the watchdog's crash recovery owns that outcome), and the next healthy
+* process answers the still-stale poll.
+* @param ctx - context owning the Loader service.
+* @returns probe consulted by every boot-generation poll.
+*/
+function applicationReadyProbe(ctx) {
+	const settled = ctx.get("loader")?.await();
+	if (settled === void 0) return () => true;
+	let ready = false;
+	settled.then(() => {
+		ready = true;
+	}, () => {});
+	return () => ready;
+}
 //#endregion
 //#region lib/types/restart-request.js
 /**
@@ -628,6 +664,29 @@ async function requestRestart(request, context) {
 }
 //#endregion
 //#region lib/types/index.js
+let presetRegistryProbe;
+/**
+* Resolve the preset-registry module by name. The 0.1.7-rc.1 host renamed
+* `@deepseek-ai/dsh-agent-presets` to `@deepseek-ai/dsh-agent-preset-registry`
+* (the resolve/mount/livePresetMounts/agentPresetProjectionDefinition API
+* carried over); 0.1.5/0.1.6 hosts install only the old name, and a host
+* without preset composition installs neither — `null`, and the derivation
+* then receives `{}`, the established no-preset degrade (the resume falls
+* back to the deployment's default preset). A STATIC import of either name is
+* a module-resolution failure at load on hosts installing only the other —
+* pack-dist strips `dependencies`, so the specifier resolves against the
+* host's install tree. Both specifiers stay static string literals so tsdown
+* externalizes them and tsc type-checks them.
+* @returns the module namespace, or null when neither name resolves.
+*/
+function loadPresetRegistry() {
+	presetRegistryProbe ??= import("@deepseek-ai/dsh-agent-preset-registry").catch(() => import("@deepseek-ai/dsh-agent-presets")).catch(() => null);
+	return presetRegistryProbe;
+}
+/** Test seam: drop the cached probe so a mocked resolution path re-runs. */
+function resetPresetRegistryProbeForTest() {
+	presetRegistryProbe = void 0;
+}
 /**
 * Which preset a session actually runs, newest selection winning. The rc host
 * exports `resolveSessionPreset` for exactly this fold; the 0.1.2 host
@@ -649,6 +708,25 @@ function deriveSessionPreset(host, session) {
 	}
 	return host.resolveSessionPreset?.(session);
 }
+/** Probe the session-persistence service's cold-read face. */
+function probeColdReader(ctx) {
+	const service = ctx.get("sessionPersistence");
+	if (service === void 0 || service === null) return void 0;
+	return typeof service.open === "function" ? service : void 0;
+}
+/** Read one persisted session's header and full log through a read handle. */
+async function readColdLog(persistence, id) {
+	const handle = await persistence.open(id, "read");
+	try {
+		const cold = await handle.read(0);
+		return {
+			meta: handle.header,
+			events: cold.events
+		};
+	} finally {
+		await handle.close();
+	}
+}
 const Config = z.object({
 	maxAgeMinutes: z.natural().min(1).default(10),
 	stateDir: z.string().default(""),
@@ -769,7 +847,7 @@ function apply(ctx, config) {
 				text
 			}],
 			source: {
-				kind: "plugin",
+				kind: "ankh-guard",
 				plugin: name,
 				form: "snapshot",
 				sections: [{
@@ -789,9 +867,9 @@ function apply(ctx, config) {
 			if (probe === void 0) {
 				probe = (async () => {
 					try {
-						const persistence = ctx.get("sessionPersistence");
+						const persistence = probeColdReader(ctx);
 						if (persistence === void 0) return false;
-						const { events } = await persistence.inspect(id);
+						const { events } = await readColdLog(persistence, id);
 						return isParkedOnUserInput(events);
 					} catch {
 						return false;
@@ -812,7 +890,11 @@ function apply(ctx, config) {
 			if (cutoverBlocksWake(stateDir)) return;
 			const id = agent.id;
 			const exitAt = pendingContinue.get(id);
-			const record = followupReport ? pendingRestartRecord(stateDir) : null;
+			let record = followupReport ? pendingRestartRecord(stateDir) : null;
+			if (record !== null && record.initiator === void 0 && record.unexpected !== true && record.compositionRecovered !== true && record.error === void 0) {
+				acknowledgeRestartRecord(stateDir, record, Date.now());
+				record = null;
+			}
 			const owesReport = record !== null && (record.initiator === void 0 || id === record.initiator);
 			if (exitAt !== void 0) {
 				(async () => {
@@ -876,10 +958,10 @@ function apply(ctx, config) {
 			if (selection?.model !== void 0) agentOptions.model = selection.model;
 			let setup;
 			const presets = ctx.get("agentPresets");
-			const persistence = ctx.get("sessionPersistence");
+			const persistence = probeColdReader(ctx);
 			if (presets !== void 0 && persistence !== void 0) {
-				const inspected = await persistence.inspect(id);
-				const presetId = deriveSessionPreset(agentPresetsHost, {
+				const inspected = await readColdLog(persistence, id);
+				const presetId = deriveSessionPreset(await loadPresetRegistry() ?? {}, {
 					header: inspected.meta,
 					events: inspected.events
 				});
@@ -965,7 +1047,7 @@ function apply(ctx, config) {
 					text
 				}],
 				source: {
-					kind: "plugin",
+					kind: "ankh-guard",
 					plugin: name,
 					form: "snapshot",
 					sections: [{
@@ -1043,4 +1125,4 @@ function apply(ctx, config) {
 	})();
 }
 //#endregion
-export { Config, apply, deriveSessionPreset, inject, name };
+export { Config, apply, deriveSessionPreset, inject, loadPresetRegistry, name, resetPresetRegistryProbeForTest };

package/lib/preflight-runner.js

@@ -121,7 +121,7 @@ var PreflightInfraError = class extends Error {};
 * bundle layers in `dsh.profile.bundles` order, the profile user layer, the
 * home-level user layer, `--patch` overlays, the agent-presets roots overlay
 * (rc host line only; the 0.1.2 line's preset package self-ships its root),
-* then the telemetry switch. Two host API generations are mirrored and
+* then the telemetry switch. Three host API generations are mirrored and
 * feature-detected per run — see the `hostLine` branch below. Exported so
 * the drift tripwire can compare this assembly against the launcher's own
 * dump without booting anything.
@@ -147,13 +147,15 @@ async function composePreflightPatches(profile, patchFiles, root, home, binding
 	}
 	const composeEntries = appBoot.composeEntries;
 	const healProfilesModuleFallback = appBoot.healProfilesModuleFallback;
+	const createProfileResolutionGeneration = appBoot.createProfileResolutionGeneration;
+	const createRuntimeResolution = appBoot.createRuntimeResolution;
 	const loadOptionalPatches = appBoot.loadOptionalPatches;
 	const loadOverlayPatches = appBoot.loadOverlayPatches;
 	const loadProfile = appBoot.loadProfile;
 	const resolveDshHome = homePaths.resolveDshHome;
 	const anchor = binding.installAnchor;
 	const resolvedHome = resolveDshHome(home);
-	const hostLine = "DEFAULT_PROFILE_PATCH_RELOAD" in appBoot ? "0.1.2" : "rc";
+	const hostLine = "createRuntimeResolution" in appBoot ? "0.1.7" : "createProfileResolutionGeneration" in appBoot ? "0.1.6" : "DEFAULT_PROFILE_PATCH_RELOAD" in appBoot ? "0.1.2" : "rc";
 	if (hostLine === "rc") healProfilesModuleFallback(anchor, resolvedHome);
 	const composed = loadProfile(NAME, profile, anchor, resolvedHome, { userLayer: true });
 	writeFileSync(join(composed.dir, PROFILE_ROOT_FILENAME), PROFILE_ROOT_CONFIG);
@@ -162,6 +164,15 @@ async function composePreflightPatches(profile, patchFiles, root, home, binding
 		profile: composed,
 		home: resolvedHome
 	});
+	else if (hostLine === "0.1.6") await createProfileResolutionGeneration({
+		installAnchor: anchor,
+		profile: composed,
+		home: resolvedHome
+	});
+	else if (hostLine === "0.1.7") await createRuntimeResolution({
+		installAnchor: anchor,
+		profile: composed
+	});
 	const homePatches = loadOptionalPatches(NAME, join(resolvedHome, HOME_PATCH_FILENAME)) ?? [];
 	const overlays = patchFiles.flatMap((file) => loadOverlayPatches(NAME, resolve(file)));
 	const bundlePatches = composed.layers.flatMap((layer) => layer.patches);

package/lib/{restart-context-DUyExi9O.js → restart-context-DlaDZWKq.js}

@@ -902,12 +902,17 @@ function activeCutover(stateDir) {
 * Restart-record context injection and interrupted-session continuity. After
 * a scheduled restart, the FULL report waits for the initiating session's
 * root agent, whenever it resumes (session restore is lazy, so no other
-* session is ever woken for reporting); a record without an initiator is
-* claimed by the first root agent created. Separately, a snapshot written at
-* SIGTERM time (`interrupted-sessions.json`) records which root sessions had
-* a live turn when the process stopped, so the next restart boot can resume
-* those sessions and queue a "continue" turn. Pure logic reads the durable
-* files; the plugin wires them into `agent/created` and `agent.followup`.
+* session is ever woken for reporting). A record without an initiator splits
+* by kind: one carrying diagnostics someone must hear about (an unplanned
+* recovery, a composition rollback, a failed restart) is claimed by the
+* first root agent created, while a bare planned outcome — the restart was
+* driven from outside the host and the operator's terminal already has the
+* announcement — is settled without waking anyone. Separately, a snapshot
+* written at SIGTERM time (`interrupted-sessions.json`) records which root
+* sessions had a live turn when the process stopped, so the next restart
+* boot can resume those sessions and queue a "continue" turn. Pure logic
+* reads the durable files; the plugin wires them into `agent/created` and
+* `agent.followup`.
 */
 /** Absolute path of the restart record inside a state directory. */
 function restartRecordFile(stateDir) {

package/lib/types/browser-handoff.d.ts

@@ -41,6 +41,12 @@ interface BrowserHandoffDependencies {
     connection?: ConnectionSlice;
     /** Resolve lazily because WebServer can activate before the optional connection service. */
     connectionProvider?: () => ConnectionSlice | undefined;
+    /**
+     * Whether the serving composition has finished mounting, consulted only by
+     * the boot-generation channel. Omitted means ready — a hand-built tree
+     * without a Loader is already complete.
+     */
+    applicationReady?: () => boolean;
     /** Test seams; production defaults turn idle polling into a held request. */
     longPollMs?: number;
     longPollIntervalMs?: number;