soloforge 1.1.37 → 1.1.40

package/templates/gates/shared/gate-/347/274/226/347/240/201/344/270/216/345/215/225/345/205/203/346/265/213/350/257/225.yaml

@@ -1,14 +1,40 @@
 # 编码门禁配置
-# 每个切片完成后即时校验
+# 对照方案 6.5 — 2 项检查（每切片即时校验）
 
 stage: "编码与单元测试"
 description: "每切片即时覆盖率校验"
 
 checks:
-  - name: "单元测试覆盖率"
+  - id: CODE-S01
+    name: "切片测试覆盖率达标"
+    category: "quality_check"
+    severity: error
+    check_type: deterministic
     required_artifact: "覆盖率报告"
     rule: "新系统行覆盖率≥70%，老系统增量覆盖率≥80%"
+    evidence_required:
+      - "当前切片覆盖率报告"
+      - "覆盖率数值（须≥阈值）"
 
-  - name: "切片隔离"
+  - id: CODE-S02
+    name: "切片隔离"
+    category: "quality_check"
+    severity: error
+    check_type: deterministic
     required_artifact: "已通过切片列表"
-    rule: "当前切片不得修改已通过切片涉及的文件"
+    rule: "当前切片不得修改已通过切片涉及的文件（交集为空）"
+    evidence_required:
+      - "已通过切片涉及文件列表"
+      - "当前切片 diff 文件列表"
+      - "交集对比结果（须为空集）"
+
+decision_model:
+  promote:
+    condition: "所有 error 项通过"
+    action: "当前切片通过，继续下一切片"
+  hold:
+    condition: "无 warning 项"
+    action: "无 hold 场景"
+  rollback:
+    condition: "任何 error 项未通过"
+    action: "当前切片回退修复"

package/templates/gates/shared/gate-/347/274/226/347/240/201/345/207/206/345/244/207.yaml

@@ -1,14 +1,50 @@
 # 编码准备门禁配置
-# 编码前校验就绪条件与设计产物完备性
+# 对照方案 6.2 — 3 项检查
 
 stage: "编码准备"
 description: "编码就绪条件与设计产物完备性校验"
 
 checks:
-  - name: "编码就绪状态"
+  - id: CODE-P01
+    name: "CodingReadiness 非 blocked"
+    category: "input_check"
+    severity: error
+    check_type: deterministic
     required_artifact: ""
     rule: "CodingReadinessGate status 非 blocked，所有前置条件已满足"
+    evidence_required:
+      - "CodingReadiness 报告文件路径"
+      - "status 字段值（须为 allowed）"
 
-  - name: "OOD 摘要存在"
+  - id: CODE-P02
+    name: "前置设计产物完备"
+    category: "input_check"
+    severity: error
+    check_type: deterministic
+    required_artifact: ""
+    rule: "gate-任务规划和 gate-详细设计已通过"
+    evidence_required:
+      - "gate-任务规划通过记录"
+      - "gate-详细设计通过记录"
+
+  - id: CODE-P03
+    name: "OOD 摘要存在（如适用）"
+    category: "input_check"
+    severity: warning
+    check_type: deterministic
     required_artifact: "OOD设计摘要模版"
-    rule: "OOD 设计摘要已生成且包含类/方法/协作关系定义"
+    rule: "OOD 设计摘要已生成且包含类/方法/协作关系定义；不适用时须提供理由"
+    evidence_required:
+      - "OOD 摘要文件路径"
+      - "或不适用的理由说明"
+
+decision_model:
+  promote:
+    condition: "CODE-P01 和 CODE-P02 通过"
+    action: "推进到编码实现阶段"
+  hold:
+    condition: "CODE-P03 未通过（OOD 摘要缺失）"
+    action: "标注 warning，由用户决定是否继续"
+  rollback:
+    condition: "CODE-P01 或 CODE-P02 未通过"
+    action: "回退到编码准备重新检查"

package/templates/gates/shared/gate-/347/274/226/347/240/201/345/256/236/347/216/260.yaml

@@ -1,14 +1,52 @@
 # 编码实现门禁配置
-# 编码阶段校验变更文件完整性与代码质量
+# 对照方案 6.3 — 3 项检查
 
 stage: "编码实现"
 description: "变更文件完整性与代码质量门禁"
 
 checks:
-  - name: "变更文件非空"
+  - id: CODE-I01
+    name: "变更文件在涉及范围内"
+    category: "output_check"
+    severity: error
+    check_type: deterministic
     required_artifact: ""
-    rule: "编码产生的变更文件列表不为空，至少包含一个源代码文件"
+    rule: "git diff --name-only 产生的变更文件列表在切片涉及文件范围内，偏差≤2 文件"
+    evidence_required:
+      - "git diff --name-only 输出"
+      - "切片涉及文件列表"
+      - "偏差对比结果"
 
-  - name: "代码质量门禁"
+  - id: CODE-I02
+    name: "代码质量无硬失败"
+    category: "quality_check"
+    severity: error
+    check_type: deterministic
     required_artifact: ""
     rule: "lazy_pattern_detector 0 hard_fail，代码中无空函数体、空 catch、未实现占位"
+    evidence_required:
+      - "lazy_pattern_detector 输出（hard_fail=0）"
+      - "空函数体扫描结果（0 匹配）"
+      - "空 catch 扫描结果（0 匹配）"
+
+  - id: CODE-I03
+    name: "扫描记录存在"
+    category: "input_check"
+    severity: error
+    check_type: deterministic
+    required_artifact: ""
+    rule: "编码前必须完成文件扫描，扫描记录包含文件/行号/变更类型"
+    evidence_required:
+      - "扫描记录文件路径"
+      - "扫描记录摘要（文件数/行数/变更类型统计）"
+
+decision_model:
+  promote:
+    condition: "所有 error 项通过"
+    action: "推进到切片执行验证"
+  hold:
+    condition: "无 warning 项"
+    action: "无 hold 场景"
+  rollback:
+    condition: "任何 error 项未通过"
+    action: "回退修复后重新执行"

package/templates/gates/shared/gate-/347/274/226/347/240/201/351/252/214/350/257/201.yaml

@@ -1,18 +1,47 @@
 # 编码验证门禁配置
-# 验证阶段校验构建、测试与覆盖率
+# 对照方案 6.4 — 3 项检查
 
 stage: "编码验证"
 description: "构建通过、测试通过与覆盖率达标校验"
 
 checks:
-  - name: "构建通过"
+  - id: CODE-V01
+    name: "构建通过"
+    category: "quality_check"
+    severity: error
+    check_type: deterministic
     required_artifact: ""
     rule: "tsc --noEmit 零错误，项目构建成功"
+    evidence_required:
+      - "构建输出（0 error）"
 
-  - name: "测试通过"
+  - id: CODE-V02
+    name: "测试通过"
+    category: "quality_check"
+    severity: error
+    check_type: deterministic
     required_artifact: ""
     rule: "全量测试通过，无失败用例"
+    evidence_required:
+      - "测试报告（passed/failed/total）"
 
-  - name: "覆盖率达标"
+  - id: CODE-V03
+    name: "覆盖率达标"
+    category: "quality_check"
+    severity: error
+    check_type: deterministic
     required_artifact: ""
     rule: "增量代码行覆盖率≥80%（或项目自定义覆盖率阈值）"
+    evidence_required:
+      - "覆盖率报告（增量行覆盖率数值）"
+
+decision_model:
+  promote:
+    condition: "所有 error 项通过"
+    action: "推进到切片审查阶段"
+  hold:
+    condition: "无 warning 项"
+    action: "无 hold 场景"
+  rollback:
+    condition: "任何 error 项未通过"
+    action: "回退修复后重新执行"

package/templates/gates/shared/gate-/350/201/224/350/260/203/351/252/214/350/257/201.yaml

@@ -1,14 +1,53 @@
 # 联调验证门禁配置
-# 联调验证阶段校验集成产物完备性
+# 对照方案 6.7 门禁层 — 6 项检查 + severity + evidence_required + decision_model
 
 stage: "联调验证"
-description: "联调验证产物完备性校验"
+description: "联调验证产物完备性、端到端校验与设计缺陷判定"
 
 checks:
-  - name: "测试计划"
-    required_artifact: "测试计划模版"
-    rule: "联调验证必须有对应的测试计划覆盖核心业务流程"
+  - id: IV-G01
+    name: "测试计划完备"
+    severity: error
+    check_type: deterministic
+    evidence_required: "文件路径 + P0 条目数 ≥ 1"
+    rule: "联调验证必须有对应的测试计划覆盖核心业务流程，P0 条目至少 1 条"
 
-  - name: "接口契约验证"
-    required_artifact: "接口对接方案模版"
-    rule: "所有外部接口对接方案必须在联调中得到验证"
+  - id: IV-G02
+    name: "接口契约验证"
+    severity: error
+    check_type: deterministic
+    evidence_required: "对接方案路径 + 沙箱证据已填写"
+    rule: "所有外部接口对接方案必须在联调中得到验证，沙箱验证证据章节已填写"
+
+  - id: IV-G03
+    name: "端到端验证通过"
+    severity: error
+    check_type: deterministic
+    evidence_required: "全部 PASS + Evidence ≥ E1"
+    rule: "端到端核心业务流程验证必须全部通过，证据级别至少 E1（运行时证据）"
+
+  - id: IV-G04
+    name: "构建通过"
+    severity: error
+    check_type: deterministic
+    evidence_required: "0 errors + 产物时间戳"
+    rule: "项目构建必须无错误通过，产物时间戳为本次构建"
+
+  - id: IV-G05
+    name: "设计缺陷回退判定"
+    severity: error
+    check_type: semantic
+    evidence_required: "DEF-* 执行结果 + 判定结论"
+    rule: "必须执行 DEF-01~04 设计缺陷判定，确认未触发回退条件或已执行回退"
+
+  - id: IV-G06
+    name: "验收证据充分"
+    severity: warning
+    check_type: deterministic
+    evidence_required: "P0 条目 evidence 路径列表"
+    rule: "所有 P0 测试条目必须有 Evidence 文件路径，建议核心流程达到 E2 级别"
+
+decision_model:
+  PROMOTE: "所有 error 通过 + warning 通过或标注已知取舍"
+  HOLD: "error 全通过但 warning 未处理"
+  ROLLBACK: "任何 error 失败或 DEF-* 触发回退"

package/templates/gates/shared/gate-/350/257/246/347/273/206/350/256/276/350/256/241.yaml

@@ -1,14 +1,123 @@
 # 详细设计门禁配置
-# 详细设计阶段完成后校验设计产物与切片计划一致性
+# 对照方案 §六 G-01 — 15 项检查 + PROMOTE/HOLD/ROLLBACK 决策模型
+# 核心产物仅 DB 设计 + API 规格，不强制检查详细设计文档
 
-stage: "详细设计"
-description: "详细设计产物完备性校验"
+gate_id: gate-详细设计
+description: "详细设计阶段质量门禁"
+scope: shared
+
+decision_model:
+  PROMOTE: "所有 error 项通过 + warning 项通过或标注已知取舍"
+  HOLD: "error 项全通过但 warning 项未处理（需用户确认）"
+  ROLLBACK: "任何 error 项失败或证据缺失"
+  all_clear: "所有 error 通过 + 无 HOLD/ROLLBACK 失败 → PROMOTE"
 
 checks:
-  - name: "详细设计文档"
-    required_artifact: "详细设计模版"
-    rule: "详细设计文档必须包含类设计、方法签名和关键算法描述"
+  # === 输入检查（2 项）===
+  - id: DD-G01
+    description: "架构设计文档存在且已通过门禁"
+    severity: error
+    check_type: deterministic
+    evidence_required: "架构设计文档路径 + gate-架构设计 通过记录"
+
+  - id: DD-G02
+    description: "输入产物探索完整"
+    severity: error
+    check_type: deterministic
+    pattern: "Agent 必须引用所有上游产物（架构设计文档、ADR），引用包含文件路径+章节编号"
+    evidence_required: "Agent 执行日志中的文件读取记录"
+
+  # === 核心产物检查（2 项 — 仅检查 DB 设计 + API 规格，不强制检查详细设计文档）===
+  - id: DD-G03
+    description: "数据库设计文档完备"
+    severity: error
+    check_type: deterministic
+    pattern: "Ch1~Ch8 结构完整 + SQL/migration 文件存在"
+    evidence_required: "8 章标题列表 + SQL/migration 文件路径"
+
+  - id: DD-G04
+    description: "API 接口规格完备 + openapi.yaml 同步"
+    severity: error
+    check_type: deterministic
+    pattern: "每个 Endpoint 含基本信息/请求/响应/错误码/验收场景 + openapi.yaml operation 数匹配"
+    evidence_required: "Endpoint 列表 + openapi.yaml 路径 + 端点数对比"
+
+  # === 质量检查（4 项）===
+  - id: DD-G05
+    description: "三大核心产物无禁止空洞"
+    severity: error
+    check_type: deterministic
+    pattern: "数据库设计文档 Ch1~Ch8 + API 规格 Endpoint 无空章节/空字段"
+    evidence_required: "空章节/空字段扫描输出（须为工具执行结果）"
+
+  - id: DD-G06
+    description: "DD-* 编号声明完整"
+    severity: error
+    check_type: deterministic
+    pattern: "数据库设计 DD-T* 编号 + API 规格 DD-A* 编号已声明且唯一"
+    evidence_required: "DD-T*/DD-A* 编号列表 + 唯一性校验结果"
+
+  - id: DD-G07
+    description: "SQL/migration 权威资产存在"
+    severity: error
+    check_type: deterministic
+    pattern: "数据库设计文档 Ch1 声明的路径对应文件存在"
+    evidence_required: "文件存在性检查结果"
+
+  - id: DD-G08
+    description: "OOD 工作流触发合规"
+    severity: warning
+    check_type: semantic
+    pattern: "涉及复杂对象边界/变化点/领域服务时 OOD 已执行；否则有不适用理由记录"
+    evidence_required: "OOD 输出摘要表 或 不适用理由文本"
+
+  # === 交叉验证检查（5 项）===
+  - id: DD-G09
+    description: "架构覆盖完整性"
+    severity: error
+    check_type: semantic
+    pattern: "架构设计中所有模块/接口在详细设计中有对应覆盖"
+    evidence_required: "架构模块列表 vs 详细设计覆盖清单"
+
+  - id: DD-G10
+    description: "追踪矩阵覆盖"
+    severity: error
+    check_type: deterministic
+    pattern: "DD-T* 计数 = 数据库表数 且 DD-A* 计数 = API 端点数"
+    evidence_required: "追踪矩阵中 DD-T*/DD-A* 条目数 vs 实际计数"
+
+  - id: DD-G11
+    description: "OpenAPI 与文档一致"
+    severity: error
+    check_type: deterministic
+    pattern: "openapi.yaml 的 paths/schemas/responses 与 API 文档一一对应"
+    evidence_required: "路径/字段/错误码匹配率"
+
+  - id: DD-G12
+    description: "companion_rules 已触发"
+    severity: warning
+    check_type: deterministic
+    pattern: "产物 frontmatter 声明的 :check 规则已执行（DD-REV-*/CON-DD-*）"
+    evidence_required: "每个 :check 规则的执行结果"
+
+  - id: DD-G13
+    description: "实现锚点可供消费"
+    severity: warning
+    check_type: semantic
+    pattern: "DD-* 锚点有唯一编号 + 文件路径 + 验收标准"
+    evidence_required: "锚点列表 + 唯一性校验结果"
+
+  # === 格式校验检查（2 项）===
+  - id: DD-G14
+    description: "API 格式校验通过"
+    severity: error
+    check_type: deterministic
+    pattern: "AI Agent 格式校验 8 项全部通过"
+    evidence_required: "格式校验结果清单"
 
-  - name: "设计一致性"
-    required_artifact: "设计一致性验收报告模版"
-    rule: "详细设计必须与架构设计中定义的接口和分层保持一致"
+  - id: DD-G15
+    description: "兼容性检查规则执行"
+    severity: warning
+    check_type: deterministic
+    pattern: "COMP-01/03/04/05/07（详细设计阶段 applicable）已执行"
+    evidence_required: "COMP-* 执行结果"

package/templates/gates/shared/gate-/351/234/200/346/261/202/345/210/206/346/236/220.yaml

@@ -1,18 +1,164 @@
 # 需求分析门禁配置
-# 需求分析阶段完成后校验产物完备性
+# 对照方案 §六 改进 G-01 — 15 项检查 + PROMOTE/HOLD/ROLLBACK 决策模型
+# AI Agent 门禁原则：独立验证 > AI 自查；确定性检查优先；探索覆盖度可度量
 
 stage: "需求分析"
 description: "需求分析产物完备性校验"
 
+decision_model:
+  PROMOTE: "所有 error 项通过（证据完备），warning 项通过或标注已知取舍"
+  HOLD: "error 项全部通过但 warning 项未处理（需用户确认是否接受）"
+  ROLLBACK: "任何 error 项失败或证据缺失"
+
 checks:
-  - name: "需求文档完整性"
-    required_artifact: "需求分析模版"
-    rule: "需求分析文档必须包含功能需求、非功能需求和约束条件"
+  # ===== 原型说明模版（4 项）=====
+
+  - name: "原型源码包存在"
+    category: "input_check"
+    severity: "error"
+    check_type: "deterministic"
+    required_artifact: "原型源码包"
+    rule: "原型源码包必须存在且可读取"
+    evidence_required:
+      - "已读取的源码文件路径列表"
+
+  - name: "原型说明结构完备"
+    category: "output_check"
+    severity: "error"
+    check_type: "deterministic"
+    required_artifact: "原型说明模版"
+    rule: "原型说明模版必须完整覆盖 10 个章节（含新增第 10 章无障碍），不得有空章节"
+    evidence_required:
+      - "章节标题完整列表"
+      - "章节数计数结果（必须 = 10）"
+
+  - name: "无禁止空洞"
+    category: "quality_check"
+    severity: "error"
+    check_type: "deterministic"
+    required_artifact: "原型说明模版"
+    rule: "所有章节无空标题、无 TODO 占位、无 `-` 单独占位"
+    evidence_required:
+      - "空标题检测结果（须为 0 处）"
 
-  - name: "原型设计对齐"
+  - name: "证据标记覆盖"
+    category: "evidence_check"
+    severity: "warning"
+    check_type: "deterministic"
     required_artifact: "原型说明模版"
-    rule: "需求分析必须关联到原型设计中定义的页面或接口"
+    rule: "内容使用统一标记体系 [SRC]/[LOG]/[CFG]/[REF]/[DES]/[INF]，标记引用的文件路径必须存在"
+    evidence_required:
+      - "标记正则匹配结果"
+      - "标记引用文件路径存在性校验结果"
+
+  # ===== 需求分析模版（4 项）=====
 
-  - name: "追踪矩阵覆盖"
+  - name: "需求分析结构完备"
+    category: "output_check"
+    severity: "error"
+    check_type: "deterministic"
+    required_artifact: "需求分析模版"
+    rule: "需求分析模版必须完整覆盖 10 个章节（含新增第 8 章 NFR、第 9 章角色、第 10 章外部接口）"
+    evidence_required:
+      - "章节标题完整列表"
+      - "章节数计数结果（必须 = 10）"
+
+  - name: "非功能需求量化"
+    category: "quality_check"
+    severity: "error"
+    check_type: "semantic"
+    required_artifact: "需求分析模版"
+    rule: "第 8 章每条 NFR 必须包含量化验收指标（数字或百分比），禁止'高性能''安全'等模糊表述"
+    evidence_required:
+      - "NFR 表中「验收指标」列非空且含数字或百分比的工具校验结果"
+      - "模糊表述关键词扫描结果（须为 0 处）"
+
+  - name: "用户角色一致性"
+    category: "quality_check"
+    severity: "error"
+    check_type: "semantic"
+    required_artifact: "需求分析模版"
+    rule: "第 6 章菜单权限和第 2 章功能点引用的角色在第 9 章有定义，三处角色名称一致"
+    evidence_required:
+      - "三处角色名称交叉引用校验结果"
+      - "未定义角色列表（须为空）"
+
+  - name: "外部接口声明"
+    category: "completeness_check"
+    severity: "warning"
+    check_type: "deterministic"
+    required_artifact: "需求分析模版"
+    rule: "第 10 章无空洞或显式标注'无外部依赖'"
+    evidence_required:
+      - "章节内容非空检测结果"
+
+  # ===== 追踪矩阵（3 项）=====
+
+  - name: "追踪矩阵结构完备"
+    category: "output_check"
+    severity: "error"
+    check_type: "deterministic"
+    required_artifact: "需求原型设计实现追踪矩阵模版"
+    rule: "追踪矩阵模版必须完整覆盖 6 个章节"
+    evidence_required:
+      - "章节标题完整列表"
+      - "章节数计数结果（必须 = 6）"
+
+  - name: "覆盖分析完整"
+    category: "quality_check"
+    severity: "warning"
+    check_type: "semantic"
     required_artifact: "需求原型设计实现追踪矩阵模版"
-    rule: "每个需求点必须在追踪矩阵中有对应的实现规划"
+    rule: "第 6 章正向覆盖无'未覆盖'行，或'已排除'行有排除原因"
+    evidence_required:
+      - "覆盖状态列值枚举校验结果"
+      - "已排除行原因列非空校验结果"
+
+  - name: "验证方法声明"
+    category: "quality_check"
+    severity: "warning"
+    check_type: "deterministic"
+    required_artifact: "需求原型设计实现追踪矩阵模版"
+    rule: "总矩阵每行必须有验证方法（Test/Demonstration/Analysis/Inspection）"
+    evidence_required:
+      - "验证方法列非空检测结果"
+
+  # ===== 引擎机制集成（2 项）=====
+
+  - name: "未确认项分级完备"
+    category: "quality_check"
+    severity: "warning"
+    check_type: "deterministic"
+    required_artifact: "需求分析模版"
+    rule: "第 4 章所有未确认项使用四级分级 {blocking, material, minor, non_blocking}，无二分法值"
+    evidence_required:
+      - "分级列值枚举校验结果"
+
+  - name: "阻塞级收敛完成"
+    category: "evidence_check"
+    severity: "error"
+    check_type: "semantic"
+    required_artifact: "需求分析模版"
+    rule: "blocking 级未确认项附带候选方案和用户确认结果"
+    evidence_required:
+      - "blocking 行的候选方案列非空校验结果"
+      - "blocking 行的用户确认结果列非空校验结果"
+
+  # ===== AI Agent 专项（2 项）=====
+
+  - name: "输入产物探索完整"
+    category: "input_check"
+    severity: "error"
+    check_type: "semantic"
+    rule: "Agent 必须引用所有输入产物（需求来源材料、原型源码包、现有系统源码），引用证据包含具体文件路径，不得泛化引用"
+    evidence_required:
+      - "已读取的所有输入文件路径列表"
+      - "各输入产物类型覆盖确认（需求/原型/源码）"
+
+  - name: "确定性检查通过率"
+    category: "meta_check"
+    severity: "error"
+    check_type: "deterministic"
+    rule: "所有确定性检查项（章节数/空标题/标记存在性/列非空）须 100% 通过"
+    evidence_required:
+      - "确定性检查项工具执行结果汇总表（检查项/结果/证据）"

package/templates/internal/patterns/Diff/345/275/222/345/261/236/350/277/275/350/270/252.md

@@ -1,31 +1,20 @@
 ---
 name: diff_ownership
-when: 'Diff 归属, 变更追踪, CAS 校验, 代码变更'
 scope: ['*']
 products:
   - '*'
 id: ka-pattern-diff_ownership
-asset_kind: pattern
 lifecycle_status: active
 authority: supporting
-routes:
-  - '*'
-primary_triggers:
-  - Diff 归属
-  - 变更追踪
-  - CAS 校验
-  - 代码变更
 priority: P2
-specificity: 3
 version: 1.1.0
 last_reviewed: '2026-06-01'
 consumes: []
 emits: []
-secondary_triggers: []
-negative_triggers: []
 type: pattern
 stages: ["*"]
 owner_mechanism_id: mc-engine-runtime
+triggers: ["Diff 归属","变更追踪","CAS 校验","代码变更"]
 ---
 
 ## 决策规则

package/templates/internal/patterns/Hook/345/261/202/344/272/247/347/211/251/347/273/223/346/236/204/346/240/241/351/252/214.md

@@ -1,26 +1,20 @@
 ---
 name: hook-product-structure-validation
 type: pattern
-when: 'L4校验, 产物结构, check_write, check_bash, artifact_validator'
 scope: ['*']
 products:
   - '*'
 id: cap-kdoc-write-artifact-validator
-asset_kind: pattern
 lifecycle_status: active
 authority: supporting
-routes:
-  - '*'
 priority: P2
-specificity: 2
 version: 1.1.0
 last_reviewed: '2026-06-01'
 consumes: []
 emits: []
-secondary_triggers: []
-negative_triggers: []
 stages: ["*"]
 owner_mechanism_id: mc-engine-runtime
+triggers: ["L4校验","产物结构","check_write","check_bash","artifact_validator"]
 ---
 
 # Hook 层产物结构校验

package/templates/internal/patterns/Java/350/264/250/351/207/217/351/227/250/347/246/201.md

@@ -1,32 +1,20 @@
 ---
 name: java_quality_guard
-when: 'Java 代码质量, 代码审查, 质量门禁, 空catch, raw type'
 scope: ['*']
 products:
   - '*'
 id: ka-pattern-java_quality_guard
-asset_kind: pattern
 lifecycle_status: active
 authority: supporting
-routes:
-  - '*'
-primary_triggers:
-  - Java 代码质量
-  - 代码审查
-  - 质量门禁
-  - 空catch
-  - raw type
 priority: P2
-specificity: 3
 version: 1.1.0
 last_reviewed: '2026-06-01'
 consumes: []
 emits: []
-secondary_triggers: []
-negative_triggers: []
 type: pattern
 stages: ["*"]
 owner_mechanism_id: mc-engine-runtime
+triggers: ["Java 代码质量","代码审查","质量门禁","空catch","raw type"]
 ---
 
 ## 决策规则