feat(people): re-arm face recognition on person edits (spec 038) #760
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/people-merge-suggestions"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Spec 038. Based on origin/main
80437ff7.What / why
Person edits (rename/merge/split/dissolve, face assign/remove/confirm) change the assignment set that face recognition matches against, but recognition only armed on NEW embedding evidence (face_recognition_cursor watermark, V121). Already-seen owner_tentative faces were never re-matched after users named/merged persons. This PR adds owner-scoped dirty markers + a reconcile scheduler that re-enqueues owner_face_recognition deliberately WITHOUT the unseen-embedding guard (job completion stamps the cursor, so no infinite loop).
72f06e61(generic GET/POST /api/discovery/domains/{domainKey}/merge-suggestion[/reject], threshold 0.5, rejection filtering, deterministic ranking, full test coverage). Removed orphaned legacy PersonMergeSuggestionView types from discovery.ts.919370f1): missing :domainKey/:classKey bindings in personMedia/personSummary; dr2.detection_confidence -> dr2.confidence; dr.confidence alias for representativeFaces mapper; media_owner_profiles.display_name in H2 test schema.Test plan