Test parity audit across Go, Rust, and TypeScript

[abienkowski]

Problem

Each implementation has its own test suite with different counts (Go: 58, Rust: 104, TypeScript: 80), plus 26 integration tests. It is not confirmed that all three languages cover the same security-critical scenarios.

Solution

Audit test coverage per package across all three languages and fill gaps:

Area	Go	Rust	TypeScript
policy	9	15	10
middleware	21	48	37
proxy	28	41	26
transport	—	—	3
handler	—	—	3

Verify that for every security invariant in the Quint spec there is a corresponding unit test in each language, and that the 26 integration tests (deploy/test.sh + docker-compose) exercise the same scenarios for all three binaries.

Which implementation(s) would this affect?

• Go
• Rust
• TypeScript

Additional context

• make test-all runs all suites
• Tracked by epic First release prep: Quint spec review, test parity, and release pipeline validation #4