dsh-loop-engine 0.1.5-rc1 → 0.1.5-rc3

package/README.md

@@ -20,30 +20,120 @@ Restart `dsh web`, then open **Settings → Loop engine**.
 > span changes.
 
 > **pnpm users:** pnpm 10+ blocks dependency build scripts by default, so the
-> install may report `@google/genai`, `node-pty`, and `protobufjs` as blocked.
-> This is expected — click **"Allow build scripts and retry"** (or run
-> `pnpm approve-builds`, or list them under `pnpm.onlyBuiltDependencies` in
-> your project root) and retry. Only the installing project can grant this;
-> the plugin cannot pre-approve its own dependencies.
+> install may fail with `ERR_PNPM_IGNORED_BUILDS` naming `esbuild`,
+> `@google/genai`, and `protobufjs` (all reached through the engine SDKs). This
+> is expected — allow them and retry, either interactively with
+> `pnpm approve-builds`, or by declaring them in the installing project's
+> `pnpm-workspace.yaml`:
+>
+> ```yaml
+> allowBuilds:
+>   esbuild: true
+>   '@google/genai': true
+>   protobufjs: true
+> ```
+>
+> Only the installing project can grant this; the plugin cannot pre-approve its
+> own dependencies. Note that `allowBuilds` is the pnpm 11 spelling — pnpm 11
+> **deletes** the legacy `onlyBuiltDependencies` (and `neverBuiltDependencies`,
+> `ignoredBuiltDependencies`) keys from `package.json` and no longer honors
+> them, so putting them there silently does nothing.
+
+### Running against a harness source checkout
+
+The install above assumes a **published** dsh (`npx @deepseek-ai/dsh`) and needs
+no extra setup. Booting the harness from its **source checkout**
+(`cd deepseek-harness && pnpm dsh web`) takes one more step, because the two
+halves then resolve harness packages to different files:
+
+| Side | `@deepseek-ai/dsh-scope` resolves to |
+|---|---|
+| Source-launched harness | `packages/core/scope/src/index.ts` (via tsconfig `paths`) |
+| Installed plugin (its tarball ships only `lib/`) | `packages/core/scope/lib/index.js` |
+
+That is one package loaded as two module instances. `dsh-scope` tags a context
+with a module-local `Symbol('dsh.scope')`, so a scope minted through one instance
+is invisible to the other, and resuming a session fails with:
+
+```
+agent-presets: refusing to compose an unscoped context;
+the scope key is what joins an agent to its preset
+```
+
+Bridge the profile's peers to the harness source so both halves share one
+instance. Set `HARNESS` to the harness checkout **as a `file://` URL**, then run
+this from the profile directory:
+
+```sh
+HARNESS=file:///path/to/deepseek-harness   # e.g. file:///D:/repos/deepseek-harness
+cd "$DSH_HOME/profiles/web" && mkdir -p shims
+while IFS='|' read -r name rel; do
+  mkdir -p "shims/$name"
+  printf '{"name":"@deepseek-ai/%s","version":"0.0.0","private":true,"type":"module","main":"index.mjs"}\n' \
+    "$name" > "shims/$name/package.json"
+  printf "export * from '%s/%s'\nimport * as mod from '%s/%s'\nexport default mod.default\n" \
+    "$HARNESS" "$rel" "$HARNESS" "$rel" > "shims/$name/index.mjs"
+done <<EOF
+cordis|vendor/cordis/src/index.ts
+schemastery|vendor/schemastery/src/index.ts
+dsh-agent|packages/core/agent/src/index.ts
+dsh-scope|packages/core/scope/src/index.ts
+dsh-session|packages/core/session/src/index.ts
+dsh-session-persistence|packages/session/session-persistence/src/index.ts
+dsh-settings|packages/settings/settings/src/index.ts
+dsh-subprocess|packages/subprocess/subprocess/src/index.ts
+dsh-timeout|packages/util/timeout/src/index.ts
+dsh-llm|packages/llm/llm/src/index.ts
+dsh-invariants|packages/runtime-diagnostics/invariants/src/index.ts
+dsh-home-paths|packages/util/home-paths/src/index.ts
+EOF
+```
+
+Then point the profile's `package.json` at them and reinstall:
+
+```sh
+node -e 'const f="package.json",j=require("./"+f),d=j.dependencies??={}
+for(const n of ["cordis","schemastery","dsh-agent","dsh-scope","dsh-session","dsh-session-persistence","dsh-settings","dsh-subprocess","dsh-timeout","dsh-llm","dsh-invariants","dsh-home-paths"])
+  d["@deepseek-ai/"+n]="file:./shims/"+n
+require("fs").writeFileSync(f,JSON.stringify(j,null,2)+"\n")'
+pnpm install
+```
+
+Restart `dsh web`. If something loads the `@deepseek-ai/dsh-scope/invariant`
+subpath, also give that shim an `invariant.mjs` (`export * from
+'$HARNESS/packages/core/scope/src/invariant.ts'`) and add
+`"./invariant": "./invariant.mjs"` to its `exports`.
+
+> Installing the plugin as a local **`link:`** checkout sidesteps this entirely:
+> when the checkout sits beside the harness repo it inherits the harness's own
+> `tsconfig.json` and with it the same `paths` mapping. The split only appears
+> when a *packed* plugin (npm or tarball) meets a *source* harness.
 
 ## Version compatibility
 
 dsh-loop-engine is versioned **in lockstep with the harness it targets**: the
-version is the harness version plus a plugin release counter (`0.1.5-rc1`
-targets harness `0.1.5-rc.1`), and every harness package it consumes is pinned
-exactly in `peerDependencies`. The two must be matched — a mismatch fails
-loudly at boot or session resume:
+version is the harness version plus a plugin release counter (`0.1.5-rc1` and
+`0.1.5-rc2` target harness `0.1.5-rc.1`; `0.1.5-rc3` targets harness
+`0.1.5-rc.2`), and every harness package it consumes is pinned exactly in
+`peerDependencies`. The two must be matched — a mismatch fails loudly at boot
+or session resume:
 
 | dsh-loop-engine | Requires harness |
 |---|---|
-| 0.1.5-rc1 | **0.1.5-rc.1** |
+| 0.1.5-rc3 | **0.1.5-rc.2** |
+| 0.1.5-rc1, 0.1.5-rc2 | 0.1.5-rc.1 |
 | 1.0.0-rc8 … 1.0.0-rc15 | 0.1.2-rc.1 |
 | 1.0.0-rc7 and earlier | 0.1.1-rc.2 |
 
-- **0.1.5-rc1 requires harness 0.1.5-rc.1.** It uses the 0.1.5 assistant-stream
-  contract (`assistant/message` embeds its exact timed `stream` and rejects
-  `sourceEventSeqs`), the driver-owned `Inbox` interface, the two-argument
-  `AgentSetup`, and the `SessionPersistence.create` / `open` handle seam.
+- **Each 0.1.5-rcN release requires the 0.1.5 patch it was built for.**
+  `0.1.5-rc1`/`0.1.5-rc2` require harness `0.1.5-rc.1`; `0.1.5-rc3` requires
+  harness `0.1.5-rc.2`. All three use the 0.1.5
+  assistant-stream contract (`assistant/message` embeds its exact timed
+  `stream` and rejects `sourceEventSeqs`), the driver-owned `Inbox` interface,
+  the two-argument `AgentSetup`, and the `SessionPersistence.create` / `open`
+  handle seam. `0.1.5-rc.2` is a client-UI/docs backport that leaves those
+  seams untouched, so the driver code is identical across `0.1.5-rc.1` and
+  `0.1.5-rc.2`.
 - Releases up to `1.0.0-rc15` used the plugin's own version series and target
   harness `0.1.2-rc.1`; they are not compatible with harness `0.1.5-rc.1`.
 - To use the plugin with an older harness, install the release matching it
@@ -89,11 +179,14 @@ they were created with.
   bridged into the web menu (built-ins plus user-level `~/.claude/commands/`)
   and forwarded to the engine, which expands them natively. Project-level
   `.claude/commands/` files stay engine-side and also work typed directly.
-- The Codex driver runs `codex app-server` and has no interactive tool
-  approval — permissions come from the session's `sandboxMode` +
-  `approvalPolicy`. Its `AGENTS.md` instruction files are surfaced through the
-  dsh skill-injection seam across every directory from the session cwd up to
-  the git root, plus `~/.codex/AGENTS.md`.
+- The Codex driver runs `codex app-server`; the thread starts with the
+  session's `sandboxMode` + `approvalPolicy` stance, and the model's runtime
+  approval requests (command, file-change, permissions) are answered through
+  the dsh approval seam — `request_user_input` questions go to the
+  user-questions seam and MCP elicitations are declined, all fail-closed when
+  their seam is absent. Its `AGENTS.md` instruction files are surfaced through
+  the dsh skill-injection seam across every directory from the session cwd up
+  to the git root, plus `~/.codex/AGENTS.md`.
 - The Pi driver runs `pi --mode rpc`; Pi has no permission system, so the whole
   child is sandboxed through the dsh subprocess service (default `read-only`).
   Its context files (`AGENTS.md`/`CLAUDE.md` with `AGENTS.override.md`

package/README.zh.md

@@ -14,6 +14,80 @@ dsh plugin --profile web add dsh-loop-engine
 
 > 切换引擎会重写 `cordis.patch.yml` 中一小段受管理的内容,文件里你写的其它部分都会保留,只改动插件自己的区间。
 
+> **pnpm 用户:** pnpm 10+ 默认拦截依赖的 build script,安装可能以
+> `ERR_PNPM_IGNORED_BUILDS` 失败,并列出 `esbuild`、`@google/genai`、
+> `protobufjs`(都经引擎 SDK 传递而来)。这是预期行为——放行后重试即可:可用
+> `pnpm approve-builds` 交互放行,或在安装项目的 `pnpm-workspace.yaml` 里声明:
+>
+> ```yaml
+> allowBuilds:
+>   esbuild: true
+>   '@google/genai': true
+>   protobufjs: true
+> ```
+>
+> 只有安装方能授予该权限,插件无法预先放行自己的依赖。注意 `allowBuilds` 是
+> pnpm 11 的写法——pnpm 11 会**删除** `package.json` 里遗留的
+> `onlyBuiltDependencies`(以及 `neverBuiltDependencies`、`ignoredBuiltDependencies`)
+> 且不再识别它们,写在那里会静默失效。
+
+### 源码启动 harness 时的额外步骤
+
+上面的安装针对 **发布版** dsh(`npx @deepseek-ai/dsh`),不需要额外操作。若改用**源码**启动 harness(`cd deepseek-harness && pnpm dsh web`),则要多做一步——因为两边会把 harness 的包解析到不同文件:
+
+| 一侧 | `@deepseek-ai/dsh-scope` 解析到 |
+|---|---|
+| 源码启动的 harness | `packages/core/scope/src/index.ts`(经 tsconfig `paths`) |
+| 安装的插件(包内只有 `lib/`) | `packages/core/scope/lib/index.js` |
+
+也就是同一个包被加载成了两个模块实例。`dsh-scope` 用模块私有的 `Symbol('dsh.scope')` 给 context 打标记,一个实例打的标记另一个实例读不到,于是恢复会话时报错:
+
+```
+agent-presets: refusing to compose an unscoped context;
+the scope key is what joins an agent to its preset
+```
+
+把 profile 的 peer 桥接到 harness 源码,让两边共用同一个实例。把 `HARNESS` 设为 harness checkout 的 **`file://` URL**,在 profile 目录下执行:
+
+```sh
+HARNESS=file:///path/to/deepseek-harness   # 例如 file:///D:/repos/deepseek-harness
+cd "$DSH_HOME/profiles/web" && mkdir -p shims
+while IFS='|' read -r name rel; do
+  mkdir -p "shims/$name"
+  printf '{"name":"@deepseek-ai/%s","version":"0.0.0","private":true,"type":"module","main":"index.mjs"}\n' \
+    "$name" > "shims/$name/package.json"
+  printf "export * from '%s/%s'\nimport * as mod from '%s/%s'\nexport default mod.default\n" \
+    "$HARNESS" "$rel" "$HARNESS" "$rel" > "shims/$name/index.mjs"
+done <<EOF
+cordis|vendor/cordis/src/index.ts
+schemastery|vendor/schemastery/src/index.ts
+dsh-agent|packages/core/agent/src/index.ts
+dsh-scope|packages/core/scope/src/index.ts
+dsh-session|packages/core/session/src/index.ts
+dsh-session-persistence|packages/session/session-persistence/src/index.ts
+dsh-settings|packages/settings/settings/src/index.ts
+dsh-subprocess|packages/subprocess/subprocess/src/index.ts
+dsh-timeout|packages/util/timeout/src/index.ts
+dsh-llm|packages/llm/llm/src/index.ts
+dsh-invariants|packages/runtime-diagnostics/invariants/src/index.ts
+dsh-home-paths|packages/util/home-paths/src/index.ts
+EOF
+```
+
+再把这些写进 profile 的 `package.json` 并重新安装:
+
+```sh
+node -e 'const f="package.json",j=require("./"+f),d=j.dependencies??={}
+for(const n of ["cordis","schemastery","dsh-agent","dsh-scope","dsh-session","dsh-session-persistence","dsh-settings","dsh-subprocess","dsh-timeout","dsh-llm","dsh-invariants","dsh-home-paths"])
+  d["@deepseek-ai/"+n]="file:./shims/"+n
+require("fs").writeFileSync(f,JSON.stringify(j,null,2)+"\n")'
+pnpm install
+```
+
+重启 `dsh web`。若有代码加载 `@deepseek-ai/dsh-scope/invariant` 子路径,再给该 shim 补一个 `invariant.mjs`(`export * from '$HARNESS/packages/core/scope/src/invariant.ts'`),并在它的 `exports` 里加上 `"./invariant": "./invariant.mjs"`。
+
+> 用本地 **`link:`** 方式安装插件可以完全绕开这一步:checkout 与 harness 仓库相邻时,它会继承 harness 自己的 `tsconfig.json`,从而共用同一份 `paths` 映射。这个分裂只在**打包版**插件(npm 或 tarball)遇到**源码版** harness 时出现。
+
 ### 环境要求
 
 - 使用 Claude Code 引擎时需要本机已安装并登录 Claude Code CLI。
@@ -23,15 +97,16 @@ dsh plugin --profile web add dsh-loop-engine
 
 ## 版本兼容
 
-`dsh-loop-engine` 与它针对的 harness **同版本对齐**:版本号即 harness 版本加插件发布序号(`0.1.5-rc1` 针对 harness `0.1.5-rc.1`),它消费的每个 harness 包都在 `peerDependencies` 里精确钉住。两者必须匹配——不匹配会在启动或会话恢复时响亮地失败:
+`dsh-loop-engine` 与它针对的 harness **同版本对齐**:版本号即 harness 版本加插件发布序号(`0.1.5-rc1`、`0.1.5-rc2` 针对 harness `0.1.5-rc.1`,`0.1.5-rc3` 针对 harness `0.1.5-rc.2`),它消费的每个 harness 包都在 `peerDependencies` 里精确钉住。两者必须匹配——不匹配会在启动或会话恢复时响亮地失败:
 
 | dsh-loop-engine | 需要 harness |
 |---|---|
-| 0.1.5-rc1 | **0.1.5-rc.1** |
+| 0.1.5-rc3 | **0.1.5-rc.2** |
+| 0.1.5-rc1、0.1.5-rc2 | 0.1.5-rc.1 |
 | 1.0.0-rc8 … 1.0.0-rc15 | 0.1.2-rc.1 |
 | 1.0.0-rc7 及更早 | 0.1.1-rc.2 |
 
-- **0.1.5-rc1 需要 harness 0.1.5-rc.1。** 它使用 0.1.5 的 assistant-stream 契约(`assistant/message` 内嵌精确计时的 `stream`,并禁止 `sourceEventSeqs`)、由 driver 自己实现的 `Inbox` 接口、双参数 `AgentSetup`,以及 `SessionPersistence.create` / `open` 句柄 seam。
+- **每个 0.1.5-rcN 版本需要它为之构建的那个 0.1.5 补丁。** `0.1.5-rc1`/`0.1.5-rc2` 需要 harness `0.1.5-rc.1`;`0.1.5-rc3` 需要 harness `0.1.5-rc.2`。三者都使用 0.1.5 的 assistant-stream 契约(`assistant/message` 内嵌精确计时的 `stream`,并禁止 `sourceEventSeqs`)、由 driver 自己实现的 `Inbox` 接口、双参数 `AgentSetup`,以及 `SessionPersistence.create` / `open` 句柄 seam。`0.1.5-rc.2` 是一次客户端 UI/文档 backport,没有触碰这些 seam,因此 driver 代码在 `0.1.5-rc.1` 与 `0.1.5-rc.2` 之间完全一致。
 - `1.0.0-rc15` 及以前的版本沿用插件自己的版本序列,针对 harness `0.1.2-rc.1`,与 harness `0.1.5-rc.1` 不兼容。
 - 要在更老的 harness 上使用本插件,请安装与之匹配的版本(例如 harness 0.1.2-rc.1 用 `npm i dsh-loop-engine@1.0.0-rc15`)。
 - 每个 tag 的 GitHub Release 正文会写明它针对的 harness 版本。
@@ -42,10 +117,15 @@ dsh plugin --profile web add dsh-loop-engine
 2. 要切回默认,选 **In-process** 再重启即可。
 3. 卸载插件:`dsh plugin --profile web remove dsh-loop-engine`,然后重启 `dsh web`。
 
+### 托管引擎接管什么
+
+选中托管引擎后,它接管该会话的命令与技能面:插件禁用 dsh 自己的 `/goal`,并把新会话指向一个受管理的 `loop-engine` agent 预设——它是 `standard` 的副本,去掉了外部引擎无法履行的 dsh 原生 `/compact`、`/plan`、goal 工具与 skill 行——于是斜杠菜单只显示引擎桥接过来的命令与它自己的技能目录。与引擎无关的 dsh 命令(`/export`、`/feedback`、`/permission`)照常可用、保留在菜单里。切回 `in-process` 会恢复之前的预设默认值;已经在跑的会话始终保留它创建时的预设。
+
 ### 引擎说明
 
-- Codex 驱动运行 `codex app-server`,没有交互式工具审批——权限来自会话的 `sandboxMode` + `approvalPolicy`。
-- Pi 驱动运行 `pi --mode rpc`;Pi 没有权限系统,所以整个子进程经 dsh subprocess 服务做沙箱化(默认 `read-only`)。
+- Claude Code 驱动每步跑一次 SDK query;它的斜杠命令桥接进 web 菜单(内置命令加上用户级 `~/.claude/commands/`),再转发给引擎由它原生展开。项目级 `.claude/commands/` 留在引擎侧,直接手敲同样可用。
+- Codex 驱动运行 `codex app-server`;线程以会话的 `sandboxMode` + `approvalPolicy` 姿态启动,模型运行时的工具审批请求(command、file-change、permissions)经 dsh 审批 seam 应答——用户提问走 user-questions seam,MCP elicitation 一律拒绝,seam 缺席时均失败关闭。其 `AGENTS.md` 指令文件经 dsh 技能注入接缝暴露:从会话 cwd 逐级到 git 根,外加 `~/.codex/AGENTS.md`。
+- Pi 驱动运行 `pi --mode rpc`;Pi 没有权限系统,所以整个子进程经 dsh subprocess 服务做沙箱化(默认 `read-only`)。它的上下文文件(`AGENTS.md`/`CLAUDE.md`,优先 `AGENTS.override.md`,外加 pi 配置目录下的用户级文件)与 `skills/` 目录(`~/.pi/agent/skills/` 和 `.pi/skills/`)经 dsh 技能注入接缝暴露。
 - Kimi Code 驱动运行一个常驻的 `kimi acp` 子进程(Agent Client Protocol over stdio),每步一次无状态的 `session/new` + `session/prompt`;durable 会话日志是唯一模型上下文。它把助手文本(`agent_message_chunk`)与**思考**(`agent_thought_chunk`)**增量**写入日志,并把工具调用/流(`tool_call` / `tool_call_update`)映射为 `tool/call` + `tool/result`。ACP 通过 `session/request_permission` 暴露工具审批,驱动根据会话的 dsh 审批旋钮应答(ask 策略拒绝,失败关闭)。子进程经 dsh subprocess seam 拉起——唯一权限边界(默认只读沙箱)。其项目 `AGENTS.md` 链(cwd→git 根)与 `.kimi-code/skills/` 目录(用户与项目)通过 dsh 技能注入接口暴露,其斜杠命令也已桥接(内置命令把原始 `/name` 行转发回引擎展开)。prompt 是 ACP 请求体而非 argv 位置参数,因此**不存在命令行长度上限**。注意 Kimi 剩余的斜杠命令面是纯 TUI(`/login`、`/provider`、`/settings`、`/sessions`…),这些不桥接(ACP prompt 面不扩展它们);`skill:` 命令由技能接口与 kimi 自身的 shorthand 承载。
 
 ## License

package/lib/client.js

@@ -565,6 +565,163 @@ var LoopEngineStore = class {
   }
 };
 
+// src/client/turn-status.ts
+var ENGINE_ATTR = "data-loop-engine";
+var PLUGIN_ID = "dsh-loop-engine";
+var STYLESHEET = `
+[class$="_turnStatus"]::before {
+  margin-right: 6px;
+  background: none;
+  -webkit-background-clip: border-box;
+  background-clip: border-box;
+}
+
+/*
+ * The row's own sweep, re-asserted for hosted engines.
+ *
+ * ui-chat disables that animation under \`prefers-reduced-motion: reduce\`
+ * (ChatView.module.css), and a media query carries no specificity \u2014 so this
+ * attribute-gated rule outranks it. That is deliberate here: deployment images
+ * ship with Windows' client-area animation off (SPI_GETCLIENTAREAANIMATION
+ * false), and with the guard in force EVERY indicator on this row is frozen \u2014
+ * the sweep and the glyph alike. Scoped to hosted engines, so in-process
+ * sessions keep the stock reduced-motion behaviour; delete this rule and
+ * restore the guard at the foot of the sheet to hand the decision back to the OS.
+ */
+html[${ENGINE_ATTR}] [class$="_turnStatus"] {
+  background-position: 100% 0;
+  background-size: 250% 100%;
+  animation: le-shimmer 1.8s linear infinite;
+}
+
+@keyframes le-shimmer {
+  to { background-position: 0 0; }
+}
+
+html[${ENGINE_ATTR}="claude-code"] [class$="_turnStatus"] {
+  --dsw-static-deepseek-500: #d97757;
+  --dsw-static-deepseek-200: #f5bda6;
+}
+html[${ENGINE_ATTR}="claude-code"] [class$="_turnStatus"]::before {
+  content: "\u273B";
+  color: #d97757;
+  -webkit-text-fill-color: #d97757;
+  animation: le-bloom 1.6s ease-in-out infinite;
+}
+
+html[${ENGINE_ATTR}="codex"] [class$="_turnStatus"] {
+  --dsw-static-deepseek-500: #a9b1c0;
+  --dsw-static-deepseek-200: #e6eaf2;
+}
+html[${ENGINE_ATTR}="codex"] [class$="_turnStatus"]::before {
+  content: "\u2022";
+  color: #a9b1c0;
+  -webkit-text-fill-color: #a9b1c0;
+  text-shadow: 0 0 6px currentColor;
+  animation: le-pulse 1.4s ease-in-out infinite;
+}
+
+html[${ENGINE_ATTR}="pi"] [class$="_turnStatus"] {
+  --dsw-static-deepseek-500: #8e4ec6;
+  --dsw-static-deepseek-200: #d6bff0;
+}
+html[${ENGINE_ATTR}="pi"] [class$="_turnStatus"]::before {
+  content: "\u280B";
+  color: #8e4ec6;
+  -webkit-text-fill-color: #8e4ec6;
+  font-size: 1.1em;
+  animation: le-braille 1s linear infinite;
+}
+
+html[${ENGINE_ATTR}="kimi"] [class$="_turnStatus"] {
+  --dsw-static-deepseek-500: #e5484d;
+  --dsw-static-deepseek-200: #f5b2b4;
+}
+html[${ENGINE_ATTR}="kimi"] [class$="_turnStatus"]::before {
+  content: "\u{1F317}";
+  color: #e5484d;
+  -webkit-text-fill-color: #e5484d;
+  animation: le-moon 2.5s linear infinite;
+}
+
+/* Grows from small to large each cycle \u2014 the opposite of a twinkle. The range
+   is deliberately wide (3x) because a bare size change on a thin glyph reads
+   weakly otherwise, and the large state is held briefly (50%-62%) so it blooms
+   rather than throbs. 1.35x extends ~2.5px per side at the 14px glyph, inside
+   the 6px ::before margin. */
+@keyframes le-bloom {
+  0%, 100% { transform: scale(0.45); opacity: 0.45; }
+  50%, 62% { transform: scale(1.35); opacity: 1; }
+}
+/* A terminal braille spinner. The glyph is an ordinary text character, not an
+   emoji, so the engine color actually paints \u2014 a colored emoji silently ignores
+   color/-webkit-text-fill-color. Stepping content walks the ten dot frames. */
+@keyframes le-braille {
+  0% { content: "\u280B"; }
+  10% { content: "\u2819"; }
+  20% { content: "\u2839"; }
+  30% { content: "\u2838"; }
+  40% { content: "\u283C"; }
+  50% { content: "\u2834"; }
+  60% { content: "\u2826"; }
+  70% { content: "\u2827"; }
+  80% { content: "\u2807"; }
+  90% { content: "\u280F"; }
+  100% { content: "\u280B"; }
+}
+/* A soft pulse for the codex dot: the glyph breathes between a small, dim
+   point and a larger, full-brightness one \u2014 a light dot, not a spinner. */
+@keyframes le-pulse {
+  0%, 100% { transform: scale(0.5); opacity: 0.35; }
+  50% { transform: scale(1.3); opacity: 1; }
+}
+/* Moon phases rather than a rigid rotation: a spinning moon bitmap can only
+   squash and mirror itself, never show a full or a new moon. Stepping the
+   glyph through the phase set sweeps the lit edge across the disc AND actually
+   reaches \u{1F315} and \u{1F311}. The order runs waning (full \u2192 new), so the lit edge
+   retreats right-to-left \u2014 the direction the user picked. */
+@keyframes le-moon {
+  0% { content: "\u{1F315}"; }
+  12.5% { content: "\u{1F314}"; }
+  25% { content: "\u{1F313}"; }
+  37.5% { content: "\u{1F312}"; }
+  50% { content: "\u{1F311}"; }
+  62.5% { content: "\u{1F318}"; }
+  75% { content: "\u{1F317}"; }
+  87.5% { content: "\u{1F316}"; }
+  100% { content: "\u{1F315}"; }
+}
+
+`;
+function reflect(engine, settled) {
+  const root = document.documentElement;
+  if (!settled || engine === "in-process") {
+    delete root.dataset.loopEngine;
+    return;
+  }
+  root.dataset.loopEngine = engine;
+}
+function installTurnStatusStyles(ctx, store) {
+  if (typeof document === "undefined") return;
+  ctx.effect(() => {
+    const tag = document.createElement("style");
+    tag.dataset.plugin = PLUGIN_ID;
+    tag.dataset.pluginCss = `${PLUGIN_ID}/turn-status.css`;
+    tag.textContent = STYLESHEET;
+    document.head.appendChild(tag);
+    return () => {
+      tag.remove();
+      delete document.documentElement.dataset.loopEngine;
+    };
+  }, "loop-engine: per-engine turn status styles");
+  const sync = () => {
+    const { status, engine } = store.getSnapshot();
+    reflect(engine, status === "ready");
+  };
+  ctx.effect(() => store.subscribe(sync), "loop-engine: turn status engine reflection");
+  sync();
+}
+
 // src/client/locales.ts
 var zh = {
   nav: "\u5FAA\u73AF\u5F15\u64CE",
@@ -624,6 +781,7 @@ function apply(ctx) {
       controller.dispose();
     };
   }, "loop-engine: store lifecycle");
+  installTurnStatusStyles(ctx, controller.store);
   const t = ctx.locale.bind(NS);
   const injected = () => ({
     controller,