Produces a blameless, structured incident postmortem with root-cause analysis, contributing factors, and prioritized action items. Use when the user says "write a postmortem", "post-incident review", "RCA", or pastes an incident timeline, Slack logs, or impact data after an incident is resolved. Use this for internal, learning-focused documentation — not for real-time incident comms (incident-commander-runbook) or customer-facing explanations (a status update or apology email).