Use to reconstruct PonyBunny failure paths from logs, traces, state, and runtime evidence in order to identify the first bad transition.
Use when writing ADRs, migration notes, harness principles, verification records, or other technical documentation for PonyBunny.
Use to generate high-signal evaluation cases for PonyBunny changes, including success paths, failure modes, edge cases, and regression-sensitive behaviours.
Use when defining or reviewing runtime events, lifecycle payloads, and event-order expectations for PonyBunny.
Use when designing or reviewing PonyBunny as a harness-first system, especially around boundaries, evaluation flow, observability, and migration structure.
Use when mapping PonyBunny's current state against harness-first best-practice gaps and turning those gaps into actionable engineering inputs.
Use when turning repeated failures, weak evals, weak handoffs, or trace blind spots into concrete improvements to the development harness.
Use when designing or reviewing MCP servers and MCP-exposed capabilities used by PonyBunny.