@signaliz/cli 1.0.4 → 1.0.7

package/README.md

@@ -234,6 +234,12 @@ signaliz gtm calibrate <campaign_id> --min-sample-size 10
 # Inspect and repair provider readiness without leaving the CLI
 signaliz gtm execution <campaign_id>
 signaliz gtm integrations --campaign-id <campaign_id> --include-planned
+signaliz gtm nango connect \
+  --provider-id apollo \
+  --integration-id apollo
+signaliz gtm nango tools \
+  --workspace-connection-id <workspace_connection_id> \
+  --provider-config-key apollo
 signaliz gtm route-preview --campaign-id <campaign_id> --layer sender
 signaliz gtm activate-route --campaign-id <campaign_id> \
   --provider-id instantly \
@@ -257,6 +263,86 @@ signaliz gtm feedback-webhook --provider instantly \
 
 ## Campaign Builder
 
+### Strategy-template campaign agent
+
+Use `gtm strategy-memory` to verify that private-safe strategy/workflow memory is
+seeded before asking the campaign agent to plan:
+
+```bash
+signaliz gtm strategy-memory \
+  --strategy-template non-medical-home-care \
+  --include-samples \
+  --json
+```
+
+Use `gtm agent-template` when you want the hosted MCP surface to emit reusable
+`CampaignBuilderAgentRequest` JSON before planning:
+
+```bash
+signaliz gtm agent-template \
+  --goal "Build a strategy-template campaign for mature local operators" \
+  --strategy-template non-medical-home-care \
+  --target-count 250 \
+  --use-local-leads \
+  --with-byo-placeholder \
+  --json
+```
+
+Use `gtm agent-plan` when you want the CLI to call the hosted MCP campaign-agent
+planner directly:
+
+```bash
+signaliz gtm agent-plan \
+  --goal "Build a strategy-template campaign for mature local operators" \
+  --strategy-template non-medical-home-care \
+  --target-count 500 \
+  --builtins lead_generation,local_leads,email_finding,email_verification,signals \
+  --custom-tool workspace_mcp:enrichment:account_enrich:workspace-mcp \
+  --json
+```
+
+Use `campaign-agent` when you want the CLI to assemble the full MCP plan first:
+private-safe strategy template, strategy-memory readiness, Brain risk, built-in
+Signaliz lanes, and BYO tool routes. BYO routes include read-only
+`gtm_provider_recipe_prepare` and `gtm_provider_route_activate` dry-run steps
+before any custom provider tool can run. Planning and dry-runs are
+read-only/spend-safe; launches require explicit approval flags.
+
+```bash
+signaliz campaign-agent init \
+  --strategy-template non-medical-home-care \
+  --target-count 250 \
+  --use-local-leads \
+  --with-byo-placeholder \
+  --output-file campaign-request.json
+
+signaliz campaign-agent plan \
+  --goal "Build a strategy-template campaign for mature local operators" \
+  --strategy-template non-medical-home-care \
+  --target-count 500 \
+  --builtins lead_generation,local_leads,email_finding,email_verification,signals \
+  --custom-tool workspace_mcp:enrichment:workspace_enrich:workspace-mcp \
+  --json
+
+signaliz campaign-agent plan \
+  --request-file campaign-request.json \
+  --target-count 250 \
+  --json
+
+signaliz campaign-agent dry-run \
+  --goal "Build a strategy-template campaign for mature local operators" \
+  --target-count 500 \
+  --json
+
+signaliz campaign-agent build-approved \
+  --goal "Build a strategy-template campaign for mature local operators" \
+  --confirm-launch \
+  --approve-all \
+  --approved-by operator@example.com \
+  --spend-limit 500 \
+  --json
+```
+
 ### Build a campaign
 
 ```bash