更新员工资产信息归户规则设计与计划

docs/plans/2026-03-12-employee-asset-maintenance-frontend-implementation.md

@@ -2,9 +2,9 @@
 
 > **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.
 
-**Goal:** Extend the employee maintenance page so users can maintain employee assets inside the add/edit dialog, view all assets in the detail dialog, and import asset data with a dedicated failure-record entry.
+**Goal:** Extend the employee maintenance page so users can maintain employee and family-member assets inside the add/edit dialog, view all assets in the detail dialog, and import asset data with automatic employee-family ownership resolution and a dedicated failure-record entry.
 
-**Architecture:** Keep the existing employee page and API module in place, and add a nested asset-table editing experience within `ccdiBaseStaff/index.vue`. Reuse the existing async import interaction model, but isolate all asset-import state, storage keys, dialogs, and button copy from the original employee-import flow.
+**Architecture:** Keep the existing employee page and API module in place, and add a nested asset-table editing experience within `ccdiBaseStaff/index.vue`. Frontend users edit the actual holder ID card as `personId`, while the backend derives `family_id` from the current employee during form save and from import resolution during Excel import. Reuse the existing async import interaction model, but isolate all asset-import state, storage keys, dialogs, and button copy from the original employee-import flow.
 
 **Tech Stack:** Vue 2, Element UI 2, RuoYi request wrapper, scoped SFC styles, Node-based source assertions or existing frontend unit checks
 
@@ -71,6 +71,7 @@ Assert the employee page contains:
 - an “资产信息” section inside the add/edit dialog
 - an add-asset action
 - a detail-table section for assets
+- a holder-ID-card input for asset rows
 
 **Step 2: Run test to verify it fails**
 
@@ -105,6 +106,7 @@ Add methods for:
 
 Render a section below basic employee info with columns for:
 
+- `personId`
 - `assetMainType`
 - `assetSubType`
 - `assetName`
@@ -182,6 +184,8 @@ Update:
 
 so they all preserve `assetInfoList`.
 
+Ensure `submitForm` filters empty asset rows but keeps valid `personId` values intact instead of overwriting them on the frontend.
+
 **Step 4: Run the submit-flow test**
 
 Run:
@@ -227,6 +231,8 @@ Add:
 - asset-specific upload methods
 - independent polling and completion handlers
 
+Keep the asset import copy clear that the system will auto-match the employee family and auto-fill ownership based on the holder ID card.
+
 **Step 4: Distinguish failure record copy**
 
 Ensure the failure entry text is exactly `查看员工资产导入失败记录`.
@@ -255,6 +261,7 @@ The dialog title must be `员工资产导入失败记录`.
 
 Show:
 
+- `familyId`
 - `personId`
 - `assetMainType`
 - `assetSubType`
@@ -288,6 +295,12 @@ Style:
 
 Ensure basic info layout remains readable on desktop and mobile widths.
 
+Also add clear inline hints so users understand:
+
+- `personId` is the actual holder ID card
+- if it equals the employee ID card, the asset belongs to the employee
+- if it differs, the asset is treated as a family-member asset
+
 ### Task 9: Verify the frontend changes end to end
 
 **Files:**