Merge duplicate memories, and search the graph

New

• Search a contact's memory graph. A search box above the graph finds a node by name — a fact folded into an entity's Properties still resolves to that entity's node. Matches are ringed and panned into view.
• Hide a kind of memory from the graph. Click a label in the graph's legend — Fact, Preference, Event, Entity, and so on — to hide every node of that kind. Click it again to bring it back.
• Jump from Contradictions straight to the list. The Contradictions stat on a contact's Memory page is now a link — click the number and the List view opens filtered to just the atoms involved.
• Jump from an event to its agent or contact. In an event's detail view, the agent and contact names are now links — click either to open that agent or that contact.

Fixed

• Duplicate people and companies in memory now merge. "Dr. John" and "Dr John" used to become two different graph nodes, each holding half the relationships, because names were compared for exact equality. Punctuation, spacing and accents are now folded before comparing, so the same person or company is recognized as one entity going forward.
• Rebuilding memory can now actually fix a duplicate or mis-identified entity. Rebuild memory used to leave every person, company and product untouched. That meant a duplicate node, or something that was never a real entity to begin with, survived every rebuild with no way to clear it. Entities are now archived and re-created from the same conversations like everything else a rebuild regenerates; connections already drawn to an archived entity quietly stop rendering rather than being deleted, and reappear against the fresh copy once re-extraction runs.
• A task or event could show the wrong date. When a model correctly wrote a due date into a memory's wording but left the structured date field blank, the memory rendered dated to the day it was discussed instead of the day it's actually due. The date is now recovered from the wording when the structured field is missing.
• Every connection in the memory graph now shows what it means. Only relationships with a named predicate (like SON_OF) used to carry a label — a references or supports link rendered as a bare, unexplained line. Every connection is labelled now, and where several connections join the same two nodes, their labels fan out instead of stacking unreadably on top of each other.

Notes

• The entity fix does not retroactively merge existing duplicates by itself — it stops new duplicates from forming, and lets Rebuild memory clear out ones that already exist.
• Rebuilding memory still costs 1 interaction per conversation. Regenerating entities adds nothing extra — they come out of the same pass over each conversation as everything else.