Skip to content

fix(ui): designer-audit round 6 — one time-control cluster, deduped archive rows, single first-run CTA - #605

Merged
jackwener merged 1 commit into
mainfrom
fix/ui-audit-round6
Jul 7, 2026
Merged

fix(ui): designer-audit round 6 — one time-control cluster, deduped archive rows, single first-run CTA#605
jackwener merged 1 commit into
mainfrom
fix/ui-audit-round6

Conversation

@jackwener

Copy link
Copy Markdown
Member

设计审查第 6 轮:

  1. P2-10 每日回顾头部两套时间控件分居两角(步进器最左、范围 tab 最右)读作互不相关 → 合为左侧一簇:先选范围(今日/本周/本月)再步进,步进按所选跨度走。
  2. P2-11 报告列表行重复详情卡的整个头部(状态+生成时间)→ 列表行只负责识别(标题 + N 对话,仅异常时附状态),其余归详情卡。
  3. P2-15 残余 首启页底部主按钮「打开设置·模型」与点击任意 provider 行的行为重复(列表头就写着「点一个进入设置」)→ 删除,保留两条真正不同的路径。
  4. Round-4 补漏:stories 里残留的 focus prop 导致 storybook 工程 typecheck 红 → 清理。

截图验证;typecheck 0;2143/2143。

…rchive rows, single first-run CTA

- P2-10: the daily-review header had two time controls at opposite
  corners (stepper far-left, range tabs far-right) that read as
  unrelated widgets. They now form one left-aligned cluster: pick the
  range (今日/本周/本月), then step through it.
- P2-11: archive list rows repeated the detail card's entire header
  (status + generation timestamp). Rows now identify only (title +
  conversation count, plus status only when it isn't ok); the detail
  card owns the rest.
- P2-15 residual: the first-run footer's primary 打开设置·模型 button
  duplicated what clicking any provider row does (the list header says
  点一个进入设置) — removed; the footer keeps the two genuinely
  distinct paths (刷新检测 / 跳过).
- Round-4 followup: capability-audit stories still passed the removed
  focus prop (typecheck was red in the storybook project) — cleaned.

Verified via screenshots. typecheck 0; 2143/2143 tests.
@jackwener
jackwener merged commit 44f5b2c into main Jul 7, 2026
3 checks passed
@jackwener
jackwener deleted the fix/ui-audit-round6 branch July 7, 2026 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant