Reliability improvements for household imports and Reports search

This release includes a set of reliability improvements to household creation, contact imports, and the Reports page.

What's new

You can now update households via spreadsheet without including client details. Upload a spreadsheet that contains only Household IDs and household-level fields like Lead Advisor or Marginal Tax Bracket, and SurgeTK will update those households — no Client ID or client name needed in every row. Useful for bulk advisor reassignments and quick household-level field updates.

Bug fixes

• Manual household IDs now work with imports. When you create a household manually, the Household ID shown on the details page is now a copyable, full identifier you can paste into a spreadsheet to update that household. Previously the displayed value couldn't be matched by the importer, so update attempts ended up creating duplicate households.
• Reports page search now matches client names. The Households view on the Reports page now searches against the head of household's first or last name in addition to internal IDs. Typing a partial name like "smith" returns matching households.
• Imports no longer create empty households. When an import row would create a brand-new household but is missing client name or Client ID, that row is rejected with a clear error message — instead of silently creating an empty household with no client attached.
• Advisor auto-linking now respects the Lead Advisor role. The contact import only auto-links the Advisor column to team members who are classified as Lead Advisors. Team members with other roles (Admin, Assistant, etc.) are no longer attached to households as the Lead Advisor on import. Their imported names appear in Settings → Team Members → Unlinked Imported Advisors for an admin to reconcile manually.
• Demoting a Lead Advisor properly cleans up linked references. When you change a team member from Lead Advisor to a different role, the platform now also clears their links from imported advisor records and any related advisor fields. Previously some of these references persisted and could resurface on a later import.