Household import reliability and Value-Add report improvements

This release ships a set of reliability fixes for household imports and manual household creation, polish updates to the Guardrails and Buckets value-add reports, and a few small usability fixes on the Household Details page.

What's improved

The Guardrails and Buckets comparative tables now lead with Monthly Income above Distribution Rate. Reading the table top-to-bottom, Monthly Income — the figure most clients ask about first — now sits directly under Portfolio Value, with Distribution Rate as the supporting detail beneath it.

Empty cells in the Distribution Rate row of the Guardrails and Buckets tables now display as clean blank space instead of bordered empty boxes. The Upper Guardrail and Lower Guardrail cells in this row are intentionally blank by design — guardrails define thresholds on portfolio value, not on rate — and they previously read as if data had failed to load.

Disabled Value-Add cards on the Household Details page (cards for Value-Adds your firm has turned off in Settings) no longer navigate when clicked. The "turned off in Settings" tooltip continues to appear on hover, but now after a subtle half-second pause rather than instantly, so it doesn't fire while you're moving past the card.

Bug fixes

• Spelling fix on the Guardrails report. The "CURRENT DISTRUBUTION" label under the value bar was misspelled. It is now correctly spelled "CURRENT DISTRIBUTION".
• Households export search matches Head of Household names. Searching your Households export by name now matches against the Head of Household field, aligning with the column most users expect to search.
• Manual household IDs are portable to CSV imports. When you create a household manually and later reference it by ID in an import, the ID format is now consistent with imported households. Previously, manually-created household IDs could cause import-update operations to miss those records.
• Imports with missing household names are rejected up front. Rows that don't include a household name are now blocked at validation rather than creating partial or unnamed records.
• Refined how Lead Advisor role changes propagate across household assignments and permissions. (Users may need to log out and back in once for permission changes to take effect.)
• Permissions are correctly applied when a user is promoted into or demoted out of the Lead Advisor role, including their access to household data appropriate to the new role.
• CSV import rows that only update household-level fields process correctly. Previously, import rows containing only household-level updates (without accompanying client or account changes) could be skipped or misprocessed.

Behind the scenes

This release includes upstream dependency patches across our third-party integrations. No user-facing behavior change — we're keeping dependencies current and patched against known CVEs.