* feat(web): incident records use case for audits The compliance use case covers the public half, telling customers through the status page (CC2.3). Nothing covered the half an auditor actually samples: the internal incident record. Add a use case that maps the record's fields (two timestamps, severity, commander, append-only timeline, approved postmortem, frozen close) to SOC 2 CC7.3-7.5, ISO 27001 A.5.25-5.28, the NIS2 cascade and the DORA clock, and is explicit about where the product stops. - new /use-case/incident-records with the incident timeline demo and question-shaped FAQs - product page audit-trail links and the compliance use case's CC7 line point at the new page instead of the status-page one - enterprise sales FAQ answers the "incident response process" questionnaire question with the record - compliance guides and the incident management hub link across - product page FAQ: the agent drafts the postmortem from the dashboard too; Slack only adds the channel history to the draft - use-case listing: brand casing, mention incident records * fix(web): qualify audit claims in incident records content Scope CC7 to supported parts, gate agent drafting by plan, drop the awareness/classification timestamp claims the record does not hold, and tie ISO retention to policy rather than the cert cycle. * fix(web): link incident records use case from compliance FAQ