soloforge 1.1.33 → 1.1.34

package/templates/rules/shared//345/217/221/345/270/203/345/220/216/345/256/241/346/237/245/350/247/204/345/210/231.md

@@ -0,0 +1,58 @@
+---
+name: post-release-review
+type: review_rule
+when: '发布后, 上线观察, post-release review'
+scope:
+  - backend
+  - frontend
+products:
+  - '*'
+id: ka-review-rule-发布后审查规则
+asset_kind: review_rule
+lifecycle_status: active
+owner_mechanism_id: mc-delivery-gate
+authority: supporting
+routes:
+  - code_change
+primary_triggers:
+  - 发布后审查规则
+secondary_triggers:
+  - 发布后审查
+  - 上线观察
+negative_triggers: []
+priority: P1
+specificity: 5
+version: 1.1.0
+last_reviewed: '2026-06-01'
+stages: ["代码审查"]
+---
+
+# 发布后审查规则
+
+## REL-01: 监控指标在阈值内
+
+pattern: 发布后关键监控指标必须在正常范围内
+severity: warning
+scope: [backend, frontend]
+description: 错误率、响应时间、吞吐量等关键指标在发布后 30 分钟内必须在历史基线 ±20% 范围内
+
+## REL-02: 无新增告警
+
+pattern: 发布后不得产生新的异常告警
+severity: warning
+scope: [backend, frontend]
+description: 发布后检查告警系统，不得有因本次发布新增的错误日志或异常告警
+
+## REL-03: 回滚预案已验证
+
+pattern: 回滚操作必须在发布前验证过
+severity: warning
+scope: [backend, frontend]
+description: 回滚预案必须经过实际演练或自动化验证，确认回滚操作可在 5 分钟内完成
+
+## REL-04: 数据一致性确认
+
+pattern: 发布后必须验证数据一致性
+severity: warning
+scope: backend
+description: 涉及数据库变更的发布，发布后必须验证新老数据的一致性（数据校验脚本通过）

package/templates/rules/shared//345/220/216/347/253/257/345/256/236/347/216/260/345/267/245/347/250/213/345/256/241/346/237/245/350/247/204/345/210/231.md

@@ -1,5 +1,5 @@
 ---
-name: 后端实现工程审查规则
+name: backend-implementation-review
 type: review_rule
 when: '后端审查, Controller, DTO, 事务, 幂等, 权限'
 scope:
@@ -20,11 +20,13 @@ secondary_triggers:
 negative_triggers: []
 priority: P1
 specificity: 5
+consumes:
+  - mc-ood-solid-contract
 required_evidence:
   - code_review_findings
-version: 1.0.0
-last_reviewed: '2026-05-26'
-status: active
+version: 1.1.0
+last_reviewed: '2026-06-01'
+stages: ["编码与单元测试", "联调验证"]
 ---
 
 ## 硬失败检查

package/templates/rules/shared//345/256/211/345/205/250/345/256/241/346/237/245/350/247/204/345/210/231.md

@@ -10,6 +10,7 @@ products:
 id: ka-review-rule-安全审查规则
 asset_kind: review_rule
 lifecycle_status: active
+owner_mechanism_id: mc-generic-review
 authority: supporting
 routes:
   - code_change
@@ -19,12 +20,9 @@ secondary_triggers: []
 negative_triggers: []
 priority: P1
 specificity: 5
-required_evidence:
-  - execution_evidence
-version: 1.0.0
-last_reviewed: '2026-05-22'
-migration_note: 知识资产标准化迁移
-status: active
+version: 1.1.0
+last_reviewed: '2026-06-01'
+stages: ["代码审查"]
 ---
 
 ## SEC-01: SQL 字符串拼接导致注入风险

package/templates/rules/shared//345/271/266/345/217/221/345/256/241/346/237/245/350/247/204/345/210/231.md

@@ -9,6 +9,7 @@ products:
 id: ka-review-rule-并发审查规则
 asset_kind: review_rule
 lifecycle_status: active
+owner_mechanism_id: mc-generic-review
 authority: supporting
 routes:
   - code_change
@@ -18,12 +19,9 @@ secondary_triggers: []
 negative_triggers: []
 priority: P1
 specificity: 5
-required_evidence:
-  - execution_evidence
-version: 1.0.0
-last_reviewed: '2026-05-22'
-migration_note: 知识资产标准化迁移
-status: active
+version: 1.1.0
+last_reviewed: '2026-06-01'
+stages: ["代码审查"]
 ---
 
 ## CON-01: 共享可变状态无并发保护

package/templates/rules/shared//346/200/247/350/203/275/345/256/241/346/237/245/350/247/204/345/210/231.md

@@ -10,6 +10,7 @@ products:
 id: ka-review-rule-性能审查规则
 asset_kind: review_rule
 lifecycle_status: active
+owner_mechanism_id: mc-generic-review
 authority: supporting
 routes:
   - code_change
@@ -19,12 +20,9 @@ secondary_triggers: []
 negative_triggers: []
 priority: P1
 specificity: 5
-required_evidence:
-  - execution_evidence
-version: 1.0.0
-last_reviewed: '2026-05-22'
-migration_note: 知识资产标准化迁移
-status: active
+version: 1.1.0
+last_reviewed: '2026-06-01'
+stages: ["代码审查"]
 ---
 
 ## PER-01: 循环内逐条数据库调用（N+1 问题）

package/templates/rules/shared//346/216/245/345/217/243/345/245/221/347/272/246/345/256/241/346/237/245/350/247/204/345/210/231.md

@@ -9,6 +9,7 @@ products:
 id: ka-review-rule-接口契约审查规则
 asset_kind: review_rule
 lifecycle_status: active
+owner_mechanism_id: mc-generic-review
 authority: supporting
 routes:
   - code_change
@@ -18,12 +19,9 @@ secondary_triggers: []
 negative_triggers: []
 priority: P1
 specificity: 5
-required_evidence:
-  - execution_evidence
-version: 1.0.0
-last_reviewed: '2026-05-22'
-migration_note: 知识资产标准化迁移
-status: active
+version: 1.1.0
+last_reviewed: '2026-06-01'
+stages: ["代码审查"]
 ---
 
 ## API-01: Controller 返回 Entity 而非 DTO

package/templates/rules/shared//346/236/266/346/236/204/345/256/241/346/237/245/350/247/204/345/210/231.md

@@ -10,6 +10,7 @@ products:
 id: ka-review-rule-架构审查规则
 asset_kind: review_rule
 lifecycle_status: active
+owner_mechanism_id: mc-generic-review
 authority: supporting
 routes:
   - code_change
@@ -19,12 +20,9 @@ secondary_triggers: []
 negative_triggers: []
 priority: P1
 specificity: 5
-required_evidence:
-  - execution_evidence
-version: 1.0.0
-last_reviewed: '2026-05-22'
-migration_note: 知识资产标准化迁移
-status: active
+version: 1.1.0
+last_reviewed: '2026-06-01'
+stages: ["代码审查"]
 ---
 
 ## ARC-01: Controller 包含业务逻辑

package/templates/rules/shared//347/274/226/347/240/201/345/260/261/347/273/252/345/256/241/346/237/245/350/247/204/345/210/231.md

@@ -0,0 +1,58 @@
+---
+name: coding-readiness-review
+type: review_rule
+when: '编码准备, 编码就绪, coding readiness'
+scope:
+  - backend
+  - frontend
+products:
+  - '*'
+id: ka-review-rule-编码就绪审查规则
+asset_kind: review_rule
+lifecycle_status: active
+owner_mechanism_id: mc-coding-readiness
+authority: supporting
+routes:
+  - code_change
+primary_triggers:
+  - 编码就绪审查规则
+secondary_triggers:
+  - 编码准备
+  - 就绪检查
+negative_triggers: []
+priority: P1
+specificity: 5
+version: 1.1.0
+last_reviewed: '2026-06-01'
+stages: ["编码与单元测试"]
+---
+
+# 编码就绪审查规则
+
+## READY-01: CodingReadiness 非空
+
+pattern: 编码前必须确认 CodingReadiness 检查已通过
+severity: warning
+scope: [backend, frontend]
+description: CodingReadiness 报告必须存在且 status 非 blocked；blocked 状态必须先解决前置问题
+
+## READY-02: OOD 摘要完整
+
+pattern: OOD 设计摘要必须包含类定义、方法签名和协作关系
+severity: warning
+scope: [backend, frontend]
+description: OOD 摘要至少包含：核心类名、公开方法签名、类间协作关系图；缺少任一项必须补充后再编码
+
+## READY-03: 前置产物已确认
+
+pattern: 编码依赖的设计产物必须全部就绪
+severity: warning
+scope: [backend, frontend]
+description: API 接口规格、数据库设计文档、切片计划等编码依赖产物必须已生成且无 hard_fail
+
+## READY-04: 技术栈明确
+
+pattern: 编码前必须确认使用的技术栈和框架版本
+severity: warning
+scope: [backend, frontend]
+description: 语言版本、框架版本、关键依赖版本必须在编码前明确，避免编码过程中变更技术栈

package/templates/rules/shared//350/201/224/350/260/203/351/252/214/350/257/201/346/270/205/345/215/225.md

@@ -1,13 +1,16 @@
 ---
-name: 联调验证清单
+name: integration-verification-list
 type: review_rule
-asset_kind: pipeline_rule
+asset_kind: review_rule
 routes:
   - code_change
 primary_triggers:
   - 联调验证
   - 验证清单
-scope: [shared]
+scope: ['*']
+stages: ["联调验证"]
+lifecycle_status: active
+owner_mechanism_id: mc-generic-review
 ---
 
 # 联调验证清单

package/templates/rules/shared//350/246/206/347/233/226/347/216/207/346/240/207/345/207/206.md

@@ -1,12 +1,15 @@
 ---
-name: 覆盖率标准
+name: coverage-standard
 type: review_rule
 when: 测试覆盖率校验
-scope: [shared]
+scope: ['*']
 products: ['*']
-status: active
-routes: [code_change, verification_only]
+lifecycle_status: active
+asset_kind: review_rule
+owner_mechanism_id: mc-generic-review
+routes: ['code_change', 'review']
 primary_triggers: [覆盖率, 测试, 覆盖]
+stages: ["编码与单元测试", "联调验证"]
 ---
 # 覆盖率标准
 

package/templates/rules/shared//350/264/250/351/207/217/345/256/241/346/237/245/350/247/204/345/210/231.md

@@ -10,6 +10,7 @@ products:
 id: ka-review-rule-质量审查规则
 asset_kind: review_rule
 lifecycle_status: active
+owner_mechanism_id: mc-generic-review
 authority: supporting
 routes:
   - code_change
@@ -19,12 +20,9 @@ secondary_triggers: []
 negative_triggers: []
 priority: P1
 specificity: 5
-required_evidence:
-  - execution_evidence
-version: 1.0.0
-last_reviewed: '2026-05-22'
-migration_note: 知识资产标准化迁移
-status: active
+version: 1.1.0
+last_reviewed: '2026-06-01'
+stages: ["编码与单元测试"]
 ---
 
 ## QUA-01: 生产代码包含 console.log 调试输出

package/templates/rules/shared//351/234/200/346/261/202/350/264/250/351/207/217/345/256/241/346/237/245/350/247/204/345/210/231.md

@@ -0,0 +1,64 @@
+---
+name: requirement-quality-review
+type: review_rule
+when: '需求分析, 需求审查, requirement review'
+scope:
+  - backend
+  - frontend
+products:
+  - '*'
+id: ka-review-rule-需求质量审查规则
+asset_kind: review_rule
+lifecycle_status: active
+authority: supporting
+routes: ['code_change', 'planning']
+primary_triggers:
+  - 需求质量审查规则
+secondary_triggers:
+  - 需求审查
+  - 需求质量
+negative_triggers: []
+priority: P1
+specificity: 5
+version: 1.1.0
+last_reviewed: '2026-06-01'
+stages: ["编码与单元测试", "联调验证"]
+owner_mechanism_id: mc-intent-router
+---
+
+# 需求质量审查规则
+
+## REQ-01: 需求可测试性
+
+pattern: 需求描述必须包含可量化的验收标准
+severity: warning
+scope: [backend, frontend]
+description: 每个需求点必须至少有一条可验证的验收标准，避免模糊表述（如"性能好"应改为"响应时间<200ms"）
+
+## REQ-02: 功能/非功能/约束三维度覆盖
+
+pattern: 需求分析必须覆盖功能需求、非功能需求和约束条件
+severity: warning
+scope: [backend, frontend]
+description: 需求文档必须明确区分功能需求（做什么）、非功能需求（性能、安全、可用性等）和约束条件（技术栈、时间、资源等）
+
+## REQ-03: 需求无歧义表达
+
+pattern: 需求描述不得使用模糊量词或条件
+severity: warning
+scope: [backend, frontend]
+description: 禁止使用"等"、"相关"、"适当的"、"必要时"等模糊表述；每个需求点必须有一个明确的动作和对象
+
+## REQ-04: 需求间无矛盾
+
+pattern: 需求文档中不得存在相互矛盾的描述
+severity: warning
+scope: [backend, frontend]
+description: 检查需求间是否存在矛盾（如"支持离线使用"与"实时同步数据"），发现矛盾必须标注并请求澄清
+
+## REQ-05: 需求完整性
+
+pattern: 每个功能需求必须包含触发条件、处理逻辑和预期结果
+severity: warning
+scope: [backend, frontend]
+description: 缺少触发条件、处理逻辑或预期结果的需求必须标注为"待补充"，不得留空

package/templates/rules/shared//351/252/214/346/224/266/346/240/207/345/207/206/345/256/241/346/237/245/350/247/204/345/210/231.md

@@ -0,0 +1,58 @@
+---
+name: acceptance-criteria-review
+type: review_rule
+when: '本地验收, 验收标准, acceptance review'
+scope:
+  - backend
+  - frontend
+products:
+  - '*'
+id: ka-review-rule-验收标准审查规则
+asset_kind: review_rule
+lifecycle_status: active
+owner_mechanism_id: mc-local-acceptance
+authority: supporting
+routes:
+  - code_change
+primary_triggers:
+  - 验收标准审查规则
+secondary_triggers:
+  - 验收审查
+  - 验收标准
+negative_triggers: []
+priority: P1
+specificity: 5
+version: 1.1.0
+last_reviewed: '2026-06-01'
+stages: ["编码与单元测试", "联调验证"]
+---
+
+# 验收标准审查规则
+
+## ACC-01: 验收场景覆盖三路径
+
+pattern: 验收场景必须覆盖正常路径、边界条件和异常路径
+severity: warning
+scope: [backend, frontend]
+description: 验收测试至少包含：正常业务流程（happy path）、边界值输入（最大/最小/空值）、异常处理（错误输入、网络超时、权限不足）
+
+## ACC-02: 验收证据含截图或日志
+
+pattern: 每个验收场景必须有执行证据
+severity: warning
+scope: [backend, frontend]
+description: 验收证据可以是：UI 截图、API 响应日志、测试输出报告；纯文字描述不构成有效证据
+
+## ACC-03: 用户确认记录
+
+pattern: 验收结果必须经用户确认
+severity: warning
+scope: [backend, frontend]
+description: sf_accept 返回的验收结果必须有用户确认的记录；AI 不得自行标记验收通过
+
+## ACC-04: 回归验证
+
+pattern: 验收必须包含回归验证
+severity: warning
+scope: [backend, frontend]
+description: 变更代码的验收必须运行全量回归测试，确认变更未破坏已有功能

package/templates/scaffolds/react/ErrorBoundary.tsx.hbs

@@ -0,0 +1,49 @@
+import React, { Component, ErrorInfo, ReactNode } from 'react';
+
+/**
+ * {{ModuleName}} 错误边界 — 捕获 {{moduleName}} 模块渲染异常并展示降级 UI。
+ */
+interface ErrorBoundaryProps {
+  children: ReactNode;
+  fallback?: ReactNode;
+}
+
+interface ErrorBoundaryState {
+  hasError: boolean;
+  error: Error | null;
+}
+
+export class {{ModuleName}}ErrorBoundary extends Component<ErrorBoundaryProps, ErrorBoundaryState> {
+  constructor(props: ErrorBoundaryProps) {
+    super(props);
+    this.state = { hasError: false, error: null };
+  }
+
+  static getDerivedStateFromError(error: Error): ErrorBoundaryState {
+    return { hasError: true, error };
+  }
+
+  componentDidCatch(error: Error, errorInfo: ErrorInfo): void {
+    console.error('[{{ModuleName}}ErrorBoundary] 渲染异常:', error, errorInfo);
+  }
+
+  render(): ReactNode {
+    if (this.state.hasError) {
+      if (this.props.fallback) {
+        return this.props.fallback;
+      }
+      return (
+        <div className="{{moduleName}}-error-boundary" role="alert">
+          <h2>{{ModuleName}} 模块渲染异常</h2>
+          <p>{this.state.error?.message ?? '未知错误'}</p>
+          <button onClick={() => this.setState({ hasError: false, error: null })}>
+            重试
+          </button>
+        </div>
+      );
+    }
+    return this.props.children;
+  }
+}
+
+export default {{ModuleName}}ErrorBoundary;

package/templates/scaffolds/react/Layout.tsx.hbs

@@ -0,0 +1,20 @@
+import React from 'react';
+
+/**
+ * {{ModuleName}} 布局组件 — 提供 {{moduleName}} 模块的页面框架结构。
+ * 包含侧边导航、顶部操作栏和内容区域。
+ */
+export const {{ModuleName}}Layout: React.FC<{ children?: React.ReactNode }> = ({ children }) => {
+  return (
+    <div className="{{moduleName}}-layout">
+      <header className="{{moduleName}}-layout__header">
+        <h1>{{ModuleName}}</h1>
+      </header>
+      <main className="{{moduleName}}-layout__content">
+        {children}
+      </main>
+    </div>
+  );
+};
+
+export default {{ModuleName}}Layout;

package/templates/scaffolds/spring-boot/ControllerTest.java.hbs

@@ -0,0 +1,36 @@
+package {{basePackage}}.controller;
+
+import org.junit.jupiter.api.Test;
+import org.junit.jupiter.api.extension.ExtendWith;
+import org.mockito.InjectMocks;
+import org.mockito.Mock;
+import org.mockito.junit.jupiter.MockitoExtension;
+
+import static org.junit.jupiter.api.Assertions.*;
+
+/**
+ * {{ModuleName}} 控制器单元测试 — 验证 HTTP 接口的入参校验与响应格式。
+ */
+@ExtendWith(MockitoExtension.class)
+class {{ModuleName}}ControllerTest {
+
+    @InjectMocks
+    private Object {{moduleName}}Controller;
+
+    @Mock
+    private Object {{moduleName}}Service;
+
+    /**
+     * 验证 Spring 上下文加载正常。
+     */
+    @Test
+    void contextLoads() {
+        assertNotNull({{moduleName}}Controller);
+    }
+
+    // 请按 API 契约补齐接口测试：
+    // - 正常请求返回 200 + 预期数据结构
+    // - 缺少必填参数返回 400
+    // - 未授权访问返回 401/403
+    // - 资源不存在返回 404
+}

package/templates/scaffolds/spring-boot/Mapper.xml.hbs

@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8" ?>
+<!DOCTYPE mapper PUBLIC "-//mybatis.org//DTD Mapper 3.0//EN"
+        "http://mybatis.org/dtd/mybatis-3-mapper.dtd">
+<!--
+  {{ModuleName}} Mapper — {{moduleName}} 表的 MyBatis XML 映射文件。
+  请按项目规范补齐查询方法与结果映射。
+-->
+<mapper namespace="{{basePackage}}.mapper.{{ModuleName}}Mapper">
+
+    <!-- 结果映射 -->
+    <resultMap id="BaseResultMap" type="{{basePackage}}.entity.{{ModuleName}}">
+        <!-- 请补齐字段映射 -->
+    </resultMap>
+
+    <!-- 按主键查询 -->
+    <select id="selectById" parameterType="long" resultMap="BaseResultMap">
+        SELECT * FROM {{table_name}} WHERE id = #{id}
+    </select>
+
+    <!-- 按条件分页查询 -->
+    <select id="selectByCondition" parameterType="map" resultMap="BaseResultMap">
+        SELECT * FROM {{table_name}}
+        <where>
+            <if test="status != null">AND status = #{status}</if>
+        </where>
+        ORDER BY id DESC
+    </select>
+
+</mapper>