@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/02-baseline.schema.json

@@ -0,0 +1,850 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "Harmony must-run test roster",
+  "type": "object",
+  "required": [
+    "package_name",
+    "ecosystem",
+    "test_source",
+    "baseline_status",
+    "meta"
+  ],
+  "properties": {
+    "package_name": {
+      "type": "string"
+    },
+    "ecosystem": {
+      "type": "string"
+    },
+    "host_platform": {
+      "type": "string",
+      "description": "宿主平台标识，如 linux-x86_64 / windows-x86_64 / macos-arm64。仅用于解释 host_result 的参照系；本阶段**不要求**在宿主上跑通。"
+    },
+    "test_framework": {
+      "type": "string",
+      "description": "pytest / gtest / ctest / cargo test / go test / junit / xts 等"
+    },
+    "test_source": {
+      "type": "string",
+      "enum": [
+        "reused",
+        "generated",
+        "mixed",
+        "none"
+      ],
+      "description": "名册用例的来源：reused=全部取自原库自带用例；generated=原库无可用用例，全部为本阶段补写；mixed=两者兼有（常态：原库用例 + 覆盖缺口补齐）；none=建不起名册（此时 baseline_status 只能是 blocked）。source/ 下明明有测试却填 generated，由验收规则 upstream-suite-preferred 点名——**唯一例外是 baseline_mode=app-smoke**（app 形态冒烟名册，豁免须有 01-scan 的 app/Electron/Qt 路由佐证）。"
+    },
+    "discovery": {
+      "type": "object",
+      "description": "上游测试套件的发现结果——名册的原材料。先读 CI 配置（.github/workflows/*.yml、tox.ini、noxfile.py、Makefile）拿官方命令与排除集，再逐目录扫。",
+      "properties": {
+        "existing_test_dirs": {
+          "type": "array",
+          "items": {
+            "type": "string"
+          }
+        },
+        "existing_case_count": {
+          "type": "integer"
+        },
+        "run_command_detected": {
+          "type": "string"
+        },
+        "ci_config_refs": {
+          "type": "array",
+          "items": {
+            "type": "string"
+          },
+          "description": "官方测试命令的出处，如 .github/workflows/ci.yml:42"
+        }
+      }
+    },
+    "api_surface": {
+      "type": "object",
+      "description": "**覆盖度锚点之一：公共导出面**。provenance 不是自选项——机器算得出的生态（今天是 C/C++ 的头文件声明）一律以机器算的那份为准，声明只能补充不能缩减（由验收规则 baseline-roster-anchored 执法）。",
+      "required": [
+        "provenance",
+        "symbols"
+      ],
+      "properties": {
+        "provenance": {
+          "type": "string",
+          "enum": [
+            "machine-symbol",
+            "declared",
+            "unavailable"
+          ],
+          "description": "machine-symbol=机器从头文件/导出表算出（C/C++）；declared=本阶段声明，须给 source_refs 供抽查；unavailable=取不到公共导出面的概念（此时 baseline_status 上限 partial）"
+        },
+        "symbols": {
+          "type": "array",
+          "items": {
+            "type": "string"
+          },
+          "description": "公共导出面的符号名。**下界是 01-scan.json 的 prd.features[].covered_apis.source[] 并集**——那是阶段 1 已逐功能点列过的原库符号，语言无关，少于它即为漏枚举。"
+        },
+        "source_refs": {
+          "type": "array",
+          "items": {
+            "type": "string"
+          },
+          "description": "符号面出处（导出清单文件或 file:line），provenance=declared 时必填。验收会抽查：路径真在盘、且符号名在该文件里字面出现。"
+        },
+        "uncovered": {
+          "type": "array",
+          "items": {
+            "type": "string"
+          },
+          "description": "symbols 中没有任何名册用例覆盖到的符号（symbols − ⋃ cases[].api_refs）。非空即写不出 planned。别手写——验收规则现算对账。"
+        },
+        "notes": {
+          "type": "string"
+        }
+      }
+    },
+    "feature_coverage": {
+      "type": "object",
+      "description": "**覆盖度锚点之二：PRD 功能点**（01-scan.json 的 prd.features[]）。与 api_surface 互为补充：符号面查「接口有没有被测到」，功能点查「用户可感知能力有没有被测到」。形状与 05-testcases.schema.json 的 coverage 一致。",
+      "required": [
+        "features_total",
+        "covered",
+        "uncovered"
+      ],
+      "properties": {
+        "features_total": {
+          "type": "integer",
+          "minimum": 0
+        },
+        "covered": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "被名册用例覆盖的功能点数（去重 cases[].prd_refs 条数）"
+        },
+        "uncovered": {
+          "type": "array",
+          "items": {
+            "type": "string"
+          },
+          "description": "没有任何名册用例覆盖的 prd feature id。非空即写不出 planned。同样别手写。"
+        }
+      }
+    },
+    "host_run": {
+      "type": "object",
+      "description": "宿主预跑的**整体**状态。它存在的意义是给「自证」提供前提：`cases[].host_result=not-run` 本身语义歧义——既可能是「整个库在宿主上跑不了」，也可能是「这条没被选集覆盖」。补写用例要不要自证、能不能自证，先看这里。**只需跑补写的那批用例，不必跑全量上游套件**。",
+      "required": [
+        "status"
+      ],
+      "properties": {
+        "status": {
+          "type": "string",
+          "enum": [
+            "not-required",
+            "ran",
+            "unavailable"
+          ],
+          "description": "**先看 cases[] 里有没有 source=generated**：没有 → 恒填 not-required（全是上游用例、有上游 CI 背书，宿主跑不跑都不改变名册；别花时间去证明宿主编不动）。有补写用例时：ran=宿主上真跑了（至少覆盖了补写用例那批）；unavailable=宿主编不了/跑不了这个库（交叉编译目标、缺平台专有依赖），补写用例无从自证"
+        },
+        "reason": {
+          "type": "string",
+          "description": "status=unavailable 时必填：宿主为什么跑不了（如「库依赖 Linux 专有的 sys/epoll.h，macOS 宿主编不出」）。not-required 不必填——「没有补写用例」本身就是理由"
+        },
+        "command": {
+          "type": "string",
+          "description": "宿主预跑用的命令（可与 run_command 不同——只跑补写用例即可）"
+        },
+        "stopped_by": {
+          "type": "string",
+          "enum": [
+            "exit",
+            "silence-timeout",
+            "run-timeout",
+            "spawn-failed"
+          ],
+          "description": "这次宿主运行**是怎么停下来的**。exit=跑到自然结束（用例过没过看 cases[].host_result）；silence-timeout / run-timeout=被守卫拦下，即挂起；spawn-failed=命令没起来。由 `ohpt-agent host-run -w <workspace>` 产出——**裸跑填不出这个字段**，这正是 status=ran 时它必填的原因：没有截止的运行一旦挂起就会烧到工具兜底超时（SISL 实测两次各 20 分钟、合计占掉该阶段 55% 墙钟），而且拿回的是空输出，无从知道挂在哪条用例"
+        },
+        "hung_after": {
+          "type": "string",
+          "description": "被守卫拦下时：输出里**最后一条被认出的用例名**——挂住的是它之后那条。stopped_by=exit 时不填"
+        }
+      }
+    },
+    "baseline_mode": {
+      "type": "string",
+      "enum": [
+        "full",
+        "app-smoke"
+      ],
+      "description": "名册模式。缺省 = full（完整名册：上游套件发现 + 符号面枚举 + 覆盖补齐 + 宿主预跑——库形态的默认）。app-smoke = **app 形态（Electron/Qt 配方路由）的默认冒烟名册**：只锚定应用级启动冒烟（安装/拉起/首帧非白屏/不崩溃，**固定 4 条**——核心功能验证不进名册，UI 交互用例机器无从执行，由配方 Phase 5「待人工复核」节 + 04-summary remaining_todos 承接），不枚举符号面（api_surface.provenance 填 unavailable）、不收上游套件、不做宿主预跑（host_run.status 填 unavailable + reason）。此模式下 baseline_status=partial 是**模式语义**（覆盖缺口 = 未纳入的 PRD 功能点，如实列 feature_coverage.uncovered），不是缺陷。验收规则按 01-scan 的 delivery_form=app + host_runtime=electron-oh（或 qt-toolchain 域）佐证豁免——库冒充 app 填 app-smoke 会被打回完整判据。用户明示「全量验证」时走 full。"
+    },
+    "baseline_status": {
+      "type": "string",
+      "enum": [
+        "planned",
+        "partial",
+        "blocked"
+      ],
+      "description": "**必跑名册建成了吗**（不是「原平台跑分」——本阶段不要求在宿主上跑通）。planned=名册成立且双锚覆盖无缺口；partial=名册成立但有覆盖缺口（缺口如实列进 api_surface.uncovered / feature_coverage.uncovered）；blocked=建不起名册（源码读不到、scan 判 infeasible、或库本身无可测面）。判定条件见 semantics/enum-semantics.md。",
+      "$comment": "阶段 3 的门禁读这个字段。planned/partial 放行——阶段 3 只对名册里已固定的那份负责。"
+    },
+    "cases": {
+      "type": "array",
+      "description": "**必跑名册**。名册 = 本数组中 platform_exclusive !== true 的条目——它是派生视图，不另立数组（另立立刻产生两表漂移，正是 failure-registry-accounting 在治的病）。阶段 3 必须对名册逐条交代：跑过、或带证据豁免。",
+      "items": {
+        "type": "object",
+        "required": [
+          "name",
+          "source"
+        ],
+        "properties": {
+          "node_library": {
+            "type": "object",
+            "required": [
+              "hosts"
+            ],
+            "properties": {
+              "hosts": {
+                "type": "array",
+                "minItems": 1,
+                "uniqueItems": true,
+                "items": {
+                  "enum": [
+                    "device-node",
+                    "electron-oh"
+                  ]
+                }
+              },
+              "reason": {
+                "type": "string"
+              },
+              "evidence": {
+                "type": "array",
+                "items": {
+                  "type": "string"
+                }
+              },
+              "process": {
+                "enum": [
+                  "main",
+                  "preload",
+                  "renderer",
+                  "multi-process"
+                ]
+              }
+            }
+          },
+          "name": {
+            "type": "string",
+            "description": "用例标识，须与 run_command 输出里的名字一字不差——阶段 3 靠它逐条对账"
+          },
+          "source": {
+            "type": "string",
+            "enum": [
+              "upstream",
+              "generated"
+            ],
+            "description": "upstream=原库自带；generated=本阶段为补齐覆盖缺口补写（落 tests-generated/）"
+          },
+          "platform_exclusive": {
+            "type": "boolean",
+            "description": "true=平台独有用例（只在原平台成立，鸿蒙上本就不该要求它过）——**不进必跑名册**。必须给 exclusive_evidence。"
+          },
+          "exclusive_evidence": {
+            "type": "string",
+            "description": "平台独有的证据，指回 source/ 下的 file:line（如 tests/win32.c:88 #ifdef _WIN32）或 CI 配置的平台矩阵排除项。platform_exclusive=true 时必填——豁免不带证据就是放水通道。"
+          },
+          "api_refs": {
+            "type": "array",
+            "items": {
+              "type": "string"
+            },
+            "description": "本用例覆盖的公共导出面符号（api_surface.symbols 的子集）。覆盖度的分子。"
+          },
+          "covered_apis_source": {
+            "type": "array",
+            "items": {
+              "type": "string"
+            },
+            "description": "本用例承接的原库符号（缺口对账键）。仅 generated 条目必填；上游用例豁免。gap-case 时须 ⊆ gap-ledger 的 gap_apis（roster-l0-gap-ledger 据此查静默缺口与 gap-case 漂移）；roster-assertion-symbol-floor 用它当断言下限分母（空则回落 api_refs）。与 api_refs 的分工：api_refs 是覆盖度分子（⊆ api_surface.symbols），本字段是缺口账的对账键。"
+          },
+          "prd_refs": {
+            "type": "array",
+            "items": {
+              "type": "string"
+            },
+            "description": "本用例覆盖的 PRD 功能点 id（形如 F-01-02）。覆盖度的另一个分子。"
+          },
+          "host_result": {
+            "type": "string",
+            "enum": [
+              "pass",
+              "fail",
+              "skip",
+              "not-run"
+            ],
+            "description": "宿主预跑结果。对**原库用例**它只是归因参照（宿主跑不过很正常：平台独有、上游本来就坏），不影响 baseline_status；对**补写用例**它是自证通道——`host_run.status=ran` 时补写用例必须 pass（见顶层 allOf）。"
+          },
+          "validation": {
+            "type": "string",
+            "enum": [
+              "upstream-backed",
+              "self-validated",
+              "unvalidated"
+            ],
+            "description": "**用例的可信度来源**，决定阶段 3 在它失败时允许做什么：upstream-backed=原库自带（上游 CI 背书）；self-validated=补写且宿主真跑过并通过；unvalidated=补写但宿主跑不了/没跑到。**只有 unvalidated 一档允许阶段 3 判 `testcase-defect`（用例本身写错）**——另两档的断言都有背书，判它们写错要指向上游 issue 或 musl 事实差异。三档都要求最终在鸿蒙上通过，分档只决定「允许改什么」。由 source+host_result+host_run.status 推导，**别手写**：验收规则 baseline-selfvalidation 现算对账"
+          },
+          "host_evidence": {
+            "type": "string",
+            "description": "host_result=fail 时的报错首行 + file:line，供阶段 3 归因参照"
+          },
+          "executability": {
+            "type": "object",
+            "description": "本用例在鸿蒙 app 域的可执行性预判（正向三层模型：语言薄提取器需求提取 → 域能力矩阵匹配信号 → 纯函数判定三值）。上游用例必填（platform_exclusive 判不死的再走本分诊）；generated 用例豁免（宿主自证是另一层把关，见 host_run.status）。判据只引用 knowledge 双矩阵（app域测试前置条件矩阵 / POSIX-NDK能力探针矩阵 / app域执行二进制与JIT限制），本字段只承载结论。verdict=blocked 的用例剔出名册，其 prd_refs 覆盖的功能点自动重算 uncovered（由规则 roster-blocked-upstream-coverage 执法强制第二载体或 gaps 留账）。套件级先行：harness 前置多是套件级（discovery.suite_executability[] 一次判整族），用例级默认继承、只记特例。",
+            "required": [
+              "verdict"
+            ],
+            "properties": {
+              "verdict": {
+                "type": "string",
+                "enum": [
+                  "runnable",
+                  "degraded",
+                  "blocked"
+                ],
+                "description": "runnable=静态审查未发现阻塞（不承诺运行时行为，SELinux 竞态/HMDFS 语义仍归阶段3 testenv-limited）；degraded=矩阵部分行不可满足但有等价构造法（收编+blockers 留账）；blocked=矩阵确认不可满足且无等价构造法（剔除，功能点覆盖重算）。扫出而矩阵查不到的需求记 unknown——不许放行，判定后回填矩阵行。"
+              },
+              "blockers": {
+                "type": "array",
+                "items": {
+                  "type": "string"
+                },
+                "description": "可执行性阻塞点（root/sudo、特权端口、/dev 专有节点、沙箱系统调用受限如 shm_open/mmap MAP_FIXED、harness 联网拉依赖、专有测试框架、GAS 汇编）"
+              },
+              "evidence": {
+                "type": "array",
+                "items": {
+                  "type": "string"
+                },
+                "description": "判据出处：知识库文档行（如 pc-knowledge-base/platform/鸿蒙PC-app域执行二进制与JIT限制.md 关卡②）或 01-scan.json capability_dependencies 字段"
+              }
+            }
+          },
+          "blocked_by": {
+            "type": "array",
+            "items": {
+              "type": "string"
+            },
+            "description": "本用例设计期的功能点前置依赖（prd feature id 清单）。组合/依赖链用例用它登记『前置功能点挂了 → 本用例 blocked-by』的归因——阶段 3 按此直接归因 blocked，不重诊断。载体前置失败（起屏幕/GL 上下文/装 HAP）也可登记，归因『载体前置失败』。由生成侧设计期推导登记，不是 03 侧事后补写。粒度三问判出『序列』形态的用例把自身各步登进本字段。"
+          },
+          "oracle_plan": {
+            "type": "array",
+            "description": "断言级 provenance 结构化落点（断言写作五步法的物理承载，逐断言可溯源）。**一条目一 [cp:N] 锚点**（ref 与代码锚点一一对应，双向对账按键去重）。生成用例逐条必有；上游用例豁免（CI 背书即 provenance）。对账红线 roster-assertion-symbol-floor：len(distinct symbol ∪ 声明支持性) ≥ len(covered_apis_source)——防「17 API 5 断言」。",
+            "items": {
+              "type": "object",
+              "required": [
+                "ref",
+                "symbol",
+                "source",
+                "grade",
+                "ref_note"
+              ],
+              "properties": {
+                "ref": {
+                  "type": "string",
+                  "description": "断言锚点引用，形如 cp:2",
+                  "pattern": "^cp:\\d+$"
+                },
+                "symbol": {
+                  "type": "string",
+                  "description": "该断言面向的符号（一句一判——禁一句多判，合并判定暴露静态半边从未真测）"
+                },
+                "source": {
+                  "type": "string",
+                  "enum": [
+                    "S1",
+                    "S2",
+                    "S3",
+                    "S4",
+                    "S5"
+                  ],
+                  "description": "预期值来源：S1=PRD checkpoint+evidence / S2=属性（平台无关真值，须核对关系失效前提）/ S3=平台实测契约（E1 分歧表 | E2 官方声明 | 探针校准回填）/ S4=宿主实测（须过闸A/闸B）/ S5=行为级。合法 source-grade 组合见 pc-roster-generation 五源表。L0 禁 S5。"
+                },
+                "grade": {
+                  "type": "string",
+                  "enum": [
+                    "E1",
+                    "E2",
+                    "E3",
+                    "host",
+                    "n-a"
+                  ],
+                  "description": "证据等级：E1=设备实测 / E2=官方声明 / E3=上游 musl 源码（永不定案）/ host=宿主实测 / n-a=属性或行为级。合法组合：S1→n-a、S2→n-a、S3→E1|E2、S4→host、S5→n-a。"
+                },
+                "plane": {
+                  "type": "string",
+                  "enum": [
+                    "state",
+                    "log",
+                    "artifact",
+                    "screen",
+                    "audio",
+                    "environment"
+                  ],
+                  "description": "验证取证观测层（可选，缺省=state 语义）：本断言跑完后的比对从哪个观测层取证。与 grade 正交——grade 管预期值从哪来（输入端），plane 管验证时从哪层取证（验证端）。取值：state=库内/宿主可观测状态（返回值/结构体/退出码，结果行即可）；log=设备侧行为序列（PTY 流/hilog 结果行）；artifact=用例写出的文件/图像（须真在盘非空）；screen=屏幕/终端呈现（terminal: buffer-assert JSON 含本 case+ref 结论；gui: demo-verify 渲染记录；通用截图不算）；audio=真实出声（audio-verify.json）；environment=运行前提在位（探针结果行出自 device 通道文件）。层地板：声明了非 state 层的断言，其专属层证据必须在场——库态断言/日志行永不充当非 state 层的地板（readline 实证）。方法学见 pc-roster-generation。"
+                },
+                "ref_note": {
+                  "type": "string",
+                  "description": "留痕：S1 带 `出处: prd F-xx-xx + file:line`，且钉精确值须带四澄清结论 `澄清: 类型=…单位=…结构=…失败形态=…`（roster-assertion-four-clarify 执法）；S2 带 `属性: <关系>（前提: …）`——往返/守恒/幂等/单调/等价表示各失效模式见 pc-roster-generation（roster-assertion-four-clarify 执法）；S3 带 `分歧表族N + musl 版本锚 + 版本核对: V_dev=… ✓`（E2/E1 引用必须过版本锚核对子步骤）；S4 带 `宿主实测 <命令> → <值>` 与闸A/闸B 证据；S5 带 `行为级`（UB 禁用此档；L0 禁用此档）。"
+                }
+              }
+            }
+          },
+          "tolerance": {
+            "type": "object",
+            "description": "容差带元数据（浮点/DSP 观测物跨架构舍入差异（NEON 等）时钉死容差，逐观测物）。",
+            "required": [
+              "metric",
+              "eps"
+            ],
+            "properties": {
+              "metric": {
+                "type": "string",
+                "enum": [
+                  "absolute",
+                  "relative"
+                ]
+              },
+              "eps": {
+                "type": "number",
+                "minimum": 0
+              }
+            }
+          },
+          "observable_via": {
+            "type": "array",
+            "description": "两档覆盖判据的**弱档声明**（可选）：符号不在强档（名字面在断言/checkpoint 里）、但效果真实流入某条判定行（setter 经 getter 回读验证、init 失败使后续断言无法满足）。仅 L1/L2 开放；L0 恒强档（L0 符号的覆盖证据只认强档）。弱档占比 >30% 告警。",
+            "items": {
+              "type": "object",
+              "required": [
+                "symbol",
+                "via_symbol",
+                "verdict_ref"
+              ],
+              "properties": {
+                "symbol": {
+                  "type": "string",
+                  "description": "被声明可观察的符号（必须 ∈ 本用例 api_refs）"
+                },
+                "via_symbol": {
+                  "type": "string",
+                  "description": "观察途径符号（必须 ∈ api_surface 公共符号——反幻觉锚）"
+                },
+                "verdict_ref": {
+                  "type": "string",
+                  "description": "失败传播路径：本用例真实存在的判定行/锚点（形如 [cp:2]）。『symbol 失效，该判定行会红』——人审语义检查，写不出传播路径的声明不构成覆盖"
+                }
+              }
+            }
+          },
+          "notes": {
+            "type": "string"
+          }
+        },
+        "allOf": [
+          {
+            "if": {
+              "properties": {
+                "platform_exclusive": {
+                  "const": true
+                }
+              },
+              "required": [
+                "platform_exclusive"
+              ]
+            },
+            "then": {
+              "required": [
+                "exclusive_evidence"
+              ]
+            }
+          }
+        ]
+      }
+    },
+    "run_command": {
+      "type": "string",
+      "description": "名册的可复现运行命令——阶段 3 一字不差地做设备路径改写后复跑，所以必须带上游 CI 的用例选集。**宿主侧用 `ohpt-agent host-run` 跑它**：防挂由运行器的两级预算承担（构建段不受静默约束、用例段受），挂起时给出 stopped_by 与 hung_after"
+    },
+    "setup_commands": {
+      "type": "array",
+      "items": {
+        "type": "string"
+      },
+      "description": "准备依赖/环境的命令（宿主预跑用；阶段 3 改写成设备侧）"
+    },
+    "coverage_notes": {
+      "type": "string",
+      "description": "覆盖缺口的说明：哪些符号/功能点没覆盖到、为什么、补不补"
+    },
+    "tests_generated_hashes": {
+      "type": "object",
+      "description": "tests-generated/ 全文件的 sha256 指纹（key=相对路径，value=sha256 hex）。**指纹链存档 1**：阶段 2 名册定稿时由 agent 落（脚本级计算），verify 每轮验收与 verdict.state_fingerprint 组成指纹链——静默改断言不申报 = 实锤判 false（verify-testcode-fingerprint 执法）。纯 upstream 名册可省略（无补写用例无指纹义务）。",
+      "additionalProperties": {
+        "type": "string",
+        "pattern": "^[a-f0-9]{64}$"
+      }
+    },
+    "gap_ledger_ref": {
+      "type": "string",
+      "description": "L0 缺口账文件引用（.ohos-adaptation-pc/gap-ledger.json）。字段契约与判据见 pc-roster-generation §缺口账 + pc-workspace-layout 产物表；roster-l0-gap-ledger 执法对账。名册含 L0 功能点时必填。"
+    },
+    "device_budget": {
+      "type": "object",
+      "description": "G3 设备预算（软上限 20 min/库，对齐 withDeviceLease 的持锁硬上限 LEASE_MAX_HOLD_MS=20min）。验收 = `estimated_min ≤ cap_min` 机判；超限 = 可机判事件，触发三层降级阶梯（第二用例群采样 → 后缀深度下移 → 上报），每层降级记入 degraded[]。名册含 generated 用例 → 必填（D3 条件 allOf）；纯 upstream 名册 optional（上游 CI 背书即 provenance）。",
+      "required": [
+        "cap_min",
+        "estimated_min",
+        "degraded"
+      ],
+      "properties": {
+        "cap_min": {
+          "type": "number",
+          "minimum": 1,
+          "description": "软上限，默认 20（=LEASE_MAX_HOLD_MS 持锁硬上限），模板可配"
+        },
+        "estimated_min": {
+          "type": "number",
+          "minimum": 0,
+          "description": "估时模型现算：载体系数表 × 用例数 + 注入 wait_ms + 双跑 ×2 + 分组启动摊销"
+        },
+        "degraded": {
+          "type": "array",
+          "items": {
+            "type": "string"
+          },
+          "description": "超限降级事件清单（三层降级阶梯留账）。降级与超限双向绑定：超限必附非空 degraded[]；未超限而 degraded[] 非空 = 无依据降级，点名。条目自说明（降了哪群/哪层、依据哪条阶梯）。"
+        }
+      }
+    },
+    "baseline_dir": {
+      "type": "string",
+      "description": "补写用例与预跑日志的落盘目录，工作区顶层 tests-generated/"
+    },
+    "evidence": {
+      "type": "array",
+      "items": {
+        "type": "string"
+      }
+    },
+    "notes": {
+      "type": "string"
+    },
+    "meta": {
+      "type": "object",
+      "required": [
+        "schema_version"
+      ],
+      "properties": {
+        "schema_version": {
+          "type": "string"
+        },
+        "generator": {
+          "type": "string"
+        },
+        "confidence_overall": {
+          "type": "string",
+          "enum": [
+            "high",
+            "medium",
+            "low"
+          ]
+        },
+        "warnings": {
+          "type": "array",
+          "items": {
+            "type": "string"
+          }
+        },
+        "userRequestedFullsuite": {
+          "type": "boolean",
+          "description": "**用户明示「全量验证」的放行标记**（app 形态专用，唯一写入口是 pc-02-dev-test-cases）。app 形态名册契约默认 baseline_mode=app-smoke（固定 4 条冒烟、单启动周期，核心功能验证不进名册——由 04-summary remaining_todos 与配方「待人工复核」承接）；仅当用户在对话中明确要求全量验证、且编排器把该明示注入派发 prompt 时，才允许 baseline_mode=full 并置本标记=true（来源写进 meta.warnings）。gate 阶段 2 据此放行，否则打回收缩——分母由用户决定，不由模型决定。库形态无此约束（full 是库形态默认）。"
+        },
+        "generated_backfill": {
+          "type": "boolean",
+          "description": "生成侧补写开关在本次名册的生效值（contract 侧信道 generated_backfill 的回写）。false = 关模式且名册为存活上游形态（补写清单为空），gap-ledger 不落账是合法态（roster-l0-gap-ledger 豁免账缺失告警）。缺省/true = 开模式，含 L0 功能点时账必须存在。"
+        }
+      }
+    }
+  },
+  "allOf": [
+    {
+      "description": "反假名册：planned 意味着「名册成立且双锚覆盖无缺口」——覆盖不到 100% 就写不出这个终态。这是「功能（接口）100% 覆盖」在合同层的落点。",
+      "if": {
+        "properties": {
+          "baseline_status": {
+            "const": "planned"
+          }
+        },
+        "required": [
+          "baseline_status"
+        ]
+      },
+      "then": {
+        "required": [
+          "cases",
+          "run_command",
+          "api_surface",
+          "feature_coverage"
+        ],
+        "properties": {
+          "cases": {
+            "minItems": 1
+          },
+          "api_surface": {
+            "properties": {
+              "uncovered": {
+                "maxItems": 0
+              }
+            }
+          },
+          "feature_coverage": {
+            "properties": {
+              "uncovered": {
+                "maxItems": 0
+              }
+            }
+          }
+        }
+      }
+    },
+    {
+      "description": "D3 状态相关：名册含 generated 用例 → device_budget 必填（可机判验收只对生成侧有估时义务）；纯 upstream 名册 optional（上游 CI 背书即 provenance）；旧产物重写时按名册形态补字段。",
+      "if": {
+        "properties": {
+          "cases": {
+            "contains": {
+              "type": "object",
+              "properties": {
+                "source": {
+                  "const": "generated"
+                }
+              },
+              "required": [
+                "source"
+              ]
+            }
+          }
+        },
+        "required": [
+          "cases"
+        ]
+      },
+      "then": {
+        "required": [
+          "device_budget"
+        ]
+      }
+    },
+    {
+      "description": "partial 同样要求名册非空且可复跑——「有缺口」说的是覆盖度，不是「没有名册」。缺口本身如实列进两个 uncovered[]。",
+      "if": {
+        "properties": {
+          "baseline_status": {
+            "const": "partial"
+          }
+        },
+        "required": [
+          "baseline_status"
+        ]
+      },
+      "then": {
+        "required": [
+          "cases",
+          "run_command"
+        ],
+        "properties": {
+          "cases": {
+            "minItems": 1
+          }
+        }
+      }
+    },
+    {
+      "description": "provenance=unavailable 时取不到公共导出面，符号面这一锚失效——只能靠功能点单锚，故不得定稿 planned。",
+      "if": {
+        "required": [
+          "api_surface"
+        ],
+        "properties": {
+          "api_surface": {
+            "properties": {
+              "provenance": {
+                "const": "unavailable"
+              }
+            },
+            "required": [
+              "provenance"
+            ]
+          }
+        }
+      },
+      "then": {
+        "properties": {
+          "baseline_status": {
+            "not": {
+              "const": "planned"
+            }
+          }
+        }
+      }
+    },
+    {
+      "description": "provenance=declared 必须给出符号面出处，否则无从抽查——「凭空声明一个 api_surface」正是本字段最容易被绕过的方式。",
+      "if": {
+        "required": [
+          "api_surface"
+        ],
+        "properties": {
+          "api_surface": {
+            "properties": {
+              "provenance": {
+                "const": "declared"
+              }
+            },
+            "required": [
+              "provenance"
+            ]
+          }
+        }
+      },
+      "then": {
+        "properties": {
+          "api_surface": {
+            "required": [
+              "source_refs"
+            ],
+            "properties": {
+              "source_refs": {
+                "minItems": 1
+              }
+            }
+          }
+        }
+      }
+    },
+    {
+      "description": "test_source=none 意味着没有任何可用用例，名册不成立。",
+      "if": {
+        "properties": {
+          "test_source": {
+            "const": "none"
+          }
+        },
+        "required": [
+          "test_source"
+        ]
+      },
+      "then": {
+        "properties": {
+          "baseline_status": {
+            "const": "blocked"
+          }
+        }
+      }
+    },
+    {
+      "description": "**补写用例的自证门槛**：宿主真跑过时，`source: generated` 的用例不许是 fail。自己写的用例在一个已知正确的环境里都不过，说明断言就是错的——该在本阶段修掉，而不是带到鸿蒙侧去要求「修产物到它通过」。原库用例不受此限（宿主跑不过很正常：平台独有、上游自身损坏）。",
+      "if": {
+        "required": [
+          "host_run"
+        ],
+        "properties": {
+          "host_run": {
+            "required": [
+              "status"
+            ],
+            "properties": {
+              "status": {
+                "const": "ran"
+              }
+            }
+          }
+        }
+      },
+      "then": {
+        "properties": {
+          "cases": {
+            "items": {
+              "if": {
+                "required": [
+                  "source"
+                ],
+                "properties": {
+                  "source": {
+                    "const": "generated"
+                  }
+                }
+              },
+              "then": {
+                "properties": {
+                  "host_result": {
+                    "not": {
+                      "const": "fail"
+                    }
+                  }
+                }
+              }
+            }
+          }
+        }
+      }
+    },
+    {
+      "description": "宿主跑不了要说清为什么——这决定了补写用例能不能自证，是下游判定的输入而非可省略的备注。",
+      "if": {
+        "required": [
+          "host_run"
+        ],
+        "properties": {
+          "host_run": {
+            "required": [
+              "status"
+            ],
+            "properties": {
+              "status": {
+                "const": "unavailable"
+              }
+            }
+          }
+        }
+      },
+      "then": {
+        "properties": {
+          "host_run": {
+            "required": [
+              "reason"
+            ]
+          }
+        }
+      }
+    },
+    {
+      "description": "定稿 planned 必须交代宿主预跑情况：要么跑了（补写用例已自证），要么明说跑不了。不填等于回避了「补写用例对不对」这个问题。",
+      "if": {
+        "properties": {
+          "baseline_status": {
+            "const": "planned"
+          }
+        },
+        "required": [
+          "baseline_status"
+        ]
+      },
+      "then": {
+        "required": [
+          "host_run"
+        ]
+      }
+    }
+  ]
+}