fix: hash full query in gate audit events for cross-path hash parity

[CGFixIT]

Problem

In gate.py, the /query handler logged two audit events with a truncated query:

audit_log({"event": "prompt_injection_blocked", "query": req.query[:50]})
...
audit_log({"event": "graph_error", "query": req.query[:50], "error": safe_msg})

But audit_log() (utils/logger.py) does not store the query verbatim — it replaces the query field with its SHA-256 hash:

if "query" in event and audit_fields.get("include_query_hash", True):
    raw_query = event.pop("query")
    event["query_hash"] = hash_query(raw_query)

So req.query[:50] produces a query_hash of only the first 50 characters. That hash does not match the canonical full-query hash written for the same query by:

• the graph audit node — graph.py passes the full query to audit_log, and
• the MCP path — mcp_hybrid_server.py passes the full query (this was a deliberate fix; tests/test_mcp_server.py:292 asserts event["query_hash"] == hash_query(long_query)).

Result: for any query longer than 50 chars, an injection-blocked or graph-error event can never be correlated by hash with the same query seen on the MCP/graph paths — defeating the purpose of the shared query_hash.

Change

Pass the full req.query in both audit_log calls (truncation removed). Added a short comment noting the field is hashed downstream.

Benefit

• Restores cross-path query_hash parity (HTTP gate ↔ graph audit ↔ MCP) for queries of any length — the same guarantee already test-asserted for MCP.
• No privacy change: the query is hashed before persistence either way; raw text is never written. Truncation gave no size benefit (the stored value is a fixed-length hash) while silently breaking correlation.

🤖 Generated with Claude Code

---

Generated by Claude Code