agentworkshop 0.7.40 → 0.7.41

package/.output/server/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentworkshop-prod",
-  "version": "0.7.40",
+  "version": "0.7.41",
   "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.7.39</b> · 14 个执行引擎 · 5 种现场协议 · 99 个运行时设置项 · 双语文档（简体中文 / English）</sub>
+<sub><b>v0.7.41</b> · 14 个执行引擎 · 6 种现场协议（5 内置 + 串口插件） · 99 个运行时设置项 · 双语文档（简体中文 / English）</sub>
 
 <br />
 
@@ -146,7 +146,7 @@ AgentWorkShop 起家于**多智能体软件工作坊**——Channel 内的编码
 
 | 能力 | 为何重要 |
 |---|---|
-| **五协议现场总线** | Modbus TCP、Modbus RTU-over-TCP（串口网关）、OPC UA、MQTT、HTTP/REST——数采**与**写控双驱动带连接池、分类错误文案与逐驱动连接测试；`mock` 覆盖演示/CI；插件可注册新协议。 |
+| **六协议现场总线** | Modbus TCP、Modbus RTU-over-TCP（串口网关）、OPC UA、MQTT、HTTP/REST，外加**内置串口插件**（RS-232/485 直连：Modbus RTU + ASCII 行）——数采**与**写控双驱动带连接池、分类错误文案与逐驱动连接测试；`mock` 覆盖演示/CI；协议即插件：`ctx.daq.registerDriver` / `ctx.dcw.registerWriteDriver` 注入后，前端协议下拉与参数表单即插即现（带 ⌁ 徽标）。 |
 | **Agent 团队 × 工业作用域** | 把 Agent 绑定到数采/数控节点。Agent 看到的是语义卡（物理含义、单位、安全量程、配方窗口）——而不是裸寄存器。 |
 | **人工审批的写控** | 数控下发经过「**安全量程 ∩ 活动配方窗口**」联锁 → 可选 **HITL 审批** → PLC 写入 → **回读校验** → 带签名的写历史。 |
 | **数控读写通道** | 每个控制节点都能沿它写入时所用的同一套标定**读回 PLC 当前值**：周期读 + 按需读 + Agent 读取，SET 与 ACT 并排呈现——读是被动观测，永不被写联锁阻断。 |
@@ -162,7 +162,7 @@ AgentWorkShop 起家于**多智能体软件工作坊**——Channel 内的编码
 | **产线级权限** | 工业数据按**产线**三态门控（无权/仅查看/可操控），强制点在数据面——普通用户未授权前看不到任何产线数据。 |
 | **全操作审计日志** | 用户 / Agent / 系统 的每个动作都落进同一份可检索日志；操作者归属「Channel名/成员名」，与用户和系统天然区分。经 WS 实时推送。 |
 | **团队级插件开关** | 每个团队（Channel）持有**独立插件开关组**（`channel_plugins`）：被关闭插件的工具不注入该团队 Agent。插件本体经 `aw plugin` 与 `/plugins` 页热管理。 |
-| **插件扩展 API** | `plugins/<name>/` 下的一个自包含目录**同时增强两半**：`index.mjs`（服务端：钩子、路由、Agent 工具、数采驱动/处理器/模板、配置分组、KV、定时器）与 `client.mjs`（浏览器：注入具名插槽的面板、i18n、设置 UI）。三种作用域——`builtin`（随包发布）> `project`（检出）> `user`（`~/.AgentWorkShop`）——启停**与代码修改**均有约 1 秒热重载。完整契约见 [`docs/plugins.md`](./docs/plugins.md)。 |
+| **插件扩展 API** | `plugins/<name>/` 下的一个自包含目录**同时增强两半**：`index.mjs`（服务端：钩子、路由、Agent 工具、**数采读驱动/写控写驱动**/帧处理器/节点模板、配置分组、KV、定时器）与 `client.mjs`（浏览器：注入具名插槽的面板、i18n、设置 UI）。三种作用域——`builtin`（随包发布）> `project`（检出）> `user`（`~/.AgentWorkShop`）——启停**与代码修改**均有约 1 秒热重载；停用插件的驱动随热重载立即摘除。内置示例 **serial-bridge**（串口通信：读/写驱动 + 串口探针 API + 前端面板）。完整契约见 [`docs/plugins.md`](./docs/plugins.md)。 |
 | **AML —— 自动建模实验室** | 数据集构建 → 训练作业 → 排行榜 → 晋级门禁 → 模型引用，全部可在 `/aml` 页驱动，也可由 Agent 通过 10 个 `aml_*` 工具驱动。Python 运行时由 `uv` 引导至 `./aml` 资产根；产物与元数据都留在配置根下。 |
 | **全量配置驱动运行时** | 全部运行旋钮（记忆预算、上下文压缩、回退护栏、保留策略、备份、日志级别…）在设置描述符注册表声明一次，优先级 **config.yml < runtime-settings < env**——**99 个设置项、16 组**，代码零硬编码默认。 |
 | **可配置节拍** | 采样与查询的默认值/下限全部是 **live 设置**（`daq.sampling.*`、`daq.query.*`）：热重载、create/patch 时钳制，Agent 工具描述实时携带当前值。 |
@@ -365,7 +365,7 @@ aw update --check                      # 只报告，不安装
 npm install -g agentworkshop@latest    # 手动等效
 ```
 
-版本遵循 semver。每次 `aw start` 都会校验配置根，并把 `home` 之前的旧版 `data/` 布局迁移进来（最新文件胜出），因此数据可以跨版本存活。SQLite schema 迁移在服务端启动时执行。当前版本：**v0.7.39**——见[版本发布](https://github.com/kingdol666/AgentWorkShop/releases)。
+版本遵循 semver。每次 `aw start` 都会校验配置根，并把 `home` 之前的旧版 `data/` 布局迁移进来（最新文件胜出），因此数据可以跨版本存活。SQLite schema 迁移在服务端启动时执行。当前版本：**v0.7.41**——见[版本发布](https://github.com/kingdol666/AgentWorkShop/releases)。
 
 ### 第一次「Agent × 产线」会话（约 2 分钟）
 
@@ -453,7 +453,7 @@ export async function run(argv, ctx) {
 
 ### 数据采集（DAQ）
 
-- **五协议驱动**：Modbus TCP、Modbus RTU-over-TCP（串口网关）、OPC UA、MQTT、HTTP/REST——连接池、分类错误文案、逐驱动连接测试；驱动注册表接受插件注册新协议。
+- **六协议驱动**：Modbus TCP、Modbus RTU-over-TCP（串口网关）、OPC UA、MQTT、HTTP/REST，加 **serial-bridge 内置插件**（RS-232/485 直连：Modbus RTU 帧机 + ASCII 行协议，写侧带同址回读校验，附串口枚举/探针 API 与前端面板）——连接池、分类错误文案、逐驱动连接测试；驱动注册表接受插件注册任意新协议（自带 meta 自描述时前端表单零改动）。
 - **逐节点边缘运行时**：独立采样节拍、下发节拍、节点级在飞互斥——一个慢驱动绝不拖累邻居。采样与查询的默认值/下限由 `daq.sampling.*`、`daq.query.*` live 设置驱动。
 - **管线**：驱动 → 队列（进程内 / MQTT，断连离线缓冲）→ 消费泵乱序防御 → 三路分发：WS 实时直推（节拍门控）、TSDB 批量落库、设备孪生回写。
 - **鲁棒性**：TSDB 单 in-flight 写 + 有界重试，缓冲背压带丢弃计数，真实丢失指标随 `daq.controller` 帧暴露。

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.7.39</b> · 14 agent engines · 5 field protocols · 99 runtime settings · bilingual docs (简体中文 / English)</sub>
+<sub><b>v0.7.41</b> · 14 agent engines · 6 field protocols · 99 runtime settings · bilingual docs (简体中文 / English)</sub>
 
 <br />
 
@@ -75,7 +75,7 @@
 
 Supervisory layer, second-level soft real-time<br/>
 14 harness engines · 4 entry points<br/>
-5 field protocols (read + write)<br/>
+6 field protocols (5 built-in + serial plugin, read + write)<br/>
 7-state task machine · FTS5 + vector memory<br/>
 Hot-reloadable plugins · SDK · CLI · TUI
 
@@ -146,7 +146,7 @@ Recorded against a running instance: real DAQ history, real write control, real
 
 | Capability | Why it matters |
 |---|---|
-| **Five field protocols** | Modbus TCP, Modbus RTU-over-TCP (serial gateway), OPC UA, MQTT and HTTP/REST — acquisition **and** write-control drivers with connection pools, classified error messages and per-driver connection tests. `mock` covers demos/CI; plugins can register new protocols. |
+| **Six field protocols** | Modbus TCP, Modbus RTU-over-TCP (serial gateway), OPC UA, MQTT and HTTP/REST, plus a **built-in serial plugin** (direct RS-232/485: Modbus RTU + ASCII line) — acquisition **and** write-control drivers with connection pools, classified error messages and per-driver connection tests. `mock` covers demos/CI. Protocols are plugins: `ctx.daq.registerDriver` / `ctx.dcw.registerWriteDriver` inject straight into the frontend protocol dropdown and dynamic forms (⌁ badge), zero frontend changes. |
 | **Agent teams, industrial scope** | Agents bind to DAQ/DCW nodes and see semantic cards — physical meaning, units, safe range, recipe window — never raw registers. |
 | **Human-approved write control** | DCW writes flow through **safe-range ∩ recipe-window** interlock → optional **HITL approval** → PLC write → **readback verification** → signed write history. |
 | **Read-write DCW channels** | Every control node also **reads its PLC value back** through the same calibration path it writes with: periodic + on-demand + agent reads surface **SET vs ACT** side by side — passive observation, never blocked by write interlocks. |
@@ -162,7 +162,7 @@ Recorded against a running instance: real DAQ history, real write control, real
 | **Line-level permissions** | Industrial data is gated **per production line** with three states (none / read-only / operate), enforced in the data plane — regular users see no line data until granted. |
 | **Full-operation audit log** | Every user / agent / system action lands in one queryable log; operators are attributed to "Channel/Member", distinct from users and the system. Streamed live over WS. |
 | **Team-scoped plugin switches** | Each team (channel) keeps an **independent plugin switch set** (`channel_plugins`): a disabled plugin's tools are not injected into that team's agents. Plugins themselves are hot-managed via `aw plugin` and the `/plugins` page. |
-| **Plugin extension API** | A self-contained directory under `plugins/<name>/` enhances **both halves at once**: `index.mjs` (server: hooks, routes, agent tools, DAQ drivers/processors/templates, config groups, KV, timers) and `client.mjs` (browser: panels injected into named slots, i18n, settings UI). Three scopes — `builtin` (shipped) > `project` (checkout) > `user` (`~/.AgentWorkShop`) — with ~1 s hot reload on enable/disable **and on code edits**. Full contract in [`docs/plugins.md`](./docs/plugins.md). |
+| **Plugin extension API** | A self-contained directory under `plugins/<name>/` enhances **both halves at once**: `index.mjs` (server: hooks, routes, agent tools, **DAQ read drivers / DCW write drivers**, frame processors, node templates, config groups, KV, timers) and `client.mjs` (browser: panels injected into named slots, i18n, settings UI). Three scopes — `builtin` (shipped) > `project` (checkout) > `user` (`~/.AgentWorkShop`) — with ~1 s hot reload on enable/disable **and on code edits**; a disabled plugin's drivers are removed on hot reload immediately. Built-in example: **serial-bridge** (serial communication: read/write drivers, serial probe API, frontend panel). Full contract in [`docs/plugins.md`](./docs/plugins.md). |
 | **AML — auto-modeling lab** | Dataset build → training job → leaderboard → promotion gates → model reference, all driven from `/aml` or by agents through 10 `aml_*` tools. Python runtime bootstrapped with `uv` into an `./aml` asset root; artifacts and metadata stay under the config root. |
 | **Fully config-driven runtime** | Every runtime knob (memory budgets, compaction, rollback guardrails, retention, backups, log level…) is declared once in the settings descriptor registry with precedence **config.yml < runtime-settings < env** — **99 settings across 16 groups**, no hardcoded defaults in code. |
 | **Configurable cadences** | Sampling and query defaults/floors are **live settings** (`daq.sampling.*`, `daq.query.*`): hot-reloaded, clamped on node create/patch, and agent tool descriptions always carry the current values. |
@@ -355,7 +355,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.7.39** — 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.7.41** — see [Releases](https://github.com/kingdol666/AgentWorkShop/releases).
 
 ### Your first agent × line session (~2 minutes)
 
@@ -443,7 +443,7 @@ export async function run(argv, ctx) {
 
 ### Data acquisition (DAQ)
 
-- **Five protocol drivers**: Modbus TCP, Modbus RTU-over-TCP (serial gateway), OPC UA, MQTT, HTTP/REST — connection pools, classified error messages, per-driver connection tests; the driver registry accepts plugin-registered protocols.
+- **Six protocol drivers**: Modbus TCP, Modbus RTU-over-TCP (serial gateway), OPC UA, MQTT, HTTP/REST, plus the **serial-bridge built-in plugin** (direct RS-232/485: Modbus RTU framing + ASCII line protocol, write side with same-address readback verification, serial enumeration/probe API and a frontend panel) — connection pools, classified error messages, per-driver connection tests; the driver registry accepts plugin-registered protocols of any kind (with self-describing metadata, the frontend forms render with zero changes).
 - **Per-node edge runtimes**: independent sampling cadence, publish cadence, in-flight mutex per node — one slow driver never blocks its neighbors. Sampling and query defaults/floors are driven by the live `daq.sampling.*` / `daq.query.*` settings.
 - **Pipeline**: driver → queue (in-process or MQTT, offline buffer on disconnect) → consumer with out-of-order defense → three-way fan-out: WS live push (gated), TSDB batch write, device-twin writeback.
 - **Robustness**: TSDB single-in-flight writes with bounded retries, buffer backpressure with drop counters, real loss metrics exposed on `daq.controller` frames.

package/app/composables/workshop/useDaqStream.ts

@@ -10,7 +10,7 @@ import { reactive } from 'vue'
 import { useTownBus } from './useTownBus'
 import { apiFetch } from './apiClient'
 import type { AepEnvelope } from '#shared/workshop-protocol'
-import { DAQ_TEMPLATES, type AepDaqControllerState, type AepDaqFrame, type AepDaqReading, type AepDaqNodeChange, type AepDaqTemplateChange, type DaqNodeView, type DaqTemplateDef, type DaqTemplateInput } from '#shared/daq-protocol'
+import { DAQ_TEMPLATES, DAQ_DRIVERS, type AepDaqControllerState, type AepDaqFrame, type AepDaqReading, type AepDaqNodeChange, type AepDaqTemplateChange, type DaqDriverCatalogEntry, type DaqNodeView, type DaqTemplateDef, type DaqTemplateInput } from '#shared/daq-protocol'
 
 /** 历史缓冲长度(1s 默认周期 ≈ 最近 5 分钟趋势) */
 const HIST_CAP = 60
@@ -57,7 +57,8 @@ interface DaqControllerState {
 interface DaqBackendMeta {
   tsdb: string
   queue: string
-  drivers: Array<{ kind: string, label: string, status: 'builtin' | 'planned' | 'real' }>
+  /** 驱动目录(REST `drivers` 权威收敛:内置 + 协议插件自描述;首帧先用内置目录) */
+  drivers: DaqDriverCatalogEntry[]
   produced: number
   consumed: number
   dropped: number
@@ -110,7 +111,7 @@ const createStore = () => {
   const alarms = reactive<DaqAlarmRow[]>([]) // S5:未确认报警(轮询 + ack 后刷新)
   const controller = reactive<DaqControllerState>({ running: true, defaultIntervalMs: 1000, defaultPublishIntervalMs: 0, queryDisplayIntervalMs: 5000, nodesTotal: 0, nodesOnline: 0 })
   const meta = reactive<DaqBackendMeta>({
-    tsdb: '…', queue: '…', drivers: [], driverAvailable: {},
+    tsdb: '…', queue: '…', drivers: DAQ_DRIVERS.map(d => ({ kind: d.kind, label: d.label, status: d.status, configFields: d.configFields })), driverAvailable: {},
     infra: undefined,
     produced: 0, consumed: 0, dropped: 0, samplesStored: 0,
   })
@@ -266,7 +267,7 @@ const createStore = () => {
 
   async function load(): Promise<void> {
     try {
-      const data = await api<{ controller: DaqControllerState, nodes: DaqNodeView[], meta: DaqBackendMeta, driverAvailable?: Record<string, boolean>, infra?: DaqInfraState, templates?: DaqTemplateDef[] }>('')
+      const data = await api<{ controller: DaqControllerState, nodes: DaqNodeView[], meta: DaqBackendMeta, driverAvailable?: Record<string, boolean>, drivers?: DaqDriverCatalogEntry[], infra?: DaqInfraState, templates?: DaqTemplateDef[] }>('')
       // 快照合并:hist 是客户端读数流资产,轮询重载不得清零;
       // 已有节点就地 assign(保留对象身份 → Vue 只补丁变化字段,不触发整表数组级失效),hist 自然保留
       const prev = new Map(nodes.map(n => [n.id, n]))
@@ -291,6 +292,8 @@ const createStore = () => {
       Object.assign(controller, data.controller)
       Object.assign(meta, data.meta ?? {})
       meta.driverAvailable = data.driverAvailable ?? {}
+      // 驱动目录 server 权威(含协议插件);server 未下发(旧版)时保留内置目录
+      if (data.drivers?.length) meta.drivers = data.drivers
       meta.infra = data.infra
       if (data.templates?.length) applyTemplates(data.templates)
       store.loaded = true

package/app/composables/workshop/useDcwStream.ts

@@ -8,7 +8,8 @@ import { reactive } from 'vue'
 import { useTownBus } from './useTownBus'
 import { apiFetch } from './apiClient'
 import type { AepEnvelope } from '#shared/workshop-protocol'
-import { DCW_TEMPLATES, type AepDcwControllerState, type AepDcwNodeChange, type AepDcwRead, type AepDcwWritten, type DcwNodeView, type DcwParamLedger, type DcwTemplateDef, type DcwTemplateInput, type LineInput, type LineQueryOpts, type LineQueryResult, type LineRunState, type LineView, type OptimizationRecord, type OptimizationVerdict, type ProductInput, type ProductView, type RecipeInput, type RecipeParam, type RecipeRunView, type RecipeView, type RecipeRunData } from '#shared/dcw-protocol'
+import { DCW_TEMPLATES, DCW_DRIVERS, type AepDcwControllerState, type AepDcwNodeChange, type AepDcwRead, type AepDcwWritten, type DcwNodeView, type DcwParamLedger, type DcwTemplateDef, type DcwTemplateInput, type LineInput, type LineQueryOpts, type LineQueryResult, type LineRunState, type LineView, type OptimizationRecord, type OptimizationVerdict, type ProductInput, type ProductView, type RecipeInput, type RecipeParam, type RecipeRunView, type RecipeView, type RecipeRunData } from '#shared/dcw-protocol'
+import type { DaqDriverCatalogEntry } from '#shared/daq-protocol'
 
 export type { DcwNodeView }
 
@@ -35,6 +36,8 @@ function createStore() {
   const lineStates = reactive<Record<string, LineRunState>>({})
   /** Agent 优化记录(调控闭环;dcw.optimization.changed 实时收敛) */
   const optimizations = reactive<OptimizationRecord[]>([])
+  /** 写驱动目录(REST `drivers` 权威:内置 + 协议插件自描述;首帧先用内置目录) */
+  const driverCatalog = reactive<DaqDriverCatalogEntry[]>(DCW_DRIVERS.map(d => ({ kind: d.kind, label: d.label, status: d.status, configFields: d.configFields })))
 
   function upsert(node: DcwNodeView): void {
     const i = nodes.findIndex(x => x.id === node.id)
@@ -112,12 +115,14 @@ function createStore() {
 
   async function load(): Promise<void> {
     try {
-      const data = await api<{ controller: AepDcwControllerState, nodes: DcwNodeView[], templates?: DcwTemplateDef[], recipes?: RecipeView[], runs?: RecipeRunView[], history?: DcwWriteHistoryEntry[], products?: ProductView[], lines?: LineView[], lineStates?: LineRunState[] }>('')
+      const data = await api<{ controller: AepDcwControllerState, nodes: DcwNodeView[], templates?: DcwTemplateDef[], drivers?: DaqDriverCatalogEntry[], recipes?: RecipeView[], runs?: RecipeRunView[], history?: DcwWriteHistoryEntry[], products?: ProductView[], lines?: LineView[], lineStates?: LineRunState[] }>('')
       nodes.splice(0, nodes.length, ...data.nodes)
       nodeIndex.clear()
       for (const n of nodes) nodeIndex.set(n.id, n)
       Object.assign(controller, data.controller)
       if (data.templates?.length) templates.splice(0, templates.length, ...data.templates.map(t => ({ ...t })))
+      // 写驱动目录 server 权威(含协议插件);server 未下发(旧版)时保留内置目录
+      if (data.drivers?.length) driverCatalog.splice(0, driverCatalog.length, ...data.drivers)
       recipes.splice(0, recipes.length, ...(data.recipes ?? []))
       runs.splice(0, runs.length, ...(data.runs ?? []))
       history.splice(0, history.length, ...(data.history ?? []))
@@ -144,6 +149,7 @@ function createStore() {
     lines,
     lineStates,
     optimizations,
+    driverCatalog,
     loaded: false,
     error: '',
     ensureWsFeed,

package/app/pages/daq/[id].vue

@@ -9,7 +9,7 @@ import { useRoute } from 'vue-router'
 import { useDcwStream } from '@/app/composables/workshop/useDcwStream'
 import { useDaqStream, type DaqFrameLive, type DaqTsdbPoint } from '@/app/composables/workshop/useDaqStream'
 import { useDeviceTwins } from '@/app/composables/workshop/useDeviceTwins'
-import { daqKeyFromRef, DAQ_DRIVERS, type DaqDriverKind, type DaqNodeState, type DriverConfigField, type DriverTestResult as DaqDriverTestResult } from '#shared/daq-protocol'
+import { daqKeyFromRef, DAQ_DRIVERS, type DaqDriverCatalogEntry, type DaqDriverKind, type DaqNodeState, type DriverConfigField, type DriverTestResult as DaqDriverTestResult } from '#shared/daq-protocol'
 
 const { t } = useI18n()
 
@@ -129,9 +129,13 @@ watch(node, (n) => {
 }, { immediate: true })
 
 // 驱动连接参数编辑(真实协议:host/register/endpoint...;schema 驱动渲染)
+// 驱动目录:server 权威(内置 + 协议插件自描述;REST 未返回时回落静态目录)
+const driverCatalog = computed<DaqDriverCatalogEntry[]>(() => daq.meta.drivers.length
+  ? daq.meta.drivers
+  : DAQ_DRIVERS.map(d => ({ ...d })))
 const driverCfg = ref<Record<string, string | number>>({})
 const driverFields = computed<DriverConfigField[]>(() =>
-  DAQ_DRIVERS.find(d => d.kind === form.driver)?.configFields ?? [])
+  driverCatalog.value.find(d => d.kind === form.driver)?.configFields ?? [])
 watch(node, (n) => {
   if (n) driverCfg.value = { ...(n.driverConfig as Record<string, string | number>) }
 }, { immediate: true })
@@ -508,12 +512,12 @@ watch(effectiveRefreshMs, () => armHistTimer())
               class="input"
             >
               <option
-                v-for="d in DAQ_DRIVERS"
+                v-for="d in driverCatalog"
                 :key="d.kind"
                 :value="d.kind"
                 :disabled="d.status === 'planned'"
               >
-                {{ d.label }}{{ d.status === 'planned' ? $t('daqDetail.kz8zr9v035') : '' }}
+                {{ d.label }}{{ d.plugin ? ' ⌁' : '' }}{{ d.status === 'planned' ? $t('daqDetail.kz8zr9v035') : '' }}
               </option>
             </select>
           </label>
@@ -655,7 +659,7 @@ watch(effectiveRefreshMs, () => armHistTimer())
         <!-- 驱动连接参数(mock 空;真实协议 schema 动态表单 + 测试连接) -->
         <template v-if="driverFields.length">
           <h3 class="sec mt">
-            {{ $t('daqDetail.k1p9gioa033') }} {{ DAQ_DRIVERS.find(d => d.kind === form.driver)?.label }}
+            {{ $t('daqDetail.k1p9gioa033') }} {{ driverCatalog.find(d => d.kind === form.driver)?.label }}
           </h3>
           <div class="driver-grid">
             <label

package/app/pages/daq/index.vue

@@ -9,7 +9,7 @@ import { message } from 'ant-design-vue'
 import { useDaqStream, type DaqNodeLive } from '@/app/composables/workshop/useDaqStream'
 import { useDcwStream } from '@/app/composables/workshop/useDcwStream'
 import { useWorkshopWs } from '@/app/composables/workshop/useWorkshopWs'
-import { DAQ_TEMPLATES, DAQ_DRIVERS, DAQ_TEMPLATE_ICONS, daqKeyFromRef, type DaqNodeView, type DaqNodeState, type DriverConfigField, type DriverTestResult as DaqDriverTestResult, type DaqTemplateDef, type DaqTemplateIcon } from '#shared/daq-protocol'
+import { DAQ_TEMPLATES, DAQ_DRIVERS, DAQ_TEMPLATE_ICONS, daqKeyFromRef, type DaqDriverCatalogEntry, type DaqNodeView, type DaqNodeState, type DriverConfigField, type DriverTestResult as DaqDriverTestResult, type DaqTemplateDef, type DaqTemplateIcon } from '#shared/daq-protocol'
 import { useDeviceTwins } from '@/app/composables/workshop/useDeviceTwins'
 import { useOpsLog } from '@/app/composables/workshop/useOpsLog'
 import { useVisibleInterval } from '@/app/composables/workshop/useVisibleInterval'
@@ -353,7 +353,10 @@ const addTest = ref<DaqDriverTestResult | null>(null)
 const addSaving = ref(false)
 const addError = ref('')
 
-const addDriverMeta = computed(() => DAQ_DRIVERS.find(d => d.kind === addDriver.value))
+// 驱动目录:server 权威(内置 + 协议插件自描述;REST 未返回时回落静态目录)
+const driverCatalog = computed<DaqDriverCatalogEntry[]>(() =>
+  daq.meta.drivers.length ? daq.meta.drivers : DAQ_DRIVERS.map(d => ({ ...d })))
+const addDriverMeta = computed(() => driverCatalog.value.find(d => d.kind === addDriver.value))
 const addFields = computed<DriverConfigField[]>(() => addDriverMeta.value?.configFields ?? [])
 const driverReady = (kind: string): boolean =>
   daq.meta.drivers.find(d => d.kind === kind)?.status !== 'planned' && (daq.meta.driverAvailable?.[kind] !== false)
@@ -841,11 +844,11 @@ async function doReconnect(): Promise<void> {
                 class="inp"
               >
                 <option
-                  v-for="d in DAQ_DRIVERS.filter(x => x.status !== 'planned')"
+                  v-for="d in driverCatalog.filter(x => x.status !== 'planned')"
                   :key="d.kind"
                   :value="d.kind"
                 >
-                  {{ d.label }}{{ driverReady(d.kind) ? '' : $t('daq.kjbqphp098') }}
+                  {{ d.label }}{{ d.plugin ? ' ⌁' : '' }}{{ driverReady(d.kind) ? '' : $t('daq.kjbqphp098') }}
                 </option>
               </select>
             </label>
@@ -1574,9 +1577,9 @@ async function doReconnect(): Promise<void> {
               class="vs-pad"
               aria-hidden="true"
             >
-              <td
-                :colspan="11"
-                :style="{ height: padTopPx + 'px' }"
+              <td
+                :colspan="11"
+                :style="{ height: padTopPx + 'px' }"
               />
             </tr>
             <WorkshopDaqNodeRow
@@ -1590,9 +1593,9 @@ async function doReconnect(): Promise<void> {
               class="vs-pad"
               aria-hidden="true"
             >
-              <td
-                :colspan="11"
-                :style="{ height: padBottomPx + 'px' }"
+              <td
+                :colspan="11"
+                :style="{ height: padBottomPx + 'px' }"
               />
             </tr>
             <tr v-if="daq.loaded && daq.nodes.length === 0">

package/app/pages/dcw/[id].vue

@@ -2,7 +2,7 @@
 import { computed, onUnmounted, reactive, ref } from 'vue'
 import { useRoute } from 'vue-router'
 import { DCW_DRIVERS, type DcwParamLedger, type DcwTemplateIcon, type LineQueryResult, type RecipeRunData, type RecipeView } from '#shared/dcw-protocol'
-import type { DriverConfigField } from '#shared/daq-protocol'
+import type { DaqDriverCatalogEntry, DriverConfigField } from '#shared/daq-protocol'
 import { useDcwStream } from '~/composables/workshop/useDcwStream'
 import { useDaqStream } from '~/composables/workshop/useDaqStream'
 import { useDeviceTwins } from '~/composables/workshop/useDeviceTwins'
@@ -191,7 +191,11 @@ const addTest = ref<{ ok: boolean, message: string } | null>(null)
 const addSaving = ref(false)
 const addError = ref('')
 
-const addDriverMeta = computed(() => DCW_DRIVERS.find(d => d.kind === addDriver.value))
+// 写驱动目录:server 权威(内置 + 协议插件自描述;REST 未返回时回落静态目录)
+const driverCatalog = computed<DaqDriverCatalogEntry[]>(() => dcw.driverCatalog.length
+  ? dcw.driverCatalog
+  : DCW_DRIVERS.map(d => ({ ...d })))
+const addDriverMeta = computed(() => driverCatalog.value.find(d => d.kind === addDriver.value))
 const addFields = computed<DriverConfigField[]>(() => addDriverMeta.value?.configFields ?? [])
 
 function resetAddCfg(): void {
@@ -1132,11 +1136,11 @@ function fmtPoint(p: { value?: number, avg?: number } | undefined): string {
                 class="inp"
               >
                 <option
-                  v-for="d in DCW_DRIVERS.filter(x => x.status !== 'builtin')"
+                  v-for="d in driverCatalog.filter(x => x.status !== 'builtin')"
                   :key="d.kind"
                   :value="d.kind"
                 >
-                  {{ d.label }}
+                  {{ d.label }}{{ d.plugin ? ' ⌁' : '' }}
                 </option>
               </select>
             </label>

package/docs/cli.en.md

@@ -62,7 +62,7 @@ pnpm tui             # the terminal workbench
 ### 3. Quick use via npx (no global install)
 
 ```bash
-npx agentworkshop start            # fetch and start (pin a version with: npx agentworkshop@0.7.38 start)
+npx agentworkshop start            # fetch and start (pin a version with: npx agentworkshop@0.7.41 start)
 npx agentworkshop doctor           # subcommands work as usual
 npx -p agentworkshop aw doctor     # use -p when you want the name aw
 ```
@@ -79,7 +79,7 @@ npx -p agentworkshop aw doctor     # use -p when you want the name aw
 | Package manager | `pnpm@11.9.0` (`packageManager`, needed only for source development) |
 | Module format | ESM (`type: module`) |
 | License | `PolyForm-Noncommercial-1.0.0` |
-| Current version | `0.7.38` (`package.json`) |
+| Current version | `0.7.41` (`package.json`) |
 
 ## 2. First start (the Claude Code experience)
 

package/docs/cli.md

@@ -60,7 +60,7 @@ pnpm tui             # 终端工作台
 ### 3. npx 快速使用（免全局安装）
 
 ```bash
-npx agentworkshop start            # 拉取并启动(可锁定版本: npx agentworkshop@0.7.38 start)
+npx agentworkshop start            # 拉取并启动(可锁定版本: npx agentworkshop@0.7.41 start)
 npx agentworkshop doctor           # 子命令照常可用
 npx -p agentworkshop aw doctor     # 需要 aw 这个名字时用 -p 指定包
 ```
@@ -76,7 +76,7 @@ npx -p agentworkshop aw doctor     # 需要 aw 这个名字时用 -p 指定包
 | 包管理器 | `pnpm@11.9.0`（`packageManager`，仅源码开发需要） |
 | 模块形态 | ESM（`type: module`） |
 | 许可证 | `PolyForm-Noncommercial-1.0.0` |
-| 当前版本 | `0.7.38`（`package.json`） |
+| 当前版本 | `0.7.41`（`package.json`） |
 
 ## 二、首次启动（Claude Code 式）
 

package/docs/plugins.en.md

@@ -9,7 +9,7 @@
 >
 > Applies to: plugin system v2 has been available since **v0.7.29** (frontend component
 > injection / plugin settings / plugin i18n / runtime services surface); this document
-> describes **v0.7.38**. `ctx.sdkVersion` is currently `0.3.0`.
+> describes **v0.7.41**. `ctx.sdkVersion` is currently `0.3.0`.
 
 ## 1. Folder layout & quick start
 
@@ -210,10 +210,41 @@ async setup(ctx) {
 | Events | `ctx.events.on(type, fn)` / `ctx.events.off(type, fn)` | scene-event sugar: subscribes to `event:<type>` internally (see §7) |
 | Paths | `ctx.paths.home / configRoot / dataDir`; `ctx.dataDir` | `ctx.dataDir` is this plugin's KV folder, `<configRoot>/data/plugins/<plugin>` |
 | DAQ | `ctx.daq.registerDriver / registerProcessor / registerTemplate / onFrame / onSample / query / nodes` | driver, sink-processor and node-template registration + time-series queries + node metadata snapshot |
+| Write control | `ctx.dcw.registerWriteDriver(driver)` | write-driver injection (symmetric to DAQ read drivers): contract `{ kind, available(), write(input), test(cfg), read?(input), meta? }`; disabled plugins lose their drivers on hot reload |
 | Tools | `ctx.omp.registerTool({ name, label?, description, parameters, roles?, handler })` | agent tool injection; `roles` accepts `'lead'` and `'worker'` only (see §10) |
 | Services | `ctx.services.names()` / `.get(name)` / `.provide(name, getter)` | runtime object surface: `get('daq' \| 'lines' \| 'channels' \| 'plugins')`; `provide` auto-prefixes `<plugin>.` |
 | Permissions | `ctx.permissions.lineMode / visibleLineIds / listGrants / setGrants` | line-grant queries and management |
 
+### Communication-protocol plugins (custom interface connections)
+
+`ctx.daq.registerDriver` / `ctx.dcw.registerWriteDriver` are the **protocol plug-in points**: serial
+links, other PLC protocols and private buses all inject here — the main pipelines (sampling loop /
+write gateway / frontend forms) need zero changes.
+
+```js
+ctx.daq.registerDriver({
+  kind: 'serial',                    // custom protocol kind (overriding a builtin logs a warning)
+  async available() { return true }, // protocol-stack probe (missing package → UI shows "not installed")
+  async sample({ driverConfig }) { return 25.3 },   // reading (scalar or v2 frame envelope)
+  async test(driverConfig) { return { ok: true, message: 'connected', sampleValue: 25.3 } },
+  meta: {                            // self-description (frontend "add node" dropdown + dynamic form)
+    label: 'Serial (RS-232/485)',
+    status: 'real',
+    configFields: [{ key: 'path', label: 'Port path', type: 'string', required: true, placeholder: 'COM3' }],
+  },
+})
+```
+
+Key points:
+- The driver catalog is served via the `drivers` field of `GET /api/workshop/daq` (read) and
+  `GET /api/workshop/dcw` (write); the DAQ/DCW pages render plugin protocols and their forms from it
+  (with a ⌁ badge). Drivers registered without `meta` only appear in availability;
+- Hot reload clears all plugin drivers first, then re-loads: **disabled/unloaded protocol drivers
+  take effect immediately upon removal** and never linger until restart;
+- Builtin example: `server/plugins-builtin/serial-bridge` (serial Modbus RTU + ASCII line protocol,
+  with read/write drivers, `health`/`ports`/`probe` APIs, a frontend panel and the `serial_ports`
+  agent tool) — use it as the template for new protocol plugins.
+
 ### Where KV lives
 
 `<configRoot>/data/plugins/<plugin>/kv.json` — **not** inside the plugin folder. Writes are authoritative in memory and flushed atomically (`tmp` + `rename`) after a 200 ms debounce; on shutdown and hot reload the pending debounce is cancelled and the state is flushed synchronously. `ctx.kv` has exactly four methods: `get / set / all / bump`.
@@ -524,6 +555,7 @@ export default {
 - **A newly enabled browser plugin injects within 15 s** (instantly when the WS channel is up).
 - **`server:close` / `onDispose` depend on graceful shutdown signals**; a forced kill on Windows does not trigger them.
 - **`aw plugin list` only scans directories** — it reflects neither load failures nor runtime health.
+- **Protocol plugins share the host process with their native stacks**: serial-bridge's RTU framing is a self-contained implementation (single serialport native stack; modbus-serial is deliberately NOT used — its wrapper reproducibly crashed under dev mode). Known boundary: **inside the `aw dev` process, a serial transaction that ends in write → timeout → close can trigger a native V8 crash in `bindings-cpp`** (HandleScope fatal — not catchable in JS, regardless of which port is used); **production mode (`aw start`) is unaffected — the exact same sequence was verified live to return an honest timeout with the server healthy**, and open-only probes are also fine under dev. Connect real hardware during development with this in mind; for hardened deployments, run the serial gateway in its own process (see the plc-node-simulator child-process pattern).
 
 ## 13. Pre-release checklist
 

package/docs/plugins.md

@@ -6,7 +6,7 @@
 > 本文是唯一权威参考;`docs/site/plugins/` 的分页文档与本文同源。
 >
 > 适用版本:插件系统 v2 自 **v0.7.29** 起可用(前端组件注入 / 插件设置 / 插件 i18n /
-> 运行时服务面);本文档对应当前版本 **v0.7.38**。`ctx.sdkVersion` 当前为 `0.3.0`。
+> 运行时服务面);本文档对应当前版本 **v0.7.41**。`ctx.sdkVersion` 当前为 `0.3.0`。
 
 ## 一、目录结构与快速开始
 
@@ -207,10 +207,37 @@ async setup(ctx) {
 | 事件 | `ctx.events.on(type, fn)` / `ctx.events.off(type, fn)` | scene 实时事件糖:内部订阅 `event:<type>`(见 §7) |
 | 路径 | `ctx.paths.home / configRoot / dataDir`;`ctx.dataDir` | `ctx.dataDir` 即本插件 KV 目录 `<配置根>/data/plugins/<插件名>` |
 | 数采 | `ctx.daq.registerDriver / registerProcessor / registerTemplate / onFrame / onSample / query / nodes` | 驱动、下沉处理器、节点模板注册 + 时序查询 + 节点元数据快照 |
+| 写控 | `ctx.dcw.registerWriteDriver(driver)` | 写驱动注入(与数采读驱动对称):契约 `{ kind, available(), write(input), test(cfg), read?(input), meta? }`;热重载停用即失效 |
 | 工具 | `ctx.omp.registerTool({ name, label?, description, parameters, roles?, handler })` | Agent 工具注入;`roles` 仅 `'lead'` 与 `'worker'`(见 §10) |
 | 服务 | `ctx.services.names()` / `.get(name)` / `.provide(name, getter)` | 运行时对象面:`get('daq' \| 'lines' \| 'channels' \| 'plugins')`;`provide` 自动加 `<插件名>.` 前缀 |
 | 权限 | `ctx.permissions.lineMode / visibleLineIds / listGrants / setGrants` | 产线授权查询与管理 |
 
+### 通信协议插件(自定义接口连接方式)
+
+`ctx.daq.registerDriver` / `ctx.dcw.registerWriteDriver` 是**协议接入点**:串口、其他 PLC 协议、
+私有总线的连接实现都从这里注入,主链路(采样循环 / 写控网关 / 前端表单)零改动。
+
+```js
+ctx.daq.registerDriver({
+  kind: 'serial',                    // 自定义协议 kind(与内置冲突时插件覆盖并告警)
+  async available() { return true }, // 协议栈包探测(缺失时 UI 显示「未安装」)
+  async sample({ driverConfig }) { return 25.3 },   // 读数(标量或 v2 帧信封)
+  async test(driverConfig) { return { ok: true, message: '连接成功', sampleValue: 25.3 } },
+  meta: {                            // 自描述(前端「添加节点」下拉 + 动态参数表单)
+    label: '串口 Serial(RS-232/485)',
+    status: 'real',
+    configFields: [{ key: 'path', label: '串口路径', type: 'string', required: true, placeholder: 'COM3' }],
+  },
+})
+```
+
+要点:
+- 驱动目录经 `GET /api/workshop/daq`(读)与 `GET /api/workshop/dcw`(写)的 `drivers` 字段下发,
+  前端数采/写控页据此渲染插件协议与参数表单(带 ⌁ 徽标);不带 `meta` 的驱动只出现在可用性里;
+- 热重载先清空全部插件驱动再重装载:**停用/卸载的协议驱动立即失效**,不会残留到重启;
+- 内置示例:`server/plugins-builtin/serial-bridge`(串口 Modbus RTU + ASCII 行协议,含读/写驱动、
+  `health`/`ports`/`probe` API、前端面板与 `serial_ports` Agent 工具)——新协议插件建议以它为模板。
+
 ### KV 落在哪里
 
 `<configRoot>/data/plugins/<插件名>/kv.json` —— **不在插件目录里**。写入以内存为准,200ms 防抖后 `tmp + rename` 原子落盘;关机与热重载时取消挂起的防抖并同步落盘。`ctx.kv` 只有 `get / set / all / bump` 四个方法。
@@ -521,6 +548,7 @@ export default {
 - **浏览器新启用插件注入延迟 ≤15s**(WS 可用时即时)。
 - **`server:close` / `onDispose` 依赖优雅关闭信号**,Windows 强杀进程不触发。
 - **`aw plugin list` 只做目录扫描**,不反映装载失败与运行态健康。
+- **协议插件的原生栈与宿主同进程**:serial-bridge 的 RTU 帧机为自研实现(单 serialport 原生栈;弃用 modbus-serial —— 其包装层在 dev 模式实测触发 V8 原生崩溃)。已知边界:**`aw dev` 进程内,串口事务「写→超时→关闭」序列可能触发 bindings-cpp 的 V8 原生崩溃**(HandleScope fatal,JS 层不可捕获,与具体串口无关);**生产模式(`aw start`)不受影响 —— 已实测同一序列在生产下诚实返回超时且服务存活**,纯打开(ASCII 探针)在 dev 下同样正常。开发期连接真实硬件请知悉此风险;对稳定性要求极高的部署可把串口网关放进独立进程(参考 plc-node-simulator 的子进程模式)。
 
 ## 十三、发布前验证清单
 

package/docs/sdk.en.md

@@ -7,7 +7,7 @@
 
 **SDK version constants**: server-side `SDK_VERSION = '0.3.0'`, browser-side `CLIENT_SDK_VERSION = '0.3.0'`.
 These two constants are the **interface version of the SDK itself** and evolve **independently**
-from the npm package version (the `version` field in `package.json`, currently 0.7.38) —
+from the npm package version (the `version` field in `package.json`, currently 0.7.41) —
 them being out of sync is expected. Never use `SDK_VERSION` to infer the package version, or the reverse.
 **Module format**: ESM only (only `import` / `export`; there is no CJS entry).
 **Types**: `sdk/index.d.mts` and `sdk/client.d.mts` ship with the package, so TypeScript projects

package/docs/sdk.md

@@ -5,7 +5,7 @@
 > 零第三方运行时依赖,Node ≥ 23.4 与现代浏览器双端可用。
 
 **SDK 版本常量**:服务端 `SDK_VERSION = '0.3.0'`,浏览器端 `CLIENT_SDK_VERSION = '0.3.0'`。
-这两个常量是 **SDK 自身接口的版本号**,与 npm 包版本(`package.json` 的 `version`,当前 0.7.38)
+这两个常量是 **SDK 自身接口的版本号**,与 npm 包版本(`package.json` 的 `version`,当前 0.7.41)
 **各自独立演进** —— 常数不同步是预期行为,不要拿 `SDK_VERSION` 去推断包版本,反之亦然。
 **模块形态**:ESM only(只有 `import` / `export`,没有 CJS 入口)。
 **类型**:`sdk/index.d.mts`、`sdk/client.d.mts` 随包发布,TS 项目零配置获得提示(覆盖范围见 §7)。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentworkshop",
-  "version": "0.7.40",
+  "version": "0.7.41",
   "type": "module",
   "description": "AgentWorkShop 软件开发系统 - 基于 Nuxt 4 的配置驱动运行范式",
   "license": "PolyForm-Noncommercial-1.0.0",
@@ -145,7 +145,8 @@
     "zod": "^3.24.1"
   },
   "optionalDependencies": {
-    "onnxruntime-node": "^1.20.1"
+    "onnxruntime-node": "^1.20.1",
+    "serialport": "^13.0.0"
   },
   "devDependencies": {
     "@commitlint/cli": "^19.6.1",