[milestone Milestone 2 ] Update `on_http_response_headers()` in `crates/proxy-wasm-evidence/src/filter.rs...

[telleroutlook]

🤖 Auto-filed from milestone doc bullet.

Repo: WasmAgent/wasmagent-proxy
Milestone: Milestone 2 — MCP Header Leakage API
Bullet:

Update on_http_response_headers() in crates/proxy-wasm-evidence/src/filter.rs: call classify_mcp_headers(), pass result to build_evidence(), and emit x-aep-mcp-header-risk response header when non-None

Relevant code context (from worktree)

symbol: crates: crates/aep-core/src/mcp_headers.rs:140
symbol: crates: crates/aep-core/src/mcp_headers.rs:151
symbol: crates: crates/proxy-wasm-evidence/src/recorder.rs:372
symbol: crates: crates/aep-core/src/evidence.rs:84
symbol: crates: crates/aep-core/src/recording.rs:143
symbol: evidence: crates/aep-core/src/evidence.rs:42
symbol: evidence: crates/aep-core/src/lib.rs:7
symbol: evidence: crates/proxy-wasm-evidence/src/recorder.rs:18
symbol: filter: crates/proxy-wasm-evidence/src/recorder.rs:354
symbol: classify_mcp_headers: crates/aep-core/src/mcp_headers.rs:38

Acceptance criteria

• Command cargo build && cargo test passes
• The specific work described in the bullet above is implemented in the smallest number of files required.
• No unrelated files touched (git status --short output limited to the intended change).

Notes for the implementer

This issue was auto-created by SweepMilestoneBulletToIssue. The bullet text is verbatim
from the milestone doc. If ambiguous or too large for a single implement cycle,
verify-first should return NEEDS_SPLIT with sub-issue proposals or NEEDS_HUMAN with the blocker.

---

Filed automatically.