[FEATURE] Implement Zero-Code-Intrusion Drop-In Reverse Proxy Traffic Redirect Layer

Problem

Currently, our Go control daemon provides isolated endpoints for state storage tracking, but lacks a centralized transparent drop-in HTTP reverse proxy handler layer. To adopt FaultPlane, client developers are forced to modify their codebase scripts or inject heavy application middlewares, breaking our absolute "zero-code-intrusion" technical design constraints rule [1.5, 1.6].

Proposed Solution

Implement a high-throughput, non-blocking reverse proxy module inside internal/proxy/ utilizing Go's native net/http/httputil primitives:

1. The Ingress Request Splicer: Capture incoming model inference trajectories asynchronously and forward payloads transparently to target client API endpoints (e.g., Anthropic/OpenAI servers) without thread thread latency.
2. The Atomic Context Frame Interceptor: Cache and map returning tool calls response arrays frames into our internal storage engine (CacheManager) on-the-fly, creating automated step checkpoints before returning data to the client application [1.5].

Alternatives

Forcing developers to inject software SDK hooks or complex third-party middlewares inside their code repositories, which increases thread scheduling overhead and degrades processing tail performance boundaries [1.5, 1.6].

Use Case

Enables instant enterprise onboarding lock-in. System operators can route thousands of concurrent agentic request streams through FaultPlane seamlessly by changing a single base URL config variable, shielding workloads non-intrusively [1.5, 1.6].

Start by inspecting internal/proxy/ and the existing CacheManager, then review Go's net/http/httputil primitives. The work is complete when transparent requests reach configured Anthropic/OpenAI-compatible endpoints, returning tool-call response frames are mapped into storage checkpoints, and client code requires only a base-URL change.