What problem does it solve? Users evaluating the ponytail approach lack a quick, honest summary of its measured impact, and risk seeing fabricated per-repo savings numbers that have no real baseline. ## Core Features & Use Cases - Benchmark Scoreboard: Renders a compact ASCII-bar scoreboard showing median reductions in lines of code (80–94%), cost (47–77%), and speed (3–6× faster) across 5 tasks and 3 models. - Honesty Boundary: Refuses to invent per-repo savings figures and instead points to /ponytail-debt and /ponytail-audit for real per-repo data. - One-Shot Display: Changes no mode, writes no files, and persists nothing; "stop ponytail" reverts. - Use Case: A developer asks "what does ponytail save" and immediately sees the published benchmark medians without any repo state being modified. ## Quick Start Ask the assistant to show the ponytail gain scoreboard to see the benchmark median savings for code, cost, and speed.