agentworkshop 0.8.3 → 0.8.4

package/.output/server/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentworkshop-prod",
-  "version": "0.8.3",
+  "version": "0.8.4",
   "type": "module",
   "private": true,
   "dependencies": {

package/README-zh.md

@@ -28,7 +28,7 @@
 
 **[English](./README.md)** · **[在线文档](https://kingdol666.github.io/AgentWorkShop)** · **[版本发布](https://github.com/kingdol666/AgentWorkShop/releases)** · **[更新日志](./changelog.md)** · **[插件 API](./docs/plugins.md)** · **[SDK](./docs/sdk.md)**
 
-<sub><b>v0.8.3</b> · 14 个执行引擎 · 6 种现场协议（5 内置 + 串口插件）+ MES REST 集成（镜像与直连双路径）· 数据分析台账（产线级权限隔离）· 工艺参数优化器（过程模型 → AML → OSQP 求解 → 治理下发）· **本体服务 + AI 先行模型闭环**（本体 · 孪生 · 求解器 · AML 采纳）· 104 个宿主工具 · 126 个运行时设置项 · 双语文档（简体中文 / English）</sub>
+<sub><b>v0.8.4</b> · 14 个执行引擎 · 6 种现场协议（5 内置 + 串口插件）+ MES REST 集成（镜像与直连双路径）· 数据分析台账（产线级权限隔离）· 工艺参数优化器（过程模型 → AML → OSQP 求解 → 治理下发）· **本体服务 + AI 先行模型闭环**（本体 · 孪生 · 求解器 · AML 采纳）· 104 个宿主工具 · 126 个运行时设置项 · 双语文档（简体中文 / English）</sub>
 
 <br />
 
@@ -129,11 +129,13 @@ AgentWorkShop 起家于**多智能体软件工作坊**——Channel 内的编码
 
 <div align="center">
 
-### 🎬 实机演示（4 分 11 秒，英文配音 + 字幕）
+### 🎬 3 分钟产品演示（英文界面 · 英文配音 · 汉英双语字幕）
 
-<a href="https://github.com/kingdol666/AgentWorkShop/blob/main/docs/site/public/demo/agentworkshop-demo.mp4"><img src="docs/site/public/demo/poster.jpg" alt="AgentWorkShop 实机演示：数采中心、写控下发回读、串口插件、Agent 团队执行、闭环趋势与 3D 数字孪生" width="86%" /></a>
+<a href="https://kingdol666.github.io/AgentWorkShop/demo/player.html"><img src="docs/site/public/demo/agentworkshop-core-demo-poster.png" alt="AgentWorkShop 3 分钟演示：仪表盘、实时数采、EDA 管道、工具治理目录、已发布本体、Agent 工作区、插件与分析台账" width="86%" /></a>
 
-<sub><b>点击封面观看完整演示。</b>真实 PLC 模拟器 + 真实串口枚举 + 真实 Agent 团队执行，全程无剪辑造假。<br/>场景：仪表盘 → 数采中心（实时） → 写控下发与回读 → 串口协议插件 → Agent 团队执行 → 闭环趋势 → 3D 数字孪生。</sub>
+<sub><b>点击封面打开独立播放页。</b>一段连续实机录屏：运行中的实例 + Mock PLC 产线，1920×1080，英文界面、英文旁白、英/简中字幕。<br/>场景：仪表盘 → 实时数采 → EDA 分析管道 → 受治理的工具目录 → 已发布本体 → Agent 工作区 → 插件 → 分析台账 → EDA 工坊。</sub>
+
+[直接 MP4](https://github.com/kingdol666/AgentWorkShop/blob/main/docs/site/public/demo/agentworkshop-core-demo.mp4) · [独立播放页](https://kingdol666.github.io/AgentWorkShop/demo/player.html) · [VitePress 演示页](https://kingdol666.github.io/AgentWorkShop/demo)
 
 </div>
 
@@ -168,6 +170,7 @@ AgentWorkShop 起家于**多智能体软件工作坊**——Channel 内的编码
 | **配方链路优化闭环** | Agent 像人类工艺员一样通过配方管理做优化：`recipe_trial` 把多参数候选**整批试验（不写版本）**→ 复测 → 有进步用 `recipe_update` 固化（同一配方 id，版本+1）→ 劣化触发**统一回退**（`recipe_rollback` 带 `dispatch:true` = 定义回退 + PLC 整批恢复）。单参数直调移出闭环；试验受四层限界与同线节拍卡控。 |
 | **频道绑定产线（只读授权）** | 频道可绑定一条产线：全员无需节点绑定即可读取该线的产线日志（仅产线域记录，可按产线/配方/时间检索）、配方历史与实时状态（工具回执标注「频道绑定，只读」），写操作仍需节点授权。产线简报自动注入成员提示词；换绑即时回收成员运行时。 |
 | **数据分析台账（v0.7.62）** | Agent 的分析结果作为一等记录留痕：原生 `analysis_save` / `analysis_query` 宿主工具写入独立的 `analysis_reports` 表，按产线 + 配方 + 时间窗组织，含关键结论、指标、数据来源与操作者归因。台账对 Agent 只增不改；人类经 REST 修订并刷新编辑者归因。专属 `/analysis` 页面经 WS 实时前插新报告，支持产线 / 配方 / 时间 / 关键词多维检索，改删受产线权限门控（`operate` 可改、删除仅 admin）。外部分析插件经同一台账集成——`diag_run` 以后台任务运行 IDD **六种分析意图**（深度根因诊断 / 产线稳定报告 / 快速筛查 / DOE 试验分析 / 调参经验挖掘 / 优化战役，按情景注入分析提示词），提交即返 `task_id`，`diag_status` 按 taskId 查进度，完成后报告经 `analysis_save` 落账。 |
+| **IDD 结果库（v0.8.1，默认关闭）** | diag-bridge 插件进一步接入 IDD 侧的**全量分析结果历史**（不限本平台发起的运行）：`diag_results` 按关键词/意图/分类/标签/场景/harness/评分检索索引（brief 模式省 token），`diag_result_get` 取详情卡（关键数字溯源 + 工件绝对 URL），`diag_result_annotate` 编辑元数据（描述/标签/标题）。五项治理开关控制可见面——总开关默认**关闭**，结果可见面等于诊断 API Token 属主（平台级、不按产线隔离），读工具默认仅 lead、编辑始终仅 lead。`/plugins` 页同源「分析结果库」面板镜像三条路由（`GET /results` · `/results/detail` · `PATCH /results/edit`）。 |
 | **数据管理台与 EDA 工坊（/data · /studio）** | 数据面一站式：多字段复合查询（产线/节点/时间窗/批次/降采样护栏）、批量导出（manifest + merged.csv 作业台账）、标量/数组/图像**三形态**镜像（测厚断面与 CCD 帧经 ingest 推送或协议采集，WS 实时上屏）。EDA 工坊提供图表与栅格看板、**golden 相位参考轨迹**（偏差分叠加）、**FDC 特征**（参考带 z 判定）、**SPC 控制图**（Nelson 1-8 / I-MR / EWMA / CUSUM）、共性分析（四因子 lift）、OCAP 处置单、虚拟量测（集成外推 + OOD 拒判）与派生数据集（白名单算子），全部受产线级权限与引用归属预检约束。 |
 | **工艺参数语义面与调控闭环** | 全部可下发写收敛到**配方面**（`recipe_update` / `recipe_apply` / `recipe_trial`，各受「绑定 → HITL 理由 → 运行门」三门约束）。写入仍被**四层限界**逐层收窄——节点安全量程 ∩ 工艺参数基准限界 ∩ 活动产品限界 ∩ 活动配方工艺窗口——且每次下发自动开一条调控记录，由 `dcw_judge` 落判定（keep / rollback / uncertain），`dcw_rollback` 执行回退。（v0.7.63 摘除了 `param_control` / `param_read` / `dcw_read` 直连节点的遗留死工具面，Agent 工具清单保持干净。） |
 | **产线运营** | 产线 → 产品 → 配方 → 批次。配方窗口门控采集并联锁写入；每条样本打标 `product/recipe/run`，实现按批次隔离。 |
@@ -405,7 +408,7 @@ aw update --check                      # 只报告，不安装
 npm install -g agentworkshop@latest    # 手动等效
 ```
 
-版本遵循 semver。每次 `aw start` 都会校验配置根，并把 `home` 之前的旧版 `data/` 布局迁移进来（以最新文件为准），因此数据可以跨版本存活。SQLite schema 迁移在服务端启动时执行。当前版本：**v0.8.3**——见[版本发布](https://github.com/kingdol666/AgentWorkShop/releases)。
+版本遵循 semver。每次 `aw start` 都会校验配置根，并把 `home` 之前的旧版 `data/` 布局迁移进来（以最新文件为准），因此数据可以跨版本存活。SQLite schema 迁移在服务端启动时执行。当前版本：**v0.8.4**——见[版本发布](https://github.com/kingdol666/AgentWorkShop/releases)。
 
 ### 第一次「Agent × 产线」会话（约 2 分钟）
 

package/README.md

@@ -28,7 +28,7 @@
 
 **[简体中文](./README-zh.md)** · **[Documentation](https://kingdol666.github.io/AgentWorkShop)** · **[Releases](https://github.com/kingdol666/AgentWorkShop/releases)** · **[Changelog](./changelog.md)** · **[Plugin API](./docs/plugins.md)** · **[SDK](./docs/sdk.md)**
 
-<sub><b>v0.8.3</b> · 14 engines · 6 field protocols (5 built-in + serial plugin) + MES REST integration (mirror & live) · data-analysis ledger with line-scoped permissions · process optimizer (process model → AML → OSQP solver → governed dispatch) · **ontology service + AI-first model loop** (ontology · twin · solver · AML adoption) · 104 host tools · 126 runtime settings · bilingual docs (简体中文 / English)</sub>
+<sub><b>v0.8.4</b> · 14 engines · 6 field protocols (5 built-in + serial plugin) + MES REST integration (mirror & live) · data-analysis ledger with line-scoped permissions · process optimizer (process model → AML → OSQP solver → governed dispatch) · **ontology service + AI-first model loop** (ontology · twin · solver · AML adoption) · 104 host tools · 126 runtime settings · bilingual docs (简体中文 / English)</sub>
 
 <br />
 
@@ -129,11 +129,13 @@ Recorded against a running instance: real DAQ history, real write control, real
 
 <div align="center">
 
-### 🎬 Live demo (4 min 11 s, English voice-over & captions)
+### 🎬 3-minute product demo (English UI · English voice-over · bilingual captions)
 
-<a href="https://github.com/kingdol666/AgentWorkShop/blob/main/docs/site/public/demo/agentworkshop-demo.mp4"><img src="docs/site/public/demo/poster.jpg" alt="AgentWorkShop live demo: DAQ console, governed write + read-back, serial protocol plugin, agent team execution, closed-loop trend and the 3D digital twin" width="86%" /></a>
+<a href="https://kingdol666.github.io/AgentWorkShop/demo/player.html"><img src="docs/site/public/demo/agentworkshop-core-demo-poster.png" alt="AgentWorkShop 3-minute demo: dashboard, live DAQ, EDA pipeline, governed tool catalog, published ontology, agent workspaces, plugins and analysis ledger" width="86%" /></a>
 
-<sub><b>Click the cover to watch the full demo.</b> Real PLC simulator, real serial-port enumeration, real agent-team execution — no cuts, no fakes.<br/>Scenes: dashboard → live DAQ → governed write & read-back → serial protocol plugin → agent team execution → closed-loop trend → 3D digital twin.</sub>
+<sub><b>Click the cover to play the standalone player.</b> One continuous screencast of a running instance with a mock PLC line — 1920×1080, English interface, English narration, EN / 简体中文 captions.<br/>Scenes: dashboard → live DAQ → EDA pipeline → governed tool catalog → published ontology → agent workspaces → plugins → analysis ledger → EDA studio.</sub>
+
+[Direct MP4](https://github.com/kingdol666/AgentWorkShop/blob/main/docs/site/public/demo/agentworkshop-core-demo.mp4) · [Standalone player](https://kingdol666.github.io/AgentWorkShop/demo/player.html) · [VitePress demo page](https://kingdol666.github.io/AgentWorkShop/en/demo)
 
 </div>
 
@@ -169,6 +171,7 @@ Recorded against a running instance: real DAQ history, real write control, real
 | **Recipe-chain optimization loop** | Agents optimize through recipe management, the way human process engineers do: `recipe_trial` batch-dispatches multi-parameter candidates **without writing a version** → re-measure → progress adopts via `recipe_update` (same recipe id, version +1) → regression triggers a **unified rollback** (`recipe_rollback` with `dispatch: true` = definition revert + batch restore to the PLC). Single-knob direct dispatch is out of the loop; trials run under four-layer bounds and a per-line cadence. |
 | **Channel-bound lines (read-only grant)** | A channel can bind a line: every member reads that line's ops logs, recipe history and live status without any node binding (tool outputs are tagged "channel-bound, read-only"), while writes still require node authorization. The line brief is injected into member prompts; binding changes hot-recycle member runtimes. |
 | **Data-analysis ledger (v0.7.62)** | Agents persist analysis results as first-class records: native `analysis_save` / `analysis_query` host tools write a dedicated `analysis_reports` table keyed by line + recipe + time window, with conclusions, metrics, data sources and actor attribution. The ledger is append-only for agents; humans revise via REST with editor attribution. A dedicated `/analysis` page streams new reports live (ops-log WS), filters by line / recipe / time / keyword, and edit/delete are permission-gated (`operate` line mode; admin-only delete). External analysis plugins integrate through the same ledger — `diag_run` runs IDD analyses in the background across **six intents** (deep root-cause diagnosis, line stability report, quick screening, DOE analysis, tuning-experience mining, optimization campaign — scenario prompts injected per intent), returns a `task_id` immediately, tracks progress via `diag_status`, and the finished report lands in the ledger via `analysis_save`. |
+| **IDD results library (v0.8.1, off by default)** | The diag-bridge plugin also surfaces the IDD-side **full results history** (not only runs started from this platform): `diag_results` searches an index by keyword / intent / category / tag / scene / harness / score (brief mode saves tokens), `diag_result_get` returns a detail card with key-number provenance and absolute artifact URLs, and `diag_result_annotate` edits metadata (description / tags / title). Five governance switches control the surface — the master switch ships **off**, visibility follows the diagnostic API token owner (platform-level, not line-isolated), read tools default to the lead role and editing stays lead-only. A same-origin results panel on `/plugins` mirrors the three routes (`GET /results` · `/results/detail` · `PATCH /results/edit`). |
 | **Data workbench & EDA studio (/data · /studio)** | One-stop data plane: multi-field compound queries (line/node/time-window/batch/downsampling guardrails), bulk export (manifest + merged.csv job ledger), and **three data shapes** — scalars, array profiles (thickness scans) and CCD images — mirrored via protocol collection or external `ingest` push, streamed live over WS. The EDA studio adds charts and grid dashboards, **golden phase-referenced trajectories** with deviation scoring, **FDC features** (reference-band z scoring), **SPC control charts** (Nelson 1-8 / I-MR / EWMA / CUSUM), commonality analysis (four-factor lift), OCAP disposition records, virtual metrology (ensemble extrapolation with OOD rejection) and derived datasets (whitelisted operators) — all under line-scoped permissions and per-call reference preflight. |
 | **Semantic parameter surface & tuning loop** | Every dispatchable write converges on the **recipe face** (`recipe_update` / `recipe_apply` / `recipe_trial`, each gated by binding → HITL reason → active-run). Writes stay narrowed by the **four-layer bound** — node safe range ∩ parameter baseline bounds ∩ active product bounds ∩ active recipe window — and each adjustment opens a tuning record that `dcw_judge` must close (keep / rollback / uncertain), with `dcw_rollback` executing the undo. (v0.7.63 removed the legacy `param_control` / `param_read` / `dcw_read` direct-node tools — dead surface under permission model v2 — so the agent tool list stays clean.) |
 | **Line operations** | Lines → products → recipes → batch runs. Recipe windows gate acquisition and interlock writes; every sample is tagged `product/recipe/run` for per-batch isolation. |
@@ -396,7 +399,7 @@ aw update --check                      # only report; nothing is installed
 npm install -g agentworkshop@latest    # manual equivalent
 ```
 
-Releases follow semver. `aw start` verifies the config root on every launch and migrates the legacy pre-`home` `data/` layout into it (newest file wins), so data survives upgrades. SQLite schema migrations run server-side at boot. Current version: **v0.8.3** — see [Releases](https://github.com/kingdol666/AgentWorkShop/releases).
+Releases follow semver. `aw start` verifies the config root on every launch and migrates the legacy pre-`home` `data/` layout into it (newest file wins), so data survives upgrades. SQLite schema migrations run server-side at boot. Current version: **v0.8.4** — see [Releases](https://github.com/kingdol666/AgentWorkShop/releases).
 
 ### Your first agent × line session (~2 minutes)
 

package/app/components/AwChart.vue

@@ -47,6 +47,19 @@ const props = defineProps({
     type: Object as PropType<EChartsOption>,
     required: true,
   },
+  /** 图表高度(px 数字或 CSS 长度);此前经 $attrs 落到 DOM 属性上不生效,导致容器高 0 */
+  height: {
+    type: [Number, String],
+    default: null,
+  },
+})
+
+const chartStyle = computed(() => {
+  if (props.height == null) return undefined
+  return {
+    width: '100%',
+    height: typeof props.height === 'number' ? `${props.height}px` : props.height,
+  }
 })
 
 // 未显式给 color 的图表统一走编辑色板;给了的尊重页面意图
@@ -94,6 +107,7 @@ const updateOptions = computed<SetOptionOpts>(() => ({
 <template>
   <VChart
     v-bind="$attrs"
+    :style="chartStyle"
     :option="merged"
     :update-options="updateOptions"
     autoresize

package/app/pages/ontology/index.vue

@@ -69,7 +69,7 @@ const entityOptions = computed(() => (doc.value?.entities ?? []).map(e => ({ val
 const largeGraph = computed(() => (doc.value?.entities.length ?? 0) > 60)
 const draftOptions = computed(() => overview.value.drafts.map(d => ({
   value: d.id,
-  label: `${d.ontologyId} · rev ${d.rev}${d.baseVersion ? ` · 基线 v${d.baseVersion}` : ''}`,
+  label: `${d.ontologyId} · rev ${d.rev}${d.baseVersion ? ` · ${t('ontology.graph.baseline')} v${d.baseVersion}` : ''}`,
 })))
 const versionOptions = computed(() => versions.value.map(v => ({ value: v.version, label: `v${v.version}(${v.status})` })))