Contact, peer directory and local trust model

This model has local peer directory, contact nickname, protocol partition, ignored and trust projections. The message model uses it but does not own it.

Actual boundary

• MeshPeerIdentity / MeshPeerRecord: Cross-protocol directory records.
• IMeshPeerDirectory: Directory writing, query, flags, deletion and flush.
• ContactService: Old node/contact projection and user actions.
• INodeStore / IContactStore: Independent persistence of node observation and nickname.

Not yet closed

The old and new directory expressions coexist;isNodeVisible() Currently returns true unconditionally; trusted, manually verified and Mesh verified key do not have unified certification semantics; the IdentityLink from the protocol identity to the business contact has not yet been formed.

Drill-down: peer observation, contact improvement and local trust