[Docs]: Create local BENCHMARKS.md Ledger tracking Latency and Memory Overheads

Problem

To assert total dominance over application-layer monitoring tools (like TraceRoot.AI), FaultPlane needs a clean local reference file tracking baseline resource allocations and latency optimization profiles clearly inside the master branch [1.5, 1.6].

Proposed Solution

Scaffold a standardized tracking file named BENCHMARKS.md directly inside the root repository framework tree:

1. The Performance Delta Framework Tables: Structure responsive markdown comparison grids detailing explicit system parameters:
   • FaultPlane transport failover latency: < 2ms nominal tail boundary [1.5, 1.6].
   • Syscall tracing overhead: < 0.8% processing footprint.
2. Replication Instructions: Include short terminal snippet logs detailing how external engineers can execute localized profiling tests inside their own Docker setups.

Use Case

Provides undisputed, transparent mathematical proof regarding our infrastructure layer’s efficiency, giving system architects absolute conviction to star and fork our repository [1.5, 1.6].

Create the root-level BENCHMARKS.md requested in the issue. Use the proposed Performance Delta Framework values and include short Docker profiling instructions; done means the file contains the comparison tables, the stated latency and overhead targets, and reproducible terminal snippets.