The crew does not build the same thing twice (#7792)
Guard. A build run (assigned) on an issue is refused while a twin holds the work (src/crew/twin.ts): another open issue with the same title (case and edge spaces aside) that has a queued or running agent run; an open or merged pull on that twin's branch (<agent>/<number>[-slug]); or any open pull titled the same, or a pull titled the same that merged after this issue was opened (so a title that comes round again, like "Fix typo", can be built again). When the guard refuses, the agent posts one comment on the issue naming the twin and its standing (#N already holds this work (running|open|landed)). The check runs in the same write transaction as the run is created, beside the 10-minute fresh-pull guard. Closed, unmerged pulls hold nothing, so a failed attempt can be retried. Not covered: near-duplicate titles (different words, same idea).
Scorecard. Settings → Crew shows "Wasted runs per day", and GET /api/v1/crew/scorecard / the MCP scorecard tool carry wastedDays: agent runs ending "pull closed", "no changes pushed" or "already done", per UTC day, with their cost (src/core/wasted_days.ts). Retried outages are not counted. The terminal's "Crew scorecard" screen lists the same days (wasted <day>).