soloforge 1.2.19 → 1.3.0

package/templates/knowledge/procedures//346/236/266/346/236/204/350/256/276/350/256/241/345/267/245/344/275/234/346/265/201.md

@@ -0,0 +1,95 @@
+---
+name: architecture-design-workflow
+type: procedure
+when: '架构设计, 架构, architecture, 设计系统, 多端设计, 系统设计, 技术方案设计'
+scope:
+  - backend
+  - frontend
+  - infrastructure
+products:
+  - '*'
+owner_mechanism_id: mc-architecture-design
+consumed_contracts:
+  - architecture_design_contract_entry
+  - technology_decision_contract
+  - brainstorm_contract
+  - detail_discipline_contract
+  - first_principles_contract
+required_sections:
+  - 输入集确认
+  - 输出目录决策
+  - 技术栈策略
+  - 前端仓库策略
+  - 不确定项决策
+  - Mermaid 图要求
+  - 架构设计审查
+hard_rules:
+  - 输出目录名必须给推荐并进入用户确认；未确认时不得 delivered
+  - 后端必须默认优先 Java，除非存在项目证据或用户确认 override
+  - 前端必须默认优先最新稳定 Vue 生态 + TypeScript，除非存在项目证据或用户确认 override
+  - 不同前端端必须默认不同项目仓库或独立应用边界；合并仓库必须用户确认
+  - 不确定项必须包含推荐、理由、备选、风险和用户确认问题
+  - 架构级不确定项必须接 Brainstorm / Decision Sovereignty / User Confirmation
+  - 关键业务流程必须有 Mermaid sequenceDiagram
+  - Mermaid 必须可渲染
+acceptance_checks:
+  - ArchitectureDesignContract 已创建且 status 非 pending
+  - 输出目录决策 status 为 confirmed
+  - 所有 required_source_artifacts 已覆盖
+  - Mermaid 图 render_check_status 为 passed
+  - 架构设计审查 review.passed 为 true
+id: ka-procedure-架构设计工作流
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+routes:
+  - code_change
+primary_triggers:
+  - 架构设计工作流
+secondary_triggers: []
+negative_triggers: []
+priority: P1
+specificity: 5
+consumes:
+  - mc-intent-router
+emits:
+  - execution_result
+  - evidence
+required_evidence:
+  - workflow_id
+  - required_mechanisms
+version: 1.0.0
+last_reviewed: '2026-05-22'
+migration_note: 知识资产标准化迁移
+status: active
+---
+
+## 适用场景
+从多个 task 输入（原型说明、需求文档等）到完整架构设计产出的工作流。适用于多端、多模块、有不确定项的系统设计。
+
+## 步骤
+1. **输入集确认**: 识别所有 task-* 目录下的原型说明及需求文档，确认覆盖所有端
+2. **输出目录决策**: 给出推荐目录名，等待用户确认
+3. **技术栈策略**:
+   - 后端默认 Java 优先（项目证据或用户确认可 override）
+   - 前端默认最新稳定 Vue 生态 + TypeScript（语言、构建工具、路由、状态管理、接口类型、测试、lint/format）
+   - 项目已有技术栈优先于 SoloForge 默认
+4. **前端仓库策略**: 不同前端端默认不同仓库；合并仓库需用户确认
+5. **不确定项决策**: 每个不确定项包含推荐、理由、备选、风险和用户确认问题
+6. **架构级不确定项**: 接入 Brainstorm → Decision Sovereignty → User Confirmation
+7. **Mermaid 图**: 关键业务流程、登录鉴权、跨端协作、前后端交互、异步任务必须有 sequenceDiagram
+8. **架构设计审查**: reviewArchitectureDesign 验证所有硬规则通过
+
+## 检查点
+- [ ] 所有 task-* 输入已识别并覆盖
+- [ ] 输出目录已用户确认
+- [ ] 技术栈有项目证据或用户确认支撑
+- [ ] 不确定项全部有推荐和用户确认问题
+- [ ] Mermaid sequenceDiagram 覆盖关键流程
+- [ ] reviewArchitectureDesign passed
+
+## 禁止退化
+- 未确认目录不得 delivered
+- 缺少 Mermaid 图不得 completed
+- 架构级决策无 human gate 不得 approved
+- 模板章节缺失不得 completed

package/templates/knowledge/procedures//346/236/266/346/236/204/350/256/276/350/256/241/346/265/201/347/250/213.md

@@ -1,9 +1,36 @@
 ---
 name: architecture-design
 type: procedure
-when: 架构设计, 模块划分, 系统设计, 技术方案, 方案设计, architecture, 架构评审
-scope: [backend, frontend]
-products: ["*"]
+when: '架构设计, 模块划分, 系统设计, 技术方案, 方案设计, architecture, 架构评审'
+scope:
+  - backend
+  - frontend
+products:
+  - '*'
+id: ka-procedure-架构设计流程
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+owner_mechanism_id: mc-architecture-design
+routes:
+  - code_change
+primary_triggers:
+  - 架构设计流程
+secondary_triggers: []
+negative_triggers: []
+priority: P1
+specificity: 5
+consumes:
+  - mc-intent-router
+emits:
+  - execution_result
+  - evidence
+required_evidence:
+  - execution_evidence
+version: 1.0.0
+last_reviewed: '2026-05-22'
+migration_note: 知识资产标准化迁移
+status: active
 ---
 
 ## 适用场景

package/templates/knowledge/procedures//346/246/202/345/277/265/351/252/214/350/257/201/346/265/201/346/260/264/347/272/277.md

@@ -1,9 +1,36 @@
 ---
 name: poc-pipeline
 type: pipeline_procedure
-when: "技术验证, POC, 可行性验证, 技术选型, 技术调研, 原型验证, spike"
-scope: [backend, frontend]
-products: ["*"]
+when: '技术验证, POC, 可行性验证, 技术选型, 技术调研, 原型验证, spike'
+scope:
+  - backend
+  - frontend
+products:
+  - '*'
+id: ka-procedure-概念验证流水线
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+owner_mechanism_id: mc-brainstorm-contract
+routes:
+  - code_change
+primary_triggers:
+  - 概念验证流水线
+secondary_triggers: []
+negative_triggers: []
+priority: P1
+specificity: 5
+consumes:
+  - mc-intent-router
+emits:
+  - execution_result
+  - evidence
+required_evidence:
+  - execution_evidence
+version: 1.0.0
+last_reviewed: '2026-05-22'
+migration_note: 知识资产标准化迁移
+status: active
 ---
 
 # 技术验证管线

package/templates/knowledge/procedures//346/265/213/350/257/225/344/274/230/345/205/210/347/274/226/347/240/201/345/267/245/344/275/234/346/265/201.md

@@ -0,0 +1,91 @@
+---
+name: test-first-coding-workflow
+type: procedure
+when: '实现需求, 编码, 开发功能, 写代码, coding, test first, 测试优先, 先写测试'
+scope:
+  - backend
+  - frontend
+products:
+  - '*'
+owner_mechanism_id: mc-coding-readiness
+consumed_contracts:
+  - coding_readiness_contract_entry
+  - existing_system_analysis_contract_entry
+  - architecture_design_contract_entry
+  - detail_discipline_contract
+  - first_principles_contract
+required_sections:
+  - 编码准备门
+  - 测试优先计划
+  - 约束消费报告
+  - 主线消费检查
+  - 编码完成审查
+hard_rules:
+  - coding workflow 不得直接进入实现
+  - 必须先生成 CodingReadinessGate
+  - 必须先生成 TestFirstPlan 或合法 not_applicable_with_reason
+  - 有测试框架且行为可断言时，必须先写失败测试或回归测试
+  - readiness_status=blocked/manual_required 时不得写实现代码
+  - 现有项目新需求必须消费 ExistingSystemAnalysis 和 RequirementGapAnalysis
+  - 根据架构设计编码时必须消费 ArchitectureDesignContract
+  - 测试失败不得删除测试、降低断言、skip 后声称通过
+acceptance_checks:
+  - CodingReadinessGate status 非 blocked
+  - TestFirstPlan 已创建且 status 为 written 或 expected_failure_recorded
+  - 约束消费报告无 blocking_missing_constraints
+  - 主线消费检查无 orphan_findings
+  - 编码完成审查 review.passed 为 true
+id: ka-procedure-测试优先编码工作流
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+routes:
+  - code_change
+primary_triggers:
+  - 测试优先编码工作流
+secondary_triggers: []
+negative_triggers: []
+priority: P1
+specificity: 5
+consumes:
+  - mc-intent-router
+emits:
+  - execution_result
+  - evidence
+required_evidence:
+  - workflow_id
+  - required_mechanisms
+version: 1.0.0
+last_reviewed: '2026-05-22'
+migration_note: 知识资产标准化迁移
+status: active
+---
+
+## 适用场景
+任何编码实现前必须先通过编码准备门和测试优先计划。适用于有测试框架和可断言业务逻辑的项目。
+
+## 步骤
+1. **编码准备门**:
+   - 检查是否有验证计划 (verification_plan_ref)
+   - 检查前置条件（现有项目需差距分析，架构设计需 ArchitectureDesignContract）
+   - 检查约束消费
+2. **测试优先计划**:
+   - 有测试框架且行为可断言 → test_first（先写失败测试）
+   - 不能自动测试 → verification_case_first 或 manual_acceptance_first
+   - TestFirstPlan 绑定需求、主链路入口和验收标准
+3. **编码实现**: 按 TestFirstPlan 先写测试、再写实现
+4. **主线消费检查**: 新增文件、组件、API、service 被真实消费
+5. **编码完成审查**: reviewCodingCompletion 验证所有硬规则
+
+## 检查点
+- [ ] CodingReadinessGate allowed
+- [ ] TestFirstPlan status 为 written
+- [ ] 约束消费无 blocking_missing
+- [ ] 主线消费无 orphan
+- [ ] 编码完成审查 passed
+
+## 禁止退化
+- 缺验证计划不得编码
+- blocked/manual_required 不得写实现代码
+- 测试失败不得删测试或降断言
+- 未消费前置条件不得编码

package/templates/knowledge/procedures//346/272/220/347/240/201/345/216/237/345/236/213/344/272/244/344/273/230/346/265/201/347/250/213.md

@@ -1,9 +1,36 @@
 ---
 name: source-prototype-to-delivery
 type: pipeline_procedure
-when: "用户提供需求文档、原型源码"
-scope: [backend, frontend]
-products: ["*"]
+when: 用户提供需求文档、原型源码
+scope:
+  - backend
+  - frontend
+products:
+  - '*'
+id: ka-procedure-源码原型交付流程
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+owner_mechanism_id: mc-artifact-contract
+routes:
+  - code_change
+primary_triggers:
+  - 源码原型交付流程
+secondary_triggers: []
+negative_triggers: []
+priority: P1
+specificity: 5
+consumes:
+  - mc-intent-router
+emits:
+  - execution_result
+  - evidence
+required_evidence:
+  - execution_evidence
+version: 1.0.0
+last_reviewed: '2026-05-22'
+migration_note: 知识资产标准化迁移
+status: active
 ---
 
 # 源码原型需求到交付

package/templates/knowledge/procedures//347/216/260/346/234/211/347/263/273/347/273/237/345/267/256/350/267/235/345/210/206/346/236/220/345/267/245/344/275/234/346/265/201.md

@@ -0,0 +1,97 @@
+---
+name: existing-system-gap-analysis-workflow
+type: procedure
+when: '现有项目, 新需求, 已有系统, 现有系统, 差距分析, gap analysis, existing system, 现有源码'
+scope:
+  - backend
+  - frontend
+  - infrastructure
+products:
+  - '*'
+owner_mechanism_id: mc-existing-system-analysis
+consumed_contracts:
+  - existing_system_analysis_contract_entry
+  - architecture_design_contract_entry
+  - technology_decision_contract
+  - brainstorm_contract
+  - detail_discipline_contract
+  - first_principles_contract
+required_sections:
+  - 项目上下文检测
+  - 现有系统分析
+  - 需求差距分析
+  - 主线集成计划
+  - 验证计划
+hard_rules:
+  - >-
+    existing_system + new_requirement 必须先生成 ExistingSystemAnalysisContract 和
+    RequirementGapAnalysis
+  - new_system / empty_project 不得强制执行 ExistingSystemAnalysis
+  - unknown 必须 manual_required，不能猜测继续
+  - 现有系统分析必须读取真实代码和相关文档，不能只读需求文档
+  - >-
+    分析结论必须区分 fact / inference / assumption / unknown，并带 confidence 和
+    evidence_refs
+  - 差距分析必须列出现有能力、缺失能力、复用模块、required_changes、兼容/数据/权限/集成风险
+  - 实现前必须有 MainlineIntegrationPlan
+  - VerificationPlan 必须从 RequirementGapAnalysis 生成
+acceptance_checks:
+  - project_context_type 已检测且非 unknown
+  - ExistingSystemAnalysisContract 已创建
+  - RequirementGapAnalysis 已创建
+  - 现有项目已有技术栈和项目约定优先于 SoloForge 默认
+  - 分析结论包含 fact/inference/assumption/unknown 分类
+id: ka-procedure-现有系统差距分析工作流
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+routes:
+  - code_change
+primary_triggers:
+  - 现有系统差距分析工作流
+secondary_triggers: []
+negative_triggers: []
+priority: P1
+specificity: 5
+consumes:
+  - mc-intent-router
+emits:
+  - execution_result
+  - evidence
+required_evidence:
+  - workflow_id
+  - required_mechanisms
+version: 1.0.0
+last_reviewed: '2026-05-22'
+migration_note: 知识资产标准化迁移
+status: active
+---
+
+## 适用场景
+已有源码、路由、API、前端页面、权限模型和测试脚本的项目中开发新需求。必须先分析现有系统、再做差距分析、最后才进入设计或编码。
+
+## 步骤
+1. **项目上下文检测**: detectProjectContext 判断 project_context_type
+2. **现有系统分析**:
+   - 读取真实代码和相关文档
+   - 识别技术栈、路由、API、前端页面、权限模型、测试脚本
+   - 区分 fact / inference / assumption / unknown
+3. **需求差距分析**:
+   - 列出现有能力、缺失能力、复用模块
+   - 列出 required_changes、optional_changes、out_of_scope
+   - 列出兼容/数据/权限/集成风险、前后端影响、测试回归范围
+4. **主线集成计划**: 新增文件、组件、API、service、DTO/model、配置必须被真实消费
+5. **验证计划**: VerificationPlan 从 RequirementGapAnalysis 生成
+
+## 检查点
+- [ ] project_context_type 已检测
+- [ ] 现有系统分析读取了真实代码
+- [ ] 差距分析包含完整风险列表
+- [ ] MainlineIntegrationPlan 已创建
+- [ ] VerificationPlan 已从差距分析生成
+
+## 禁止退化
+- existing_system 未分析不得进入设计或编码
+- unknown 类型不得猜测继续，必须 manual_required
+- 不能只读需求文档，必须读代码
+- 缺差距分析不得 coding

package/templates/knowledge/procedures//347/237/245/350/257/206/347/273/264/346/212/244/346/265/201/346/260/264/347/272/277.md

@@ -1,9 +1,36 @@
 ---
 name: knowledge-maintenance-pipeline
 type: pipeline_procedure
-when: "知识维护, 知识更新, 知识审计, 新增知识, 知识库维护, SoloForge维护"
-scope: [backend, frontend]
-products: ["*"]
+when: '知识维护, 知识更新, 知识审计, 新增知识, 知识库维护, SoloForge维护'
+scope:
+  - backend
+  - frontend
+products:
+  - '*'
+id: ka-procedure-知识维护流水线
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+owner_mechanism_id: mc-knowledge-injection-boundary
+routes:
+  - code_change
+primary_triggers:
+  - 知识维护流水线
+secondary_triggers: []
+negative_triggers: []
+priority: P1
+specificity: 5
+consumes:
+  - mc-intent-router
+emits:
+  - execution_result
+  - evidence
+required_evidence:
+  - execution_evidence
+version: 1.0.0
+last_reviewed: '2026-05-22'
+migration_note: 知识资产标准化迁移
+status: active
 ---
 
 # 知识维护管线

package/templates/knowledge/procedures//347/264/247/346/200/245/344/277/256/345/244/215/346/265/201/346/260/264/347/272/277.md

@@ -1,9 +1,36 @@
 ---
 name: hotfix-pipeline
 type: pipeline_procedure
-when: "紧急修复管线, 生产事故处理管线, P0管线, 热修复管线, hotfix pipeline, 线上故障管线"
-scope: [backend, frontend]
-products: ["*"]
+when: '紧急修复管线, 生产事故处理管线, P0管线, 热修复管线, hotfix pipeline, 线上故障管线'
+scope:
+  - backend
+  - frontend
+products:
+  - '*'
+id: ka-procedure-紧急修复流水线
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+owner_mechanism_id: mc-delivery-gate
+routes:
+  - code_change
+primary_triggers:
+  - 紧急修复流水线
+secondary_triggers: []
+negative_triggers: []
+priority: P1
+specificity: 5
+consumes:
+  - mc-intent-router
+emits:
+  - execution_result
+  - evidence
+required_evidence:
+  - execution_evidence
+version: 1.0.0
+last_reviewed: '2026-05-22'
+migration_note: 知识资产标准化迁移
+status: active
 ---
 
 # 紧急修复管线

package/templates/knowledge/procedures//347/264/247/346/200/245/344/277/256/345/244/215/346/265/201/347/250/213.md

@@ -1,9 +1,36 @@
 ---
 name: hotfix-procedure
 type: procedure
-when: 紧急修复, hotfix, 线上问题修复, 线上报错, 紧急上线, P0, P1, 事故修复, 止血
-scope: [backend, frontend]
-products: ["*"]
+when: '紧急修复, hotfix, 线上问题修复, 线上报错, 紧急上线, P0, P1, 事故修复, 止血'
+scope:
+  - backend
+  - frontend
+products:
+  - '*'
+id: ka-procedure-紧急修复流程
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+owner_mechanism_id: mc-delivery-gate
+routes:
+  - code_change
+primary_triggers:
+  - 紧急修复流程
+secondary_triggers: []
+negative_triggers: []
+priority: P1
+specificity: 5
+consumes:
+  - mc-intent-router
+emits:
+  - execution_result
+  - evidence
+required_evidence:
+  - execution_evidence
+version: 1.0.0
+last_reviewed: '2026-05-22'
+migration_note: 知识资产标准化迁移
+status: active
 ---
 
 ## 适用场景

package/templates/knowledge/procedures//347/274/226/347/240/201/345/211/215/346/276/204/346/270/205/346/265/201/347/250/213.md

@@ -1,3 +1,36 @@
+---
+name: 编码前澄清流程
+scope:
+  - '*'
+products:
+  - '*'
+id: ka-procedure-编码前澄清流程
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+owner_mechanism_id: mc-coding-readiness
+routes:
+  - code_change
+primary_triggers:
+  - 编码前澄清流程
+secondary_triggers: []
+negative_triggers: []
+priority: P1
+specificity: 5
+consumes:
+  - mc-intent-router
+emits:
+  - execution_result
+  - evidence
+required_evidence:
+  - execution_evidence
+version: 1.0.0
+last_reviewed: '2026-05-22'
+migration_note: 知识资产标准化迁移
+type: pipeline_procedure
+when: 编码前澄清流程
+status: active
+---
 # 编码前澄清流程
 
 ## 适用场景

package/templates/knowledge/procedures//347/274/272/351/231/267/344/277/256/345/244/215/346/265/201/346/260/264/347/272/277.md

@@ -1,9 +1,36 @@
 ---
 name: bug-fix-pipeline
 type: pipeline_procedure
-when: "缺陷修复, Bug修复, 问题修复, 异常修复, 错误修复, bug fix, 缺陷处理"
-scope: [backend, frontend]
-products: ["*"]
+when: '缺陷修复, Bug修复, 问题修复, 异常修复, 错误修复, bug fix, 缺陷处理'
+scope:
+  - backend
+  - frontend
+products:
+  - '*'
+id: ka-procedure-缺陷修复流水线
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+owner_mechanism_id: mc-verifier
+routes:
+  - code_change
+primary_triggers:
+  - 缺陷修复流水线
+secondary_triggers: []
+negative_triggers: []
+priority: P1
+specificity: 5
+consumes:
+  - mc-intent-router
+emits:
+  - execution_result
+  - evidence
+required_evidence:
+  - execution_evidence
+version: 1.0.0
+last_reviewed: '2026-05-22'
+migration_note: 知识资产标准化迁移
+status: active
 ---
 
 # 缺陷修复管线

package/templates/knowledge/procedures//350/207/252/344/270/273/351/200/211/345/236/213/346/265/201/347/250/213.md

@@ -1,9 +1,36 @@
 ---
 name: autonomous-tech-selection
 type: procedure
-when: 技术选型, 不知道用什么, 选型, 方案对比, 架构选型, 方案选择, 技术方案
-scope: [backend, frontend]
-products: ["*"]
+when: '技术选型, 不知道用什么, 选型, 方案对比, 架构选型, 方案选择, 技术方案'
+scope:
+  - backend
+  - frontend
+products:
+  - '*'
+id: ka-procedure-自主选型流程
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+owner_mechanism_id: mc-decision-sovereignty
+routes:
+  - code_change
+primary_triggers:
+  - 自主选型流程
+secondary_triggers: []
+negative_triggers: []
+priority: P1
+specificity: 5
+consumes:
+  - mc-intent-router
+emits:
+  - execution_result
+  - evidence
+required_evidence:
+  - execution_evidence
+version: 1.0.0
+last_reviewed: '2026-05-22'
+migration_note: 知识资产标准化迁移
+status: active
 ---
 
 ## 适用场景

package/templates/knowledge/procedures//350/257/246/347/273/206/350/256/276/350/256/241/346/265/201/347/250/213.md

@@ -1,9 +1,36 @@
 ---
 name: detailed-design
 type: procedure
-when: 详细设计, 接口设计, 数据库设计, DDL设计, 类设计, 详细方案, detailed design
-scope: [backend, frontend]
-products: ["*"]
+when: '详细设计, 接口设计, 数据库设计, DDL设计, 类设计, 详细方案, detailed design'
+scope:
+  - backend
+  - frontend
+products:
+  - '*'
+id: ka-procedure-详细设计流程
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+owner_mechanism_id: mc-architecture-design
+routes:
+  - code_change
+primary_triggers:
+  - 详细设计流程
+secondary_triggers: []
+negative_triggers: []
+priority: P1
+specificity: 5
+consumes:
+  - mc-intent-router
+emits:
+  - execution_result
+  - evidence
+required_evidence:
+  - execution_evidence
+version: 1.0.0
+last_reviewed: '2026-05-22'
+migration_note: 知识资产标准化迁移
+status: active
 ---
 
 ## 适用场景