重构 PC 首页与报销列表降噪（frontend-simplification-refactor）

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

@@ -195,6 +195,36 @@ point and prevents each route from inventing a different title/action layout.
   `Topbar`, `NavLinks`, `PageHeader`, `WorkspaceHeader`, login, Portal or other
   A-class pages.
 
+## Convention: A-Class PC Task-First Pages
+
+**What**: A-class PC pages such as Portal, approvals, reimbursement list and
+reimbursement detail should make the current user task obvious before exposing
+secondary operations:
+
+- First visible task surface should answer: what needs attention, what can be
+  started, and where recent progress lives.
+- Keep one primary action in the first screen. Allow at most two secondary
+  entries; move export, batch, delete, templates, complex filters, statistics
+  and admin/finance tools into `更多`, `高级 / 台账`, detail actions, role-only
+  panels or confirmation dialogs.
+- Explanation text should only be default-visible for risk, exception or empty
+  states. Do not use repeated subtitles or notice cards to explain normal
+  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.
+
+**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
+and admin tools available without dominating the default path.
+
+**Tests Required**:
+
+- `cd client && npm run typecheck`
+- `cd client && npm run build`
+- Focused Playwright or screenshot checks for changed A-class PC pages,
+  asserting the task surface, primary action and secondary/advanced entry
+  behavior.
+
 ## Convention: Detail And Mobile Command Surfaces
 
 **What**: PC detail pages and notification-like flows should reuse the Wave3