docs: clarify gossip type relationships

CLUSTER_MEMBERSHIP_GOSSIP.md

@@ -40,19 +40,27 @@ classDiagram
     class Gossiper
     class GossipActor
     class Gossip
+    class GossipState
     class MemberStateDeltaBuilder
     class GossipSender
+    class GossipRequest
+    class GossipResponse
     class IGossipTransport
     class GossipTransport
     Gossiper o-- Gossip
     Gossiper --> GossipActor : commands
     Gossiper --> GossipSender : uses
     GossipActor --> Gossip : merges
+    Gossip --> GossipState : holds
     Gossip --> MemberStateDeltaBuilder : uses
+    GossipSender ..> GossipRequest : sends
+    GossipSender ..> GossipResponse : receives
     GossipSender ..> IGossipTransport
     IGossipTransport <|-- GossipTransport
 ```
 
+`Gossip` maintains a `GossipState` and exchanges `GossipRequest` and `GossipResponse` messages via `IGossipTransport` to synchronize that state across nodes.
+
 ## Detecting members
 
 Cluster providers (e.g., Kubernetes) watch the environment for running nodes and

logs/log1756021716.md

@@ -0,0 +1,6 @@
+# Update Type Relationships in Gossip Documentation
+
+- Added `GossipState`, `GossipRequest`, and `GossipResponse` to the type relationship diagram to clarify how gossip state is maintained and exchanged.
+- Installed .NET 8 SDK to satisfy repository requirements and run tests.
+
+Motivation: The `Type relationships` section omitted core message and state types, which confused the mapping between the code and documentation. Including them helps contributors and users understand how gossip messages carry state across nodes.