npm - soloforge - Versions diffs - 1.1.36 → 1.1.38 - Mend

soloforge 1.1.36 → 1.1.38

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (847) hide show

package/templates/patterns//347/272/246/346/235/237/345/256/236/347/216/260/350/247/204/350/214/203.md CHANGED Viewed

@@ -11,8 +11,6 @@ asset_kind: pattern
 lifecycle_status: active
 owner_mechanism_id: mc-general-pattern
 authority: supporting
-routes:
-  - '*'
 primary_triggers:
   - 编码实现
   - 写代码

package/templates/patterns//347/274/223/345/255/230/347/255/226/347/225/245/350/247/204/350/214/203.md CHANGED Viewed

@@ -10,8 +10,6 @@ asset_kind: pattern
 lifecycle_status: active
 owner_mechanism_id: mc-backend-pattern
 authority: supporting
-routes:
-  - '*'
 primary_triggers:
   - 缓存策略
   - 缓存

package/templates/patterns//347/274/226/347/240/201/350/264/250/351/207/217/350/247/204/350/214/203.md CHANGED Viewed

@@ -11,8 +11,6 @@ asset_kind: pattern
 lifecycle_status: active
 owner_mechanism_id: mc-general-pattern
 authority: supporting
-routes:
-  - '*'
 primary_triggers:
   - 编码质量
   - 代码规范

package/templates/patterns//347/274/272/351/231/267/347/256/241/347/220/206/350/247/204/350/214/203.md CHANGED Viewed

@@ -11,8 +11,6 @@ asset_kind: pattern
 lifecycle_status: active
 owner_mechanism_id: mc-general-pattern
 authority: supporting
-routes:
-  - '*'
 primary_triggers:
   - 缺陷管理
   - Bug修复

package/templates/patterns//350/260/203/350/257/225/346/226/271/346/263/225/350/256/272.md CHANGED Viewed

@@ -11,8 +11,6 @@ asset_kind: pattern
 lifecycle_status: active
 owner_mechanism_id: mc-general-pattern
 authority: supporting
-routes:
-  - '*'
 primary_triggers:
   - 调试
   - debug

package/templates/patterns//350/276/223/345/205/245/346/240/241/351/252/214/350/247/204/350/214/203.md CHANGED Viewed

@@ -10,8 +10,6 @@ asset_kind: pattern
 lifecycle_status: active
 owner_mechanism_id: mc-backend-pattern
 authority: supporting
-routes:
-  - '*'
 primary_triggers:
   - 参数校验
   - 输入验证

package/templates/patterns//351/224/231/350/257/257/345/244/204/347/220/206/350/247/204/350/214/203.md CHANGED Viewed

@@ -10,8 +10,6 @@ asset_kind: pattern
 lifecycle_status: active
 owner_mechanism_id: mc-backend-pattern
 authority: supporting
-routes:
-  - '*'
 primary_triggers:
   - 异常处理
   - 错误处理

package/templates/patterns//351/224/231/350/257/257/350/276/271/347/225/214/350/247/204/350/214/203.md CHANGED Viewed

@@ -12,8 +12,6 @@ asset_kind: pattern
 lifecycle_status: active
 owner_mechanism_id: mc-frontend-pattern
 authority: supporting
-routes:
-  - '*'
 primary_triggers:
   - 错误边界
   - 错误处理

package/templates/patterns//351/242/206/345/237/237/351/251/261/345/212/250/350/256/276/350/256/241/350/247/204/350/214/203.md CHANGED Viewed

@@ -10,8 +10,6 @@ asset_kind: pattern
 lifecycle_status: active
 owner_mechanism_id: mc-backend-pattern
 authority: supporting
-routes:
-  - '*'
 primary_triggers:
   - 领域驱动设计
   - DDD

package/templates/procedures/OOD/350/256/276/350/256/241/345/267/245/344/275/234/346/265/201.md CHANGED Viewed

@@ -12,9 +12,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-ood-solid-contract
-routes:
-  - code_change
-  - artifact_generation
 primary_triggers:
   - OOD设计工作流
 secondary_triggers:

package/templates/procedures/Schema/345/217/230/346/233/264/346/265/201/346/260/264/347/272/277.md CHANGED Viewed

@@ -11,8 +11,6 @@ asset_kind: pipeline_procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-knowledge-asset-governance
-routes:
-  - code_change
 primary_triggers:
   - Schema变更流水线
 secondary_triggers: []
@@ -38,17 +36,17 @@ stages: ["编码与单元测试", "联调验证"]
 评估变更类型（加列/改列/删列/加索引/数据迁移/新建表）。确认向前兼容性（新列默认值或允许 NULL）。制定四层兼容策略（数据库→接口契约→前端展示→导出逻辑）。
 模版：数据库变更方案模版.md
 产出保存到：.soloforge/output/01-变更方案.md
-工具：sf_classify
+工具：sf_command
 ### 第2步：迁移脚本
 编写 migration 脚本（正向 + 回滚），确保幂等。大表加列使用分批更新策略。大表加索引使用 ONLINE DDL。禁止 migration 中写业务逻辑。
 产出保存到：.soloforge/output/02-migration.sql
-工具：sf_expand
+工具：sf_stage_execute
 ### 第3步：代码适配
 更新 Entity/DTO 映射。更新接口契约（请求/响应字段）。更新前端展示和表单。更新导出逻辑（如有）。更新相关测试数据和测试用例。
-工具：sf_expand
+工具：sf_stage_execute
 ### 第4步：验证验收
 开发环境执行 migration 验证表结构。运行全量测试。代码审查重点关注：四层兼容完整性、回滚脚本有效性、大表性能影响评估。
-工具：sf_verify, sf_review, sf_learn
+工具：sf_gate_check, sf_review, sf_stage_advance

package/templates/procedures//344/270/273/351/223/276/350/267/257/346/216/245/345/205/245/351/252/214/350/257/201/346/265/201/347/250/213.md CHANGED Viewed

@@ -9,8 +9,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-main-path-integration
-routes:
-  - code_change
 primary_triggers:
   - 主链路接入验证流程
 secondary_triggers: []

package/templates/procedures//344/273/243/347/240/201/351/227/250/347/246/201/346/265/201/347/250/213.md CHANGED Viewed

@@ -12,8 +12,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-guard-evaluation
-routes:
-  - code_change
 primary_triggers:
   - 代码门禁流程
 secondary_triggers: []

package/templates/procedures//344/273/273/345/212/241/346/213/206/350/247/243/346/265/201/347/250/213.md CHANGED Viewed

@@ -12,8 +12,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-intent-expander
-routes:
-  - code_change
 primary_triggers:
   - 任务拆解流程
 secondary_triggers: []

package/templates/procedures//344/274/232/350/257/235/346/201/242/345/244/215/346/265/201/347/250/213.md CHANGED Viewed

@@ -11,9 +11,6 @@ id: ka-procedure-会话恢复流程
 asset_kind: procedure
 lifecycle_status: active
 authority: supporting
-routes:
-  - code_change
-  - planning
 primary_triggers:
   - 会话恢复流程
 secondary_triggers:

package/templates/procedures//345/205/250/347/224/237/345/221/275/345/221/250/346/234/237/345/267/245/344/275/234/346/265/201/345/257/274/350/210/252.md CHANGED Viewed

@@ -12,7 +12,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-workflow-navigation-contract
-routes: ['operation', 'artifact_generation']
 primary_triggers:
   - 全生命周期工作流导航
 secondary_triggers:
@@ -106,7 +105,7 @@ stages: ["需求分析", "架构设计", "详细设计", "任务规划", "编码
 - 不得取消任务后直接写代码
 - 不得改用 Bash 绕过受控任务、设计复验或追踪矩阵
 - 不得手动删除 `.soloforge/state`
-- 若确认为陈旧任务，必须通过 `sf_status action=archive_stale confirm=true` 或导航推荐命令归档，再重新 `sf_classify -> sf_expand`
+- 若确认为陈旧任务，必须通过 `sf_status action=archive_stale confirm=true` 或导航推荐命令归档，再重新 `sf_command -> sf_stage_execute`
 ## 常见导航场景

package/templates/procedures//345/212/237/350/203/275/345/274/200/345/217/221/346/265/201/347/250/213.md CHANGED Viewed

@@ -12,8 +12,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-task-context-lifecycle
-routes:
-  - code_change
 primary_triggers:
   - 功能开发流程
 secondary_triggers: []

package/templates/procedures//345/220/216/347/253/257/346/216/245/345/217/243/345/256/236/347/216/260/345/267/245/344/275/234/346/265/201.md CHANGED Viewed

@@ -11,9 +11,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-backend-implementation-contract
-routes:
-  - code_change
-  - artifact_generation
 primary_triggers:
   - 后端接口实现工作流
 secondary_triggers:

package/templates/procedures//345/221/275/344/273/244/346/211/247/350/241/214/346/265/201/347/250/213.md CHANGED Viewed

@@ -9,8 +9,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-command-execution
-routes:
-  - code_change
 primary_triggers:
   - 命令执行流程
 secondary_triggers: []

package/templates/procedures//345/221/275/344/273/244/350/267/257/347/224/261/346/265/201/347/250/213.md ADDED Viewed

@@ -0,0 +1,38 @@
+---
+name: command-routing-workflow
+scope:
+  - '*'
+products:
+  - '*'
+id: ka-procedure-命令路由流程
+type: procedure
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+owner_mechanism_id: mc-command-router
+primary_triggers:
+  - 命令路由流程
+secondary_triggers: []
+negative_triggers: []
+priority: P1
+specificity: 5
+stages: ["任务规划", "编码与单元测试"]
+version: 1.0.0
+last_reviewed: '2026-06-02'
+---
+# 命令路由流程
+## 步骤
+1. 接收用户命令 (command)
+2. 状态机裁决命令类型和目标阶段
+3. 检查 command_state 是否有效
+4. 确定执行形状 (execution_shape)
+5. 如果 degraded=true，记录降级日志
+6. 传递给阶段执行器
+## 注意事项
+- 命令路由替代已废弃的意图路由
+- 快捷命令 (sf_direct_answer / sf_single_artifact) 绕过完整管线

package/templates/procedures//345/256/211/345/205/250/345/212/240/345/233/272/346/265/201/346/260/264/347/272/277.md CHANGED Viewed

@@ -12,8 +12,6 @@ asset_kind: pipeline_procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-privacy-boundary
-routes:
-  - code_change
 primary_triggers:
   - 安全加固流水线
 secondary_triggers: []
@@ -39,7 +37,7 @@ stages: ["编码与单元测试", "联调验证"]
 扫描现有代码和配置的安全漏洞（OWASP Top 10 维度）。检查认证授权机制的完整性。检查数据加密和脱敏策略。检查第三方依赖的已知漏洞。
 模版：安全审计模版.md
 产出保存到：.soloforge/output/01-安全审计.md
-工具：sf_classify, sf_analyze
+工具：sf_command, sf_analyze
 ### 第2步：方案设计
 按风险等级（Critical/High/Medium/Low）排序修复优先级。针对每个漏洞设计修复方案。评估修复对现有功能的影响。确定合规要求（数据加密/审计日志/访问控制）。
@@ -47,11 +45,11 @@ stages: ["编码与单元测试", "联调验证"]
 ### 第3步：安全修复
 按优先级逐个修复安全漏洞。每个修复后回归验证功能无影响。禁止降级安全等级来通过测试。
-工具：sf_expand
+工具：sf_stage_execute
 ### 第4步：验证验收
 重新扫描确认漏洞已修复。代码审查专注安全维度。学习记录（漏洞类型、修复模式、预防规则）。
-工具：sf_verify, sf_review, sf_learn
+工具：sf_gate_check, sf_review, sf_stage_advance
 ### 第5步：深度安全扫描
 运行依赖漏洞扫描（npm audit / OWASP Dependency-Check），高危漏洞阻断构建。运行容器镜像扫描（Trivy / Snyk），检测基础镜像已知漏洞。检查生产环境配置（禁用 debug 模式、关闭 actuator 暴露端点、验证 HTTPS 强制）。

package/templates/procedures//345/267/245/345/205/267/350/260/203/347/224/250/346/265/201/347/250/213.md CHANGED Viewed

@@ -9,8 +9,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-tool-invocation-contract
-routes:
-  - code_change
 primary_triggers:
   - 工具调用流程
 secondary_triggers: []

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

@@ -12,8 +12,6 @@ asset_kind: pipeline_procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-metric-governance
-routes:
-  - code_change
 primary_triggers:
   - 性能流水线
 secondary_triggers: []
@@ -39,7 +37,7 @@ stages: ["编码与单元测试", "联调验证"]
 量化性能指标（当前值/目标值）。定位瓶颈（慢查询/内存/CPU/网络/前端渲染）。收集证据（APM/慢查询日志/浏览器 DevTools/压测数据）。确定优化优先级（收益/成本排序）。
 模版：性能分析模版.md
 产出保存到：.soloforge/output/01-性能分析.md
-工具：sf_classify, sf_analyze
+工具：sf_command, sf_analyze
 ### 第2步：方案设计
 针对瓶颈设计优化方案（索引优化/SQL 重写/缓存/连接池/异步/分页/懒加载）。评估方案影响范围和风险。确定可衡量的优化目标。
@@ -47,8 +45,8 @@ stages: ["编码与单元测试", "联调验证"]
 ### 第3步：优化实施
 按优先级逐步实施，每步优化后重新测量性能指标。禁止一次改多处再测量。保持优化前后功能行为一致。
-工具：sf_expand
+工具：sf_stage_execute
 ### 第4步：效果验证
 对比优化前后的性能指标。全量测试确认无功能回归。代码审查关注：优化是否引入新问题、缓存一致性、并发安全。
-工具：sf_verify, sf_review, sf_learn
+工具：sf_gate_check, sf_review, sf_stage_advance

package/templates/procedures//346/204/217/345/233/276/350/267/257/347/224/261/346/265/201/347/250/213.md CHANGED Viewed

@@ -1,4 +1,6 @@
 ---
+deprecated: true
+deprecated_note: 此模板已由 mc-command-router (命令路由) 替代。保留仅为向后兼容。
 name: intent-routing-workflow
 scope:
   - '*'
@@ -8,9 +10,7 @@ id: ka-procedure-意图路由流程
 asset_kind: procedure
 lifecycle_status: active
 authority: supporting
-owner_mechanism_id: mc-intent-router
-routes:
-  - code_change
+owner_mechanism_id: mc-command-router
 primary_triggers:
   - 意图路由流程
 secondary_triggers: []

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

@@ -12,8 +12,6 @@ asset_kind: pipeline_procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-artifact-contract
-routes:
-  - code_change
 primary_triggers:
   - 接口集成流水线
 secondary_triggers: []
@@ -39,20 +37,20 @@ stages: ["编码与单元测试", "联调验证"]
 梳理第三方 API 能力清单（认证方式、请求/响应格式、错误码、限流配额、沙箱环境）。识别核心交互场景和数据映射关系。
 模版：接口对接方案模版.md
 产出保存到：.soloforge/output/01-接口对接方案.md
-工具：sf_classify
+工具：sf_command
 ### 第2步：适配层实现
 实现统一的 API 客户端封装（超时、重试、熔断、日志）。定义请求/响应 DTO 映射。配置 Mock 方案（沙箱/本地 Mock）支持独立开发。错误码映射为业务异常。
-工具：sf_expand, sf_scaffold
+工具：sf_stage_execute, sf_scaffold
 ### 第3步：联调测试
 使用 Mock 环境验证基本流程。切换到沙箱环境验证真实交互。覆盖：正常流程、网络超时、服务端错误、限流响应、数据格式异常。
 模版：测试计划模版.md
-工具：sf_verify
+工具：sf_gate_check
 ### 第4步：验收上线
 代码审查重点：超时配置、错误处理、敏感信息、日志脱敏。生产配置确认（URL、密钥、限流参数）。监控告警配置（调用成功率、响应时间）。
-工具：sf_review, sf_verify, sf_deliver
+工具：sf_review, sf_gate_check, sf_stage_advance
 ### 第5步：契约管理与监控增强
 定义接口契约（OpenAPI/Swagger），明确请求/响应格式、错误码、版本号。编写接口 Mock 服务，前后端并行开发。接口变更必须更新文档并通知消费方，给予充足迁移时间。集成测试覆盖正常流 + 异常流（超时、错误响应、边界值）。接口上线后配置监控告警（响应时间 P99、错误率、调用量）。

package/templates/procedures//346/225/260/346/215/256/345/272/223/350/277/201/347/247/273/346/265/201/347/250/213.md CHANGED Viewed

@@ -11,8 +11,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-knowledge-asset-governance
-routes:
-  - code_change
 primary_triggers:
   - 数据库迁移流程
 secondary_triggers: []

package/templates/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 CHANGED Viewed

@@ -39,8 +39,6 @@ id: ka-procedure-本地浏览器验收工作流
 asset_kind: procedure
 lifecycle_status: active
 authority: supporting
-routes:
-  - code_change
 primary_triggers:
   - 本地浏览器验收工作流
 secondary_triggers: []

package/templates/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 CHANGED Viewed

@@ -13,8 +13,6 @@ id: ka-procedure-architecture-decision-workshop
 asset_kind: procedure
 lifecycle_status: active
 authority: supporting
-routes:
-  - artifact_generation
 primary_triggers:
   - 架构决策研讨
 priority: P0

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

@@ -46,8 +46,6 @@ id: ka-procedure-架构设计工作流
 asset_kind: procedure
 lifecycle_status: active
 authority: supporting
-routes:
-  - code_change
 primary_triggers:
   - 架构设计工作流
 secondary_triggers: []

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

@@ -12,8 +12,6 @@ asset_kind: pipeline_procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-brainstorm-contract
-routes:
-  - code_change
 primary_triggers:
   - 概念验证流水线
 secondary_triggers: []
@@ -38,14 +36,14 @@ stages: ["架构设计"]
 ### 第1步：调研分析
 明确验证目标和成功标准。调研候选方案的生态成熟度、社区活跃度、性能基准、与现有技术栈兼容性。列出关键评估维度和权重。
 产出保存到：.soloforge/output/01-调研报告.md
-工具：sf_classify
+工具：sf_command
 ### 第2步：原型实现
 选择 1-2 个最有前景的方案实现最小原型。原型聚焦核心验证点，不追求完整功能。记录实现过程中的关键发现（坑、限制、惊喜）。
-工具：sf_expand, sf_scaffold
+工具：sf_stage_execute, sf_scaffold
 ### 第3步：评估结论
 对比各方案在关键维度的表现（附量化数据）。给出推荐方案和理由。列出遗留风险和后续关注点。明确结论：推荐采用/需进一步验证/不建议采用。
 模版：POC结论模版.md
 产出保存到：.soloforge/output/03-POC结论.md
-工具：sf_verify, sf_learn
+工具：sf_gate_check, sf_stage_advance

package/templates/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 CHANGED Viewed

@@ -39,8 +39,6 @@ id: ka-procedure-测试优先编码工作流
 asset_kind: procedure
 lifecycle_status: active
 authority: supporting
-routes:
-  - code_change
 primary_triggers:
   - 测试优先编码工作流
 secondary_triggers: []

package/templates/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 CHANGED Viewed

@@ -12,8 +12,6 @@ asset_kind: pipeline_procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-artifact-contract
-routes:
-  - code_change
 primary_triggers:
   - 源码原型交付流程
 secondary_triggers: []
@@ -57,8 +55,8 @@ stages: ["架构设计"]
 ### 第5步：编码实现
 根据切片计划和追踪矩阵绑定的 `SLICE-*`、`DD-*`、`AC-*` 进行前后端编码实现。可使用脚手架生成骨架代码。
-工具：sf_scaffold, sf_expand
+工具：sf_scaffold, sf_stage_execute
 ### 第6步：测试与审查验收
 执行自动验证（构建 + 测试）、代码审查（质量/安全/性能/架构/技术债务五维度）、学习记录。
-工具：sf_verify, sf_review, sf_learn
+工具：sf_gate_check, sf_review, sf_stage_advance

package/templates/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 CHANGED Viewed

@@ -45,8 +45,6 @@ id: ka-procedure-现有系统差距分析工作流
 asset_kind: procedure
 lifecycle_status: active
 authority: supporting
-routes:
-  - code_change
 primary_triggers:
   - 现有系统差距分析工作流
 secondary_triggers: []

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

@@ -12,8 +12,6 @@ asset_kind: pipeline_procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-knowledge-injection-boundary
-routes:
-  - code_change
 primary_triggers:
   - 知识维护流水线
 secondary_triggers: []
@@ -39,7 +37,7 @@ stages: ["需求分析", "架构设计", "详细设计", "任务规划", "编码
 工具：sf_knowledge_audit
 ### 第2步：知识新增
-根据审计结果和 sf_learn 积累的高频问题，生成新知识条目草稿。草稿保存到 .soloforge/knowledge/drafts/ 目录，人工 review 后移入正式目录。
+根据审计结果和 sf_stage_advance 积累的高频问题，生成新知识条目草稿。草稿保存到 .soloforge/knowledge/drafts/ 目录，人工 review 后移入正式目录。
 工具：sf_knowledge_add
 ### 第3步：知识更新
@@ -48,7 +46,7 @@ stages: ["需求分析", "架构设计", "详细设计", "任务规划", "编码
 ### 第4步：一致性验证
 重新构建知识索引，验证新增/更新条目可被正确匹配。运行全量测试确认无功能影响。更新设计文档中的知识规模统计。
-工具：sf_verify, sf_learn
+工具：sf_gate_check, sf_stage_advance
 ### 第5步：定期审计与质量控制
 定期审计知识库（每月），检查过期/重复/不准确的条目。新增知识条目必须经过 review 后才发布（草稿 → 审核 → 正式）。知识条目使用统计数据纳入监控，低使用率条目评估是否保留。知识条目格式必须符合规约（字段顺序、body 标题、when 风格），使用 sf_knowledge_audit 检查。

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

@@ -12,8 +12,6 @@ asset_kind: pipeline_procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-delivery-gate
-routes:
-  - code_change
 primary_triggers:
   - 紧急修复流水线
 secondary_triggers: []
@@ -38,21 +36,21 @@ stages: ["联调验证"]
 ### 第1步：故障定位
 确认问题影响范围和严重程度，通知相关干系人。评估止血方案（配置回滚/功能开关关闭/服务降级/版本回滚），执行止血操作。
 产出保存到：.soloforge/output/01-故障定位.md
-工具：sf_classify, sf_analyze
+工具：sf_command, sf_analyze
 ### 第2步：最小修复
 从 main/release 分支拉取 hotfix 分支。编写最小修复代码（仅修复问题，不重构不优化），快速验证修复场景 + 回归核心功能。
-工具：sf_expand, sf_verify
+工具：sf_stage_execute, sf_gate_check
 ### 第3步：验证部署
 合并到 main 和 release 分支，打 hotfix tag。部署到生产环境，验证修复效果，监控 30 分钟。
-工具：sf_verify, sf_deliver
+工具：sf_gate_check, sf_stage_advance
 ### 第4步：故障复盘
-编写事故复盘（根因、影响范围、修复过程、暴露的监控盲区、后续改进项）。与 sf_learn 配合形成闭环。
+编写事故复盘（根因、影响范围、修复过程、暴露的监控盲区、后续改进项）。与 sf_stage_advance 配合形成闭环。
 模版：故障复盘模版.md
 产出保存到：.soloforge/output/04-故障复盘.md
-工具：sf_learn
+工具：sf_stage_advance
 ### 第5步：验证与闭环
 确认修复影响范围，评估是否需要数据修复脚本。修复代码必须包含回归测试，防止相同问题复现。修复后执行冒烟测试验证关键路径。修复上线后持续观察 1 小时监控，确认无副作用。修复完成后编写故障复盘（根因、影响、修复、预防措施）。

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

@@ -9,8 +9,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-core-engineering-principles
-routes:
-  - code_change
 primary_triggers:
   - 编码前澄清流程
 secondary_triggers: []

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

@@ -12,8 +12,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-decision-sovereignty
-routes:
-  - code_change
 primary_triggers:
   - 自主选型流程
 secondary_triggers: []
@@ -45,7 +43,7 @@ stages: ["架构设计"]
 6. 输出方案边界声明: 如实告知推荐方案的天花板，不做糖衣炮弹
 7. A/B 决策诱导: 输出两个精确选项，禁止提问"你想怎么做"
 8. 等待人类决策: 输入"选 A"或"选 B"后进入自动编码模式
-9. 基于选定方案继续 sf_expand 流程
+9. 基于选定方案继续 sf_stage_execute 流程
 ## 检查点
 - [ ] 至少 3 个行业标准方案已检索

package/templates/procedures//350/256/276/350/256/241/344/272/247/347/211/251/347/224/237/346/210/220/344/270/216/345/244/215/351/252/214/345/267/245/344/275/234/346/265/201.md CHANGED Viewed

@@ -13,8 +13,6 @@ id: ka-procedure-design-artifact-pack
 asset_kind: procedure
 lifecycle_status: active
 authority: supporting
-routes:
-  - artifact_generation
 primary_triggers:
   - 设计产物包
 priority: P0