调整待处理页任务优先体验（portal-task-first-redesign）

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

@@ -257,6 +257,32 @@ and admin tools available without dominating the default path.
   asserting the task surface, primary action and secondary/advanced entry
   behavior.
 
+### Convention: Approval Task List Defaults
+
+**What**: PC approval task lists such as `/workflow/tasks` should make
+`查看处理` the default row action. List-level `通过` is only a secondary shortcut
+for low-risk items where the row itself carries enough decision context.
+
+**Contracts**:
+
+- The row must answer what the item is, who requested it, why it is assigned to
+  the current user, how long it has waited, and the public business reference.
+- History entry text should be explicit, such as `已处理记录`; avoid user-facing
+  `高级 / 历史` on the default task surface.
+- Time labels should prefer `已等待多久` and `接收于` over database-shaped labels
+  such as `更新时间` when the source field is task creation/arrival time.
+- A quick `通过` button may appear only when the task is pending, the server
+  allows `approve`, the item is a low-risk leave/attendance task, required row
+  summary fields are present, and the task has not exceeded the pending window
+  available to the frontend. Reimbursement, procurement, travel, contract and
+  other amount/evidence-heavy tasks should route through `查看处理` first.
+- The confirm dialog for list quick approval must still explain action
+  consequences and include the specific task summary.
+
+**Why**: Small-team approvers need to clear work quickly without training
+themselves to approve financial or evidence-heavy items from an under-specified
+row.
+
 ## Convention: Workbench Onboarding And Profile Scope
 
 **What**: PC workbench and account settings should stay task-first, not become