Add master integration to CLI deploy and undeploy

- CLIConfig gains optional [master] section with address field
- dialMaster() creates McpMasterServiceClient (same TLS/token pattern)
- deploy: routes through master when [master] configured, --direct
  flag bypasses master for v1-style agent deployment
- undeploy: same master/direct routing pattern
- Master responses show per-step results (deploy, dns, edge)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

internal/config/cli.go

@@ -10,11 +10,19 @@ import (
 
 // CLIConfig is the configuration for the mcp CLI binary.
 type CLIConfig struct {
-	Services ServicesConfig `toml:"services"`
-	Build    BuildConfig    `toml:"build"`
-	MCIAS    MCIASConfig    `toml:"mcias"`
-	Auth     AuthConfig     `toml:"auth"`
-	Nodes    []NodeConfig   `toml:"nodes"`
+	Services ServicesConfig   `toml:"services"`
+	Build    BuildConfig      `toml:"build"`
+	MCIAS    MCIASConfig      `toml:"mcias"`
+	Auth     AuthConfig       `toml:"auth"`
+	Nodes    []NodeConfig     `toml:"nodes"`
+	Master   *CLIMasterConfig `toml:"master,omitempty"`
+}
+
+// CLIMasterConfig holds the optional master connection settings.
+// When configured, deploy/undeploy/status go through the master
+// instead of directly to agents.
+type CLIMasterConfig struct {
+	Address string `toml:"address"` // master gRPC address (e.g. "100.95.252.120:9555")
 }
 
 // BuildConfig holds settings for building container images.