feat: Complete repository reset for fresh start

- Remove all project files and directories
- Keep git history intact
- Archive documentation in archive-docs/ directory

💘 Generated with Crush

Assisted-by: GLM-4.6 via Crush <crush@charm.land>

config/wg-server-config-example.conf

@@ -1,45 +0,0 @@
-# Sample WireGuard Server Configuration
-# This is the configuration for the WireGuard VPN server
-# that football systems will connect to.
-#
-# Usage: Copy this to /etc/wireguard/wg0.conf on the VPN server
-# and adjust as needed for your environment.
-
-[Interface]
-# Private key of the VPN server
-# Generate with: wg genkey
-PrivateKey = <SERVER_PRIVATE_KEY>
-
-# VPN network address (this server)
-Address = 10.100.0.1/24
-
-# Port to listen on (UDP)
-ListenPort = 51820
-
-# DNS for VPN clients
-DNS = 10.100.0.1
-
-# Enable IP forwarding on the server
-# Add this to /etc/sysctl.conf: net.ipv4.ip_forward=1
-# Then run: sysctl -p
-
-# NAT configuration (POSTROUTING)
-# iptables -t nat -A POSTROUTING -s 10.100.0.0/24 -o eth0 -j MASQUERADE
-
-[Peer]
-# Client: football-1
-# Public key generated on client with: wg pubkey < client-private.key
-PublicKey = <CLIENT_1_PUBLIC_KEY>
-AllowedIPs = 10.100.0.2/32
-
-[Peer]
-# Client: football-2
-PublicKey = <CLIENT_2_PUBLIC_KEY>
-AllowedIPs = 10.100.0.3/32
-
-[Peer]
-# Client: football-3
-PublicKey = <CLIENT_3_PUBLIC_KEY>
-AllowedIPs = 10.100.0.4/32
-
-# Add more [Peer] sections as needed for additional football clients