Home Assistant instance registry commands (parity with hadron-server#641)

[shadowbrush]

hadron-server#641 ships the org-scoped HomeAssistantInstance registry behind hadrontool-home-assistant (the #640 plan). Per the CLI-feature-complete rule, the CLI needs coverage before the surface counts as done.

Mirror the hadron mcp-server command family (hadron-cli#220):

• hadron ha create --org <ref> --slug <slug> --name <n> --url <url> --token <access-token> [--allow-op <op>]... [--disabled] → createHomeAssistantInstance (token is write-only; never echoed back)
• hadron ha ls [--org <ref>] → homeAssistantInstances (uniform page)
• hadron ha get <ref> → homeAssistantInstance
• hadron ha ops <ref> → homeAssistantInstanceOps (the closed catalog filtered by allowlist — shows the exact ha__<slug>__<op> names to put in data.tools)
• hadron ha update <ref> [--name] [--url] [--token] [--allow-op]... [--enabled/--disabled] → updateHomeAssistantInstance (slug immutable)
• hadron ha rm <ref> → deleteHomeAssistantInstance

The six catalog ops: call_service, get_state, list_states, render_template, fire_event, list_services.

🤖 Generated with Claude Code