docs: update project documentation with recent architecture changes

Reflect the addition of Trojan protocol support, UDP handling, and
updated file structure in the project guide. Update configuration
options and request flow description to match current implementation.

Author: 6Kmfi6HP

CLAUDE.md

@@ -4,7 +4,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Project Overview
 
-EDtunnel is a Cloudflare Worker/Pages-based VLESS proxy tool that implements WebSocket transport protocol for tunneling traffic. It runs on Cloudflare's serverless infrastructure and provides a web-based proxy service with multi-protocol support.
+EDtunnel is a Cloudflare Worker/Pages-based proxy tool that implements WebSocket transport protocol for tunneling traffic. It runs on Cloudflare's serverless infrastructure and provides a web-based proxy service with multi-protocol support (VLESS and Trojan).
 
 ## Development Commands
 
@@ -33,12 +33,17 @@ src/
 ├── handlers/
 │   ├── main.js           # Main request router
 │   ├── http.js           # HTTP request handling
-│   └── websocket.js      # WebSocket upgrade and VLESS processing
+│   └── websocket.js      # WebSocket upgrade and protocol processing
 ├── protocol/
 │   ├── vless.js          # VLESS protocol parsing
+│   ├── trojan.js         # Trojan protocol parsing
 │   └── dns.js            # DNS query handling over UDP
 ├── proxy/
 │   ├── tcp.js            # TCP connection management
+│   ├── udp.js            # UDP connection handling
+│   ├── udp-handler.js    # UDP packet processing
+│   ├── http.js           # HTTP proxy support
+│   ├── vless.js          # VLESS proxy implementation
 │   ├── stream.js         # Stream processing utilities
 │   └── socks5.js         # SOCKS5 proxy client
 ├── generators/
@@ -48,21 +53,24 @@ src/
     ├── encoding.js       # Base64 encoding/decoding
     ├── validation.js     # UUID validation
     ├── parser.js         # Configuration parsing
+    ├── crypto.js         # Cryptographic utilities
+    ├── proxyResolver.js  # Proxy address resolution
     └── websocket.js      # WebSocket utilities
 ```
 
 ### Production Files
 
 - **`_worker.js`** - Obfuscated bundle for Cloudflare deployment
 - **`wrangler.toml`** - Cloudflare Worker configuration
+- **`dist/bundle.js`** - Non-obfuscated bundle (intermediate build)
 
 ### Request Flow
 
 1. `src/index.js` → exports `fetch` handler
-2. `handlers/main.js` → routes by URL path (`/cf`, `/{uuid}`, `/sub/{uuid}`)
-3. `handlers/websocket.js` → WebSocket upgrade for VLESS tunneling
-4. `protocol/vless.js` → parse VLESS header, extract destination
-5. `proxy/tcp.js` or `proxy/socks5.js` → establish outbound connection
+2. `handlers/main.js` → routes by URL path (`/cf`, `/{uuid}`, `/sub/{uuid}`, `/trojan`)
+3. `handlers/websocket.js` → WebSocket upgrade for VLESS/Trojan tunneling
+4. `protocol/vless.js` or `protocol/trojan.js` → parse protocol header, extract destination
+5. `proxy/tcp.js`, `proxy/udp.js`, or `proxy/socks5.js` → establish outbound connection
 
 ## Configuration
 
@@ -73,13 +81,19 @@ Environment variables (set in `wrangler.toml` or Cloudflare Dashboard):
 | `UUID` | User authentication (comma-separated for multiple) |
 | `PROXYIP` | Proxy server addresses (comma-separated, with optional port) |
 | `SOCKS5` | SOCKS5 proxy (`user:pass@host:port`) |
-| `SOCKS5_RELAY` | Enable SOCKS5 relay (`true`/`false`) |
+| `TROJAN_PASSWORD` | Trojan protocol password (optional, uses UUID if not set) |
 
-URL query parameters can override: `proxyip`, `socks5`, `socks5_relay` (UUID cannot be overridden for security).
+URL query parameters can override: `proxyip`, `socks5` (UUID cannot be overridden for security).
 
 ## Key Implementation Details
 
 - Uses Cloudflare's `cloudflare:sockets` for TCP connections
 - VLESS protocol version 0 with WebSocket transport
+- Trojan protocol support with SHA-224 password hashing
+- UDP support for DNS queries
 - Multi-proxy load balancing via random selection
 - Subscription formats: VLESS links, Clash YAML, Base64 encoded
+
+## Testing
+
+Test files are located in the `test/` directory. Run tests during development to verify changes.