@hmos-library-adapter/fast 0.0.17-beta.0 → 0.0.17-beta.2

package/node_modules/@ohos-agent/pc-adapter/skills/pc-schemas/references/schemas/03-adapt.schema.json

@@ -0,0 +1,327 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "PC library/application adaptation & validation report",
+  "type": "object",
+  "required": ["package_name", "ecosystem", "build_system", "strategy", "status", "build_status", "meta"],
+  "properties": {
+    "examples": {"type": "array", "description": "Node/Electron 示例结果，独立于主名册计数；未完成须明确列出阻塞。", "items": {"type": "object", "required": ["project_dir", "host_runtime", "status"], "properties": {"project_dir": {"type": "string"}, "result_file": {"type": "string", "description": "Node.js 库本工程的 node-demo-results 工具结果，相对工作区路径"}, "host_runtime": {"enum": ["device-node", "electron-oh"]}, "status": {"enum": ["not-run", "built", "passed", "failed", "blocked"]}, "runtime_version": {"type": "string"}, "evidence": {"type": "array", "items": {"type": "string"}}, "notes": {"type": "string"}}, "allOf": [{"if": {"properties": {"status": {"const": "passed"}}}, "then": {"required": ["evidence"], "properties": {"evidence": {"minItems": 1}}}}]}},
+    "package_name": { "type": "string" },
+    "host_runtime": { "type": "string",
+      "description": "本轮实际按哪个宿主的装载契约构建（缺省回落 manifest，再回落生态默认）。验收规则 load-contract-consistent 拿它选契约，但**判据只信产物本体**（.dynsym 的 UND 集 / DT_NEEDED / PT_INTERP）——声明与产物矛盾时两个方向都会被点名（`ohpt-agent check -w <ws> --stage 3` 可随时自查）。取值 `hap-dlopen`（缺省）/ `device-node` / `electron-oh`" },
+    "ecosystem": { "type": "string",
+      "enum": ["python", "java", "nodejs", "cpp", "rust", "go", "dotnet", "other"] },
+    "build_system": { "type": "string" },
+    "strategy": { "type": "string" },
+    "status": { "type": "string",
+      "enum": ["built-and-verified", "built-pending-verification", "partial", "failed", "skipped"],
+      "description": "built-and-verified=产物+真机验证通过；built-pending-verification=产物+runbook 齐备待设备验证（≠failed）；partial=真有未解决阻塞；failed=编不出；skipped=scan 判 infeasible 跳过" },
+    "build_status": { "type": "string", "enum": ["pass", "fail", "partial", "skipped"] },
+    "delivery_form": { "type": "string",
+      "enum": ["pure-runtime", "native-extension", "cpp-lib", "cli", "app", "app-unsupported"],
+      "description": "交付形态（与 01-scan.json 的 harmony_adaptation.delivery_form 一致）" },
+    "artifacts": { "type": "array", "items": { "type": "string" }, "description": "产物工作区顶层相对路径（patches/、build/、dist/lib|app/、harmony-demo|app/ 等）" },
+    "deps_built": {
+      "type": "array",
+      "description": "本次编译的依赖记录（写 registry-staging.json 供同轮复用）",
+      "items": {
+        "type": "object",
+        "required": ["name"],
+        "properties": {
+          "name": { "type": "string" },
+          "version": { "type": "string" },
+          "native_class": { "type": "string", "enum": ["pure-runtime", "native-extension", "native-lib", "toolchain-bound"] },
+          "status": { "type": "string", "enum": ["reuse", "recipe-build", "fresh-adapt"] },
+          "reuse_source": { "type": "string", "enum": ["local-registry", "central-registry"],
+            "description": "status=reuse 时的实际来源：local-registry=个人库产物拷回；central-registry=中心制品仓拉取。同轮已编/自编省略" },
+          "artifact_url": { "type": ["string", "null"],
+            "description": "从中心制品仓拉取时的制品 URL；其他来源省略" },
+          "workspace_path": { "type": "string", "description": "deps/<dep>-<ver> 相对路径" },
+          "build_status": { "type": "string", "enum": ["pass", "fail", "skipped"] }
+        }
+      }
+    },
+    "build_commands": { "type": "array", "items": { "type": "string" } },
+    "patches_applied": { "type": "array", "items": { "type": "string" } },
+    "issues_resolved": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "properties": {
+          "error_id": { "type": "string" },
+          "description": { "type": "string" },
+          "fix_applied": { "type": "string" }
+        }
+      }
+    },
+    "runtime_assets": {
+      "type": "array",
+      "description": "依赖运行时数据资产声明（delivery 必做项 E1 符号审计 / E2 路径缺失探针产出）。判定方法与数据族-环境变量映射见 pc-capability-domains runtime-data-assets；症状见 pc-error-atlas E130",
+      "items": {
+        "type": "object",
+        "required": ["family", "declared_path"],
+        "properties": {
+          "family": { "type": "string", "description": "数据族（terminfo/locale/CA 信任库/插件数据…）" },
+          "declared_path": { "type": "string", "description": "运行时读取的系统路径（设备上缺失的那条）" },
+          "source": { "type": "string", "enum": ["source-literal", "dependency-metadata"],
+            "description": "声明来源：source-literal=源码闭包路径字面量；dependency-metadata=依赖包元数据" },
+          "packaged_path": { "type": ["string", "null"],
+            "description": "随包后的 HNP/HAP 内路径（如 pkg/share/terminfo）；未随包为 null（此时须有 remaining_blockers 或探针降级说明）" }
+        }
+      }
+    },
+    "test_run": {
+      "type": "object",
+      "description": "在鸿蒙 PC 设备侧跑原库用例的自验证结果",
+      "properties": {
+        "executed": { "type": "boolean" },
+        "test_command": { "type": "string" },
+        "test_source": { "type": "string", "enum": ["reused", "generated", "mixed", "none"],
+          "description": "用例来源（与 02-baseline.json 同名字段同一套取值）：reused=原库自带用例；generated=原库无用例，本阶段在 tests-generated/ 补写的冒烟用例；mixed=两者兼有；none=没跑用例（此时写不出 built-and-verified）" },
+        "total_cases": { "type": "integer" },
+        "passed": { "type": "integer" },
+        "failed": { "type": "integer" },
+        "skipped": { "type": "integer" },
+        "pass_rate": { "type": "number", "minimum": 0, "maximum": 1 },
+        "regressions": { "type": "array", "items": { "type": "string" },
+          "description": "在鸿蒙设备侧未通过的用例（自验证未过项）——非空即不能定稿 built-and-verified。语义：failures[] 中 resolution=open 条目的名字派生名册，与注册表零漂移（acceptance 的 failure-registry-accounting 核对）" },
+        "failures": {
+          "type": "array",
+          "description": "FAIL/CRASH 注册表（审计轨迹）：设备用例失败或进程崩溃时逐条登记，归因分诊后按解决路径闭环。成功标准恒为零 FAIL/零 CRASH——复测转 PASS 的条目从本表与 regressions 中消失（怎么修的记入本轮 notes/issues_resolved，修复落点曾在此留 fix_ref）。判定程序见 semantics/enum-semantics.md",
+          "items": {
+            "type": "object",
+            "required": ["name", "result", "attribution", "resolution"],
+            "properties": {
+              "name": { "type": "string", "description": "用例标识（与设备日志逐条对齐，与 regressions 名字一致）" },
+              "result": { "type": "string", "enum": ["fail", "crash"],
+                "description": "crash=进程级异常终止（SIGSYS/SIGSEGV 等），用例结果不可判" },
+              "attribution": { "type": "string",
+                "enum": ["product-defect", "platform-divergence", "testenv-limited", "harness-bug", "testcase-defect", "unknown"],
+                "description": "FAIL/CRASH 的根因归属（六值分类学）。判定程序见 semantics/enum-semantics.md。unknown 不得作为终态挂在 built-* 状态下。testcase-defect=用例本身写错了，**仅对 02-baseline 名册里 validation=unvalidated 的补写用例开放**——上游用例在原平台是对的、宿主自证过的用例断言也成立，判它们「写错」需要指向上游 issue" },
+              "evidence": { "type": "string",
+                "description": "归因证据：musl 源码行/双方文档差异点/崩溃信号+定位/seccomp 拦截记录。attribution≠unknown 时必填" },
+              "resolution": { "type": "string",
+                "enum": ["open", "fixed-product", "fixed-test", "fixed-harness"],
+                "description": "open=未解决（必在 regressions 里）；fixed-product=patch/重链/编译配置修复；fixed-test=测试预期或测试方法修复（**须填 amendment**）；fixed-harness=测试壳/采集链修复" },
+              "fix_ref": { "type": "string",
+                "description": "修复落点引用（patches/xxx、build/xxx、测试文件路径），resolution≠open 时必填。**须真在盘**——验收规则 test-fix-evidenced 逐条核对存在性" },
+              "amendment": {
+                "type": "object",
+                "description": "**改动评判标准的留痕**（resolution=fixed-test 时必填）。改测试是合法且高频的处置（libbsd 实证：72 个 FAIL 里语义分歧与测试前置限制占六成），但它同时是「掩盖产物缺陷最顺手的后门」——所以这个动作必须比改产物留下更多痕迹：改了什么、依据什么，逐条摆出来供 pc-03-dev-verify 与人工复核。边界见 enum-semantics：**平台特定字面量可改，API 契约级断言（返回码语义/错误码枚举）保持**",
+                "required": ["class", "basis", "before", "after"],
+                "properties": {
+                  "class": { "type": "string",
+                    "enum": ["platform-literal", "test-method", "testcase-defect"],
+                    "description": "platform-literal=断言的平台特定字面量按 musl 事实重写（须有分歧表/musl 源码背书）；test-method=测试方法改等价构造（沙箱内路径/常量构造输入/产物自身当 fixture）；testcase-defect=用例本身写错（仅限 validation=unvalidated 的补写用例）" },
+                  "basis": { "type": "string",
+                    "description": "改动依据：musl 源码行（如 musl src/errno/strerror.c:42）/ 语义分歧表条目 / 上游 issue 链接 / 沙箱前置不可满足的说明。**空泛表述会被验收点名**——「平台差异」不是依据，指得回去的来源才是" },
+                  "before": { "type": "string", "description": "改前的断言/测试方法（原文摘录）" },
+                  "after": { "type": "string", "description": "改后的断言/测试方法（原文摘录）" }
+                }
+              }
+            },
+            "allOf": [
+              { "if": { "properties": { "attribution": { "not": { "const": "unknown" } } }, "required": ["attribution"] },
+                "then": { "required": ["evidence"] } },
+              { "if": { "properties": { "resolution": { "enum": ["fixed-product", "fixed-test", "fixed-harness"] } }, "required": ["resolution"] },
+                "then": { "required": ["fix_ref"] } },
+              {
+                "description": "**堵直通车**：产物真有缺陷就修产物，不许改测试把它抹掉。此前 product-defect + fixed-test 是 schema 合法且零告警的组合——「借改测试放水真缺陷」的最短路径。",
+                "if": { "properties": { "attribution": { "const": "product-defect" } }, "required": ["attribution"] },
+                "then": { "properties": { "resolution": { "not": { "const": "fixed-test" } } } }
+              },
+              {
+                "description": "改评判标准必须留痕：fixed-test 要交代改了什么、依据什么。",
+                "if": { "properties": { "resolution": { "const": "fixed-test" } }, "required": ["resolution"] },
+                "then": { "required": ["amendment"] }
+              },
+              {
+                "description": "归因与处置自洽：判了 testcase-defect（用例写错）就该修用例，走 fixed-test。",
+                "if": { "properties": { "attribution": { "const": "testcase-defect" }, "resolution": { "not": { "const": "open" } } }, "required": ["attribution", "resolution"] },
+                "then": { "properties": { "resolution": { "const": "fixed-test" } } }
+              }
+            ]
+          }
+        },
+        "completed": { "type": "boolean",
+          "description": "测试套件是否跑到完成标记（如 SUMMARY 行/测试框架正常退出）。false=输出中途终止（崩溃/截断），此前计数不可作全量证据。executed=true 时必填；built-and-verified 要求 true" },
+        "roster": {
+          "type": "object",
+          "description": "对**阶段 2 必跑名册**的逐条交代。分母不在本阶段——它是 02-baseline.json 的 cases[] 中 platform_exclusive!==true 的条数，本阶段只负责说清每条的下落。验收规则 roster-accounting 现算对账，别手写数字。",
+          "required": ["source_total", "ran", "missing"],
+          "properties": {
+            "source_total": { "type": "integer", "minimum": 0,
+              "description": "02-baseline.json 的必跑名册条数（取自阶段 2，不自报）" },
+            "ran": { "type": "integer", "minimum": 0,
+              "description": "本轮在设备上真跑到的名册用例数" },
+            "missing": { "type": "array", "items": { "type": "string" },
+              "description": "既没跑、也没进 exemptions[] 的名册用例——**非空即写不出 built-and-verified**。漏掉的用例既不算过也不算不过，那正是「跑了 3 条全过」看起来像全量通过的老毛病" }
+          }
+        },
+        "exemptions": {
+          "type": "array",
+          "description": "本阶段新发现的豁免（阶段 2 已标 platform_exclusive 的不必在此重复）。豁免一条用例等于把它移出分母，所以必须取证——「平台独有」是掩盖没跑完最顺手的借口，由验收规则 exemption-evidenced 执法。",
+          "items": {
+            "type": "object",
+            "required": ["name", "reason", "evidence"],
+            "properties": {
+              "name": { "type": "string", "description": "名册里的用例名，须与 02-baseline.json 的 cases[].name 对得上" },
+              "reason": { "type": "string",
+                "enum": ["platform-exclusive-api", "platform-exclusive-fixture", "upstream-known-broken"],
+                "description": "platform-exclusive-api=用例验的是原平台独有 API；platform-exclusive-fixture=依赖原平台专有的测试夹具/设备；upstream-known-broken=上游自己已知坏且有 issue 记录" },
+              "evidence": { "type": "string",
+                "description": "可复核的证据：source/ 下的 file:line（如 tests/win32.c:88 #ifdef _WIN32）、CI 配置的平台矩阵排除项，或上游 issue 链接。写不出证据的说明它其实该跑" }
+            }
+          }
+        },
+        "notes": { "type": "string" },
+        "carriers": {
+          "type": "array",
+          "description": "各**验证载体**的执行结果。同一个库被 HAP 进程 dlopen 调用，与被链进 ELF 在 app 域子进程里跑，是两条加载路径——库形态两者都要跑过。哪些载体必需由验收按「交付形态 × 能力域」算（app 与上屏库只需 hap，cli 只需 cli，其余库形态两者都要）",
+          "items": {
+            "type": "object",
+            "required": ["carrier", "executed"],
+            "properties": {
+              "carrier": { "type": "string", "enum": ["hap", "cli"],
+                "description": "hap=HAP 进程内调用（napi 壳/上屏）；cli=私有 HNP 执行器在 app 域 fork+execv" },
+              "executed": { "type": "boolean", "description": "该载体是否真在设备上跑过" },
+              "evidence": { "type": "array", "items": { "type": "string" },
+                "description": "该载体的设备侧证据文件（原始输出/TAP/截图），须真在盘且非空" },
+              "notes": { "type": "string" }
+            }
+          }
+        },
+        "device": {
+          "type": "object",
+          "description": "真机验证的设备指纹，便于复现与判断证据强度。隐私红线：只记设备类别+OS版本，绝不记序列号",
+          "properties": {
+            "os_version": { "type": "string", "description": "设备 OS 版本。照抄 00-env.json 的 capabilities.device_fingerprint.os_version（`param get const.ohos.fullname`）" },
+            "device_class": { "type": "string", "description": "设备型号（不是权限档——鸿蒙 PC 只有商用机一种）。**照抄 00-env.json 的 capabilities.device_fingerprint.device_class**，那是 `param get const.product.model` 探出来的；不自填、不写序列号" },
+            "arch": { "type": "string", "description": "如 aarch64" },
+            "page_size": { "type": "integer", "description": "设备页大小字节，如 4096（决定是否需 max-page-size=0x1000）" }
+          }
+        }
+      }
+    },
+    "runtime_provisioning": {
+      "type": "object",
+      "description": "设备侧生态运行时（java/node/python）的自带供给记录。鸿蒙 PC 上运行时一律随交付物自带；程序见 pc-knowledge-base 的 platform/鸿蒙PC-设备语言运行时探测与供给.md；值语义见 enum-semantics.md",
+      "required": ["ecosystem", "device_status"],
+      "properties": {
+        "ecosystem": { "type": "string", "enum": ["java", "node", "python", "other"] },
+        "device_status": { "type": "string",
+          "enum": ["bundled", "missing", "not_required"],
+          "description": "bundled=本轮随交付物自带（打进私有 HNP、随执行器 HAP 装机）；missing=需要但本轮未能自带（此时 status 应为 built-pending-verification 而非 partial）；not_required=本库不需要设备侧运行时。**鸿蒙 PC 上没有「设备预装可直接用」这一档**——app 域只能用自带的" },
+        "method": { "type": "string", "description": "自带方式（如：宿主交叉编译产物打进私有 HNP / 从中心制品仓拉预编译运行时后打包）" },
+        "evidence": { "type": "array", "items": { "type": "string" },
+          "description": "自带证据：打包命令+产物路径，以及设备上真跑起来的输出摘要" },
+        "notes": { "type": "string" }
+      }
+    },
+    "target_path_covered": { "type": "string", "enum": ["covered", "partial", "uncovered", "n/a"],
+      "description": "设备侧通过用例集对鸿蒙侧目标代码路径的覆盖度（阶段 4 的唯一来源）。covered 要求 test_run.executed=true" },
+    "remaining_blockers": { "type": "array", "items": { "type": "string" } },
+    "notes": { "type": "string" },
+    "meta": {
+      "type": "object",
+      "required": ["schema_version"],
+      "properties": {
+        "schema_version": { "type": "string" }
+      }
+    }
+  },
+  "allOf": [
+    {
+      "description": "反假成功：built-and-verified 必须有产物、真机验证已执行、且**阶段 2 的必跑名册逐条有下落、全部通过**，否则应降级为 built-pending-verification / partial。分母不由本阶段提供——`roster.missing` 非空即写不出本状态。`source_total=0`（本轮没有分母）**只在阶段 2 确实不在拓扑里时成立**，由验收规则 roster-accounting 跨文件复核，schema 本身看不见拓扑、不作此判。joal 案曾把 5 条回归的产物定稿为本状态，流水线据此提前终态、修复环一轮未转",
+      "if": {
+        "required": ["status"],
+        "properties": { "status": { "const": "built-and-verified" } }
+      },
+      "then": {
+        "required": ["artifacts", "test_run"],
+        "properties": {
+          "artifacts": { "minItems": 1 },
+          "test_run": {
+            "required": ["executed", "regressions", "total_cases", "passed", "test_source", "completed", "roster"],
+            "properties": {
+              "executed": { "const": true },
+              "completed": { "const": true },
+              "regressions": { "maxItems": 0 },
+              "total_cases": { "minimum": 1 },
+              "passed": { "minimum": 1 },
+              "test_source": { "not": { "const": "none" } },
+              "roster": { "required": ["missing"], "properties": { "missing": { "maxItems": 0 } } },
+              "carriers": { "minItems": 1,
+                "description": "填了就至少一条（**不进 required**：哪些载体必需取决于形态×能力域，schema 看不到 manifest；缺载体由 gate 的有界修复环与验收 dual-carrier-evidence 执法，避免用钝的形状规则误伤只需单载体的形态）" }
+            }
+          }
+        }
+      }
+    },
+    {
+      "description": "套件完整性：设备回归真跑过（executed=true）就必须交代测试套件是否跑到完成标记——输出中途终止（崩溃/日志截断）时，此前的计数不是全量证据。libbsd 第 1 轮实测：日志断在 fparseln，靠人眼才发现套件没跑完",
+      "if": {
+        "required": ["test_run"],
+        "properties": {
+          "test_run": {
+            "required": ["executed"],
+            "properties": { "executed": { "const": true } }
+          }
+        }
+      },
+      "then": {
+        "properties": {
+          "test_run": { "required": ["completed"] }
+        }
+      }
+    },
+    {
+      "description": "built-pending-verification 至少要有产物（本机编出、待设备验证）",
+      "if": {
+        "required": ["status"],
+        "properties": { "status": { "const": "built-pending-verification" } }
+      },
+      "then": {
+        "required": ["artifacts"],
+        "properties": { "artifacts": { "minItems": 1 } }
+      }
+    },
+    {
+      "description": "反 gaming：宣称设备侧覆盖 covered，必须真的执行过设备回归",
+      "if": {
+        "required": ["target_path_covered"],
+        "properties": { "target_path_covered": { "const": "covered" } }
+      },
+      "then": {
+        "required": ["test_run"],
+        "properties": {
+          "test_run": {
+            "required": ["executed"],
+            "properties": { "executed": { "const": true } }
+          }
+        }
+      }
+    },
+    {
+      "description": "供给可追溯：device_status=bundled 必须记录自带方式与证据",
+      "if": {
+        "required": ["runtime_provisioning"],
+        "properties": {
+          "runtime_provisioning": {
+            "required": ["device_status"],
+            "properties": { "device_status": { "const": "bundled" } }
+          }
+        }
+      },
+      "then": {
+        "properties": {
+          "runtime_provisioning": {
+            "required": ["ecosystem", "device_status", "method", "evidence"],
+            "properties": {
+              "evidence": { "minItems": 1 }
+            }
+          }
+        }
+      }
+    }
+  ]
+}

package/node_modules/@ohos-agent/pc-adapter/skills/pc-schemas/references/schemas/04-summary.schema.json

@@ -0,0 +1,99 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "PC library/application adaptation summary & sediment",
+  "type": "object",
+  "required": ["package_name", "ecosystem", "build_system", "adaptation_status", "build_status", "meta"],
+  "properties": {
+    "package_name": { "type": "string" },
+    "ecosystem": { "type": "string",
+      "enum": ["python", "java", "nodejs", "cpp", "rust", "go", "dotnet", "other"] },
+    "build_system": { "type": "string" },
+    "adaptation_status": { "type": "string",
+      "enum": ["success", "partial", "failed", "infeasible", "blocked"],
+      "description": "success=设备侧用例零未过且目标路径已验证；partial=待验证/有未通过用例/覆盖不足；failed=编不出；infeasible=scan 判定核心不可移植；blocked=前置阶段被门禁拦下、适配未实际进行（≠ infeasible：库可能完全可适配）" },
+    "build_status": { "type": "string",
+      "enum": ["pass", "fail", "partial", "skipped"] },
+    "feasibility": { "type": "string",
+      "enum": ["feasible", "feasible_with_effort", "hard", "infeasible"] },
+    "baseline": {
+      "type": "object",
+      "description": "阶段 3 照**阶段 2 的必跑名册**跑下来的汇总。⚠️ 字段名叫 baseline，语义却是**阶段 3 的执行结果**——阶段 2 产出的是名册本身（02-baseline.json），这里汇总的是「照名册跑得怎么样」",
+      "properties": {
+        "roster_total": { "type": "integer", "minimum": 0,
+          "description": "必跑名册条数，取 03-adapt.json 的 test_run.roster.source_total" },
+        "roster_missing": { "type": "integer", "minimum": 0,
+          "description": "名册里既没跑也没豁免的条数，取 03-adapt.json 的 test_run.roster.missing 长度。**adaptation_status=success 要求为 0**——「把库转出来并通过测试用例」这个目标在出口状态上的落点" },
+        "origin_pass_rate": { "type": "number", "minimum": 0, "maximum": 1,
+          "description": "宿主预跑通过率（阶段 2 的 cases[].host_result 现算）。仅供归因参照、不参与判定；宿主未跑则留空" },
+        "ohos_pass_rate": { "type": "number", "minimum": 0, "maximum": 1,
+          "description": "鸿蒙设备侧通过率，取 03-adapt.json 的 test_run.pass_rate" },
+        "regression_count": { "type": "integer",
+          "description": "设备侧未通过的用例条数，取 03-adapt.json 的 test_run.regressions 长度" }
+      }
+    },
+    "artifacts": { "type": "array", "items": { "type": "string" } },
+    "patches_applied": { "type": "array", "items": { "type": "string" } },
+    "issues_resolved_count": { "type": "integer" },
+    "remaining_todos": { "type": "array", "items": { "type": "string" } },
+    "solution_overview": { "type": "string",
+      "description": "整体解决方案概述：路径、关键改动、复用资产" },
+    "reusable_assets": {
+      "type": "array",
+      "description": "可复用资产（补丁、构建脚本、工具链配置）",
+      "items": {
+        "type": "object",
+        "properties": {
+          "kind": { "type": "string", "enum": ["patch", "build_script", "toolchain", "doc", "other"] },
+          "path": { "type": "string" },
+          "description": { "type": "string" }
+        }
+      }
+    },
+    "sediment_suggestions": {
+      "type": "array",
+      "description": "经验沉淀候选条目，按 platform / adaptation 两类视角",
+      "items": {
+        "type": "object",
+        "required": ["category", "title"],
+        "properties": {
+          "category": { "type": "string", "enum": ["platform", "adaptation"] },
+          "kind": { "type": "string", "enum": ["memory", "capability-domain"], "default": "memory",
+            "description": "候选的落地形态：memory=经验条目（默认，落个人知识库 memory/）；capability-domain=**新能力域方案**，promote 时落 capability-domains/<domain>.md 成为下一轮可引的域文件。01-scan 里 solution_source=field-judgment 的域必须在此产出对应候选——否则「方案库待建」永远待建（joal 案：sediment 精准写了「audio 域待建」，却没有任何路径让它变成域文件）" },
+          "domain": { "type": "string", "description": "kind=capability-domain 时的能力域名，须与 01-scan 的 capability_dependencies[].domain 对齐" },
+          "title": { "type": "string" },
+          "summary": { "type": "string" },
+          "trigger": { "type": "string", "description": "下次遇到什么场景适用" },
+          "relates_to": { "type": "string",
+            "description": "已核对既有知识（错误图谱/内置文档）后声明的增量参照，如 \"E083\" 或文档名——带此字段的候选不会被查重标记、promote 不拦；纯重复的认知应直接不沉淀" }
+        }
+      }
+    },
+    "notes": { "type": "string" },
+    "meta": {
+      "type": "object",
+      "required": ["schema_version"],
+      "properties": {
+        "schema_version": { "type": "string" }
+      }
+    }
+  },
+  "allOf": [
+    {
+      "description": "反假成功：adaptation_status=success 必须**必跑名册逐条交代完**、设备侧用例零未过、且有产物证据，否则只能是 partial。名册零未跑是「转换的目标＝把库转出来并通过测试用例」的可判定表达——只看 regression_count 会让「只跑了 3 条、其余没跑」看起来和全量通过一样",
+      "if": {
+        "required": ["adaptation_status"],
+        "properties": { "adaptation_status": { "const": "success" } }
+      },
+      "then": {
+        "required": ["baseline", "artifacts"],
+        "properties": {
+          "artifacts": { "minItems": 1 },
+          "baseline": {
+            "required": ["regression_count", "roster_missing"],
+            "properties": { "regression_count": { "const": 0 }, "roster_missing": { "const": 0 } }
+          }
+        }
+      }
+    }
+  ]
+}