修正企微主办边界与工作台摘要（portal-task-first-redesign）

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

@@ -278,8 +278,8 @@ and admin tools available without dominating the default path.
 ### 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.
+`查看处理` the default row action. List-level `通过` is disabled by default unless
+a later Trellis task adds an explicit backend eligibility contract.
 
 **Contracts**:
 
@@ -289,17 +289,23 @@ for low-risk items where the row itself carries enough decision context.
   `高级 / 历史` 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.
+- HR/attendance items owned by Enterprise WeChat, including leave, missed
+  punch, outing, overtime and check-in related approvals, must not show OA
+  list-level quick approval. OA may show mirror/history/status/exception
+  context and emergency-takeover records according to the business boundary,
+  but normal approval remains in Enterprise WeChat.
+- Reimbursement, procurement, travel, contract and other amount/evidence-heavy
+  OA-owned tasks should route through `查看处理` first.
+- Future list-level quick approval requires the backend to expose an explicit
+  eligibility flag such as `quickApproveEligible=true`, plus task-domain and
+  audit semantics in the current Trellis task. Frontend heuristics based only on
+  entity type, duration or row text are not enough.
+- If list quick approval is reintroduced later, its confirm dialog 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.
+**Why**: Small-team approvers should build the habit of opening the task detail
+before approval, and the OA/Enterprise WeChat ownership boundary must stay clear
+for HR/attendance workflows.
 
 ## Convention: Workbench Onboarding And Profile Scope