Implement sophisticated conflict resolution and finalize cluster

Features completed:
- Sophisticated conflict resolution with majority vote system
- Oldest node tie-breaker for even cluster scenarios
- Two-phase conflict resolution (majority vote → oldest node)
- Comprehensive logging for conflict resolution decisions
- Member querying for distributed voting
- Graceful fallback to oldest node rule when no quorum available

Technical implementation:
- resolveConflict() function implementing full design specification
- resolveByOldestNode() for 2-node scenarios and tie-breaking
- queryMemberForData() for distributed consensus gathering
- Detailed logging of vote counts, winners, and decision rationale

Configuration improvements:
- Updated .gitignore for data directories and build artifacts
- Test configurations for 3-node cluster setup
- Faster sync intervals for development/testing

The KVS now fully implements the design specification:
✅ Hierarchical key-value storage with BadgerDB
✅ HTTP REST API with full CRUD operations
✅ Gossip protocol for membership discovery
✅ Eventual consistency with timestamp-based resolution
✅ Sophisticated conflict resolution (majority vote + oldest node)
✅ Gradual bootstrapping for new nodes
✅ Operational modes (normal, read-only, syncing)
✅ Structured logging with configurable levels
✅ YAML configuration with auto-generation

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

.gitignore

@@ -1 +1,6 @@
 .claude/
+data/
+data*/
+*.yaml
+!config.yaml
+kvs