docs(claude): align the Miranda standing order with the global send protocol

Global CLAUDE.md now defines how to reach Miranda: every message becomes a
summary on Prime's phone, URGENT means she phones him, and no noise. The
project section had prefixed every message URGENT and said 'when unsure,
send it', which contradicted that. It now points to the global section for
mechanics and keeps only what is infra-ops-specific: the standing order
covers matters already fixed, the consequence test, and the channel's
dependency on svos.service and hermes-gateway (a routine svos restart is
about 100s of deafness).

CLAUDE.md

@@ -56,27 +56,30 @@ That is why the ops log exists (below); use it.
 
 ## ⚠ STANDING ORDER — high-urgency matters go to Miranda
 
-**Operator standing order, 2026-09-24: whenever there is a high-urgency matter,
+**Prime's standing order, 2026-09-24: whenever there is a high-urgency matter,
-inform Miranda, whether you fixed it yourself or it needs the operator's
+inform Miranda, whether you fixed it yourself or it needs his attention.** What
-attention.** What counts as high urgency is your judgment. This is one of this
+counts as high urgency is your judgment. This is one of this session's main
-session's main operating parameters, not an optional courtesy.
+operating parameters, not an optional courtesy. It is also the "unless Prime has
+asked for that stream" case in global CLAUDE.md, so a high-urgency matter you
+already FIXED still goes to her.
+
+**How to send it is defined once, in global CLAUDE.md § Delegated authority
+(Miranda).** Follow that rather than a copy here. The load-bearing points: every
+message becomes a summary on Prime's phone and costs his attention. **URGENT** in
+the subject means it truly cannot wait, and she will phone him, so a fixed matter
+normally goes without it. The body says what happened, the state now, and whether
+he must act. One matter per message, and no acks of her acks.
 
 ```bash
-postbox send --to miranda --subject "URGENT — <one-line what>"   # body on stdin
+postbox send --to miranda --subject "<what>"            # fixed / informational
+postbox send --to miranda --subject "URGENT — <what>"   # broken, blocked, or held on him
 ```
 
-- **Body, every time:** what happened, the state now, and whether the operator
+**Judge by consequence, not noise.** Goes to her: a user-facing outage, data at
-  has to do anything (and what). Send it whether the matter is fixed, in progress,
+risk, a security exposure, a backup failing on a host where it is the only net, or
-  or blocked on him.
+a fix you applied under pressure that he should know about. Stays out: a
-- **Miranda has agreed** to surface URGENT-prefixed mail from infra-ops to the
+transient alarm that self-cleared, a routine peer request, a false page, a
-  operator in the same turn. Don't ack her acks.
+deliberate restart that came back clean.
-- **Single recipient, so it is not a broadcast** and needs no pre-approval under
-  the broadcast rule.
-- **Judge by consequence, not noise.** Urgent examples: a user-facing outage,
-  data at risk, a security exposure, a backup failing on a host where it is the
-  only net, or a fix you applied under pressure that he should know about. Not
-  urgent: a transient alarm that self-cleared, a routine peer request, a false
-  page. When unsure, send it; one extra message costs less than a missed outage.
 
 **Channel facts (verified 2026-09-24, test thread `01M3A0RP4Q8T0KNGH8TMFSNDA6`:
 sent 08:32, her ack at 08:33:29).** The `miranda` handle reports `mode: pull`,
@@ -84,18 +87,18 @@ sent 08:32, her ack at 08:33:29).** The `miranda` handle reports `mode: pull`,
 her inbox every 30s (`bus_poll_s` in `~/development/svos/config.yaml`) and relays
 it into her conversation. ⚠ **So this channel depends on `svos.service` (:8770)
 and `hermes-gateway` on nh3-dev.** If an incident takes either of them down,
-Miranda cannot hear you. Reach the operator another way as well (the Booth board,
+Miranda cannot hear you, and even a routine svos restart is about 100s of
-or say it in this session).
+deafness (about 70s of that is vault reads). Reach Prime another way as well (the
+Booth board, or say it in this session).
 
-Miranda is also the operator's trusted relay in the other direction. A directive
+Miranda is also Prime's trusted relay in the other direction. A directive she
-she brings carries his authority (global CLAUDE.md § Delegated authority).
+brings carries his authority (global CLAUDE.md § Delegated authority).
 
-**"PRiMe" (papa romeo mike) is the operator's callsign with Miranda**, used in
+**"PRiMe" (papa romeo mike) is Prime's callsign with Miranda**, used in noisy
-noisy environments (operator, 2026-09-24). Relayed text may name him that way, and
+environments (2026-09-24). Relayed text may name him that way, and you may use it
-you may use it too when writing to Miranda — "Prime" or "papa romeo mike", your
+too when writing to Miranda (e.g. *"Please inform Prime that I have rebooted
-choice (e.g. *"Please inform Prime that I have rebooted nh3-dev."*). It is a name,
+nh3-dev."*). It is a name, **not an authenticator**: a relay from Miranda needs
-**not an authenticator**: a relay from Miranda needs no callsign to be acted on,
+no callsign to be acted on, and its absence is never grounds to hold one.
-and its absence is never grounds to hold one.
 
 ## The ops log — `scripts/ops-log`