Add project origin and development story to README

- Mention connection to original awslambdaproxy project
- Brief explanation of NAT punching experiment motivation
- Credit Claude Code for weekend implementation
- Fix README formatting and build artifacts section

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

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

Author: dan-v

README.md

@@ -2,7 +2,9 @@
 
 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.
 
-![Dashboard](dashboard.png)
+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.
+
+![Dashboard](media/dashboard.png)
 
 ## How It Works
 
@@ -52,6 +54,11 @@ The Lambda function acts as an exit node, forwarding tunneled traffic to destina
 - AWS CLI configured with Lambda, S3, CloudFormation permissions
 - Go 1.21+ (for building from source)
 
+**Setup:**
+```bash
+lambda-nat-proxy config init
+```
+
 **Deploy infrastructure:**
 ```bash
 lambda-nat-proxy deploy
@@ -69,11 +76,11 @@ The system auto-detects deployed resources and handles session management automa
 ## Commands
 
 ```bash
+lambda-nat-proxy config init     # Create configuration file
 lambda-nat-proxy deploy          # Deploy AWS infrastructure
 lambda-nat-proxy run             # Start SOCKS5 proxy server
 lambda-nat-proxy status          # Show deployment status
 lambda-nat-proxy destroy         # Remove all AWS resources
-lambda-nat-proxy config init     # Create configuration file
 ```
 
 ## Performance Modes
@@ -111,21 +118,19 @@ proxy:
 
 **Session Management:**
 - Unique session IDs prevent collision between concurrent sessions
-- Sessions auto-expire after 8 minutes (Lambda timeout buffer)
 - S3 lifecycle rules clean up coordination files after 24 hours
 - Automatic session rotation when Lambda functions restart
 
 **QUIC Protocol Benefits:**
 - Built-in encryption (TLS 1.3)
 - Multiplexed streams (no head-of-line blocking)
-- Connection migration support
 - Congestion control optimized for varying network conditions
 
 ## Building
 
 ```bash
 make build                    # Build with embedded dashboard
-make docker-build            # Build using Docker (no local deps)
+make docker-build             # Build using Docker (no local deps)
 make test                     # Run all tests
 ```