# agentgateway v1.6.0 standalone egress proof (lab copy)

Slim copy of Marketing's 2026-10-05 harness for [`/agentgateway-egress-proxy/`](/agentgateway-egress-proxy/).

**Scope:** OSS standalone binary v1.6.0. **Not claimed:** Substrate / kagent runtime. No Docker.

## Version (P1)

See [`evidence/version.json`](evidence/version.json).

- `version`: 1.6.0
- `git_revision`: ea5608642b9d5c94c5baf5fd9f2f9849b808e963
- Release: https://github.com/agentgateway/agentgateway/releases/tag/v1.6.0
- Asset: `agentgateway-linux-amd64`
- Checksum verified: `496ed27e6a96b55a9ad7cabe5c2be7172511f44a3cb113e533d22bf93a7f079d`
- Test date: 2026-10-05 09:11:12 PDT

## Mode

Tunnel CONNECT (`binds[].tunnelProtocol: connect`). Allowlist: `example.com`, `httpbin.org`. Unmatched host: no `tcpRoute`. After CONNECT 200 the client sees a TLS error, not HTTP 404.

Working config: [`egress.yaml`](egress.yaml). Port 443 uses `mode: internal` (same docs page, routing-only). Docs-literal `gateways.secure.port: 443` failed with Permission denied: [`evidence/bind443-error.txt`](evidence/bind443-error.txt).

## Tests

| ID | Case | Result | Evidence |
| --- | --- | --- | --- |
| T1 | ALLOW example.com | HTTP/2 200, exit 0 | [`evidence/t1-allow-example.com.txt`](evidence/t1-allow-example.com.txt) |
| T1c | ALLOW httpbin.org | HTTP/2 200, exit 0 | log line in [`evidence/agentgateway.log`](evidence/agentgateway.log); curl file was not in the uploaded pack |
| T2 | DENY never-allowlisted-egress-test.example | CONNECT 200, then curl 35 TLS EOF | [`evidence/t2-deny-never-allowlisted.txt`](evidence/t2-deny-never-allowlisted.txt) |
| T3 | DENY pypi.org | CONNECT 200, then curl 35 TLS EOF | [`evidence/t3-deny-pypi.org.txt`](evidence/t3-deny-pypi.org.txt) |

Deny log signal: `error="route not found"`.

P7 (route-mode basicAuth) and P8 (Kubernetes ambient egress) were not run.