07300aeff7
Some checks failed
CI / Unit & Component Tests (pull_request) Successful in 3m39s
CI / OCR Service Tests (pull_request) Successful in 20s
CI / Backend Unit Tests (pull_request) Failing after 3m45s
CI / fail2ban Regex (pull_request) Successful in 46s
CI / Semgrep Security Scan (pull_request) Successful in 20s
CI / Compose Bucket Idempotency (pull_request) Successful in 1m4s
The canonical importer creates persons via PersonRegisterImporter first (no family_member set) and then upserts them via PersonTreeImporter, but mergeCanonical never propagates family_member to existing persons — so persons with imported relationships ended up flagged family_member=false and never appeared in /api/persons family filters or the family-network view. RelationshipService is documented as the owner of the family_member flag, so the fix lives there: addRelationship now sets family_member=true on both endpoints whenever the relation type is PARENT_OF / SPOUSE_OF / SIBLING_OF (the same set getFamilyNetwork filters by). Non-family types (FRIEND/COLLEAGUE/EMPLOYER/DOCTOR/NEIGHBOR/OTHER) leave the flag alone — a family doctor isn't a family member. Extracted the type list as a FAMILY_RELATION_TYPES constant and reused it in getFamilyNetwork for a single source of truth. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>