tally connect

Provision this seat onto its relay channel via the skytale device-grant.

Registers the channel, runs the device-grant (#27), and stores the resulting channel-scoped credential to <tally_home>/relay.json so tally push/pull can reach the live relay. The owner key comes from --api-key or $SKYTALE_API_KEY; --new-account-email mints a throwaway test account first (use an undeliverable address, e.g. x@example.invalid).

Usage

tally connect [OPTIONS]

Options

--api-key <API_KEY>: Owner API key (else reads $SKYTALE_API_KEY)
--new-account-email <NEW_ACCOUNT_EMAIL>: Mint a fresh throwaway account with this email (testing only)
--channel <CHANNEL>: Channel override (default: the seat's pronoic/agents/<hex>)
--api-url <API_URL>: API base URL (default: $SKYTALE_API_URL, then tally config set api_url …, then https://api.skytale.sh)
--relay-url <RELAY_URL>: Per-owner relay URL (the CF-DO relay WsTransport connects to). The CLI syncs over WsTransport (/ws/<channel> routing), so pass a CF-DO relay here, NOT the gRPC droplet. Default: $SKYTALE_RELAY_URL, then tally config set relay_url …, then the channel's registered relay
--seat <SEAT>: Owner-facing seat label
default: cli-seat