v0.3.36

Fix: Node metrics written to wrong node when container names match across servers

Root cause: GetByContainerID("klever-node1") returned the first matching row regardless of server. When Server A and Server B both have a container named klever-node1, all metrics ended up on Server A's node.

Fix: New GetByContainerAndServer method adds AND server_id = ? to the query. handleNodeMetrics now uses the event's ServerID for an unambiguous lookup.

This was the actual cause of node1-4 showing no Nonce/Sync — their metrics were silently written to the wrong node records on the other server.

What's Changed

• fix: scope node metrics lookup by server ID by @CTJaeger in #43

Full Changelog: v0.3.35...v0.3.36