Improve README

- Add dedicated About section explaining connection to awslambdaproxy
- Describe original performance limitations with EC2/SSH tunnels
- Explain NAT punching motivation and prototype development
- Detail Claude Code collaboration process

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: dan-v

.github/workflows/go-e2e.yml

@@ -1,11 +1,13 @@
 # Lambda NAT Proxy
 
-A QUIC-based NAT traversal proxy that routes traffic through AWS Lambda functions. Uses UDP hole punching and S3 coordination to establish direct QUIC tunnels through NAT devices.
-
-This is a follow-up to [awslambdaproxy](https://github.com/dan-v/awslambdaproxy) - I wanted to experiment with NAT punching to establish direct tunnels instead of using API Gateway. After building a working prototype, I had [Claude Code](https://claude.ai/code) implement the full system over a weekend.
+A serverless proxy implementation that uses NAT hole punching to establish QUIC tunnels through AWS Lambda functions. By coordinating through S3 and using UDP traversal techniques, it creates encrypted proxy connections without requiring any dedicated servers - just Lambda functions that spin up on demand.
 
 ![Dashboard](media/dashboard.png)
 
+## About
+
+This project evolved from exploring an unconventional idea: can AWS Lambda functions work as network proxies? Building on my earlier [awslambdaproxy](https://github.com/dan-v/awslambdaproxy) experiment, this implementation solves the performance and infrastructure challenges using NAT hole punching and QUIC protocol. The result is a serverless proxy that needs no EC2 instances, no SSH tunnels - just Lambda functions and clever networking.
+
 ## How It Works
 
 The system uses a three-phase approach to establish NAT traversal:
@@ -36,9 +38,9 @@ The Lambda function acts as an exit node, forwarding tunneled traffic to destina
 
 ```
 ┌─────────┐   SOCKS5    ┌──────────────┐   QUIC/UDP   ┌─────────┐   HTTP/S   ┌───────────┐
-│ Browser │ ────────── │ lambda-nat-  │ ──────────── │ Lambda  │ ────────── │ Internet  │
-│         │ :1080      │ proxy        │              │ Function│            │ Servers   │
-└─────────┘            └──────────────┘              └─────────┘            └───────────┘
+│ Browser │ ──────────  │ lambda-nat-  │ ──────────── │ Lambda  │ ────────── │ Internet  │
+│         │ :1080       │ proxy        │              │ Function│            │ Servers   │
+└─────────┘             └──────────────┘              └─────────┘            └───────────┘
                               │                            ▲
                               │ session data               │ S3 event
                               ▼                            │
@@ -52,7 +54,6 @@ The Lambda function acts as an exit node, forwarding tunneled traffic to destina
 
 **Prerequisites:**
 - AWS CLI configured with Lambda, S3, CloudFormation permissions
-- Go 1.21+ (for building from source)
 
 **Setup:**
 ```bash
@@ -132,6 +133,4 @@ proxy:
 make build                    # Build with embedded dashboard
 make docker-build             # Build using Docker (no local deps)
 make test                     # Run all tests
-```
-
-Build artifacts: `build/lambda-nat-proxy` (CLI), `build/bootstrap` (Lambda function)
+```