Embassy v4.6.1

Embassy 4.6.1 — renamed sessions can talk again

When two Claude Code sessions share a name, Claude renames the second one to "name (2)". Embassy's registry parser rejected any session name with a space or parentheses, so such a session could neither send (every send failed with REGISTRY_INVALID_SCHEMA) nor be discovered. Nothing was wrong with the broker or its state; resetting the ledger would not have helped.

Now the session name is treated as a display label: any non-empty name up to 64 characters is accepted, and the public alias is derived from it the same way for endpoints, warnings and delivery checks — "compressor-pm (2)" becomes compressor-pm-2@host. A name with no usable letters or digits gets a stable claude-<hash> alias. Two sessions whose names normalise to the same alias are still refused with PEER_ALIAS_COLLISION rather than merged. Genuinely malformed records (missing fields, wrong types, wrong peer protocol) are still refused.

Upgrading — install and restart the broker; no state or protocol change. Update the CLI in each shell too, as with 4.6.0.

Tested with offline suite 429/429 on Node 22 (macOS and Ubuntu), including a real-registry fixture that sends and replies both ways as "compressor-pm (2)" and as a punctuation-only name.