Cleanup documentation and remove redundant comments

Author: rgilks

README.md

@@ -167,13 +167,13 @@ The worker import fix is necessary because `wasm-bindgen-rayon` generates worker
 evo/
 ├── src/                    # Rust source code
 │   ├── components.rs       # ECS components
-│   ├── genes.rs           # Genetic system
-│   ├── systems.rs         # Simulation systems
+│   ├── genes/             # Genetic system module
+│   ├── systems/           # Simulation systems modules
 │   ├── spatial_grid.rs    # Spatial optimization
-│   ├── stats.rs           # Analytics and statistics
-│   ├── simulation.rs      # Main simulation orchestration
-│   ├── config.rs          # Configuration management
-│   ├── ui.rs              # GPU-accelerated rendering (desktop)
+│   ├── stats/             # Analytics and statistics module
+│   ├── simulation/        # Main simulation orchestration module
+│   ├── config/            # Configuration management module
+│   ├── ui/                # GPU-accelerated rendering (desktop)
 │   ├── web/               # Web-specific modules
 │   └── main.rs            # Application entry point
 ├── web/                    # Web application
@@ -320,11 +320,11 @@ cargo run -- --config my_config.json
 ### Key Modules
 
 - **`components.rs`**: ECS components
-- **`genes.rs`**: Genetic system with grouped traits
-- **`systems.rs`**: Simulation systems
+- **`genes/`**: Genetic system with grouped traits
+- **`systems/`**: Simulation systems
 - **`spatial_grid.rs`**: Spatial optimization
-- **`simulation.rs`**: Main simulation orchestration
-- **`ui.rs`**: GPU-accelerated rendering (desktop)
+- **`simulation/`**: Main simulation orchestration
+- **`ui/`**: GPU-accelerated rendering (desktop)
 - **`web/`**: Web-specific modules
 
 ### Testing

docs/DEPLOYMENT.md

@@ -1,176 +1,69 @@
 # Cloudflare Deployment Guide
 
-This guide explains how to deploy the Evolution Simulation to Cloudflare Workers.
+This guide explains how to deploy the Evolution Simulation to Cloudflare Pages.
 
 ## Prerequisites
 
 1. **Cloudflare Account**: Sign up at [cloudflare.com](https://cloudflare.com)
-2. **Wrangler CLI**: Install the Cloudflare Workers CLI
-3. **Domain**: A domain name (optional, you can use the default workers.dev subdomain)
+2. **Wrangler CLI**: Install the Cloudflare Workers/Pages CLI
+3. **Rust Toolchain**: Nightly toolchain with WASM support (see README.md)
 
-## Setup
+## Deployment Steps
 
-### 1. Install Wrangler CLI
+### 1. Install Dependencies
 
 ```bash
-npm install -g wrangler
+npm install
 ```
 
 ### 2. Login to Cloudflare
 
 ```bash
-wrangler login
+npx wrangler login
 ```
 
-### 3. Configure the Project
-
-Edit `wrangler.toml` and update the following:
-
-- `name`: Your preferred worker name
-- `route`: Your domain (if you have one)
-- `kv_namespaces`: Remove or configure if you need KV storage
-
-### 4. Build the Project
+### 3. Build the Project
 
 ```bash
 npm run build:web
 ```
 
-This will:
-- Compile the Rust code to WebAssembly
-- Generate the necessary JavaScript bindings
-- Place the files in the `pkg/` directory
+This commands compiles the Rust code to WebAssembly and places the output in the `pkg/` directory.
 
-## Deployment
-
-### Quick Deploy
+### 4. Deploy to Cloudflare Pages
 
 ```bash
+# Deploy to production
 npm run deploy
-```
-
-This will:
-1. Build the web assets
-2. Deploy to Cloudflare Workers
-3. Provide you with a URL
-
-### Environment-Specific Deployments
-
-For staging and production environments, you can modify the `wrangler.toml` file and use:
-
-```bash
-# Deploy to staging
-wrangler deploy --env staging
 
-# Deploy to production
-wrangler deploy --env production
+# Or manually:
+npx wrangler pages deploy web --project-name evo
 ```
 
-### Local Development
+This uploads the `web/` directory (which includes the index.html, CSS, JS, and the generated WASM in `web/pkg/`) to Cloudflare Pages.
+
+## Local Development
 
-Test the worker locally before deploying:
+Test the Pages build locally:
 
 ```bash
 npm run dev:worker
 ```
 
-This will start a local development server that mimics the Cloudflare Workers environment.
+This builds the project and starts a local Pages server (using `wrangler pages dev`).
 
 ## Configuration
 
-### wrangler.toml
-
-The main configuration file contains:
-
-- **Worker settings**: Name, compatibility date, etc.
-- **Site configuration**: Points to the `./web` directory for static assets
-- **Build command**: Automatically runs `npm run build:web` before deployment
-- **Environment settings**: Separate configs for staging and production
-
-### Environment Variables
-
-You can add environment variables in `wrangler.toml`:
-
-```toml
-[vars]
-API_KEY = "your-api-key"
-ENVIRONMENT = "production"
-```
-
-### Custom Domains
-
-The application is deployed with a custom domain at [https://evo.tre.systems/](https://evo.tre.systems/).
-
-To use a custom domain:
+### COOP/COEP Headers regarding SharedArrayBuffer
 
-1. Add your domain to Cloudflare
-2. Update the `route` in `wrangler.toml`
-3. Deploy with `wrangler deploy --env production`
+The simulation uses `SharedArrayBuffer` for parallel processing (via `rayon`). This requires specific security headers to be served:
 
-## File Structure
+- `Cross-Origin-Opener-Policy: same-origin`
+- `Cross-Origin-Embedder-Policy: require-corp`
 
-```
-├── worker.js          # Cloudflare Worker code
-├── wrangler.toml      # Worker configuration
-├── web/               # Static assets
-│   ├── index.html
-│   ├── css/
-│   ├── js/
-│   └── pkg/           # WASM files (generated)
-└── pkg/               # WASM package (generated)
-```
+These are configured in the `web/_headers` file, which Cloudflare Pages uses to apply headers.
 
 ## Troubleshooting
 
-### Common Issues
-
-1. **WASM not loading**: Ensure CORS headers are set correctly
-2. **Build failures**: Check that all dependencies are installed
-3. **Deployment errors**: Verify your Cloudflare account and permissions
-
-### Debug Commands
-
-```bash
-# Check worker logs
-wrangler tail
-
-# Test locally
-wrangler dev
-
-# Check build output
-ls -la pkg/
-```
-
-## Performance
-
-The worker is optimized for:
-
-- **Fast loading**: WASM files are cached for 1 year
-- **CORS compliance**: Proper headers for cross-origin requests
-- **Static asset serving**: Efficient delivery of HTML, CSS, and JS
-
-## Monitoring
-
-Monitor your deployment:
-
-1. **Cloudflare Dashboard**: View analytics and logs
-2. **Worker Logs**: Use `wrangler tail` for real-time logs
-3. **Performance**: Check the Cloudflare Analytics dashboard
-
-## Security
-
-The worker includes:
-
-- **CORS headers**: Proper cross-origin resource sharing
-- **Security headers**: COEP and COOP for isolation
-- **Input validation**: Prevents directory traversal attacks
-
-## Cost
-
-Cloudflare Workers pricing:
-
-- **Free tier**: 100,000 requests/day
-- **Paid tier**: $5/month for 10M requests
-- **Additional**: $0.50 per million requests
-
-Most small to medium projects will fit within the free tier. 
+### "SharedArrayBuffer is not defined"
+If you see this error in the browser console, it means the COOP/COEP headers are missing. Ensure `web/_headers` exists and is being deployed.

src/simulation/mod.rs

@@ -222,7 +222,6 @@ impl Simulation {
         let mut new_energy = energy.current;
         let mut eaten_entity = None;
 
-        // Apply movement
         self.apply_movement_to_entity(
             genes,
             &mut new_pos,
@@ -232,15 +231,13 @@ impl Simulation {
             &nearby_entities,
         );
 
-        // Handle boundaries
         self.movement_system.handle_boundaries(
             &mut new_pos,
             &mut new_velocity,
             self.world_size,
             &self.config,
         );
 
-        // Handle interactions
         self.apply_interactions_to_entity(
             &mut new_energy,
             &mut eaten_entity,
@@ -250,11 +247,9 @@ impl Simulation {
             &nearby_entities,
         );
 
-        // Apply energy changes
         self.energy_system
             .update_energy(&mut new_energy, size, genes, &self.config);
 
-        // Check reproduction and death
         let population_density = self.calculate_population_density();
         let should_reproduce =
             self.check_reproduction_for_entity(new_energy, energy.max, genes, population_density);
@@ -496,7 +491,6 @@ impl Simulation {
             .collect()
     }
 
-    /// Get a reference to the world for stats calculation
     pub fn world(&self) -> &World {
         &self.world
     }

src/ui/mod.rs

@@ -2,7 +2,7 @@ mod state;
 
 use crate::config::SimulationConfig;
 use crate::simulation::Simulation;
-use state::State; // Import logic from state.rs
+use state::State;
 
 use std::sync::Arc;
 use winit::{

src/ui/state.rs

@@ -7,7 +7,7 @@ use wgpu::util::DeviceExt;
 struct Vertex {
     position: [f32; 2],
     color: [f32; 3],
-    center: [f32; 2], // Center position of the ball
+    center: [f32; 2],
     radius: f32,
 }
 
@@ -95,7 +95,7 @@ impl State {
                             offset: std::mem::size_of::<[f32; 2]>() as wgpu::BufferAddress
                                 + std::mem::size_of::<[f32; 3]>() as wgpu::BufferAddress,
                             shader_location: 2,
-                            format: wgpu::VertexFormat::Float32x2, // Changed to Float32x2 for center
+                            format: wgpu::VertexFormat::Float32x2,
                         },
                         wgpu::VertexAttribute {
                             offset: std::mem::size_of::<[f32; 2]>() as wgpu::BufferAddress
@@ -211,7 +211,6 @@ impl State {
             // Create a quad for each entity (will be rendered as a glowing ball)
             let color = [r, g, b];
 
-            // Quad vertices (two triangles to form a square)
             // Triangle 1
             vertices.push(Vertex {
                 position: [screen_x - quad_size, screen_y - quad_size],