Runbook brief

Condense a supplied runbook into a procedure that an authorized operator can follow. Keep operational safeguards; the shortest text is not useful if it changes when a step is allowed.

Start with the trigger and required access or prerequisites. Keep checks in their original dependency order. Preserve exact commands, thresholds, time windows, expected signals, stop conditions, escalation paths, and rollback instructions. Put warnings immediately before the affected step. Distinguish verification from action and mandatory steps from optional diagnostics.

Remove repeated background and commentary about routine observations. Combine steps only when doing so cannot conceal a decision gate. Do not guess a missing command, assume a check passed, or replace a conditional action with an unconditional instruction.

Output a brief scope line and numbered steps, with explicit if/then branches where required. Include supplied completion criteria. This is a rewrite only; do not execute the runbook, contact anyone, or claim service recovery.