Embassy v4.6.2

Embassy 4.6.2 — a wrong alias says so

embassy register-codex refused aliases that did not fit the rule — no codex- prefix, the wrong host, or the documentation's your-host placeholder used literally — under INVALID_GATEWAY_CONFIGURATION, which sent agents and operators to look for a broker problem that did not exist.

Now those refusals return INVALID_ALIAS with a hint that states the rule and the actual local host: Codex aliases are codex-<name>@<host>, lowercase letters, digits, underscore and dash before the @ (at most 32 characters including the prefix), the host from nodes.json after it. A malformed alias string is classified the same way at the request decoder, so one mistake produces one code. Genuine configuration failures keep INVALID_GATEWAY_CONFIGURATION. The accepted grammar is unchanged. README (both languages) and the packaged skill state the rule beside the example.

Upgrading — install and restart the broker; no state or protocol change.

Tested with offline suite 431/431 on Node 22 (macOS and Ubuntu), including a real CLI-to-broker fixture for each alias mistake and a real configuration failure.