agentworkshop 0.8.3 → 0.8.5

package/.AgentWorkShop/prompts/host-tools.en.json

@@ -0,0 +1,174 @@
+{
+  "daq_query": {
+    "description": "Query historical/live data for DAQ nodes you can access. Access is granted either by direct node binding or by the channel's line binding (read-only for all DAQ nodes on that line). Filters: line/product/recipe/run/time window/downsampling (product and recipe filters use per-sample tags, so a specific batch can be selected precisely). Results carry physical meaning (semantics, unit, range, statistics, recent series). By default only the **current active batch (active recipe)** is queried; pass scope=all explicitly to compare across recipes or review full history.",
+    "parameters": {
+      "properties": {
+        "node_id": { "description": "Restrict to one DAQ node id (default: all bound nodes)" },
+        "line_id": { "description": "Filter by line (data ownership)" },
+        "product_id": { "description": "Filter by product (per-sample tags); passing it overrides the default active-batch filter" },
+        "recipe_id": { "description": "Filter by recipe (per-sample tags); passing it overrides the default filter. Default: the active recipe of the node's line (no filter if the line is not running)" },
+        "run_id": { "description": "Filter by run id (pin one run when a recipe was started multiple times); passing it overrides the default filter" },
+        "scope": { "description": "Scope: active (default) = current active batch only; all = no recipe filter, return every sample in the window (cross-recipe comparison/history review)" },
+        "last_minutes": { "description": "Last N minutes (default 30)" },
+        "from_ms": { "description": "Start epoch ms (paired with to_ms; takes precedence over last_minutes)" },
+        "to_ms": { "description": "End epoch ms" },
+        "bucket_ms": { "description": "Downsampling bucket width in ms (default {queryDefaultBucketMs}, floor {queryMinBucketMs})" },
+        "limit": { "description": "Maximum number of points returned (default 500)" }
+      }
+    }
+  },
+  "recipe_catalog": {
+    "description": "List recipe definitions on lines you can read (find recipe_id / the currently running recipe / product ownership). Each entry includes recipe id, version, product, whether it is running, parameter count, each node's target and PLC value, and last good batch. Supports line_id/product_id/keyword filters. Use this first when unsure of a recipe_id; recipe_apply/recipe_trial/recipe_update can also take line_id and resolve the active recipe. Read-only.",
+    "parameters": {
+      "properties": {
+        "line_id": { "description": "Restrict to a line id (must be readable)" },
+        "product_id": { "description": "Restrict to a product id" },
+        "q": { "description": "Keyword substring filter (recipe name/description)" },
+        "limit": { "description": "Maximum rows (default 20, max 100)" }
+      }
+    }
+  },
+  "recipe_update": {
+    "description": "Save verified best parameters into a recipe as a new version with attribution and rationale. You may target the currently running recipe by passing only line_id (resolved from the active batch), or pass recipe_id explicitly. Permission model: you must be bound to the recipe (multiple bindings allowed) and pass its secondary auth; the recipe must be running (run gate). With a manual binding or manual line, the save suspends for human approval — reason is required and must cite evidence (DAQ data/analysis); the approval card shows it. This changes the definition only; use recipe_apply to push parameters to the running line.",
+    "parameters": {
+      "properties": {
+        "recipe_id": { "description": "Recipe id (mutually exclusive with line_id; explicit id wins)" },
+        "params": {
+          "description": "Parameters to update (partial merge; list only nodes that change)",
+          "items": {
+            "properties": {
+              "node_id": { "description": "DCW node id (must be one of your bound DCW nodes)" },
+              "value": { "description": "New target value" },
+              "min": { "description": "Optional new recipe window lower bound" },
+              "max": { "description": "Optional new recipe window upper bound" }
+            }
+          }
+        },
+        "reason": { "description": "Why this change is saved (required; state the evidence)" },
+        "task_id": { "description": "Optional related task id" },
+        "line_id": { "description": "Line id (mutually exclusive with recipe_id): resolve the recipe from that line's active batch" }
+      }
+    }
+  },
+  "recipe_apply": {
+    "description": "Dispatch the recipe's currently persisted parameters to the running line as one batch (use after recipe_update). You may target the running recipe with only line_id (resolved from the active batch) or pass recipe_id explicitly. Permission model: bound recipe, secondary auth, and run gate (recipe must be executing). With a manual binding or manual line, dispatch suspends for human approval — reason is required and must explain why and on what evidence. After approval the batch goes through governance interlocks (range/step/rate) with per-parameter acknowledgements. A rejection may include guidance; revise and resubmit.",
+    "parameters": {
+      "properties": {
+        "recipe_id": { "description": "Recipe id (mutually exclusive with line_id; explicit id wins)" },
+        "reason": { "description": "Why dispatch (required): data evidence/trial conclusion/goal-gap analysis; the line expert must understand your reasoning on the approval card" },
+        "emergency": { "description": "Emergency exemption from the recipe dispatch rate limit (does NOT skip approval; the card is marked [EMERGENCY] and still needs a human; abuse is audited)" },
+        "line_id": { "description": "Line id (mutually exclusive with recipe_id): resolve the recipe from the active batch; use to dispatch to the current recipe" }
+      }
+    }
+  },
+  "recipe_trial": {
+    "description": "Dispatch a multi-parameter candidate batch without writing a recipe version. You may target the running recipe with only line_id or pass recipe_id explicitly. Permission model: bound recipe, secondary auth, and run gate; candidates may only cover parameters in the recipe. With a manual binding or manual line, the trial suspends for human approval — hypothesis is required (why this trial and on what evidence). The whole batch lands at once; after re-measurement, persist improvement with recipe_update or roll back with recipe_rollback(dispatch=true). Subject to the per-line trial interval (default >=5 minutes) and the four-layer limits.",
+    "parameters": {
+      "properties": {
+        "recipe_id": { "description": "Recipe id (mutually exclusive with line_id; explicit id wins)" },
+        "params": {
+          "description": "Candidate parameters (>=1; include every change in one batch to avoid oscillation)",
+          "items": {
+            "properties": {
+              "node_id": { "description": "DCW node id" },
+              "value": { "description": "Candidate engineering value" }
+            }
+          }
+        },
+        "hypothesis": { "description": "Trial hypothesis/rationale (required: knowledge-base entry or data analysis conclusion)" },
+        "emergency": { "description": "Emergency exemption from the recipe dispatch rate limit (does NOT skip approval; the card is marked [EMERGENCY] and still needs a human; abuse is audited)" },
+        "line_id": { "description": "Line id (mutually exclusive with recipe_id): resolve the active recipe" }
+      }
+    }
+  },
+  "recipe_rollback": {
+    "description": "Roll recipe parameters back to a stable version (a historical version or the last good batch) by creating a new non-destructive version; with dispatch=true it also restores the parameters to the line as a batch. Permission model: bound recipe, secondary auth, and run gate; manual bindings suspend for HITL — reason is required (e.g. optimization degradation/out-of-limit).",
+    "parameters": {
+      "properties": {
+        "recipe_id": { "description": "Recipe id (required)" },
+        "version": { "description": "Roll back to this historical version (either version or to_last_good)" },
+        "to_last_good": { "description": "true = restore the last good batch parameters" },
+        "reason": { "description": "Rollback reason (required)" },
+        "dispatch": { "description": "true = restore the definition AND re-dispatch parameters to the PLC (use when the optimization loop degrades); default false = definition only" },
+        "emergency": { "description": "Emergency exemption from the recipe dispatch rate limit (does NOT skip approval; still needs a human; abuse is audited)" }
+      }
+    }
+  },
+  "recipe_log": {
+    "description": "Query recipe change history (create/update/trial/apply/per-parameter ACK/approval/optimization window verdict/rollback/start-batch dispatch; newest first). Returns only scope=line records, each with line and recipe attribution. Pass recipe_id to get the whole event family across kinds (including kind=write dispatch ACKs); line.start/line.stop are included (starting a line dispatches recipe parameters). Without line_id the channel-bound line is used; recipe_id narrows to that recipe's line. Time via from/to or minutes. Use dcw_journal for per-node write history.",
+    "parameters": {
+      "properties": {
+        "line_id": { "description": "Line id (must be readable; default: channel-bound line, or all readable lines when unbound)" },
+        "recipe_id": { "description": "Filter by recipe id (implies its line)" },
+        "product_id": { "description": "Filter by product id (must belong to a readable line)" },
+        "from": { "description": "Window start (ISO or 2026-10-19T08:00)" },
+        "to": { "description": "Window end (ISO; must be after from)" },
+        "minutes": { "description": "Lookback minutes when from is omitted (default 1440 = 24h)" },
+        "limit": { "description": "Maximum rows (default 20, max 100)" }
+      }
+    }
+  },
+  "recipe_versions": {
+    "description": "View the parameter version history of a recipe (old to new): version, time, source (user/agent/system), actor name, change reason, and parameter diff. Use it to confirm a target version before rollback and to review who changed what and why. Visibility = recipe line readable (node-granted line ∪ bound recipe line ∪ channel-bound line). Rollback goes through recipe_rollback (write gate; manual bindings need HITL).",
+    "parameters": {
+      "properties": {
+        "recipe_id": { "description": "Recipe id (required; visible in line_context)" },
+        "limit": { "description": "Return the latest N versions (default 20, max 50)" }
+      }
+    }
+  },
+  "mes_fetch": {
+    "description": "Fetch data from MES REST points (code-enforced guards: only your bound DCW points; window <=7 days; <=5000 rows; <=6 fetches per 60 seconds). Formats are auto-detected: scalar/vector (thickness profile)/image frame (CCD, persisted automatically)/table/event stream. Responses include field-level dictionaries; with include_data=true, sampled rows carry actual arrays (field names, labels, units, ranges, physical meaning; vector fields also list per-point meaning) so the Agent can reason on meaning, not bare numbers. If no dictionary exists it says so explicitly — do not guess units. Three modes: no from/to = current snapshot; from/to and max_rows<=2000 = synchronous inline; max_rows>2000 = asynchronous CSV dataset plus a same-name *.manifest.json (dictionary/units/ranges/batch attribution), returning job_id/dataset_id. Use mes_export for full raw offline analysis.",
+    "parameters": {
+      "properties": {
+        "ids": { "description": "Target point id array (ids from mes_catalog; must be your bound DCW points)" },
+        "from": { "description": "Window start ISO time (paired with to; omit both for a current snapshot)" },
+        "to": { "description": "Window end ISO time (paired with from; window <=7 days)" },
+        "max_rows": { "description": "Row cap (default 500, hard cap 5000; >2000 goes to an async dataset)" },
+        "param": { "description": "Business parameters passed through to the point data hook (e.g. {\"lane\":12,\"agg\":\"mean\"}); omit for points without a hook" },
+        "include_data": { "description": "Include actual sampled values/arrays in inline/snapshot responses (vectors show up to 64 points with labels; default false = statistics only)" }
+      }
+    }
+  },
+  "mes_catalog": {
+    "description": "Search the MES REST point catalog (DCW points with driver=mes-rest). Each entry includes id/name/line/unit/range, capability flags (read/write/history/hook), point description, and the field-level data dictionary (field names/labels/units/ranges/vector point count; from the MES response dictionaryPath or node driverConfig.dictionary, cached after the first mes_fetch). This is the addressing entry for mes_fetch/mes_export; supports keyword (q) and line_id filters. Read-only catalog, never touches the device. Visibility = your bound DCW points plus parameter points inside your bound recipes.",
+    "parameters": {
+      "properties": {
+        "q": { "description": "Keyword substring filter (point name and description)" },
+        "line_id": { "description": "Restrict to a line id" },
+        "limit": { "description": "Maximum rows (default 20, max 100)" },
+        "product_id": { "description": "Narrow to the product's line (rejected if it conflicts with line_id)" },
+        "recipe_id": { "description": "Narrow to the recipe's line (rejected if it conflicts with line_id)" }
+      }
+    }
+  },
+  "line_context": {
+    "description": "Read the full picture of the lines/products/recipes you control (read before acting): line scenario description, run state and active batch, product description, active recipe (name/version/description) with per-parameter target vs PLC value vs process window (plus parameter key and description), your bound nodes and recipes (running/not running), and known good batches; when no batch is active, the line's recipe definitions are listed. Visibility = node-granted line ∪ bound recipe line ∪ channel-bound line (read-only). Confirm ownership and state before using recipe_* tools. [Value semantics: value = platform setpoint, readValue = PLC measured feedback; they may differ briefly during hold/heartbeat windows or disconnections — state which one you cite.]",
+    "parameters": {
+      "properties": {
+        "line_id": { "description": "Restrict to a line id (must be a line of your bound nodes; default: all lines you own)" }
+      }
+    }
+  },
+  "my_industrial_nodes": {
+    "description": "List all your industrial bindings and semantic cards — one card per DCW node (PLC/MES point) and DAQ node: physical quantity/unit/range/precision, process semantics (mechanism and tuning rules), safe range and active-recipe process window, current setpoint, dispatch path (PLC driver or MES writeHook single field), per-step cap and operating rules; plus the recipe operation surface for your bound recipes (run state/binding mode manual=per-action HITL or auto/ secondary auth state/parameter table with keys and descriptions). Call this before any industrial operation. Binding prerequisites: daq/dcw bindings for nodes, recipe bindings for recipes — unbound objects never appear.",
+    "parameters": { "properties": {} }
+  },
+  "optimizer_solve": {
+    "description": "Solve one optimization problem under your binding authorization (numeric backends: SciPy/OSQP), returning a candidate MV trajectory and first-step suggestion. The channel must be bound to an optimizer profile; with multiple bindings pass binding_id explicitly. Missing optimization eligibility returns a locatable gap instead of fabricating a plan. Recommendations do not grant device write permission.",
+    "parameters": {
+      "properties": {
+        "binding_id": { "description": "Binding id (required with multiple bindings; optional when unique)" },
+        "timeout_ms": { "description": "Request-level timeout in milliseconds" }
+      }
+    }
+  },
+  "optimizer_status": {
+    "description": "Read the terminal state, candidates, and recommendation status of an optimization run (read-only). The run must belong to the current agent's binding; cross-agent queries return BINDING_NOT_OWNED.",
+    "parameters": {
+      "properties": {
+        "run_id": { "description": "Optimization run id (returned by optimizer_solve)" }
+      }
+    }
+  }
+}

package/.AgentWorkShop/prompts/host-tools.json

@@ -635,7 +635,7 @@
   {
     "name": "daq_query",
     "label": "DAQ Query",
-    "description": "从时序数据库检索你可访问的数采节点的历史/实时数据。授权两途径:绑定数采节点,或所在频道绑定产线(绑线后可只读查询该线全部数采节点)。支持按产线/产品/配方/批次/时间窗/降采样多维过滤(产品/配方过滤基于逐样本打标,可精确取某批次数据);返回结果携带物理含义(参数语义/单位/量程/统计摘要/最近序列)。默认只取**当前活动批次(活动配方)**的数据:产线正在跑什么配方就只查那个配方,不会把上一轮配方的样本混进本轮判读;需要跨配方看整段历史时显式传 scope=all。",
+    "description": "从时序数据库检索你可访问的数采节点的历史/实时数据。授权两途径:绑定数采节点,或所在频道绑定产线(绑线后可只读查询该线全部数采节点)。支持按产线/产品/配方/批次/时间窗/降采样多维过滤(产品/配方过滤基于逐样本打标,可精确取某批次数据);返回结果携带物理含义(参数语义/单位/量程/统计摘要/最近序列)。默认只取**当前活动批次(活动配方)**的数据:产线正在跑什么配方就只查那个配方,不会把上一轮配方的样本混进本轮判读;需要跨配方看整段历史时显式传 scope=all。 取数语义:结果来自时序库 daq_samples,返回窗口末尾的样本段(不是最旧段);每节点附带库内最新样本时间与滞后秒数,可用于判断 MQTT 等推送协议是否仍在收数。",
     "parameters": {
       "type": "object",
       "properties": {
@@ -681,7 +681,11 @@
         },
         "limit": {
           "type": "number",
-          "description": "返回点数上限(缺省 500)"
+          "description": "返回点数上限(缺省 500);窗口桶数超过 limit 时取**窗口末尾** limit 个桶(最新段),末元素始终是窗口内最新桶"
+        },
+        "agg": {
+          "type": "string",
+          "description": "桶聚合口径:avg(缺省,桶均值)|min|max。最新值 = 窗口末尾桶(受该口径影响);库内最新原始样本时间和滞后秒数在判读行单独给出"
         }
       },
       "additionalProperties": false

package/.output/.AgentWorkShop/aml-python/train-example.py

@@ -1,92 +1,92 @@
-# -*- coding: utf-8 -*-
-"""AML 参考训练实现(one-step 线性基线;e2e --real 模式与 Agent 的起点范本)。
-
-契约:
-  - 数据:amlkit.load_bundle(归一化 float32;x [N,H,nAll] / y [N,F,nTgt]);
-  - 模型:输入 [batch, H, nAll](展平)→ 输出 [batch, nTgt](下一拍目标,归一化);
-  - 产出:amlkit.export_torch_onnx(契约 ONNX)+ amlkit.save_metrics(自报指标,门禁另由平台评估器复算)。
-
-超参经作业 params 传入:lr / epochs / hidden / batch。
-"""
-import json
-import os
-from pathlib import Path
-
-import torch
-import torch.nn as nn
-
-import amlkit
-
-
-def main():
-    job_dir = Path(os.environ["AML_JOB_DIR"]).resolve()
-    job = json.loads((job_dir / "job.json").read_text(encoding="utf-8"))
-    params = job.get("params", {})
-
-    bundle = amlkit.load_bundle(job["datasetPath"])
-    manifest = bundle.manifest
-    h_steps = manifest["shapes"]["x"][1]
-    n_all = manifest["shapes"]["x"][2]
-    n_tgt = manifest["shapes"]["y"][2]
-
-    x_train = bundle.get("x", "train")
-    y_train = bundle.get("y", "train")[:, 0, :]  # 下一拍目标(第 0 个 horizon 步)
-    x_val = bundle.get("x", "val")
-    y_val = bundle.get("y", "val")[:, 0, :]
-
-    hidden = int(params.get("hidden", 128))
-    model = nn.Sequential(
-        nn.Flatten(),
-        nn.Linear(h_steps * n_all, hidden),
-        nn.ReLU(),
-        nn.Linear(hidden, n_tgt),
-    )
-    opt = torch.optim.Adam(model.parameters(), lr=float(params.get("lr", 1e-3)))
-    loss_fn = nn.MSELoss()
-
-    xt = torch.tensor(x_train, dtype=torch.float32)
-    yt = torch.tensor(y_train, dtype=torch.float32)
-    xv = torch.tensor(x_val, dtype=torch.float32) if x_val.shape[0] else None
-    yv = torch.tensor(y_val, dtype=torch.float32) if y_val.shape[0] else None
-
-    epochs = int(params.get("epochs", 80))
-    batch = int(params.get("batch", 256))
-    n = xt.shape[0]
-    best_val = float("inf")
-    train_loss = 0.0
-    val_loss = None
-    for epoch in range(epochs):
-        model.train()
-        perm = torch.randperm(n)
-        total = 0.0
-        for i in range(0, n, batch):
-            idx = perm[i:i + batch]
-            opt.zero_grad()
-            loss = loss_fn(model(xt[idx]), yt[idx])
-            loss.backward()
-            opt.step()
-            total += float(loss) * idx.shape[0]
-        train_loss = total / max(1, n)
-        if xv is not None:
-            model.eval()
-            with torch.no_grad():
-                val_loss = float(loss_fn(model(xv), yv))
-            best_val = min(best_val, val_loss)
-        amlkit.report_progress(5 + 90 * (epoch + 1) // epochs,
-                               "epoch %d/%d train=%.5f val=%s" % (epoch + 1, epochs, train_loss, val_loss if val_loss is not None else "n/a"))
-
-    amlkit.save_metrics({"agent": {
-        "kind": "mlp_one_step_baseline",
-        "epochs": epochs,
-        "train_loss_last": train_loss,
-        "val_loss_best": None if val_loss is None else best_val,
-        "params": params,
-    }})
-
-    amlkit.export_torch_onnx(model, manifest)
-    amlkit.report_progress(99, "exported onnx")
-    print("train-example done")
-
-
-if __name__ == "__main__":
-    main()
+# -*- coding: utf-8 -*-
+"""AML 参考训练实现(one-step 线性基线;e2e --real 模式与 Agent 的起点范本)。
+
+契约:
+  - 数据:amlkit.load_bundle(归一化 float32;x [N,H,nAll] / y [N,F,nTgt]);
+  - 模型:输入 [batch, H, nAll](展平)→ 输出 [batch, nTgt](下一拍目标,归一化);
+  - 产出:amlkit.export_torch_onnx(契约 ONNX)+ amlkit.save_metrics(自报指标,门禁另由平台评估器复算)。
+
+超参经作业 params 传入:lr / epochs / hidden / batch。
+"""
+import json
+import os
+from pathlib import Path
+
+import torch
+import torch.nn as nn
+
+import amlkit
+
+
+def main():
+    job_dir = Path(os.environ["AML_JOB_DIR"]).resolve()
+    job = json.loads((job_dir / "job.json").read_text(encoding="utf-8"))
+    params = job.get("params", {})
+
+    bundle = amlkit.load_bundle(job["datasetPath"])
+    manifest = bundle.manifest
+    h_steps = manifest["shapes"]["x"][1]
+    n_all = manifest["shapes"]["x"][2]
+    n_tgt = manifest["shapes"]["y"][2]
+
+    x_train = bundle.get("x", "train")
+    y_train = bundle.get("y", "train")[:, 0, :]  # 下一拍目标(第 0 个 horizon 步)
+    x_val = bundle.get("x", "val")
+    y_val = bundle.get("y", "val")[:, 0, :]
+
+    hidden = int(params.get("hidden", 128))
+    model = nn.Sequential(
+        nn.Flatten(),
+        nn.Linear(h_steps * n_all, hidden),
+        nn.ReLU(),
+        nn.Linear(hidden, n_tgt),
+    )
+    opt = torch.optim.Adam(model.parameters(), lr=float(params.get("lr", 1e-3)))
+    loss_fn = nn.MSELoss()
+
+    xt = torch.tensor(x_train, dtype=torch.float32)
+    yt = torch.tensor(y_train, dtype=torch.float32)
+    xv = torch.tensor(x_val, dtype=torch.float32) if x_val.shape[0] else None
+    yv = torch.tensor(y_val, dtype=torch.float32) if y_val.shape[0] else None
+
+    epochs = int(params.get("epochs", 80))
+    batch = int(params.get("batch", 256))
+    n = xt.shape[0]
+    best_val = float("inf")
+    train_loss = 0.0
+    val_loss = None
+    for epoch in range(epochs):
+        model.train()
+        perm = torch.randperm(n)
+        total = 0.0
+        for i in range(0, n, batch):
+            idx = perm[i:i + batch]
+            opt.zero_grad()
+            loss = loss_fn(model(xt[idx]), yt[idx])
+            loss.backward()
+            opt.step()
+            total += float(loss) * idx.shape[0]
+        train_loss = total / max(1, n)
+        if xv is not None:
+            model.eval()
+            with torch.no_grad():
+                val_loss = float(loss_fn(model(xv), yv))
+            best_val = min(best_val, val_loss)
+        amlkit.report_progress(5 + 90 * (epoch + 1) // epochs,
+                               "epoch %d/%d train=%.5f val=%s" % (epoch + 1, epochs, train_loss, val_loss if val_loss is not None else "n/a"))
+
+    amlkit.save_metrics({"agent": {
+        "kind": "mlp_one_step_baseline",
+        "epochs": epochs,
+        "train_loss_last": train_loss,
+        "val_loss_best": None if val_loss is None else best_val,
+        "params": params,
+    }})
+
+    amlkit.export_torch_onnx(model, manifest)
+    amlkit.report_progress(99, "exported onnx")
+    print("train-example done")
+
+
+if __name__ == "__main__":
+    main()

package/.output/.AgentWorkShop/prompts/host-tools.en.json

@@ -0,0 +1,174 @@
+{
+  "daq_query": {
+    "description": "Query historical/live data for DAQ nodes you can access. Access is granted either by direct node binding or by the channel's line binding (read-only for all DAQ nodes on that line). Filters: line/product/recipe/run/time window/downsampling (product and recipe filters use per-sample tags, so a specific batch can be selected precisely). Results carry physical meaning (semantics, unit, range, statistics, recent series). By default only the **current active batch (active recipe)** is queried; pass scope=all explicitly to compare across recipes or review full history.",
+    "parameters": {
+      "properties": {
+        "node_id": { "description": "Restrict to one DAQ node id (default: all bound nodes)" },
+        "line_id": { "description": "Filter by line (data ownership)" },
+        "product_id": { "description": "Filter by product (per-sample tags); passing it overrides the default active-batch filter" },
+        "recipe_id": { "description": "Filter by recipe (per-sample tags); passing it overrides the default filter. Default: the active recipe of the node's line (no filter if the line is not running)" },
+        "run_id": { "description": "Filter by run id (pin one run when a recipe was started multiple times); passing it overrides the default filter" },
+        "scope": { "description": "Scope: active (default) = current active batch only; all = no recipe filter, return every sample in the window (cross-recipe comparison/history review)" },
+        "last_minutes": { "description": "Last N minutes (default 30)" },
+        "from_ms": { "description": "Start epoch ms (paired with to_ms; takes precedence over last_minutes)" },
+        "to_ms": { "description": "End epoch ms" },
+        "bucket_ms": { "description": "Downsampling bucket width in ms (default {queryDefaultBucketMs}, floor {queryMinBucketMs})" },
+        "limit": { "description": "Maximum number of points returned (default 500)" }
+      }
+    }
+  },
+  "recipe_catalog": {
+    "description": "List recipe definitions on lines you can read (find recipe_id / the currently running recipe / product ownership). Each entry includes recipe id, version, product, whether it is running, parameter count, each node's target and PLC value, and last good batch. Supports line_id/product_id/keyword filters. Use this first when unsure of a recipe_id; recipe_apply/recipe_trial/recipe_update can also take line_id and resolve the active recipe. Read-only.",
+    "parameters": {
+      "properties": {
+        "line_id": { "description": "Restrict to a line id (must be readable)" },
+        "product_id": { "description": "Restrict to a product id" },
+        "q": { "description": "Keyword substring filter (recipe name/description)" },
+        "limit": { "description": "Maximum rows (default 20, max 100)" }
+      }
+    }
+  },
+  "recipe_update": {
+    "description": "Save verified best parameters into a recipe as a new version with attribution and rationale. You may target the currently running recipe by passing only line_id (resolved from the active batch), or pass recipe_id explicitly. Permission model: you must be bound to the recipe (multiple bindings allowed) and pass its secondary auth; the recipe must be running (run gate). With a manual binding or manual line, the save suspends for human approval — reason is required and must cite evidence (DAQ data/analysis); the approval card shows it. This changes the definition only; use recipe_apply to push parameters to the running line.",
+    "parameters": {
+      "properties": {
+        "recipe_id": { "description": "Recipe id (mutually exclusive with line_id; explicit id wins)" },
+        "params": {
+          "description": "Parameters to update (partial merge; list only nodes that change)",
+          "items": {
+            "properties": {
+              "node_id": { "description": "DCW node id (must be one of your bound DCW nodes)" },
+              "value": { "description": "New target value" },
+              "min": { "description": "Optional new recipe window lower bound" },
+              "max": { "description": "Optional new recipe window upper bound" }
+            }
+          }
+        },
+        "reason": { "description": "Why this change is saved (required; state the evidence)" },
+        "task_id": { "description": "Optional related task id" },
+        "line_id": { "description": "Line id (mutually exclusive with recipe_id): resolve the recipe from that line's active batch" }
+      }
+    }
+  },
+  "recipe_apply": {
+    "description": "Dispatch the recipe's currently persisted parameters to the running line as one batch (use after recipe_update). You may target the running recipe with only line_id (resolved from the active batch) or pass recipe_id explicitly. Permission model: bound recipe, secondary auth, and run gate (recipe must be executing). With a manual binding or manual line, dispatch suspends for human approval — reason is required and must explain why and on what evidence. After approval the batch goes through governance interlocks (range/step/rate) with per-parameter acknowledgements. A rejection may include guidance; revise and resubmit.",
+    "parameters": {
+      "properties": {
+        "recipe_id": { "description": "Recipe id (mutually exclusive with line_id; explicit id wins)" },
+        "reason": { "description": "Why dispatch (required): data evidence/trial conclusion/goal-gap analysis; the line expert must understand your reasoning on the approval card" },
+        "emergency": { "description": "Emergency exemption from the recipe dispatch rate limit (does NOT skip approval; the card is marked [EMERGENCY] and still needs a human; abuse is audited)" },
+        "line_id": { "description": "Line id (mutually exclusive with recipe_id): resolve the recipe from the active batch; use to dispatch to the current recipe" }
+      }
+    }
+  },
+  "recipe_trial": {
+    "description": "Dispatch a multi-parameter candidate batch without writing a recipe version. You may target the running recipe with only line_id or pass recipe_id explicitly. Permission model: bound recipe, secondary auth, and run gate; candidates may only cover parameters in the recipe. With a manual binding or manual line, the trial suspends for human approval — hypothesis is required (why this trial and on what evidence). The whole batch lands at once; after re-measurement, persist improvement with recipe_update or roll back with recipe_rollback(dispatch=true). Subject to the per-line trial interval (default >=5 minutes) and the four-layer limits.",
+    "parameters": {
+      "properties": {
+        "recipe_id": { "description": "Recipe id (mutually exclusive with line_id; explicit id wins)" },
+        "params": {
+          "description": "Candidate parameters (>=1; include every change in one batch to avoid oscillation)",
+          "items": {
+            "properties": {
+              "node_id": { "description": "DCW node id" },
+              "value": { "description": "Candidate engineering value" }
+            }
+          }
+        },
+        "hypothesis": { "description": "Trial hypothesis/rationale (required: knowledge-base entry or data analysis conclusion)" },
+        "emergency": { "description": "Emergency exemption from the recipe dispatch rate limit (does NOT skip approval; the card is marked [EMERGENCY] and still needs a human; abuse is audited)" },
+        "line_id": { "description": "Line id (mutually exclusive with recipe_id): resolve the active recipe" }
+      }
+    }
+  },
+  "recipe_rollback": {
+    "description": "Roll recipe parameters back to a stable version (a historical version or the last good batch) by creating a new non-destructive version; with dispatch=true it also restores the parameters to the line as a batch. Permission model: bound recipe, secondary auth, and run gate; manual bindings suspend for HITL — reason is required (e.g. optimization degradation/out-of-limit).",
+    "parameters": {
+      "properties": {
+        "recipe_id": { "description": "Recipe id (required)" },
+        "version": { "description": "Roll back to this historical version (either version or to_last_good)" },
+        "to_last_good": { "description": "true = restore the last good batch parameters" },
+        "reason": { "description": "Rollback reason (required)" },
+        "dispatch": { "description": "true = restore the definition AND re-dispatch parameters to the PLC (use when the optimization loop degrades); default false = definition only" },
+        "emergency": { "description": "Emergency exemption from the recipe dispatch rate limit (does NOT skip approval; still needs a human; abuse is audited)" }
+      }
+    }
+  },
+  "recipe_log": {
+    "description": "Query recipe change history (create/update/trial/apply/per-parameter ACK/approval/optimization window verdict/rollback/start-batch dispatch; newest first). Returns only scope=line records, each with line and recipe attribution. Pass recipe_id to get the whole event family across kinds (including kind=write dispatch ACKs); line.start/line.stop are included (starting a line dispatches recipe parameters). Without line_id the channel-bound line is used; recipe_id narrows to that recipe's line. Time via from/to or minutes. Use dcw_journal for per-node write history.",
+    "parameters": {
+      "properties": {
+        "line_id": { "description": "Line id (must be readable; default: channel-bound line, or all readable lines when unbound)" },
+        "recipe_id": { "description": "Filter by recipe id (implies its line)" },
+        "product_id": { "description": "Filter by product id (must belong to a readable line)" },
+        "from": { "description": "Window start (ISO or 2026-10-19T08:00)" },
+        "to": { "description": "Window end (ISO; must be after from)" },
+        "minutes": { "description": "Lookback minutes when from is omitted (default 1440 = 24h)" },
+        "limit": { "description": "Maximum rows (default 20, max 100)" }
+      }
+    }
+  },
+  "recipe_versions": {
+    "description": "View the parameter version history of a recipe (old to new): version, time, source (user/agent/system), actor name, change reason, and parameter diff. Use it to confirm a target version before rollback and to review who changed what and why. Visibility = recipe line readable (node-granted line ∪ bound recipe line ∪ channel-bound line). Rollback goes through recipe_rollback (write gate; manual bindings need HITL).",
+    "parameters": {
+      "properties": {
+        "recipe_id": { "description": "Recipe id (required; visible in line_context)" },
+        "limit": { "description": "Return the latest N versions (default 20, max 50)" }
+      }
+    }
+  },
+  "mes_fetch": {
+    "description": "Fetch data from MES REST points (code-enforced guards: only your bound DCW points; window <=7 days; <=5000 rows; <=6 fetches per 60 seconds). Formats are auto-detected: scalar/vector (thickness profile)/image frame (CCD, persisted automatically)/table/event stream. Responses include field-level dictionaries; with include_data=true, sampled rows carry actual arrays (field names, labels, units, ranges, physical meaning; vector fields also list per-point meaning) so the Agent can reason on meaning, not bare numbers. If no dictionary exists it says so explicitly — do not guess units. Three modes: no from/to = current snapshot; from/to and max_rows<=2000 = synchronous inline; max_rows>2000 = asynchronous CSV dataset plus a same-name *.manifest.json (dictionary/units/ranges/batch attribution), returning job_id/dataset_id. Use mes_export for full raw offline analysis.",
+    "parameters": {
+      "properties": {
+        "ids": { "description": "Target point id array (ids from mes_catalog; must be your bound DCW points)" },
+        "from": { "description": "Window start ISO time (paired with to; omit both for a current snapshot)" },
+        "to": { "description": "Window end ISO time (paired with from; window <=7 days)" },
+        "max_rows": { "description": "Row cap (default 500, hard cap 5000; >2000 goes to an async dataset)" },
+        "param": { "description": "Business parameters passed through to the point data hook (e.g. {\"lane\":12,\"agg\":\"mean\"}); omit for points without a hook" },
+        "include_data": { "description": "Include actual sampled values/arrays in inline/snapshot responses (vectors show up to 64 points with labels; default false = statistics only)" }
+      }
+    }
+  },
+  "mes_catalog": {
+    "description": "Search the MES REST point catalog (DCW points with driver=mes-rest). Each entry includes id/name/line/unit/range, capability flags (read/write/history/hook), point description, and the field-level data dictionary (field names/labels/units/ranges/vector point count; from the MES response dictionaryPath or node driverConfig.dictionary, cached after the first mes_fetch). This is the addressing entry for mes_fetch/mes_export; supports keyword (q) and line_id filters. Read-only catalog, never touches the device. Visibility = your bound DCW points plus parameter points inside your bound recipes.",
+    "parameters": {
+      "properties": {
+        "q": { "description": "Keyword substring filter (point name and description)" },
+        "line_id": { "description": "Restrict to a line id" },
+        "limit": { "description": "Maximum rows (default 20, max 100)" },
+        "product_id": { "description": "Narrow to the product's line (rejected if it conflicts with line_id)" },
+        "recipe_id": { "description": "Narrow to the recipe's line (rejected if it conflicts with line_id)" }
+      }
+    }
+  },
+  "line_context": {
+    "description": "Read the full picture of the lines/products/recipes you control (read before acting): line scenario description, run state and active batch, product description, active recipe (name/version/description) with per-parameter target vs PLC value vs process window (plus parameter key and description), your bound nodes and recipes (running/not running), and known good batches; when no batch is active, the line's recipe definitions are listed. Visibility = node-granted line ∪ bound recipe line ∪ channel-bound line (read-only). Confirm ownership and state before using recipe_* tools. [Value semantics: value = platform setpoint, readValue = PLC measured feedback; they may differ briefly during hold/heartbeat windows or disconnections — state which one you cite.]",
+    "parameters": {
+      "properties": {
+        "line_id": { "description": "Restrict to a line id (must be a line of your bound nodes; default: all lines you own)" }
+      }
+    }
+  },
+  "my_industrial_nodes": {
+    "description": "List all your industrial bindings and semantic cards — one card per DCW node (PLC/MES point) and DAQ node: physical quantity/unit/range/precision, process semantics (mechanism and tuning rules), safe range and active-recipe process window, current setpoint, dispatch path (PLC driver or MES writeHook single field), per-step cap and operating rules; plus the recipe operation surface for your bound recipes (run state/binding mode manual=per-action HITL or auto/ secondary auth state/parameter table with keys and descriptions). Call this before any industrial operation. Binding prerequisites: daq/dcw bindings for nodes, recipe bindings for recipes — unbound objects never appear.",
+    "parameters": { "properties": {} }
+  },
+  "optimizer_solve": {
+    "description": "Solve one optimization problem under your binding authorization (numeric backends: SciPy/OSQP), returning a candidate MV trajectory and first-step suggestion. The channel must be bound to an optimizer profile; with multiple bindings pass binding_id explicitly. Missing optimization eligibility returns a locatable gap instead of fabricating a plan. Recommendations do not grant device write permission.",
+    "parameters": {
+      "properties": {
+        "binding_id": { "description": "Binding id (required with multiple bindings; optional when unique)" },
+        "timeout_ms": { "description": "Request-level timeout in milliseconds" }
+      }
+    }
+  },
+  "optimizer_status": {
+    "description": "Read the terminal state, candidates, and recommendation status of an optimization run (read-only). The run must belong to the current agent's binding; cross-agent queries return BINDING_NOT_OWNED.",
+    "parameters": {
+      "properties": {
+        "run_id": { "description": "Optimization run id (returned by optimizer_solve)" }
+      }
+    }
+  }
+}

package/.output/.AgentWorkShop/prompts/host-tools.json

@@ -635,7 +635,7 @@
   {
     "name": "daq_query",
     "label": "DAQ Query",
-    "description": "从时序数据库检索你可访问的数采节点的历史/实时数据。授权两途径:绑定数采节点,或所在频道绑定产线(绑线后可只读查询该线全部数采节点)。支持按产线/产品/配方/批次/时间窗/降采样多维过滤(产品/配方过滤基于逐样本打标,可精确取某批次数据);返回结果携带物理含义(参数语义/单位/量程/统计摘要/最近序列)。默认只取**当前活动批次(活动配方)**的数据:产线正在跑什么配方就只查那个配方,不会把上一轮配方的样本混进本轮判读;需要跨配方看整段历史时显式传 scope=all。",
+    "description": "从时序数据库检索你可访问的数采节点的历史/实时数据。授权两途径:绑定数采节点,或所在频道绑定产线(绑线后可只读查询该线全部数采节点)。支持按产线/产品/配方/批次/时间窗/降采样多维过滤(产品/配方过滤基于逐样本打标,可精确取某批次数据);返回结果携带物理含义(参数语义/单位/量程/统计摘要/最近序列)。默认只取**当前活动批次(活动配方)**的数据:产线正在跑什么配方就只查那个配方,不会把上一轮配方的样本混进本轮判读;需要跨配方看整段历史时显式传 scope=all。 取数语义:结果来自时序库 daq_samples,返回窗口末尾的样本段(不是最旧段);每节点附带库内最新样本时间与滞后秒数,可用于判断 MQTT 等推送协议是否仍在收数。",
     "parameters": {
       "type": "object",
       "properties": {
@@ -681,7 +681,11 @@
         },
         "limit": {
           "type": "number",
-          "description": "返回点数上限(缺省 500)"
+          "description": "返回点数上限(缺省 500);窗口桶数超过 limit 时取**窗口末尾** limit 个桶(最新段),末元素始终是窗口内最新桶"
+        },
+        "agg": {
+          "type": "string",
+          "description": "桶聚合口径:avg(缺省,桶均值)|min|max。最新值 = 窗口末尾桶(受该口径影响);库内最新原始样本时间和滞后秒数在判读行单独给出"
         }
       },
       "additionalProperties": false

package/.output/.AgentWorkShop/schema.json

@@ -54,6 +54,8 @@
     { "key": "daq.query.minDisplayIntervalMs", "type": "number", "group": "daq", "label": "趋势图刷新下限(ms)", "labelKey": "settings.runtime.daq.queryMinDisplayIntervalMs", "description": "前端允许配置的最小趋势图刷新间隔(传入更小值时钳到该下限,防止高频查询时序库)", "applies": "live", "default": 500, "min": 100, "max": 600000, "aliases": ["DAQ_QUERY_MIN_DISPLAY_INTERVAL_MS"] },
     { "key": "daq.tsRetentionH", "type": "number", "group": "daq", "label": "标量时序保留(h)", "labelKey": "settings.runtime.daq.tsRetentionH", "description": "标量样本保留小时数(两后端一致:代码内 drop_chunks 每 30min 执行;chunk 按天+列存压缩,TSL license)", "applies": "restart", "default": 168, "min": 1, "max": 8760, "aliases": ["DAQ_TS_RETENTION_H"] },
     { "key": "daq.frameRetentionH", "type": "number", "group": "daq", "label": "帧元数据保留(h)", "labelKey": "settings.runtime.daq.frameRetentionH", "description": "daq_frames 帧元数据保留小时数(行随 drop_chunks 出清;像素对象由 GC 按天前缀清理,同用本保留期)", "applies": "restart", "default": 720, "min": 1, "max": 8760, "aliases": ["DAQ_FRAME_RETENTION_H"] },
+    { "key": "daq.export.pagesPerNode", "type": "number", "group": "daq", "label": "导出单节点分页上限", "labelKey": "settings.runtime.daq.export.pagesPerNode", "description": "daq_export/EDA 导出单节点最大页数(每页 5000 点,缺省 400=200 万点;硬上限 2000)", "applies": "live", "default": 400, "min": 1, "max": 2000 },
+    { "key": "daq.export.windowMaxH", "type": "number", "group": "daq", "label": "导出时间窗上限(h)", "labelKey": "settings.runtime.daq.export.windowMaxH", "description": "单次 DAQ 导出的最大时间窗小时数(缺省 168=7 天;硬上限 8760)", "applies": "live", "default": 168, "min": 1, "max": 8760 },
     { "key": "daq.alarmWebhookUrl", "type": "string", "group": "daq", "label": "告警 Webhook", "labelKey": "settings.runtime.daq.alarmWebhookUrl", "description": "告警升级推送的 Webhook 地址(空=不推送)", "applies": "restart", "default": "", "aliases": ["ALARM_WEBHOOK_URL"] },
     { "key": "daq.alarmEscalateMinutes", "type": "number", "group": "daq", "label": "告警升级时限(min)", "labelKey": "settings.runtime.daq.alarmEscalateMinutes", "description": "未确认告警升级通知的时延(分钟)", "applies": "restart", "default": 15, "min": 1, "max": 1440, "aliases": ["ALARM_ESCALATE_MINUTES"] },