v1.3.0

Added

• Local server support. ably accounts login --local points the CLI at a locally-running Ably server. The local server is stored as an ordinary account profile, so ably accounts list, current and switch work as usual and every data plane command runs unchanged. The guided flow prompts for the data plane URL, an API key and optionally a control plane URL and Control API token; --url and --control-url supply them explicitly for scripts. See docs/Local-Server.md.
• ABLY_URL and --url for one-off targeting. Both take host, port and TLS from a single value, e.g. ABLY_URL=https://my-endpoint.example.com ably channels publish my-channel "hello". Resolution order is --url > ABLY_URL > ABLY_ENDPOINT > account profile, and ABLY_ENDPOINT keeps its host-only semantics so existing usage is unaffected.
• Ably Chat integration rules. ably integrations create now supports the chat rule types: http/before-publish, hive/text-model-only, hive/dashboard, bodyguard/text-moderation, tisane/text-moderation, azure/text-moderation and aws/lambda/before-publish. Mismatched combinations (e.g. a chat rule type without --source-type chat.message) fail with a clear CLI error instead of an opaque Control API 4xx.
• --chat-room-filter on ably integrations create and update, for rules sourced from Ably Chat rooms (--source-type chat.message). integrations get and list display it too.

Changed

• The "Using:" banner names the endpoint whenever it is not Ably's default, and names the plane the command reaches, so e.g. ably apps list shows the control plane URL.
• ably accounts list reports each account's endpoint and control plane (dataPlane and controlUrl in JSON). ably accounts switch reports the full URL rather than a bare hostname.

Fixed

• ably integrations update can now update --target-url on http/before-publish rules.
• ably integrations update and delete no longer print Request Mode: undefined for chat rule types, and show invocationMode instead.
• ably integrations delete shows the chat room filter in its confirmation prompt.
• --chat-room-filter is rejected on channel-sourced rule types instead of producing a confusing Control API 422.
• channelFilter examples use valid regex syntax (chat:.*, not chat:*).
• Integration rule thresholds no longer accept key= as a threshold of 0, and no longer discard everything after a second =.
• The "Using:" banner shows the bare app ID when the app name cannot be resolved, instead of Unknown App (abc123).
• ably login --json labels every record with login rather than unknown.
• Control API failures are no longer reported twice.
• An invalid control plane URL is rejected up front with a message naming the value, instead of a raw TypeError on every request.
• Bumped tar to 7.5.21 to address a security advisory.