operational-docs

Apply repository templates and evidence rules to resolved-incident retrospective intake and postmortem drafting, runbook creation or edits, and durable service or alert knowledge. Also covers Confluence runbook imports and ownership or dependency lookup from existing cards. Triggers: 'draft the retro for the outage', 'update the runbook from this incident', 'capture durable operational lessons', 'which team owns payments and how do I page them'. Direct operational-document writing belongs to scribe. Active incidents use incident-investigation, alert design uses observability-engineer, and fleet prompt failures use agent-engineer.