wireguard-docs tested by Argusic Runner

What the test found

The repo's example start.sh/stop.sh scripts run successfully on the container's built-in kernel WireGuard (built wg/ip toolchain in /tmp/wgtools), establishing real encrypted tunnels and passing TCP echo traffic across the example-simple-server-to-server, example-simple-client-to-server, example-internet-browsing-vpn, example-full, and example-lan-briding configs, with stop.sh cleanly removing all wg interfaces; the example-lan-briding/vancouver key files were corrected to match the configs (originals preserved as .stale).

Kernel WireGuard is built-in (CONFIG_WIREGUARD=y, module version 1.0.0). All start.sh/stop.sh runs used the real kernel WireGuard netlink inside unshared user+network namespaces with real veth transport links and the repo's actual keys/configs; only Endpoint hostnames were remapped to the veth transport IPs (no DNS in container). Verified: simple-server-to-server, simple-client-to-server, internet-browsing-vpn (server+laptop), example-full hub (public-server1+public-server2+home-server+laptop, needed net.ipv4.ip_forward=1 exactly as docs/setup prescribe), and lan-briding 3-node full mesh (all 6 directions). Phone configs are app-import only and strip-validate. The example-iptables script requires /sbin/iptables (system package, not installable here).

Argusic installed wireguard-docs in 45 minutes and launched it; verification reached Verified running for real. 6 of 6 recorded errors were worked through (see the timeline below).

Runsall runs of wireguard-docs

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.