@fx-data/ai-diagnostics 0.1.20261026070913 → 0.1.20261107142011

package/content/knowledge/update/diagnostic/scenes/schedu.json

@@ -1,56 +0,0 @@
-{
-  "scene_id": "SCHEDU",
-  "type": 3,
-  "default_merge_mode": "ALLOW_MERGE",
-  "status": "confirmed",
-  "producers": [
-    {
-      "producer_id": "producer-schedu-abstractschedulejob-prepare",
-      "business_trigger": "A configured data-source schedule creates a schedule-marked synchronization job.",
-      "entry_kind": "job",
-      "protocol_identity": "A configured data-source schedule creates a schedule-marked synchronization job.",
-      "repository_boundary": "main-server -> external synchronization transport -> main-server",
-      "update_intent_summary": "Initialize a scheduled synchronization request. Callback handling selects table-level bundle or legacy synchronization-task gates before dispatch; the bundle scanner may release eligible successful tables earlier. Do not require all bundle work to finish for every SCHEDU update.",
-      "recipe_refs": [
-        "scene-origin-job"
-      ],
-      "evidence_level": "source-confirmed"
-    },
-    {
-      "producer_id": "producer-schedu-hidatasourceserviceimpl-triggerupdate",
-      "business_trigger": "A DM completion callback reports only scheduled results and starts scheduled synchronization.",
-      "entry_kind": "async-message-or-callback",
-      "protocol_identity": "A DM completion callback reports only scheduled results and starts scheduled synchronization.",
-      "repository_boundary": "main-server -> external synchronization transport -> main-server",
-      "update_intent_summary": "Legacy DM TASK_STATUS completion selects this scene only when the bundle does not support table-level synchronization; supported table-level bundles skip that path. STREAM_STATUS completion/incompletion instead reaches triggerUpdateOnce, which checks deduplication, completion and source capacity before selecting a handler.",
-      "recipe_refs": [
-        "scene-origin-async-message-or-callback"
-      ],
-      "evidence_level": "source-confirmed"
-    },
-    {
-      "producer_id": "producer-schedu-dm-table-status",
-      "business_trigger": "A DM table-level STREAM_STATUS completion or incompletion is received.",
-      "entry_kind": "http",
-      "protocol_identity": "A DM table-level STREAM_STATUS completion or incompletion is received.",
-      "repository_boundary": "main-server",
-      "update_intent_summary": "handleDmTableStatusChange uses bundle capability and status to call triggerUpdateOnce; only completed, non-duplicate work can dispatch through the selected handler. Incomplete work marks the group failed. The scheduled flag selects SCHEDU or MANUAL_UPDATE.",
-      "recipe_refs": [
-        "scene-origin-http"
-      ],
-      "evidence_level": "source-confirmed"
-    },
-    {
-      "producer_id": "producer-schedu-bundle-group-scan",
-      "business_trigger": "A source synchronization group has successful records eligible for incremental release.",
-      "entry_kind": "job",
-      "protocol_identity": "A source synchronization group has successful records eligible for incremental release.",
-      "repository_boundary": "main-server",
-      "update_intent_summary": "Collect eligible successful, non-ignored tables and children, group by update scene, merge stores/tables across bundles, and dispatch. Remove included group records only after submission succeeds; keep them for retry on submission failure. Scanner release and callback completion are different paths, so a callback count is not an update count.",
-      "recipe_refs": [
-        "scene-origin-job"
-      ],
-      "evidence_level": "source-confirmed"
-    }
-  ]
-}

package/content/knowledge/update/diagnostic/scenes/table-move-other-workspace.json

@@ -1,20 +0,0 @@
-{
-  "scene_id": "TABLE_MOVE_OTHER_WORKSPACE",
-  "type": 39,
-  "default_merge_mode": "FORBIDDEN_MERGE",
-  "status": "confirmed",
-  "producers": [
-    {
-      "producer_id": "producer-table-move-other-workspace-projecteventlistener-projectmoveevent",
-      "business_trigger": "A project move crosses workspace boundaries and affects dependent tables.",
-      "entry_kind": "internal-event",
-      "protocol_identity": "A project move crosses workspace boundaries and affects dependent tables.",
-      "repository_boundary": "main-server",
-      "update_intent_summary": "Publish and consume the move event, then refresh affected dependent tables.",
-      "recipe_refs": [
-        "scene-origin-internal-event"
-      ],
-      "evidence_level": "protocol-confirmed"
-    }
-  ]
-}

package/content/knowledge/update/diagnostic/scenes/user-holder-to-normal.json

@@ -1,20 +0,0 @@
-{
-  "scene_id": "USER_HOLDER_TO_NORMAL",
-  "type": 38,
-  "default_merge_mode": "FORBIDDEN_MERGE",
-  "status": "confirmed",
-  "producers": [
-    {
-      "producer_id": "producer-user-holder-to-normal-hitableupdateserviceimpl-updateuserentercorp",
-      "business_trigger": "A holder account becomes a normal corporate user.",
-      "entry_kind": "direct-service-call",
-      "protocol_identity": "A holder account becomes a normal corporate user.",
-      "repository_boundary": "main-server",
-      "update_intent_summary": "Recompute user-derived corporate fields after account normalization.",
-      "recipe_refs": [
-        "scene-origin-direct-service-call"
-      ],
-      "evidence_level": "source-confirmed"
-    }
-  ]
-}

package/content/knowledge/update/observability.md

@@ -1,16 +0,0 @@
-# 更新可观测知识入口
-
-本文件只保留 Trace 路由兼容入口，不维护独立事实副本。精确 span、attribute、结构化字段、日志 signature、产生条件、field-presence preflight 和 correlation semantics 统一位于 [`knowledge/update/diagnostic`](diagnostic/) 的 observability 索引与分片中。
-
-本文件只帮助确认 trace 是否具有更新入口、`dispatch_*`/`update` span、dagId、updateId 等更新场景线索，不在场景识别阶段调用 analyzer。识别完成后按用户目标继续：性能问题返回 `$diagnose-performance`，由 `$diagnose-update-performance` 调用 `$analyze-analysis-table-update-runtime`；只有更新来源、DAG、计数或已有运行材料解释等有界事实问题，才由根 Agent 直接调用 analyzer。
-
-analyzer 校验 Bundle 与 application 后返回命中的 evidence projection。调用方不得从这里硬编码物理 lookup，也不得用时间、tenant、表名或相似数量补齐异步关联。
-
-`source-confirmed` 不等于 `runtime-verified`。没有匹配版本、必要字段和显式关联边时，保持 needs-revalidation 或 unknown。
-只有 `tableId`，或者只有共享 Query 或 engine span，不能区分前台查询和后台更新。
-
-## SigNoZ 查询线索
-
-用户以企业更新或 dagId 开始时，无需先提供 trace 或发生时间：按目标进入上面的更新专项或有界事实 analyzer，再读取其企业／DAG 发现指引。企业无时间默认最近 24 小时，dagId 的检索窗口由助手按公共规则管理；已有范围与结果直接复用。企业发现不强加只有 `update` span 才可能承载企业信息的假设，异常在关联的更新执行上核对。
-
-遵循[公共查询收敛规则](../common/signoz-query-policy.md)。资源驱动查询沿用公共规则确定的环境和问题发生时间，在业务 server 的 `service.name` 下组合更新入口、`dispatch_*`/`update` span 与 tableId、dagId、updateId 等锚点。进入 engine 后沿本次 trace 和 taskId 查询 worker 证据；MetricOuts 使用 engine 服务、精确 taskName、logger 和执行时间窗，不能复用业务 server 的服务过滤。

package/content/knowledge/update/runtime-evidence.md

@@ -1,32 +0,0 @@
-# 更新运行证据的使用方法
-
-解释更新来源、request、chain/DAG、node attempt、requeue、load、listener、engine task 和计数时，按本文件选择证据并核对关联，本次事实以运行记录为准。慢、超时、OOM 等问题由性能入口协调更新场景。
-
-## 选当前需要的知识
-
-按输入选择一个起点，不先构建查询计划或填写应用 JSON：
-
-| 已有输入 | 优先读取 | 取证目标 |
-|---|---|---|
-| 已确认操作来源 | [场景索引](diagnostic/scene-index.json)中对应场景及其 producer/recipe | 明确触发记录及 accepted request/entry |
-| 表与发生时间 | [recipe 索引](diagnostic/recipe-index.json)的 table-history | 区分本对象的更新运行与尝试 |
-| 表和 chain | table-in-chain | 说明当前表在本链的节点与执行 |
-| dagId/chain | dag-chain | 沿本链显式关系恢复节点与尝试 |
-| 已选执行的性能片段 | performance-window 中当前阶段 | 测量请求、等待、执行与 load，关联 engine 时逐边核对 |
-
-[观测索引](diagnostic/observability-index.json)说明物理字段、必需关联键、计数单位和缺失信号；按所选 recipe 的引用只读取当前步骤的分片。索引中的 `path` 是项目知识位置，按链接读取，不预加载全部分片。
-
-已有 trace 时直接按精确 trace/必要 span 和服务补当前字段；只有对象/链时先用已确认时间和公共默认范围寻找有限候选。时间规则、企业更新、DAG 回退与查询预算见[公共规则](../common/signoz-query-policy.md)。查询意图、字段和范围明确后，由助手按当前 MCP 工具声明执行。
-
-## 适用范围
-
-[发布描述](diagnostic/manifest.json)记录知识来源、构建、部署范围、运行版本、字段契约、失效条件和解释边界。知识说明可能产生的记录及允许解释的含义，不能证明本次行为发生。
-
-- 已有材料能核对操作、环境、服务、版本及字段语义时，只使用匹配部分。已知版本与发布范围矛盾，或字段/日志含义漂移时标为 needs_revalidation，不沿用该部分含义。
-- 来源、构建或运行版本未知时保留 unknown，不要求使用者查找内部提交号，也不伪造值以通过校验。可继续整理原记录直接显示的时间、标识、状态和错误；依赖版本的恢复行为、成功含义及业务关联继续保留限制。
-- manifest 与分片记录的是知识来源和适用范围，不证明运行版本、采集、异步关联或历史物理提交已经验证。引用的分片缺失或内容互相矛盾时，按知识缺口处理并保留未知。
-- 指定 recipe 只限定知识参考范围，不证明其中每条分支都已发生，也不要求执行其全部查询。只补当前问题所缺的一项证据。
-
-## 关联、计数与返回
-
-逐边核对显式关联，遇到第一条必要边缺失即停止；同租户、同表名、时间邻近只能作为候选线索。request、chain、node、attempt、load、engine task 分别计数。身份术语、关联边、计数口径、判断方法和停止规则见 analyzer 的[证据摘要边界](../../.agents/skills/analyze-analysis-table-update-runtime/references/update-diagnostic-contract.md)。

package/content/scripts/receive_tool_result.py

@@ -1,57 +0,0 @@
-#!/usr/bin/env python3
-"""Receive one JSON tool response without echoing its contents."""
-from __future__ import annotations
-
-import argparse
-import json
-import os
-from pathlib import Path
-import sys
-import tempfile
-
-
-def main() -> int:
-    parser = argparse.ArgumentParser(
-        description=__doc__,
-        epilog=(
-            "Run with python3 -u scripts/receive_tool_result.py in a terminal session. "
-            "After READY, send the original response as one JSON line followed by a newline; "
-            "stdout returns only the saved file path and size."
-        ),
-    )
-    parser.parse_args()
-    settings = None
-    if sys.stdin.isatty():
-        if os.name == "nt":
-            print('{"status":"unsupported_input","error":"On Windows use a pipe or save the tool response directly to a file"}')
-            return 2
-        import termios
-        settings = termios.tcgetattr(sys.stdin.fileno())
-        quiet = list(settings)
-        quiet[3] &= ~(termios.ECHO | termios.ICANON)
-        termios.tcsetattr(sys.stdin.fileno(), termios.TCSANOW, quiet)
-    try:
-        print("READY", flush=True)
-        line = sys.stdin.buffer.readline()
-        if not line.endswith(b"\n"):
-            print('{"status":"incomplete","error":"send one JSON line followed by newline"}')
-            return 2
-        try:
-            value = json.loads(line)
-        except (ValueError, UnicodeError):
-            print('{"status":"invalid","error":"input must be a complete JSON response"}')
-            return 2
-        directory = Path(tempfile.mkdtemp(prefix="fx-tool-response-"))
-        output = directory / "response.json"
-        fd = os.open(output, os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o600)
-        with os.fdopen(fd, "w", encoding="utf-8") as stream:
-            json.dump(value, stream, ensure_ascii=False)
-        print(json.dumps({"status": "saved", "path": str(output), "bytes": output.stat().st_size}), flush=True)
-        return 0
-    finally:
-        if settings is not None:
-            termios.tcsetattr(sys.stdin.fileno(), termios.TCSANOW, settings)
-
-
-if __name__ == "__main__":
-    raise SystemExit(main())