Use collision-resistant request IDs in responses and logs

Problem

Request/response correlation IDs in server responses/logging can collide under concurrent traffic, weakening traceability and operational debugging.

Why now

Reference MCP servers are used as examples for production-like integrations and should model robust correlation-ID behavior.

Evidence Packet

• Version/commit under test: origin/main at 04cce79b4c2b
• Runtime environment: macOS 26.3 (arm64), Node 22.19.0, Python 3.14.0
• Minimal repro:
  1. Send high-concurrency request bursts across server tools.
  2. Inspect response/request correlation IDs and logs.
  3. Detect ambiguous or reused identifiers.
• Expected behavior: collision-resistant IDs per request/operation.
• Actual behavior: correlation identifiers are not consistently collision-resistant across server surfaces.

Why code change (not docs)

Correlation ID generation and propagation are runtime/logging contracts.

Scope / Codepaths

• src/*/src
• src/*/server

Acceptance Criteria

• Request IDs include collision-resistant component.
• IDs propagate consistently into responses and logs.
• Concurrency tests confirm uniqueness.

Validation Plan

• Add high-concurrency ID uniqueness tests.
• Validate response/log correlation contract stability.

Review the request ID code paths under src//src and src//server, starting with how identifiers are generated and propagated into responses and logs. Add high-concurrency uniqueness tests and validate that IDs remain consistently correlated across server surfaces without changing the response/logging contract.