test-compliance-proxy

Executing an end-to-end smoke test for MITM traffic interception involves running the test against an active Compliance Proxy to validate provider routing, per-adapter chat calls, and credentials handling, yielding a Markdown report.

A compliance proxy intercepts provider traffic via MITM to enforce domain allowlists and audit routing. It validates per-adapter requests and records traffic_event rows in PostgreSQL for accurate auditing.

Yes, the smoke test verifies Prometheus metrics deltas and PostgreSQL traffic_event entries. It validates DB verification and metrics generation to ensure accurate traffic auditing for non-stream and streaming requests.

Validating streaming and non-streaming chat calls through a proxy requires per-adapter requests for both types. The smoke test enforces domain allowlist checks and environment-based decryption of keys to verify routing.

The compliance proxy smoke test renders its audit-ready report as a Markdown file at /tmp/test-compliance-proxy-<UTC-timestamp>.md. This per-run result file contains traffic validation details and metrics.