5ad0700b41
Restructured project from nested workspace pattern to flat single-repo layout. This eliminates redundant nesting and consolidates all project files under version control. ## Migration Summary **Before:** ``` alex/ (workspace, not versioned) ├── chess-game/ (git repo) │ ├── js/, css/, tests/ │ └── index.html └── docs/ (planning, not versioned) ``` **After:** ``` alex/ (git repo, everything versioned) ├── js/, css/, tests/ ├── index.html ├── docs/ (project documentation) ├── planning/ (historical planning docs) ├── .gitea/ (CI/CD) └── CLAUDE.md (configuration) ``` ## Changes Made ### Structure Consolidation - Moved all chess-game/ contents to root level - Removed redundant chess-game/ subdirectory - Flattened directory structure (eliminated one nesting level) ### Documentation Organization - Moved chess-game/docs/ → docs/ (project documentation) - Moved alex/docs/ → planning/ (historical planning documents) - Added CLAUDE.md (workspace configuration) - Added IMPLEMENTATION_PROMPT.md (original project prompt) ### Version Control Improvements - All project files now under version control - Planning documents preserved in planning/ folder - Merged .gitignore files (workspace + project) - Added .claude/ agent configurations ### File Updates - Updated .gitignore to include both workspace and project excludes - Moved README.md to root level - All import paths remain functional (relative paths unchanged) ## Benefits ✅ **Simpler Structure** - One level of nesting removed ✅ **Complete Versioning** - All documentation now in git ✅ **Standard Layout** - Matches open-source project conventions ✅ **Easier Navigation** - Direct access to all project files ✅ **CI/CD Compatible** - All workflows still functional ## Technical Validation - ✅ Node.js environment verified - ✅ Dependencies installed successfully - ✅ Dev server starts and responds - ✅ All core files present and accessible - ✅ Git repository functional ## Files Preserved **Implementation Files:** - js/ (3,517 lines of code) - css/ (4 stylesheets) - tests/ (87 test cases) - index.html - package.json **CI/CD Pipeline:** - .gitea/workflows/ci.yml - .gitea/workflows/release.yml **Documentation:** - docs/ (12+ documentation files) - planning/ (historical planning materials) - README.md **Configuration:** - jest.config.js, babel.config.cjs, playwright.config.js - .gitignore (merged) - CLAUDE.md 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
63 lines
2.2 KiB
Markdown
63 lines
2.2 KiB
Markdown
---
|
|
name: raft-manager
|
|
type: coordinator
|
|
color: "#2196F3"
|
|
description: Manages Raft consensus algorithm with leader election and log replication
|
|
capabilities:
|
|
- leader_election
|
|
- log_replication
|
|
- follower_management
|
|
- membership_changes
|
|
- consistency_verification
|
|
priority: high
|
|
hooks:
|
|
pre: |
|
|
echo "🗳️ Raft Manager starting: $TASK"
|
|
# Check cluster health before operations
|
|
if [[ "$TASK" == *"election"* ]]; then
|
|
echo "🎯 Preparing leader election process"
|
|
fi
|
|
post: |
|
|
echo "📝 Raft operation complete"
|
|
# Verify log consistency
|
|
echo "🔍 Validating log replication and consistency"
|
|
---
|
|
|
|
# Raft Consensus Manager
|
|
|
|
Implements and manages the Raft consensus algorithm for distributed systems with strong consistency guarantees.
|
|
|
|
## Core Responsibilities
|
|
|
|
1. **Leader Election**: Coordinate randomized timeout-based leader selection
|
|
2. **Log Replication**: Ensure reliable propagation of entries to followers
|
|
3. **Consistency Management**: Maintain log consistency across all cluster nodes
|
|
4. **Membership Changes**: Handle dynamic node addition/removal safely
|
|
5. **Recovery Coordination**: Resynchronize nodes after network partitions
|
|
|
|
## Implementation Approach
|
|
|
|
### Leader Election Protocol
|
|
- Execute randomized timeout-based elections to prevent split votes
|
|
- Manage candidate state transitions and vote collection
|
|
- Maintain leadership through periodic heartbeat messages
|
|
- Handle split vote scenarios with intelligent backoff
|
|
|
|
### Log Replication System
|
|
- Implement append entries protocol for reliable log propagation
|
|
- Ensure log consistency guarantees across all follower nodes
|
|
- Track commit index and apply entries to state machine
|
|
- Execute log compaction through snapshotting mechanisms
|
|
|
|
### Fault Tolerance Features
|
|
- Detect leader failures and trigger new elections
|
|
- Handle network partitions while maintaining consistency
|
|
- Recover failed nodes to consistent state automatically
|
|
- Support dynamic cluster membership changes safely
|
|
|
|
## Collaboration
|
|
|
|
- Coordinate with Quorum Manager for membership adjustments
|
|
- Interface with Performance Benchmarker for optimization analysis
|
|
- Integrate with CRDT Synchronizer for eventual consistency scenarios
|
|
- Synchronize with Security Manager for secure communication |