[FEATURE] Create Docker Compose Multi-Node Failure Simulator and Python Agent Demo Script

Problem

To reliably verify and benchmark our sub-2ms network hot-swap metrics and checkpoint rollback recovery pipelines, we need a standardized localized integration script environment to let community developers simulate container failure drops scenarios cleanly [1.5, 1.6].

Proposed Solution

Establish an isolated, beginner-friendly simulation harness inside a new directory folder named data-plane/agent_sim/:

1. The Multi-Node Docker Compose Grid: Set up a clean docker-compose.yml network blueprint containing:
   • faultplane-daemon (Our native Go compiled proxy application layer runtime proxy)
   • agent-worker-primary & agent-worker-standby (Isolated mock execution endpoints)
2. The Mock Python Agent Script: Write a lightweight multi-step python automation loops script that continuously pushes mock checkpoint strings. Midway through the tool chain processing runs, it triggers a hard container kill event, allowing developers to witness FaultPlane automatically hotswapping requests context parameters onto the standby instance securely [1.5].

Alternatives

Running manual curl commands over scattered local terminal windows canvas grids, which scales poorly and limits automatic tracking repeatability parameters.

Use Case

Gives any newly boarded open-source contributor a simple local testing environment, allowing them to verify and patch system optimization bugs securely with zero host platform hardware prerequisites.

Start by inspecting the repository layout and the native Go proxy entry point, then create the proposed data-plane/agent_sim/ directory. Add docker-compose.yml for faultplane-daemon, agent-worker-primary, and agent-worker-standby, plus the Python agent script that pushes checkpoint strings and triggers a hard container kill. Done means contributors can run the harness locally and observe requests switching to the standby instance.