We catch silent coordination failures in agent systems. What should we ship next?

OSS layer for the kind of agent failures that tracing tools miss. Works for single-agent with tools, single-agent with MCP, or multi-agent workflows (CrewAI, LangGraph, custom).

What we catch today:

1. Silent loops between agents: Researcher to Writer to Reviewer that bounces forever because the Reviewer never approves.
2. Repeated agent or tool calls: Same task fired 50 times, nobody noticed.
3. Traffic spikes: Sudden burst of calls way out of pattern.

What we are working on for FinOps. The goal is actually to save money, not just the dashboard itself:

1. Workflow budget cap: Dollar limit for the whole run, halts before crossing.
2. Cost attributed to the failure or any other coordination or silent failure: "This $500 was burned in a silent loop. Here is the cycle."
3. Slow loop detection: The $0.05 per minute loop that burns $500 a week, way under any rate cap.
4. MCP retry loop detection: Agent retrying a flaky MCP server forever.
5. Approval bypass detection: A destructive tool was fired without the approval step (Replit case).

Would love to hear: is any of this actually useful, which one feels must-have versus nice-to-have, and would you try it locally if we ship it. We would rather build the thing one of you would actually run than ship five no one needs.