soloforge 1.2.20 → 1.3.1

package/templates/knowledge/procedures//346/200/247/350/203/275/346/265/201/346/260/264/347/272/277.md

@@ -1,9 +1,36 @@
 ---
 name: performance-pipeline
 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-metric-governance
+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/204/217/345/233/276/350/267/257/347/224/261/346/265/201/347/250/213.md

@@ -1,3 +1,37 @@
+---
+name: 意图路由流程
+scope:
+  - '*'
+products:
+  - '*'
+id: ka-procedure-意图路由流程
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+owner_mechanism_id: mc-intent-router
+routes:
+  - code_change
+primary_triggers:
+  - 意图路由流程
+secondary_triggers: []
+negative_triggers: []
+priority: P1
+specificity: 5
+consumes:
+  - mc-classifier
+emits:
+  - execution_result
+  - evidence
+required_evidence:
+  - route_decision
+  - execution_shape
+version: 1.0.0
+last_reviewed: '2026-05-22'
+migration_note: 知识资产标准化迁移
+type: pipeline_procedure
+when: 意图路由流程
+status: active
+---
 # 意图路由流程
 
 ## 步骤

package/templates/knowledge/procedures//346/216/245/345/217/243/351/233/206/346/210/220/346/265/201/346/260/264/347/272/277.md

@@ -1,9 +1,36 @@
 ---
 name: api-integration-pipeline
 type: pipeline_procedure
-when: "第三方接口对接, 外部服务集成, API集成, 接口联调, 服务对接, 第三方API"
-scope: [backend, frontend]
-products: ["*"]
+when: '第三方接口对接, 外部服务集成, API集成, 接口联调, 服务对接, 第三方API'
+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//346/225/260/346/215/256/345/272/223/350/277/201/347/247/273/346/265/201/347/250/213.md

@@ -1,9 +1,35 @@
 ---
 name: database-migration
 type: procedure
-when: 数据库变更, 表结构修改, migration, DDL, 加字段, 建表, 索引, 数据迁移, 表结构变更
-scope: [backend]
-products: ["*"]
+when: '数据库变更, 表结构修改, migration, DDL, 加字段, 建表, 索引, 数据迁移, 表结构变更'
+scope:
+  - backend
+products:
+  - '*'
+id: ka-procedure-数据库迁移流程
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+owner_mechanism_id: mc-knowledge-asset-governance
+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/234/254/345/234/260/346/265/217/350/247/210/345/231/250/351/252/214/346/224/266/345/267/245/344/275/234/346/265/201.md

@@ -0,0 +1,99 @@
+---
+name: local-browser-acceptance-workflow
+type: procedure
+when: '本地验收, 浏览器验收, Docker 验收, 本地测试, local acceptance, browser test, docker compose'
+scope:
+  - backend
+  - frontend
+  - infrastructure
+products:
+  - '*'
+owner_mechanism_id: mc-local-acceptance
+consumed_contracts:
+  - local_acceptance_contract_entry
+  - coding_readiness_contract_entry
+  - detail_discipline_contract
+required_sections:
+  - 服务运行规格
+  - 浏览器验收计划
+  - 修复循环策略
+  - 最终访问交付
+hard_rules:
+  - 有可运行前端/全栈服务时，不得只停在单测、静态检查或审查报告
+  - 项目已有 docker-compose 时必须优先使用
+  - 必须识别 frontend、backend、database、env、ports 和 health checks
+  - 服务启动后必须等待 container healthy、backend health、frontend reachable
+  - >-
+    浏览器验收失败必须 capture → classify → map owner → repair → rebuild → redeploy →
+    rerun
+  - 最终必须给用户本地可访问 URL、运行状态、启动/停止命令
+  - 未给最终本地 URL 不得 delivered
+acceptance_checks:
+  - requiresLocalAcceptance 判断正确
+  - ServiceRuntimeSpec 已识别所有服务
+  - 浏览器验收计划覆盖任务相关页面和路由
+  - 修复循环策略包含 max_iterations 和 stop_conditions
+  - FinalLocalReviewAccess 包含 frontend_urls/backend_urls/docs_or_swagger_urls
+  - validateFinalAccess passed
+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
+---
+
+## 适用场景
+含前端/全栈服务的项目完成开发后，必须在本地启动服务并通过浏览器验收。适用于有 docker-compose、npm start 或类似启动方式的项目。
+
+## 步骤
+1. **判断是否需要本地验收**: requiresLocalAcceptance 判断
+2. **服务运行规格**:
+   - 识别 frontend、backend、database/cache、env、ports、health checks
+   - docker-compose 优先，否则用项目启动命令
+3. **启动服务**:
+   - 启动所有服务
+   - 等待 container healthy、backend health endpoint、frontend reachable、DB migrated
+   - 检查 logs 无关键错误、port open
+4. **浏览器验收**:
+   - 覆盖任务相关页面、路由、核心交互
+   - API 联动、登录/权限、错误提示、空状态/loading
+   - 检查控制台关键错误和 network 关键失败
+5. **失败处理** (修复循环):
+   - capture failure → classify failure → map owner files
+   - repair within scope → rebuild → redeploy → rerun
+   - retry budget 内循环；超预算 → manual_required
+6. **最终交付**:
+   - 给用户 frontend/backend/docs/swagger 本地 URL
+   - 给用户运行状态、启动/停止命令、测试账号说明、人工查验步骤、未覆盖风险
+
+## 检查点
+- [ ] requiresLocalAcceptance 判断正确
+- [ ] 所有服务启动且 healthy
+- [ ] 浏览器验收覆盖关键页面
+- [ ] 修复循环有预算和停止条件
+- [ ] 最终 URL 交付完整
+
+## 禁止退化
+- 不得只停在单测或审查报告
+- 无 URL 不得 delivered
+- CI 环境无 Docker 时 not_applicable_with_reason，但不能把 runnable 项目判为 delivered
+- retry budget 超出或 scope 不足必须 manual_required

package/templates/knowledge/procedures//346/236/266/346/236/204/345/206/263/347/255/226/347/240/224/350/256/250/345/267/245/344/275/234/346/265/201.md

@@ -0,0 +1,51 @@
+---
+name: architecture-decision-workshop
+type: procedure
+when: '架构设计, 技术架构, 系统设计, 平台建设, 服务拆分'
+scope:
+  - backend
+  - frontend
+  - infrastructure
+products:
+  - '*'
+owner_mechanism_id: mc-architecture-decision-workshop
+id: ka-procedure-architecture-decision-workshop
+asset_kind: procedure
+lifecycle_status: active
+authority: canonical
+routes:
+  - artifact_generation
+primary_triggers:
+  - 架构决策研讨
+priority: P0
+specificity: 5
+version: 1.0.0
+last_reviewed: '2026-05-25'
+required_evidence:
+  - architecture_decision_workshop
+  - user_confirmation_ref
+consumes:
+  - user_intent
+  - project_context_detection
+  - existing_system_analysis
+emits:
+  - architecture_decision_workshop
+  - docs/architecture/00-架构决策记录.md
+status: active
+---
+
+# 架构决策研讨工作流
+
+## 顺序
+
+1. 判断项目为现有系统、新系统、空项目或重构升级。
+2. 现有系统先获取现状与差距证据；空项目先确认业务目标和约束。
+3. 默认按业务流程、数据、安全、后端、前端、基础设施逐域讨论。
+4. 每域提供方案、推荐、风险与需要确认的问题；确认后记录 decision ref。
+5. 全部必要域确认后生成 `docs/architecture/00-架构决策记录.md`。
+6. 仅以该决策记录驱动正式架构设计与设计产物包。
+
+## 失败处理
+
+- 缺证据、缺确认或决策返工时，停止生成正式文档并说明下一项待决事项。
+- 不得用模板默认值或模型偏好替代项目事实与用户决定。

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,104 @@
+---
+name: architecture-design-workflow
+type: procedure
+when: '架构设计, 架构, architecture, 设计系统, 多端设计, 系统设计, 技术方案设计'
+scope:
+  - backend
+  - frontend
+  - infrastructure
+products:
+  - '*'
+owner_mechanism_id: mc-architecture-design
+consumed_contracts:
+  - architecture_decision_workshop_contract
+  - design_artifact_pack_contract
+  - architecture_design_contract_entry
+  - technology_decision_contract
+  - brainstorm_contract
+  - detail_discipline_contract
+  - first_principles_contract
+required_sections:
+  - 输入集确认
+  - 输出目录决策
+  - 技术栈策略
+  - 前端仓库策略
+  - 不确定项决策
+  - Mermaid 图要求
+  - 架构设计审查
+hard_rules:
+  - 正式架构设计前必须完成六类架构决策研讨并引用用户确认的决策记录
+  - 架构设计必须进入包含数据库、API、OpenAPI/SQL 和一致性报告的设计产物包复验流程
+  - 输出目录名必须给推荐并进入用户确认；未确认时不得 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. **架构决策研讨**: 逐域闭合业务流程、数据、安全、后端、前端和基础设施决策，生成 `00-架构决策记录.md`
+3. **输出目录决策**: 给出推荐目录名，等待用户确认
+4. **技术栈策略**:
+   - 后端默认 Java 优先（项目证据或用户确认可 override）
+   - 前端默认最新稳定 Vue 生态 + TypeScript（语言、构建工具、路由、状态管理、接口类型、测试、lint/format）
+   - 项目已有技术栈优先于 SoloForge 默认
+5. **前端仓库策略**: 不同前端端默认不同仓库；合并仓库需用户确认
+6. **不确定项决策**: 每个不确定项包含推荐、理由、备选、风险和用户确认问题
+7. **架构级不确定项**: 接入 Brainstorm → Decision Sovereignty → User Confirmation
+8. **设计产物包**: 架构、数据库、API、OpenAPI/SQL 和一致性报告按权威来源联动生成/升级
+9. **Mermaid 图**: 关键业务流程、登录鉴权、跨端协作、前后端交互、异步任务必须有 sequenceDiagram
+10. **架构设计审查**: reviewArchitectureDesign 与 DesignArtifactPack 真实复验通过
+
+## 检查点
+- [ ] 所有 task-* 输入已识别并覆盖
+- [ ] 六类架构决策均已确认并记录 decision refs
+- [ ] 输出目录已用户确认
+- [ ] 技术栈有项目证据或用户确认支撑
+- [ ] 不确定项全部有推荐和用户确认问题
+- [ ] Mermaid sequenceDiagram 覆盖关键流程
+- [ ] reviewArchitectureDesign passed
+- [ ] 设计产物包进入 implementation_ready
+
+## 禁止退化
+- 未确认目录不得 delivered
+- 缺少 Mermaid 图不得 completed
+- 六类决策未确认或设计产物包未复验不得 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
 ---
 
 # 源码原型需求到交付