Description-Behavior Mismatch
- Category
- MCP Tool Poisoning
- Confidence
- 98% confidence
- Finding
The code's primary workflow is reading an existing event file and dispatching its recorded method calls to PaperEngine. It explicitly labels the output as synthetic offline replay rather than a strategy backtest. Its journal and intent exports could support ledger-related functionality, but they do not establish the declared complete strategy execution or separate Simmer mirror. PaperEngine internals are not supplied, so their capabilities cannot be verified; the visible entry point nevertheless has a materially different primary purpose.
- Content
