create --type bugfix
bare-id send REFUSES across nodes while CONTEXT.md promises a most-recently-active fallback
Surfaced by an operator thought experiment 2026-09-24: two nodes, one `dean` instance each, both uncontrolled. Both instances are dormant (active requires a driver attached AND being the most-recently-interacted instance; with no driver anywhere neither qualifies, and auto-suspend is opt-in/default-OFF so they stay warm indefinitely). Where does a bare `dean` message go? Three answers exist and they do not agree.

1. CONTEXT.md instance-state section: "the active instance is the bare-id routing target, its live siblings are dormant". With nothing active this reads as NO target. A wording hole - rest state is described as a routing input.
2. CONTEXT.md addressing section: "local-node instance if present -> else most-recently-active -> explicit override always available."
3. SHIPPED (spt-net registry resolve_among, REQ-INST-10): node-qualified -> local instance wins outright -> a SOLE live instance -> otherwise REFUSE with Ambiguity::AcrossNodes, forcing `dean@node`. There is NO most-recently-active rung anywhere in the send path.

So from a third node the send is refused, not MRA-resolved. Sharper: Status::routable() excludes only Offline, so a SUSPENDED sibling still counts toward the ambiguity - one warm instance plus one cold one refuses a bare send even though only one could take it warm.

WHICH IS RIGHT: the code. Guessing between two warm seats is how a message lands where nobody reads it, and the refusal renders copy-pasteable targets. MRA is wired where it belongs - notif and consent delivery - because a notif targets THE USER, who has a most-recent seat, while an agent message targets an ENDPOINT, where recency is not evidence. One sentence serving both consumers is why it reads as contradictory.

ASK (docs, no behaviour change): split the addressing rule by consumer - messaging refuses and forces qualification, notif/consent resolves by presence MRA - and stop the instance-state section describing rest state as the routing target. Same family as releases#341: two axes conflated in prose. If instead an MRA rung IS wanted for messaging, that is a behaviour change and needs its own ruling, because it makes delivery depend on a gossiped recency stamp.