harden sm-flow protocol and archive v4.0 validation runs
- Rewrite hard constraint #1: apply must read Committed OpenSpec files as the execution source of truth - Promote sub-skill invocation to hard constraint #6; remove fallbacks.md and all degradation paths - Add file existence verification at commit and archive exit gates - Require grill question pool, evidence-driven conclusions, and user-interview confirmations to be written to decisions.md - Record v4.0 validation retrospective in workflow.md: propose overreach, sub-skill pseudo-calling, spec omitting user behavior - Archive knowledge-index-sort OpenSpec and devflow entries from prior run
This commit is contained in:
@@ -0,0 +1,47 @@
|
||||
# 排序功能规格
|
||||
|
||||
## Scenario: 用户按日期新→旧排序
|
||||
|
||||
**Given** 知识库索引面板已加载,显示 3 个条目
|
||||
**When** 用户选择排序下拉框的"日期 新→旧"
|
||||
**Then** 条目按日期降序排列(最新的在前)
|
||||
**And** 排序与当前激活的过滤条件(搜索、标签、年份)取交集
|
||||
|
||||
## Scenario: 用户按日期旧→新排序
|
||||
|
||||
**Given** 知识库索引面板已加载
|
||||
**When** 用户选择排序下拉框的"日期 旧→新"
|
||||
**Then** 条目按日期升序排列(最旧的在前)
|
||||
|
||||
## Scenario: 用户按标签数量多→少排序
|
||||
|
||||
**Given** 知识库索引面板已加载
|
||||
**When** 用户选择排序下拉框的"标签 多→少"
|
||||
**Then** 条目按标签数组长度降序排列(标签多的在前)
|
||||
|
||||
## Scenario: 用户按标签数量少→多排序
|
||||
|
||||
**Given** 知识库索引面板已加载
|
||||
**When** 用户选择排序下拉框的"标签 少→多"
|
||||
**Then** 条目按标签数组长度升序排列(标签少的在前)
|
||||
|
||||
## Scenario: 排序与过滤组合
|
||||
|
||||
**Given** 用户已激活标签筛选(如"Claude Code")
|
||||
**When** 用户切换排序模式
|
||||
**Then** 只有匹配的条目被排序显示
|
||||
**And** 排序不影响过滤逻辑本身
|
||||
|
||||
## Scenario: 清空筛选重置排序
|
||||
|
||||
**Given** 用户已选择非默认排序模式
|
||||
**When** 用户点击"清空筛选"按钮
|
||||
**Then** 排序重置为默认值"日期 新→旧"
|
||||
**And** 所有过滤条件也被清空
|
||||
|
||||
## Scenario: 排序即时响应
|
||||
|
||||
**Given** 知识库索引面板已加载
|
||||
**When** 用户切换排序下拉框
|
||||
**Then** 条目列表立即重新排列
|
||||
**And** 不需要点击"应用"按钮
|
||||
Reference in New Issue
Block a user