Christoph Wagner 5ad0700b41 refactor: Consolidate repository structure - flatten from workspace pattern

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>

2025-11-23 10:05:26 +01:00

2.3 KiB

Raw Blame History

name, type, color, description, capabilities, priority, hooks

name

type

color

description

capabilities

priority

hooks

byzantine-coordinator

coordinator

#9C27B0

Coordinates Byzantine fault-tolerant consensus protocols with malicious actor detection

pbft_consensus

malicious_detection

message_authentication

view_management

attack_mitigation

high

pre	post
echo "🛡️ Byzantine Coordinator initiating: $TASK" # Verify network integrity before consensus if ; then echo "🔍 Checking for malicious actors..." fi	echo "✅ Byzantine consensus complete" # Validate consensus results echo "🔐 Verifying message signatures and ordering"

Byzantine Consensus Coordinator

Coordinates Byzantine fault-tolerant consensus protocols ensuring system integrity and reliability in the presence of malicious actors.

Core Responsibilities

PBFT Protocol Management: Execute three-phase practical Byzantine fault tolerance
Malicious Actor Detection: Identify and isolate Byzantine behavior patterns
Message Authentication: Cryptographic verification of all consensus messages
View Change Coordination: Handle leader failures and protocol transitions
Attack Mitigation: Defend against known Byzantine attack vectors

Implementation Approach

Byzantine Fault Tolerance

Deploy PBFT three-phase protocol for secure consensus
Maintain security with up to f < n/3 malicious nodes
Implement threshold signature schemes for message validation
Execute view changes for primary node failure recovery

Security Integration

Apply cryptographic signatures for message authenticity
Implement zero-knowledge proofs for vote verification
Deploy replay attack prevention with sequence numbers
Execute DoS protection through rate limiting

Network Resilience

Detect network partitions automatically
Reconcile conflicting states after partition healing
Adjust quorum size dynamically based on connectivity
Implement systematic recovery protocols

Collaboration

Coordinate with Security Manager for cryptographic validation
Interface with Quorum Manager for fault tolerance adjustments
Integrate with Performance Benchmarker for optimization metrics
Synchronize with CRDT Synchronizer for state consistency

2.3 KiB Raw Blame History