优化工作台与报销任务优先页面（portal-task-first-redesign）

.trellis/spec/hyb-oa/frontend-react-vite-design.md

@@ -244,6 +244,24 @@ secondary operations:
   workflow steps that the layout can express.
 - Low-frequency capabilities are hidden or moved, not removed, unless the
   current Trellis task explicitly deletes the capability.
+- Portal/workbench first screen should use a compact status summary plus
+  `今日待处理`; do not use a persistent welcome hero, fixed `报销进度` button,
+  general announcement feed, or folded placeholder sections such as
+  `团队与通知`, `角色重点` or `试点观测摘要`.
+- Workbench sections after `今日待处理` must be conditional: `团队卡点` only for
+  real blockers, `管理提醒` only for real admin/trial issues, and `我的进度`
+  only for reliable status updates. Empty data should disappear, not render as
+  collapsed drawers or statistic cards.
+- Each workbench action row should state what the item is, why the current user
+  is involved, current status/timing, and one next action. Do not represent raw
+  application counts as progress unless the payload includes an actionable or
+  status-level signal.
+- PC reimbursement list defaults to the initiator's own forms even for users
+  with finance/approval roles. The first screen may use task cards for
+  rejected corrections, drafts and reviewing progress; ledger/export/batch,
+  proxy submit, templates and travel-linking remain secondary and must be hidden
+  unless the current user has a real matching capability. Row workflow copy
+  should distinguish `待你处理` from read-only `当前节点`.
 
 **Why**: hyb-oa serves small teams with overlapping roles. Core pages must make
 the next click clear for ordinary employees and approvers, while keeping finance