Add documentation section and move GPU-FIX-README

Added a documentation section to the README with links to the MIT license and GPU Fix documentation. Moved GPU-FIX-README.md to the documentation directory for better organization.

GPU-FIX-README.md

@@ -1,158 +0,0 @@
-# Nebula Browser - GPU Error 18 Fix & Performance Optimizations
-
-## Problem Solved ✅
-**Error 18** - GPU process launch failure has been resolved. The browser now starts successfully and uses the best available rendering method.
-
-## What Was Fixed
-
-### 1. GPU Configuration System
-- **New GPU Config Manager**: Created `gpu-config.js` that intelligently handles GPU setup
-- **Automatic Fallback**: If GPU fails, automatically switches to software rendering
-- **Progressive Enhancement**: Tries GPU acceleration first, falls back gracefully
-- **No More Crashes**: Error 18 eliminated through proper GPU process handling
-
-### 2. Command Line Optimizations
-**Essential Fixes:**
-```javascript
-app.commandLine.appendSwitch('no-sandbox');
-app.commandLine.appendSwitch('disable-dev-shm-usage');
-app.commandLine.appendSwitch('disable-gpu-sandbox');
-```
-
-**Performance Improvements:**
-```javascript
-app.commandLine.appendSwitch('disable-background-timer-throttling');
-app.commandLine.appendSwitch('disable-renderer-backgrounding');
-app.commandLine.appendSwitch('max_old_space_size', '4096');
-```
-
-### 3. Smart GPU Detection
-The browser now:
-- ✅ Detects GPU capabilities at startup
-- ✅ Provides clear status information
-- ✅ Offers recommendations for improvements
-- ✅ Gracefully handles GPU failures
-
-## Performance Improvements Applied
-
-### 1. Memory Management
-- **Debounced History Recording**: Reduces file I/O operations
-- **Async File Operations**: Prevents UI blocking
-- **Garbage Collection**: Manual GC triggering available
-- **Memory Monitoring**: Built-in performance tracking
-
-### 2. Rendering Optimizations
-- **Hardware Acceleration**: When available, uses GPU for better performance
-- **Software Fallback**: Stable rendering when GPU isn't available
-- **CSS Optimizations**: Hardware-accelerated animations and scrolling
-- **Efficient Paint Management**: Reduced repaints and reflows
-
-### 3. Caching & Network
-- **Request Caching**: HTTP cache headers for faster loading
-- **Resource Preloading**: Critical resources loaded early
-- **QUIC Protocol**: Faster network connections
-- **localStorage Optimization**: Efficient bookmark and history management
-
-## Current Status
-
-### GPU Status: 
-- **Hardware Acceleration**: ❌ Not available on this system
-- **Software Rendering**: ✅ Working perfectly
-- **Stability**: ✅ No crashes, no Error 18
-- **Performance**: ✅ Optimized for software rendering
-
-### Browser Performance:
-- **Startup Time**: ⚡ Significantly improved
-- **Memory Usage**: 📉 Reduced and monitored
-- **Responsiveness**: ✅ Smooth UI interactions
-- **Stability**: ✅ Robust error handling
-
-## Diagnostic Tools Added
-
-### 1. GPU Diagnostics Page
-Location: `renderer/gpu-diagnostics.html`
-- Real-time GPU status monitoring
-- WebGL and Canvas 2D testing
-- Performance metrics
-- Manual fallback controls
-
-### 2. Performance Monitor
-- Memory usage tracking
-- CPU monitoring
-- Load time analysis
-- Automatic reporting every 5 minutes
-
-### 3. Startup Script
-Location: `start-gpu-safe.bat`
-- Multiple GPU configuration options
-- Debug mode with verbose logging
-- Administrator privilege checking
-
-## Usage Instructions
-
-### Normal Startup:
-```bash
-npm start
-```
-
-### Diagnostic Startup:
-```bash
-start-gpu-safe.bat
-```
-
-### Check GPU Status:
-1. Open browser
-2. Navigate to GPU diagnostics page
-3. View real-time status and recommendations
-
-## Why GPU Might Be Disabled
-
-Common reasons for GPU acceleration being unavailable:
-1. **Outdated Drivers**: Graphics drivers need updating
-2. **Hardware Limitations**: Older or integrated graphics
-3. **Windows Settings**: Hardware acceleration disabled in system
-4. **Virtual Environment**: Running in VM or remote desktop
-5. **Security Software**: Antivirus blocking GPU access
-
-## Recommendations
-
-### For Better Performance:
-1. **Update Graphics Drivers**: Check manufacturer website
-2. **Windows Update**: Ensure system is up to date  
-3. **Hardware Acceleration**: Enable in Windows display settings
-4. **Run as Administrator**: May help with GPU access
-5. **Check Antivirus**: Temporarily disable to test
-
-### Current Configuration Works:
-Even without GPU acceleration, the browser is now:
-- ⚡ **Fast**: Software rendering optimized
-- 🛡️ **Stable**: No crashes or errors
-- 🔧 **Configurable**: Easy to adjust settings
-- 📊 **Monitored**: Performance tracking included
-
-## Files Modified/Added
-
-### Core Files:
-- `main.js` - Enhanced GPU handling, performance optimizations
-- `preload.js` - Improved API exposure with caching
-- `performance-monitor.js` - System performance tracking
-
-### GPU Management:
-- `gpu-config.js` - Intelligent GPU configuration
-- `gpu-fallback.js` - Crash handling and fallbacks
-- `start-gpu-safe.bat` - Diagnostic startup script
-
-### UI/CSS:
-- `performance.css` - Hardware acceleration optimizations
-- `gpu-diagnostics.html` - GPU status and testing page
-
-## Result: ✅ Problem Solved
-
-Your Nebula browser now:
-1. **Starts without Error 18** ✅
-2. **Runs smoothly on your system** ✅  
-3. **Uses optimal rendering method** ✅
-4. **Provides performance monitoring** ✅
-5. **Offers diagnostic tools** ✅
-
-The browser is optimized to work great with or without GPU acceleration!