feat: extract HomeAddress card from DashboardFlow into standalone management block

[serikjensen]

Summary

Pulls the Home Address card out of the monolithic dashboard into four independently consumable pieces under Employee/HomeAddress/, following the canonical PaymentMethod template and the migrate-dashboard-card-to-block skill:

• useHomeAddressSummary — read-only BaseHookReady-shaped data hook (shared/useHomeAddressSummary/)
• HomeAddressCard — standalone, self-fetching card (management/HomeAddressCard/)
• HomeAddressEditForm — the renamed existing edit screen (was HomeAddress.tsx)
• HomeAddress — orchestrated block composing card + edit form via a local robot3 state machine

The dashboard composes the new card + edit form pieces (not the block) and routes its existing card↔edit transitions through the new scoped events. Every untouched card still goes through the legacy path; the two patterns coexist intentionally.

Scoped events

Added under componentEvents, namespaced EMPLOYEE_HOME_ADDRESS_MANAGEMENT_*:

Event	When	Payload
EDIT_REQUESTED	Card's Manage button	{ employeeId }
EDIT_CANCELLED	Edit form Back/Cancel	—
CREATED	New address saved	EmployeeAddress
UPDATED	Existing address saved	EmployeeAddress
DELETED	Address deleted	—

Legacy EMPLOYEE_HOME_ADDRESS_CREATED / _UPDATED are preserved for onboarding consumers.

Data hook split

useEmployeeBasicDetails no longer fetches home-address data — the card owns its own fetch via useHomeAddressSummary. The bundled hook now only carries work-address data, queued for the WorkAddress migration to retire entirely.

Translation decoupling

The management edit form no longer dual-loads Employee.HomeAddress. Field labels, validation messages, courtesy-withholding copy, and the no-current-address placeholder are now in Employee.HomeAddress.Management.json under form.*. Onboarding consumers (EmployeeProfile/AdminProfile) keep reading from Employee.HomeAddress unchanged. Skill updated to make single-namespace the default and reserve dual-loading for runtime-shared UI.

Also

• HomeAddress, HomeAddressCard, HomeAddressEditForm registered in the SDK dev app sidebar (regenerated generated-registry-data.ts).
• homeAddress.* keys removed from Employee.Dashboard.json.
• BasicDetailsView.stories.tsx updated to drop the removed home-address props.
• Endpoint inventory regenerated — DashboardFlow no longer hits /v1/employees/:employeeId/home_addresses; the card does.
• Docs entry added at docs/workflows-overview/employee-management/employee-management.md with block-level + per-piece sections.

Naming notes

• HomeAddress is now the orchestrated block; the previous HomeAddress edit screen was renamed to HomeAddressEditForm in the same PR (skill's naming-conflict resolution rule).
• The dashboard's "Home address" surface label is unchanged — only the code-side identity moved.

Test plan

• npm run test -- --run (234 files / 2976 tests passing locally)
• npm run lint:check (0 errors, 26 pre-existing warnings)
• npx tsc --noEmit (clean)
• Spot-check <HomeAddress />, <HomeAddressCard />, <HomeAddressEditForm /> under the Employee Management sidebar in npm run sdk-app
• Spot-check EmployeeManagement.DashboardFlow Basic Details tab still navigates card → edit → save/cancel correctly
• Confirm onboarding flows (EmployeeProfile, AdminProfile) still render Home Address field labels correctly from Employee.HomeAddress

Screen.Recording.2026-06-02.at.4.45.46.PM.mov

Made with Cursor