Separate moderation case status from decisions

docs/guides/moderation.md

@@ -132,18 +132,22 @@ priority and assign it to an eligible administrator or moderator. Filter the cas
 queue by status, priority, or assignment; active cases appear first, ordered by
 priority and most recent update.
 
-Move active cases between **Open**, **In review**, and **Escalated**, recording a
-reason for workflow changes. Close a case with one of these outcomes: **Resolved**,
-**Dismissed**, **Warning issued**, **Restriction applied**, **No action needed**,
-**Duplicate**, **Appeal upheld**, or **Appeal denied**. Every decision requires a
-reason. Reopen a closed case when new evidence or an appeal needs review; earlier
-decisions remain in its history. Editing case details does not reopen a case.
+Use **Change status** to move a case between **Open**, **In progress**, and
+**Closed**, recording a reason for each transition. Assignment is separate:
+a case can have an owner at any stage. To resume a closed case, change its status
+to Open or In progress. Evidence, assessments, actions, and earlier decisions
+remain in its history. Editing case details does not change its status.
+
+Existing closed outcomes are migrated to Closed. Previously escalated cases
+become In progress. Their previous statuses are recorded in history; existing
+decision reasons, action references, assignments, and follow-ups are preserved.
 
 Use **Edit assessment** to keep a concise current summary, list the applicable
 rules, and record a finding for each concern: hate speech, harassment, threats,
 safeguarding, spam, cheating, or another concern. Each finding is **Substantiated**,
 **Inconclusive**, or **Unsubstantiated**, with a short rationale. Findings describe
-the evidence; the case's workflow status and final outcome remain separate.
+the evidence; case status tracks whether work remains. Record the decision and
+its rationale in the assessment summary.
 Every saved assessment retains its author, timestamp, and complete previous
 revision. Assessments can be revised after closure without reopening the case.
 
@@ -174,9 +178,9 @@ external messaging delivery.
 Apply a ban or mute directly from an active case. The case fixes the target game
 and GUID and records the resulting restriction alongside the evidence. The same
 role, scope, and duration limits apply as elsewhere in Moderation. Applying a
-restriction leaves the case active so staff can finish reviewing it. Selecting a
-closure outcome records a decision; it does not itself send a warning, create a
-restriction, or revoke one. Linked restrictions can be revoked separately with
+restriction leaves the case active so staff can finish reviewing it. Changing case status
+records workflow progress; it does not send a warning, create a restriction, or
+revoke one. Linked restrictions can be revoked separately with
 the required permission and reason, including after a case closes. Reopening a
 case also leaves its restrictions in place. Check enforcement coverage after
 applying or revoking a restriction.
@@ -186,9 +190,9 @@ mute already recorded for this player with the case. This preserves the original
 action, author, time, delivery state, and expiry; it does not issue another action
 or extend a restriction. The same action can support more than one related case.
 Linking requires the current case revision and a reason, and appears in its timeline.
-When closing with **Warning issued** or **Restriction applied**, optionally reference
-one of the linked records. Warning references require a confirmed warning; failed
-or uncertain delivery remains visible without being presented as a confirmed warning.
+Linked records show what actually happened, including failed or uncertain delivery.
+They remain visible when a case closes; status changes do not require choosing
+or re-entering an action.
 
 Staff notes are explicitly labeled as notes. In match chat, select up to 100
 messages and choose **Attach to case** to open a case or add them to an existing