soloforge 1.1.36 → 1.1.38

package/templates/procedures//350/256/276/350/256/241/345/256/241/350/256/241/346/265/201/347/250/213.md

@@ -0,0 +1,184 @@
+---
+name: audit-design-procedure
+type: procedure
+when: '设计审计, 详细设计审计, 架构审计, 设计审核, 审核设计, audit design, design audit, 接口审计'
+scope:
+  - backend
+  - frontend
+  - infrastructure
+products:
+  - '*'
+id: ka-procedure-设计审计流程
+asset_kind: procedure
+lifecycle_status: active
+authority: supporting
+owner_mechanism_id: mc-intent-expander
+stages: ["代码审查"]
+primary_triggers:
+  - 设计审计
+  - 详细设计审计
+secondary_triggers:
+  - 设计审核
+  - 审核设计
+  - 架构审计
+negative_triggers: []
+priority: P2
+specificity: 5
+consumes:
+  - mc-command-router
+  - mc-knowledge-injection-boundary
+  - mc-intent-expander
+emits:
+  - audit_report
+pipeline_scope:
+  - new-system
+  - existing-system
+applicable_tech_stack:
+  - '*'
+---
+
+# 设计审计流程
+
+> **wf-audit-design** 工作流的执行流程契约。
+> 适用场景: 用户对已有设计文档（架构/详细/API/数据库设计）做 6 维度审计，**不修改源文档**。
+> 关联工具: `sf_review` (input_artifacts 模式) / `sf_stage_execute` (audit_design_prompt)。
+
+---
+
+## 1. 触发条件
+
+### 1.1 用户意图识别
+满足以下任一条件进入审计工作流:
+- 意图包含关键词: `审计` / `审核设计` / `设计审计` / `设计审核` / `架构审计` / `详细设计审计` / `audit design`
+- 调用 `sf_review` 时显式传入 `input_artifacts` 参数
+
+### 1.2 前置条件
+- 用户必须指定至少一个 `input_artifacts` 条目（kind + path）
+- 引用的设计文档必须存在于磁盘
+- 路由层推断 `mutation_allowed = false`（审计严格只读）
+
+---
+
+## 2. 6 维度审计清单
+
+每维度必须给出至少 1 条 finding，或显式标记 `no_issue_observed`。**未覆盖即失败**。
+
+### 维度 1: 跨文档一致性
+- 架构文档 / 详细设计 / API 设计 / 数据库设计 命名、边界、调用链是否一致
+- 同一概念是否在不同文档中使用不同名称
+- 接口契约（参数 / 返回 / 异常）在 API 文档与详细设计中是否完全一致
+
+### 维度 2: OOD/SOLID 合规
+- 单一职责: 模块 / 类 / 函数边界是否清晰
+- 开闭原则: 扩展点是否通过抽象隔离
+- 依赖倒置: 高层模块是否依赖抽象而非具体实现
+- 命名 / 分层是否反映职责
+
+### 维度 3: 防孤岛设计
+- 新模块与现有系统的集成点是否明确
+- 是否定义了与上游（消费者）和下游（依赖）的契约
+- 跨团队 / 跨服务协作边界是否清晰
+
+### 维度 4: 契约破坏性
+- 新设计是否破坏已有 API / 事件 / 数据契约
+- 版本兼容性: 是否有 deprecation 路径
+- 客户端 / 调用方升级成本是否评估
+
+### 维度 5: SQL/数据迁移回滚性
+- DDL 是否可回滚（DROP / ALTER 必须有 rollback 脚本）
+- 数据迁移是否可在中断后恢复
+- 是否定义了数据回滚检查点
+- 是否区分可逆 / 不可逆变更（DELETE 无回滚需特别标注）
+
+### 维度 6: 索引/性能覆盖
+- 主链路查询是否有索引支撑
+- 是否评估了 N+1、全表扫描、热点行更新风险
+- 分页 / 排序字段是否有联合索引
+
+---
+
+## 3. 严重度分级
+
+| 级别 | 含义 | 是否阻塞实施 |
+|------|------|--------------|
+| `hard_fail` | 设计错误 / 破坏性变更 / 数据丢失风险 | 是 |
+| `warning` | 建议修改，存在风险但不致命 | 否（建议修复） |
+| `advisory` | 供参考的改进建议 | 否（仅供参考） |
+
+---
+
+## 4. 输出契约 (audit_report)
+
+```typescript
+interface AuditReport {
+  dimensions: Array<{
+    name: string;                       // "跨文档一致性" | "OOD/SOLID" | ...
+    findings: Array<{
+      severity: "hard_fail" | "warning" | "advisory";
+      location: string;                 // 文档路径 + 章节/行号
+      issue_zh: string;                 // 中文问题描述
+      recommendation_zh: string;        // 中文修复建议
+    }> | Array<{ no_issue_observed: true; note_zh: string }>;
+  }>;
+  overall_status: "blocked" | "advisory";
+  blocking_findings_count: number;      // severity=hard_fail 的总数
+  input_artifacts: Array<{ kind: string; path: string }>;
+  audited_at: string;                   // ISO 8601
+}
+```
+
+### 4.1 整体状态判定
+- `blocking_findings_count > 0` → `overall_status = "blocked"`
+- `blocking_findings_count = 0` → `overall_status = "advisory"`
+
+---
+
+## 5. 流程步骤
+
+```
+[用户] sf_command (intent: "开始详细设计审计", input_artifacts: [...])
+   ↓
+[路由] 识别 audit action → workflow_intent = "audit_design"
+   ↓
+[路由] EXTENSION_WORKFLOW_MAP.audit_design → route=analysis, mutation=false
+   ↓
+[扩展] 加载 audit_design_prompt 模板 + 关联知识（review_rule / pattern）
+   ↓
+[执行] 6 维度审计，每维度遍历 input_artifacts 中相关章节
+   ↓
+[输出] audit_report + blocking_findings_count
+   ↓
+[结束] overall_status="blocked" 时建议用户先修复 hard_fail，再进入实施
+```
+
+---
+
+## 6. 关键约束
+
+1. **不修改源文档**: 审计产物独立输出，源设计文档保持只读
+2. **finding 必须可追溯**: 每条 finding 必须有 location 字段引用具体文档路径 + 章节 / 行号
+3. **不臆断**: 文档中未声明的约束不得作为 finding 依据
+4. **不漏维度**: 6 维度全部覆盖，无 finding 时必须显式标记 `no_issue_observed`
+5. **中文输出**: issue_zh / recommendation_zh / note_zh 字段必须为中文
+
+---
+
+## 7. 关联资产
+
+- **Prompt 模板**: `audit_design_prompt` (`src/engine/pipeline/intent_expander/templates.ts`)
+- **工作流契约**: `wf-audit-design` (`src/engine/workflow/workflow_contract_registry.ts`)
+- **ARTIFACT_ALIASES**: `design_doc` / `detailed_design` / `api_spec` / `database_design`
+- **Pipeline hint**: `code-review`（复用代码审查流程的规则与模式资产）
+
+---
+
+## 8. 与代码审查流程的区别
+
+| 维度 | 代码审查 (code_review) | 设计审计 (audit_design) |
+|------|------------------------|-------------------------|
+| 对象 | 源代码 / diff | 设计文档（Markdown） |
+| 输入 | changed_files + file_contents | input_artifacts (kind + path) |
+| 触发 | "审查代码" / sf_review 无 input_artifacts | "审计设计" / sf_review 带 input_artifacts |
+| 维度 | 编码规范 / BUG / 安全 / 性能 | 跨文档一致性 / OOD / 防孤岛 / 契约 / SQL / 索引 |
+| 输出 | review_report | audit_report |
+| 修改建议 | 直接改代码 | 修改设计文档后重新审计 |

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

@@ -12,8 +12,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-architecture-design
-routes:
-  - code_change
 primary_triggers:
   - 详细设计流程
 secondary_triggers: []

package/templates/procedures//350/260/203/350/257/225/346/216/222/346/237/245/346/265/201/347/250/213.md

@@ -12,8 +12,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-verifier
-routes:
-  - code_change
 primary_triggers:
   - 调试排查流程
 secondary_triggers: []

package/templates/procedures//350/277/201/347/247/273/346/265/201/346/260/264/347/272/277.md

@@ -12,8 +12,6 @@ asset_kind: pipeline_procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-knowledge-asset-governance
-routes:
-  - code_change
 primary_triggers:
   - 迁移流水线
 secondary_triggers: []
@@ -39,7 +37,7 @@ stages: ["编码与单元测试", "联调验证"]
 评估迁移范围和影响（模块数、代码量、依赖链）。评估迁移路径（渐进式/一次性）。评估兼容性风险（API 变更、行为差异、性能差异）。制定回滚方案。
 模版：迁移评估模版.md
 产出保存到：.soloforge/output/01-迁移评估.md
-工具：sf_classify, sf_analyze
+工具：sf_command, sf_analyze
 
 ### 第2步：方案设计
 制定分阶段迁移计划（每阶段可独立验证和回滚）。识别兼容层需求（适配器/Shim/Feature Flag）。定义每个阶段的完成标准和验证方式。
@@ -47,8 +45,8 @@ stages: ["编码与单元测试", "联调验证"]
 
 ### 第3步：渐进迁移
 按计划逐步迁移，每阶段完成后全量测试。保持双写/双读过渡期（如需要）。记录每阶段发现的行为差异和兼容性问题。
-工具：sf_expand, sf_verify
+工具：sf_stage_execute, sf_gate_check
 
 ### 第4步：清理验证
 移除兼容层和废弃代码。全量功能验证。性能对比确认无退化。更新文档和依赖配置。
-工具：sf_verify, sf_review, sf_deliver, sf_learn
+工具：sf_gate_check, sf_review, sf_stage_advance, sf_stage_advance

package/templates/procedures//351/203/250/347/275/262/345/217/221/345/270/203/346/265/201/347/250/213.md

@@ -12,8 +12,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-delivery-gate
-routes:
-  - code_change
 primary_triggers:
   - 部署发布流程
 secondary_triggers: []

package/templates/procedures//351/207/215/346/236/204/346/265/201/346/260/264/347/272/277.md

@@ -12,8 +12,6 @@ asset_kind: pipeline_procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-task-context-lifecycle
-routes:
-  - code_change
 primary_triggers:
   - 重构流水线
 secondary_triggers: []
@@ -39,7 +37,7 @@ stages: ["编码与单元测试", "联调验证"]
 识别当前代码的坏味道和重构目标。量化现状（圈复杂度、方法行数、类职责数）。确定重构类型（提取方法/提取类/内联/重命名/搬移/模式替换）。
 模版：重构方案模版.md
 产出保存到：.soloforge/output/01-重构分析.md
-工具：sf_classify, sf_analyze
+工具：sf_command, sf_analyze
 
 ### 第2步：方案设计
 定义重构目标和 Before/After 对比。评估影响范围（哪些模块/接口/测试受影响）。识别风险点（破坏性变更风险等级、回归风险）。制定分步执行计划（每步可独立验证）。
@@ -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//351/233/206/346/210/220/351/252/214/350/257/201/346/265/201/347/250/213.md

@@ -12,8 +12,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-verifier
-routes:
-  - code_change
 primary_triggers:
   - 集成验证流程
 secondary_triggers: []

package/templates/procedures//351/234/200/346/261/202/346/276/204/346/270/205/346/265/201/347/250/213.md

@@ -11,9 +11,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: []
@@ -21,7 +19,7 @@ negative_triggers: []
 priority: P1
 specificity: 5
 consumes:
-  - mc-intent-router
+  - mc-command-router
 emits:
   - requirement_baseline
   - terminology_glossary

package/templates/procedures//351/252/214/346/224/266/346/265/213/350/257/225/350/247/204/345/210/222.md

@@ -12,8 +12,6 @@ asset_kind: procedure
 lifecycle_status: active
 authority: supporting
 owner_mechanism_id: mc-delivery-gate
-routes:
-  - code_change
 primary_triggers:
   - 验收测试规划
 secondary_triggers: []

package/templates/rules/existing-system//345/205/274/345/256/271/346/200/247/346/243/200/346/237/245/350/247/204/345/210/231.md

@@ -2,9 +2,6 @@
 name: compatibility-check
 type: review_rule
 asset_kind: review_rule
-routes:
-  - code_change
-  - analysis
 primary_triggers:
   - 兼容性
   - 向后兼容

package/templates/rules/existing-system//350/200/246/345/220/210/346/243/200/346/265/213/350/247/204/345/210/231.md

@@ -2,9 +2,6 @@
 name: coupling-detection
 type: review_rule
 asset_kind: review_rule
-routes:
-  - code_change
-  - analysis
 primary_triggers:
   - 耦合
   - 耦合检测

package/templates/rules/existing-system//350/257/225/350/277/220/350/241/214/347/206/224/346/226/255/350/247/204/345/210/231.md

@@ -2,8 +2,6 @@
 name: trial-run-circuit-breaker
 type: review_rule
 asset_kind: review_rule
-routes:
-  - code_change
 primary_triggers:
   - 试运行
   - 熔断

package/templates/rules/existing-system//351/230/262/345/276/241/346/200/247/347/274/226/347/240/201/350/247/204/345/210/231.md

@@ -2,8 +2,6 @@
 name: defensive-coding
 type: review_rule
 asset_kind: review_rule
-routes:
-  - code_change
 primary_triggers:
   - 防御性编码
   - 防御编程

package/templates/rules/existing-system//351/233/267/345/214/272/345/217/215/346/250/241/345/274/217/346/270/205/345/215/225.md

@@ -2,9 +2,6 @@
 name: minefield-antipattern-list
 type: review_rule
 asset_kind: review_rule
-routes:
-  - code_change
-  - analysis
 primary_triggers:
   - 雷区
   - 反模式

package/templates/rules/new-system//350/201/224/350/260/203/350/256/276/350/256/241/347/274/272/351/231/267/345/210/244/345/256/232/350/247/204/345/210/231.md

@@ -2,8 +2,6 @@
 name: integration-design-defect
 type: review_rule
 asset_kind: review_rule
-routes:
-  - code_change
 primary_triggers:
   - 联调缺陷
   - 设计缺陷

package/templates/rules/shared/SOLID/344/273/243/347/240/201/345/256/241/346/237/245/350/247/204/345/210/231.md

@@ -12,8 +12,6 @@ asset_kind: review_rule
 lifecycle_status: active
 authority: canonical
 owner_mechanism_id: mc-ood-solid-contract
-routes:
-  - code_change
 primary_triggers:
   - SOLID代码审查规则
 secondary_triggers:

package/templates/rules/shared//344/270/200/350/207/264/346/200/247/346/240/241/351/252/214/350/247/204/345/210/231.md

@@ -7,7 +7,6 @@ products: ['*']
 lifecycle_status: active
 asset_kind: review_rule
 owner_mechanism_id: mc-generic-review
-routes: [code_change, artifact_generation]
 primary_triggers: [一致性, 校验, 设计产物]
 stages: ["编码与单元测试"]
 ---

package/templates/rules/shared//344/272/244/344/273/230/345/256/214/345/244/207/346/200/247/345/256/241/346/237/245/350/247/204/345/210/231.md

@@ -12,8 +12,6 @@ asset_kind: review_rule
 lifecycle_status: active
 owner_mechanism_id: mc-generic-review
 authority: supporting
-routes:
-  - code_change
 primary_triggers:
   - 交付完备性审查规则
 secondary_triggers: []

package/templates/rules/shared//344/273/243/347/240/201/345/217/257/347/273/264/346/212/244/346/200/247/344/270/216/345/217/257/350/247/202/346/265/213/346/200/247/345/256/241/346/237/245.md

@@ -10,9 +10,6 @@ asset_kind: review_rule
 lifecycle_status: active
 authority: canonical
 owner_mechanism_id: mc-code-maintainability-observability-contract
-routes:
-  - code_change
-  - review
 primary_triggers:
   - 代码审查
   - review

package/templates/rules/shared//345/206/263/347/255/226/345/256/214/346/225/264/346/200/247/345/256/241/346/237/245/350/247/204/345/210/231.md

@@ -11,7 +11,6 @@ id: ka-review-rule-决策完整性审查规则
 asset_kind: review_rule
 lifecycle_status: active
 authority: supporting
-routes: ['code_change', 'planning']
 primary_triggers:
   - 决策完整性审查规则
 secondary_triggers:

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

@@ -12,8 +12,6 @@ asset_kind: review_rule
 lifecycle_status: active
 owner_mechanism_id: mc-delivery-gate
 authority: supporting
-routes:
-  - code_change
 primary_triggers:
   - 发布后审查规则
 secondary_triggers:

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

@@ -11,8 +11,6 @@ asset_kind: review_rule
 lifecycle_status: active
 authority: canonical
 owner_mechanism_id: mc-backend-implementation-contract
-routes:
-  - code_change
 primary_triggers:
   - 后端实现工程审查规则
 secondary_triggers:

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

@@ -12,8 +12,6 @@ asset_kind: review_rule
 lifecycle_status: active
 owner_mechanism_id: mc-generic-review
 authority: supporting
-routes:
-  - code_change
 primary_triggers:
   - 安全审查规则
 secondary_triggers: []

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

@@ -11,8 +11,6 @@ asset_kind: review_rule
 lifecycle_status: active
 owner_mechanism_id: mc-generic-review
 authority: supporting
-routes:
-  - code_change
 primary_triggers:
   - 并发审查规则
 secondary_triggers: []

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

@@ -12,8 +12,6 @@ asset_kind: review_rule
 lifecycle_status: active
 owner_mechanism_id: mc-generic-review
 authority: supporting
-routes:
-  - code_change
 primary_triggers:
   - 性能审查规则
 secondary_triggers: []

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

@@ -11,8 +11,6 @@ asset_kind: review_rule
 lifecycle_status: active
 owner_mechanism_id: mc-generic-review
 authority: supporting
-routes:
-  - code_change
 primary_triggers:
   - 接口契约审查规则
 secondary_triggers: []

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

@@ -12,8 +12,6 @@ asset_kind: review_rule
 lifecycle_status: active
 owner_mechanism_id: mc-generic-review
 authority: supporting
-routes:
-  - code_change
 primary_triggers:
   - 架构审查规则
 secondary_triggers: []

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

@@ -12,8 +12,6 @@ asset_kind: review_rule
 lifecycle_status: active
 owner_mechanism_id: mc-coding-readiness
 authority: supporting
-routes:
-  - code_change
 primary_triggers:
   - 编码就绪审查规则
 secondary_triggers:

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

@@ -2,8 +2,6 @@
 name: integration-verification-list
 type: review_rule
 asset_kind: review_rule
-routes:
-  - code_change
 primary_triggers:
   - 联调验证
   - 验证清单

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

@@ -7,7 +7,6 @@ products: ['*']
 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

@@ -12,8 +12,6 @@ asset_kind: review_rule
 lifecycle_status: active
 owner_mechanism_id: mc-generic-review
 authority: supporting
-routes:
-  - code_change
 primary_triggers:
   - 质量审查规则
 secondary_triggers: []

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

@@ -11,7 +11,6 @@ id: ka-review-rule-需求质量审查规则
 asset_kind: review_rule
 lifecycle_status: active
 authority: supporting
-routes: ['code_change', 'planning']
 primary_triggers:
   - 需求质量审查规则
 secondary_triggers:
@@ -23,7 +22,7 @@ specificity: 5
 version: 1.1.0
 last_reviewed: '2026-06-01'
 stages: ["编码与单元测试", "联调验证"]
-owner_mechanism_id: mc-intent-router
+owner_mechanism_id: mc-command-router
 ---
 
 # 需求质量审查规则

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

@@ -12,8 +12,6 @@ asset_kind: review_rule
 lifecycle_status: active
 owner_mechanism_id: mc-local-acceptance
 authority: supporting
-routes:
-  - code_change
 primary_triggers:
   - 验收标准审查规则
 secondary_triggers:

package/templates//346/250/241/347/211/210/350/264/241/347/214/256/346/214/207/345/215/227.md

@@ -6,7 +6,6 @@ owner_mechanism_id: mc-standard-asset-contract
 authority: supporting
 specificity: 5
 lifecycle_status: active
-routes: ['*']
 scope:
   - '*'
 when: '新增模版文件、模版贡献、模版资产维护'
@@ -54,8 +53,6 @@ stages: ["*"]
 name: "文件中文名（kebab-case 或中文）"
 type: "见上表 9 种合法值"
 asset_kind: "与 type 兼容的注册侧分类"
-routes:
-  - "IntentRoute 值或 *"
 scope:
   - "backend / frontend / infrastructure / *"
 stages:

package/dist/engine/contracts/route_decision_contract_verifier.d.ts

@@ -1,44 +0,0 @@
-/**
- * RouteDecision 合同验证器 — 验证 route_decision 与 workflow_trace 的一致性。
- *
- * 被 sf_verify、scenario runner、negative tests 共用。
- */
-export interface RouteDecisionContractFinding {
-    severity: "hard_fail" | "blocked" | "degraded" | "advisory";
-    rule: string;
-    message: string;
-}
-export interface RouteDecisionContractInput {
-    route_decision?: {
-        route: string;
-        execution_shape: string;
-        mutation_allowed: boolean;
-        input_materials?: Array<{
-            kind: string;
-            path?: string;
-        }>;
-        missing_required_inputs?: string[];
-        scope?: {
-            read_only?: boolean;
-        };
-        constraints?: string[];
-        output_artifact?: {
-            kind?: string;
-            path?: string;
-        } | null;
-    } | null;
-    workflow_trace?: {
-        route?: string;
-        execution_shape?: string;
-    } | null;
-    expansion_input_materials?: Array<{
-        path_or_ref?: string;
-    }>;
-    expansion_output_artifact?: {
-        kind?: string;
-        path?: string;
-    } | null;
-    expansion_constraints?: string[];
-}
-export declare function verifyRouteDecisionContract(input: RouteDecisionContractInput): RouteDecisionContractFinding[];
-//# sourceMappingURL=route_decision_contract_verifier.d.ts.map

package/dist/engine/contracts/route_decision_contract_verifier.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"route_decision_contract_verifier.d.ts","sourceRoot":"","sources":["../../../src/engine/contracts/route_decision_contract_verifier.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,MAAM,WAAW,4BAA4B;IAC3C,QAAQ,EAAE,WAAW,GAAG,SAAS,GAAG,UAAU,GAAG,UAAU,CAAC;IAC5D,IAAI,EAAE,MAAM,CAAC;IACb,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,MAAM,WAAW,0BAA0B;IACzC,cAAc,CAAC,EAAE;QACf,KAAK,EAAE,MAAM,CAAC;QACd,eAAe,EAAE,MAAM,CAAC;QACxB,gBAAgB,EAAE,OAAO,CAAC;QAC1B,eAAe,CAAC,EAAE,KAAK,CAAC;YAAE,IAAI,EAAE,MAAM,CAAC;YAAC,IAAI,CAAC,EAAE,MAAM,CAAA;SAAE,CAAC,CAAC;QACzD,uBAAuB,CAAC,EAAE,MAAM,EAAE,CAAC;QACnC,KAAK,CAAC,EAAE;YAAE,SAAS,CAAC,EAAE,OAAO,CAAA;SAAE,CAAC;QAChC,WAAW,CAAC,EAAE,MAAM,EAAE,CAAC;QACvB,eAAe,CAAC,EAAE;YAAE,IAAI,CAAC,EAAE,MAAM,CAAC;YAAC,IAAI,CAAC,EAAE,MAAM,CAAA;SAAE,GAAG,IAAI,CAAC;KAC3D,GAAG,IAAI,CAAC;IACT,cAAc,CAAC,EAAE;QACf,KAAK,CAAC,EAAE,MAAM,CAAC;QACf,eAAe,CAAC,EAAE,MAAM,CAAC;KAC1B,GAAG,IAAI,CAAC;IACT,yBAAyB,CAAC,EAAE,KAAK,CAAC;QAAE,WAAW,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IAC5D,yBAAyB,CAAC,EAAE;QAAE,IAAI,CAAC,EAAE,MAAM,CAAC;QAAC,IAAI,CAAC,EAAE,MAAM,CAAA;KAAE,GAAG,IAAI,CAAC;IACpE,qBAAqB,CAAC,EAAE,MAAM,EAAE,CAAC;CAClC;AAED,wBAAgB,2BAA2B,CAAC,KAAK,EAAE,0BAA0B,GAAG,4BAA4B,EAAE,CA6J7G"}