/friction-triage — Triage accumulated friction
Use this workflow to read the Munin friction corpus, group recurring root causes, separate local fixes from upstream problems, and produce a compact issue proposal. Filing GitHub issues, adding board items, or writing Munin state requires explicit user direction; report mode is the default.
Workflow
- Read references/triage-details.md for the exact sweep-window and suppression rules, then filter the open events.
- Group repeated root causes and classify each cluster as locally actionable or upstream/covered.
- Route actionable clusters to the repository that owns the fix.
- Present a compact table before any publication.
- If the user explicitly requests filing, use the same reference for issue-body handling, board verification, and Munin updates.
Use /friction-triage report to stop after the proposed table without filing, changing board state, or writing Munin state.