@ckanner/flywheel 0.30.0 → 0.30.1

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## 0.30.1 — 任务发现与可选影子评估
+
+- 画布以任务选择为入口：按 DSH 会话 ID 找回 CLI 运行，旧记录一键选择；删除路径输入框，有实际位置时自动显示只读信息。
+- 单阶段回执独立呈现；Review 默认展示 L1 → Review、记录评分和整体交付边界，完整流程可展开。
+- 单阶段技能补充只读状态关联，区分加载技能、准备任务和实际启动。
+- JEV 默认关闭，可选全局／项目开关；开启只做有界影子评估，失败不阻断原工作流，不参与实际 Quick／Full 选择。
+- 修正 Claude 关闭 stdin 故障用例的额外子进程时序，并保留逐函数 100% 门禁。
+
+源码、开发候选与正式发布分别验收；0.30.0 安装不会自动获得本轮变更。
+
 ## 0.30.0 — 流程控制台
 
 - DSH 横向画布：规划／拆分、调度、任务、集成、终验、PR、Merge；节点运行、重跑与完整证据。

package/README.en.md

@@ -8,7 +8,7 @@ Current source supports **Auto, Quick, and Full** workflows. `flywheel-task` pre
 
 Session policy supports **fresh/scoped**: new templates explicitly choose scoped, while old configurations default to fresh. Scoped mode can continue compatible history for the same task, role, and scope after a trusted normal terminal outcome; independent re-review still checks the complete current candidate. Both modes journal main-task Codex Pro, Claude Code Pro, DSH, and Kimi calls. Unknown dispatch, outcome, or cleanup blocks execution and cannot be bypassed by switching modes. P3 adds public typed lifecycle events, durable acknowledgements, and read-only Codex/Claude receipt recovery. P4 adds role overrides, bounded quality rebuilds, and paired evaluation tools. Real-account quality, cache, and performance results remain unverified; offline tests cannot establish them. See [Interrupted calls and context quality](docs/en/session-recovery.md). See [Session policy](docs/en/configuration.md#session-policy-history-reuse-and-invocation-safety).
 
-This source targets **0.29.1**, including account defaults, account-error handling, and the current session directory. Check the npm registry before installing; merging source does not update an installed package. The desktop integration covers the checked **DSH Mac 0.2.1-rc.5 and 0.2.2-rc.1** interfaces. Version 0.28.4 declares only these two runtime versions. Check the registry before installing a version. Offline tests do not establish a live user Mac, account, or model pass.
+This source targets **0.30.1**, including account defaults, account-error handling, and the current session directory. Check the npm registry before installing; merging source does not update an installed package. The desktop integration covers the checked **DSH Mac 0.2.1-rc.5 and 0.2.2-rc.1** interfaces. Version 0.28.4 declares only these two runtime versions. Check the registry before installing a version. Offline tests do not establish a live user Mac, account, or model pass.
 
 The adaptive workflow and `flywheel-task` require a matching CLI/plugin release containing these changes. Check `flywheel control launch --help`; the older installation commands alone do not establish that this new interface is available.
 
@@ -167,3 +167,5 @@ The package currently declares **`UNLICENSED`**. An open-source license has not
 ### Workflow console (current source)
 
 The DSH view adds a horizontal task canvas, stage run/retry, per-stage configuration, controlled Provider-session interaction, declared parallel execution with serial integration, observed run metrics and PR/Merge receipts. See the [console guide](docs/en/flow-console.md). Source implementation does not imply npm publication or a local upgrade.
+
+Optional, default-off JEV shadow evaluation is included in the 0.30.1 source; see the [guide](docs/en/jev-shadow.md). Advice cannot change workflows, and observer failures do not block tasks.

package/README.md

@@ -14,7 +14,7 @@ Codex Pro、Claude Code Pro、DSH、Kimi 的主任务调用在两种模式下都
 真实账号的质量、缓存与性能结果仍待完成，不能由离线实验推断。详见
 [会话配置](docs/configuration.md#会话策略历史复用与调用安全)及[中断恢复与上下文质量](docs/session-recovery.md)。
 
-当前源码的统一发行目标为 **v0.29.1**，使用 DSH Mac 桌面为入口：Kimi CLI 规划，DSH 原生 DeepSeek Flash 执行，DSH 原生 GPT 评审，较难的执行任务默认走 Codex Pro 插件的公开 machine API。0.28.3 包含 DeepSeek 账号默认、账号错误分类与会话当前目录修复；安装前核对 npm registry，源码合并不会更新已安装的包。DSH 插件提供控制面板、配置查看和安装预检；具名 model profiles 可复用于不同阶段，Go 仍是唯一状态所有者。设计依据见 [docs/design.md](docs/design.md)，仓库约束见 [AGENTS.md](AGENTS.md)。
+当前源码的统一发行目标为 **v0.30.1**，使用 DSH Mac 桌面为入口：Kimi CLI 规划，DSH 原生 DeepSeek Flash 执行，DSH 原生 GPT 评审，较难的执行任务默认走 Codex Pro 插件的公开 machine API。0.28.3 包含 DeepSeek 账号默认、账号错误分类与会话当前目录修复；安装前核对 npm registry，源码合并不会更新已安装的包。DSH 插件提供控制面板、配置查看和安装预检；具名 model profiles 可复用于不同阶段，Go 仍是唯一状态所有者。设计依据见 [docs/design.md](docs/design.md)，仓库约束见 [AGENTS.md](AGENTS.md)。
 
 **基础安装命令适用于 0.28.0 及以后的完整 npm 发行版；Auto／Quick／Full 与 `flywheel-task` 需要包含本轮变更的同版本 CLI／插件。** 用 `flywheel control launch --help` 检查新增入口是否存在，并在安装前用 `npm view @ckanner/flywheel version` 核对 registry；源码合并或 GitHub Release 不代表 npm 已发行。旧 0.22.1 没有本教程使用的安装与 DSH 接口，当前发行状态见[发行记录](docs/releasing.md#3-失败恢复)。
 
@@ -289,3 +289,5 @@ npm run build:npm
 ### 流程控制台（当前源码）
 
 DSH 会话视图提供从左到右的任务画布、节点运行／重跑、按阶段配置、受管 Session 交互、声明式并行与串行集成、运行指标和 PR／Merge 回执。完整操作与当前能力边界见[控制台指南](docs/flow-console.md)。源码状态不等于 npm 已发布或本机已升级。
+
+可选、默认关闭的 JEV 影子评估源码实现见[使用说明](docs/jev-shadow.md)。开启仅记录建议，故障不阻断原流程；需要同版本 CLI／插件。

package/docs/claude-code-pro.md

@@ -9,7 +9,7 @@ Flywheel 现在可通过 `harness: "claude-code-pro"` 调用
 
 **源码与发行边界：**此接入要求插件 **0.4.0 / machine protocol 1**；0.3.1 只有
 DSH 工具入口，0.3.2 只有旧 machine 契约，均不满足新 lifecycle/recovery 接口。0.4.0 是本次配套源码版本，不能据此推断 npm 已
-发布。Flywheel 当前源码版本仍为 0.28.5，新增代码也不等于旧同版本安装已更新。
+发布。Flywheel 0.30.0 已发布；Claude 0.4.0 仍按下面的可选依赖流程准备。
 合并、发布及用户安装各有独立状态。现有默认 loop／route 没有切换到 Claude。
 
 ## 1. 准备依赖

package/docs/configuration.md

@@ -433,3 +433,7 @@ DSH 的「全局 / 项目配置」先读取显式作用域和文件 revision，
 ```
 
 这是字段片段，不是可直接替代完整配置的文件。控制台按实际文件读取完整草稿并校验后保存。CLI 运行索引、受管 Session 交互、指标完整性和 PR／Merge 权限边界见[流程控制台](flow-console.md)。
+
+## 可选 JEV 影子评估
+
+`jev-shadow.enabled` 默认 false，旧配置缺省同样关闭。全局／项目编辑器支持开关；开启只观察新任务，失败不阻断流程，不改变实际 Quick／Full。endpoint、固定响应版本、密钥变量名和时限详见 [JEV 指南](jev-shadow.md)。此功能需要 0.30.1 CLI／插件。

package/docs/en/claude-code-pro.md

@@ -11,8 +11,8 @@ budgets, and delivery.
 **Source and release boundary:** the integration requires plugin **0.4.0,
 machine protocol 1**. Version 0.3.1 only exposes the DSH tool interface and lacks
 the required machine receipt. The companion source version does not establish
-an npm publication. Flywheel source remains version 0.28.5; the new source does
-not update an already installed artifact. No default stage or route selects Claude.
+an npm publication. Flywheel 0.30.0 is released; prepare Claude 0.4.0 through
+the optional-dependency procedure below. No default stage or route selects Claude.
 
 ## 1. Prepare the optional dependency
 

package/docs/en/configuration.md

@@ -378,3 +378,7 @@ For example:
 ```
 
 This is a field excerpt, not a complete configuration replacement. The console reads and validates the complete selected file. See the [console guide](flow-console.md) for run indexing, controlled session interaction, observation completeness and remote-delivery authority.
+
+## Optional JEV shadow evaluation
+
+`jev-shadow.enabled` defaults to false, including older configurations that omit it. The global/project editor exposes the switch. Enabling only observes new tasks; failures never block workflows or change Quick/Full. See the [JEV guide](jev-shadow.md) for endpoint, version pin, key variable and timeout. This feature requires the 0.30.1 CLI/plugin.

package/docs/en/flow-console.md

@@ -2,9 +2,25 @@
 
 This guide describes the current source. Source, development candidates, local installation and npm publication are separate acceptance boundaries. Keep the CLI, platform packages and DSH plugin at one version.
 
+## Find a task without entering paths
+
+The canvas starts with task selection. One registered task belonging to the current DSH conversation opens automatically; multiple tasks require a choice. Terminal runs also record DSH's host session ID. This is discovery metadata, never authorization. The UI reads Go state after finding an index entry; the index is not proof of liveness or completion.
+
+Older records without a host ID remain selectable under Recent tasks on this computer. Selection performs a read-only status query and associates the task with the conversation. Refreshing the list does not start, retry or replace a manually selected task. Read failures retain the existing canvas; unresolved operations still require reconciliation against their original task.
+
+There are no editable task/project path fields. The assistant and engine supply the location; known workspace, task-record location and branch values appear as read-only information, while missing values are omitted. The task folder contains the specification, acceptance checks and progress; the workspace is the actual execution project/worktree. A prepared task can be associated by the assistant using read-only status and then selected from the list.
+
+Loading a skill does not start the engine. flywheel-task prepares and calls flywheel_launch; a research/proposal-only response must explicitly say the engine was not started. Single-stage skills query flywheel_control status afterward to associate their canvas, or disclose the exact path when that tool is absent rather than claiming association.
+
+## This stage versus the full workflow
+
+When run.kind and control.kind identify the same single-stage operation, This run shows its recorded outcome. A review-only run defaults to **L1 → Review**, including the recorded verdict and score, while stating that overall delivery is not complete. Switch to Full workflow for the larger graph.
+
+Continue workflow is behind an explicit disclosure. A passed stage does not start subsequent stages or mark the task completed. Failed, cancelled and unknown operations cannot inherit an older green verdict. Run ID, HEAD and digests are collapsed under Run details and file locations.
+
 ## Configuration
 
-The Flywheel conversation view remains after Statistics. Its pages are Workflow canvas, Global/project configuration, and Runs and comparison. Global settings require no task directory. Project settings target the selected Git root. Discovery still selects one complete file in task → project → global → embedded order; it does not deep-merge files.
+In an existing DSH conversation view, Flywheel remains after Statistics; the blank new-session landing page does not yet show these conversation views. Its pages are Workflow canvas, Global/project configuration, and Runs and comparison. Global settings require no task directory. Project settings target the selected Git root. Discovery still selects one complete file in task → project → global → embedded order; it does not deep-merge files.
 
 Read a draft, edit the resource/Harness, model, effort, permissions and history policy, then inspect the target and diff. Version defaults replace the complete configuration. Go checks the content revision, backs up the original and publishes atomically. A running engine retains its snapshot; subsequent starts load the new settings.
 
@@ -84,3 +100,5 @@ Push uses the approved commit and named task branch, without force, implicit tag
 Merge rechecks the PR, head, base and checks, using `--match-head-commit`. It never uses admin bypass or enables auto-merge on its own. Merge-queue acceptance and actual MERGED state remain distinct; see the [GitHub CLI contract](https://cli.github.com/manual/gh_pr_merge).
 
 Retries reconcile existing PR/merge results before mutations. Missing receipts remain unknown. Remote state is separate from local engine completion. Publication must bind the actual merge commit and artifacts for its own validation; Merge does not automatically publish npm packages or deploy.
+
+The configuration panel also exposes default-off **JEV shadow evaluation (optional)**. See the [JEV guide](jev-shadow.md) for the switch, transmitted data and nonblocking failures. This requires the 0.30.1 CLI/plugin.

package/docs/en/getting-started.md

@@ -223,9 +223,9 @@ flywheel control status --cwd "$PWD" --task-dir "$PWD/docs/add"
 
 In DSH Chat, the equivalent entries are `/flywheel-run <absolute-task-path>` and `/flywheel-status <same-path>`, with `/flywheel-stop <same-path>` when stopping is needed. Replace the placeholders with the real path returned during preparation. These skills resolve the project root without requiring an initial view selection.
 
-Launch/start through `flywheel_launch` or `flywheel_control` associates the exact task with the current DSH conversation. The top **Flywheel** view then requests fresh status once. For a task started from a terminal, enter that same `task_dir` in “Task files directory.” Leave “Project directory” blank only when the DSH session's current working directory is already the task's `repo_dir`; otherwise enter the project path supplied by the assistant. A shell `cd` alone does not change the DSH session directory. Expand configuration and troubleshooting when needed. A control response's `ok` means the operation succeeded; task completion is determined by `state.status`. The view displays the last refresh time and does not poll automatically.
+Launch/start through flywheel_launch or flywheel_control associates the task with this DSH conversation. Terminal runs record the host session ID; older runs are selectable from recent tasks. There are no editable path fields: known locations supplied by the assistant/engine appear read-only. Prepared tasks can also be associated through a read-only status query.
 
-Explicit task association is reconstructed from the host's public session projection and retained command/tool records across reload; a fork does not inherit the parent task. Manually entered draft paths and fetched snapshots are separate view caches with a shorter lifetime. Path edits discard old results and reject late replies without stopping the old task. Only one control request is pending per session, and launch/start/stop locks directory inputs while waiting. Opening the view never starts a task or scans directories.
+The UI separates the last stage from overall delivery and refreshes running state plus registered discovery. It does not scan directories. Public session projections restore explicit associations; forks do not inherit the parent task. Selection and status snapshots are separate, late replies cannot replace another task, and unconfirmed operations require reconciliation against their original target.
 
 After a launch/start/stop timeout or disconnect, the background task's outcome may be unconfirmed. Keep the original task and project paths, refresh that task's status, and inspect logs before deciding how to recover. The view disables further mutations until that task is successfully reconciled and never retries them automatically. A prior snapshot, closing a page, or switching sessions cannot prove the engine stopped. The native trajectory retains its parent-session records; full worker histories are not merged into it.
 
@@ -261,6 +261,10 @@ For the first real run, record whether the task reached `completed`, all require
 
 Stop active tasks and confirm their state, preserve configuration/customizations, then rerun the installation command with the original prefix/project/DSH options. To pin 0.28.0, first confirm that exact version exists in the registry and replace `@latest` with `@0.28.0`. `flywheel setup --no-global` repairs setup for the installed version without selecting a different CLI release.
 
+Inside Flywheel's own source checkout, npm may consider the matching local package satisfied and then resolve an older global executable from PATH. If the installation report shows a different version, retry outside the checkout, or run `npm install --global --ignore-scripts --include=optional @ckanner/flywheel@0.30.0` followed by `flywheel setup --no-global` from that exact prefix. Preserve a custom prefix in both steps. Check the CLI version, installation report, and desktop-profile plugin version. Reload the running desktop as directed by the host so it loads the newly installed modules.
+
+From 0.30.0, adopting the complete packaged preset is explicit: choose the global or project scope in the configuration editor, read it, load this version's defaults, review, and save. Saving backs up and replaces the selected configuration. Higher-priority task/project files still take precedence.
+
 Existing hard-route configuration remains unchanged after upgrade. To adopt the new plugin route, change the effective hard binding or profile to `harness: "codex-pro"`, preserve model/channel/thinking, inspect it, and restart. Do not use `subagent_codex_pro` as a provider.
 
 | Symptom | First check |

package/docs/en/workflow.md

@@ -214,3 +214,5 @@ Implementation references: [engine](https://github.com/ckanner/flywheel/blob/mai
 ## Interactive console delivery
 
 The [workflow console](flow-console.md) adds stage controls, handoff, declared parallelism and explicitly authorized PR/Merge operations. Local completion does not authorize remote writes. An earlier Draft PR is reconciled after push; publication validates the actual merge commit separately.
+
+Default-off [JEV shadow evaluation](jev-shadow.md) can independently observe new tasks without blocking execution on failure. Advice does not participate in Quick/Full selection or downgrade existing Full tasks. This feature requires the 0.30.1 CLI/plugin.

package/docs/flow-console.md

@@ -2,9 +2,25 @@
 
 本文描述当前源码中的控制台。源码、开发候选、本机安装与 npm 正式发行分别验收；不要仅凭本文判断 `@latest` 已包含这些功能。CLI、平台包和 DSH 插件必须同版。
 
+## 找到任务，不必填写路径
+
+新版画布先显示任务选择。当前 DSH 会话只有一个已登记任务时自动打开；有多个任务时选择其一。通过终端运行的任务也会使用 DSH 提供的会话 ID 登记；该标识只用于发现，不能授予控制权限。页面读取运行索引后再请求 Go 状态，不把索引当成仍在运行或已经完成的证明。
+
+旧版本记录没有会话 ID 时，从“本机最近任务”选择即可；选择会发送只读状态查询，并保存到当前会话关联。刷新任务列表不会启动、重试或切换你手动选中的任务。读取失败保留已打开画布；未确认的操作仍先核对原任务。
+
+界面不再提供任务路径／项目路径输入框，也不要求用户填写。助手与引擎提供实际位置；有值后显示为只读的工作区、任务记录位置及分支，没有值不显示空字段。任务文件夹保存说明、验收清单和进度，工作区是实际执行的项目／worktree。准备但尚未运行的任务由助手通过只读 status 关联，随后也能在列表中选择。
+
+Skill 已加载不代表引擎已经启动。`flywheel-task` 准备并通过 `flywheel_launch` 启动后才产生运行；只要求调研或方案时，助手应明确说明尚未启动。单阶段技能执行后通过 `flywheel_control status` 关联当前画布；没有该工具时明确给出路径，不能声称已关联。
+
+## 本次阶段与完整流程
+
+`run.kind` 与 `control.kind` 一致的单阶段任务优先显示“本次运行”和真实回执。仅运行 Review 时，默认画布为 **L1 → Review**，并显示记录结论、评分及“整体交付尚未完成”；其它未运行阶段不会盖过这次评审结果。可切换“完整流程”查看全貌。
+
+“继续整个流程”移入明确的展开项；单阶段通过不自动启动后续阶段，也不把任务改为 completed。失败、取消和结果未知不会沿用旧绿色裁决。Run ID、HEAD 和配置摘要收在“运行记录与文件位置”，需要排查时再展开。
+
 ## 从配置开始
 
-DSH 的 Flywheel 会话视图仍排在“统计”之后。内部有“运行画布”“全局／项目配置”“运行与对比”。全局配置可在没有任务目录时编辑；项目配置写入所选 Git 项目根。任务配置仍具有最高优先级，取首个完整文件，不做字段深度合并。
+在已进入对话视图的 DSH 会话中，Flywheel 排在“统计”之后；新会话的空白首页尚未显示这排会话视图。内部有“运行画布”“全局／项目配置”“运行与对比”。全局配置可在没有任务目录时编辑；项目配置写入所选 Git 项目根。任务配置仍具有最高优先级，取首个完整文件，不做字段深度合并。
 
 先读取草稿，再选择 Provider／Harness、模型、推理等级、权限与历史策略。“载入本版本默认值”导入完整默认模板；保存前显示差异与目标，Go 核对内容 revision、备份旧文件并原子写入。正在运行的引擎保留原快照，新配置在后续启动时加载。
 
@@ -88,3 +104,5 @@ CLI 和桌面启动自动登记 run ID；会话投影保留多个已确认任务
 合并再次核对 PR、源 HEAD、base 和检查状态，并使用 GitHub CLI 的 `--match-head-commit`。不使用 admin 绕过，也不擅自开启 auto-merge。仓库要求 merge queue 时，“请求已接收”和“已合并”分别记录，以远端回执为准。接口语义见 [GitHub CLI 文档](https://cli.github.com/manual/gh_pr_merge)。
 
 已确认的创建／合并操作重跑时先核对已有结果。命令失败或回执丢失保留 unknown，不猜测远端成功。PR／Merge 状态与引擎的本地完成分开；发布应绑定实际 merge commit 和发布产物重新验收，不因点击 Merge 自动发布 npm 或部署。
+
+配置面板另提供默认关闭的 **JEV 影子评估（可选）**；开关、数据发送边界与失败回退见 [JEV 指南](jev-shadow.md)。此项需要 0.30.1 CLI／插件。

package/docs/getting-started.md

@@ -294,14 +294,9 @@ flywheel control status --task-dir "$PWD/docs/add" --cwd "$PWD"
 在 DSH 对话中也可使用 `/flywheel-run <任务资料绝对路径>`、`/flywheel-status <同一路径>`，需要停止时用 `/flywheel-stop <同一路径>`。把占位内容替换成准备阶段给出的真实路径；这些技能会解析正确的项目根，不依赖先填写视图。
 
 `ok: true` 只表示控制操作成功；`running` 表示引擎是否在运行，完成看 `state.status`。
-DSH 工具 launch／start 会关联当前会话视图，确认关联后查询一次最新状态；终端
-启动或手动打开时，仍填写同一个 `task_dir` 与实际 `repo_dir`。项目目录仅在会话
-当前目录相同时可留空，shell `cd` 不改变会话目录。视图展示请求／生效模式、理由、
-阶段适用性、任务状态与刷新时间；不适用的 Plan／Judge 不算通过，也不会自动轮询。
+DSH 工具 launch／start 关联当前会话视图；终端运行按宿主会话 ID 登记，旧任务可从最近任务列表选择。界面没有路径输入框，位置由助手／引擎取得，已知值才只读显示。准备但尚未运行的任务也可由助手通过只读 status 关联。
 
-会话的工具／命令记录仍在时，重载可通过公开投影重建明确的任务关联；fork 不继承
-父会话关联。手动路径草稿与旧快照只是查看缓存，重载后可能需重选或刷新。修改路径
-忽略旧响应，不会停止旧任务。每个会话只等待一个控制请求，启动或停止期间锁定目录。
+视图展示本次阶段与完整流程的区别、真实状态和刷新时间；运行时只读刷新，任务发现只查已有登记，不扫描目录。公开会话投影可重建关联，fork 不继承父会话归属。选择和状态快照分开，晚到响应不能覆盖新任务，未知操作先核对原目标。
 
 启动或停止超时、断连后，后台任务的结果可能尚未确认。保留原任务目录，先“刷新状态”和查看日志；界面在成功核对该任务前禁止继续启动／停止，也不会自动重试。已有快照只是上次结果，不能凭页面关闭、切换会话或停止按钮失去等待状态推断引擎已经结束。原生轨迹保留父会话自己的记录，worker 完整历史不自动合并到其中。
 
@@ -346,6 +341,10 @@ npx -y @ckanner/flywheel@latest install
 
 自定义 prefix、项目 skills 或 DSH 入口时保留原参数。想固定某个已发布版本，可把 `@latest` 换成该精确版本，例如在 registry 确认 0.28.0 已发布后使用 `@0.28.0`；安装器始终为 CLI、平台包、worker 和桌面插件选择本次安装器的同一版本。已安装包的配置修复可用 `flywheel setup --no-global`，它不会将 CLI 升级到别的版本。
 
+维护者在 Flywheel 自身源码目录中运行 `npx` 时，npm 可能把同名本地 package 视为已满足，再命中 PATH 中的旧全局入口。若安装报告的版本不是请求版本，请在源码目录之外重试，或执行 `npm install --global --ignore-scripts --include=optional @ckanner/flywheel@0.30.0` 后，用该 prefix 下的 `flywheel setup --no-global` 完成设置；自定义 prefix 时两步均保留它。最终核对 `flywheel version`、安装报告版本及 DSH profile 中的插件版本。桌面已在运行时，还须按宿主要求重载，磁盘安装成功不表示旧模块已经卸载。
+
+从 0.30.0 起，若明确决定完整采用安装包内的预设，可在 **全局 / 项目配置** 中选择作用域、读取配置，点击 **载入本版本默认值**，审阅后 **保存配置**。这会备份并替换所选作用域的配置；上层任务／项目文件仍按配置优先级生效。
+
 从 0.27.x 升级到本版后，要使用新的默认插件路径，应在有效配置的 `routes.hard`（或其 profile）设置 `"harness": "codex-pro"`，保留所选 model／thinking／channel。先用 `config inspect` 找到实际配置来源；不要把 external subagent 的工具名写成 DSH provider。
 
 安装后对照新模板审阅需要迁移的配置，按宿主提示重新载入，运行 doctor，再用小任务验证。已有配置不会自动覆盖；特别检查任务级文件是否遮住了刚修改的项目或全局设置。安装不是跨 npm、DSH 与全部 skills 的单个事务：失败时报告已完成步骤，不擅自回退包管理器或删除用户文件。修正原因后重跑会重新核对版本与内容。

package/docs/workflow.md

@@ -308,3 +308,5 @@ required checks、审阅要求和授权，再按仓库策略启用；Agent 的 p
 ## 控制台交互交付
 
 新的[流程控制台](flow-console.md)提供阶段操作、接管、声明式并行与明确授权的 PR／Merge 入口。普通 run 的本地完成不自动授权远端写入；已有 Draft PR 会在推送后重新核对，Merge 后的发布另按真实 merge commit 验收。
+
+默认关闭的 [JEV 影子评估](jev-shadow.md) 可独立观察新任务，故障不阻断执行。其建议不参与本节的 Quick／Full 判定；开启也不能降级已有 Full。此项需要 0.30.1 CLI／插件。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ckanner/flywheel",
-  "version": "0.30.0",
+  "version": "0.30.1",
   "description": "A deterministic Go orchestrator for coding-agent loops, with task contracts, verification gates, Git worktrees, and DSH desktop integration.",
   "bin": {
     "flywheel": "bin/flywheel.js",
@@ -49,10 +49,10 @@
     "docs/en/session-evaluation.md"
   ],
   "optionalDependencies": {
-    "@ckanner/flywheel-darwin-arm64": "0.30.0",
-    "@ckanner/flywheel-darwin-amd64": "0.30.0",
-    "@ckanner/flywheel-linux-arm64": "0.30.0",
-    "@ckanner/flywheel-linux-amd64": "0.30.0"
+    "@ckanner/flywheel-darwin-arm64": "0.30.1",
+    "@ckanner/flywheel-darwin-amd64": "0.30.1",
+    "@ckanner/flywheel-linux-arm64": "0.30.1",
+    "@ckanner/flywheel-linux-amd64": "0.30.1"
   },
   "scripts": {
     "release:check": "node scripts/release-preflight.js",
@@ -60,10 +60,10 @@
     "test": "node --test npm/test/*.test.js",
     "test:install": "node --test npm/test/install.integration.js",
     "test:registry": "node npm/test/registry-smoke.js",
-    "build:npm": "bash scripts/build-npm.sh 0.30.0 dist-npm",
+    "build:npm": "bash scripts/build-npm.sh 0.30.1 dist-npm",
     "test:sessions": "node scripts/test-session-evaluation.js"
   },
   "dependencies": {
-    "@ckanner/dsh-plugin-flywheel": "0.30.0"
+    "@ckanner/dsh-plugin-flywheel": "0.30.1"
   }
 }