Problem
Cleanup blocker summaries are count-oriented. During disk pressure, the operator cares most about how many bytes are trapped behind each blocker category and which specific blocked rows are largest.
Desired behavior
Cleanup reports should include blocked/rejected rows grouped and sorted by blocked bytes, not just counts.
Acceptance criteria
- Summaries include bytes by blocker reason for artifacts/worktrees where size is known.
- Top blocked rows are surfaced with handle, reason, and bytes.
- Existing count summaries remain available for compatibility.
Problem
Cleanup blocker summaries are count-oriented. During disk pressure, the operator cares most about how many bytes are trapped behind each blocker category and which specific blocked rows are largest.
Desired behavior
Cleanup reports should include blocked/rejected rows grouped and sorted by blocked bytes, not just counts.
Acceptance criteria