autotouch-cli 0.2.100__tar.gz → 0.2.102__tar.gz

{autotouch_cli-0.2.100 → autotouch_cli-0.2.102}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: autotouch-cli
-Version: 0.2.100
+Version: 0.2.102
 Summary: Autotouch Smart Table CLI
 Project-URL: Homepage, https://app.autotouch.ai
 Project-URL: Documentation, https://github.com/nicolonic/autotouch_main/tree/main/docs/research-table/reference
@@ -91,6 +91,11 @@ autotouch auth bootstrap \
 autotouch auth check
 ```
 
+Demo accounts:
+
+- For a brand-new demo org plus developer key, use `autotouch auth bootstrap` as shown above.
+- For a demo login inside an existing seeded demo org, create the org with `apps/api/scripts/create_demo_org.py`, then add the user through the invite/register flow in `docs/operations/demo-accounts.md`.
+
 Config precedence:
 - Explicit flags win over environment variables.
 - Environment variables win over saved config.
@@ -183,7 +188,7 @@ For structured company builds, start with industry IDs plus geo/company-size fil
 
 For account-first prospecting from LinkedIn/Sales Navigator, build companies/accounts first, inspect the returned company IDs, then pass those IDs to `autotouch list-build leads --current-company-id ...`. Do not use Exa company search as a default pre-step for every LinkedIn list build; use it when the user's target is genuinely semantic, niche, competitor-based, or not meant to be LinkedIn-sourced.
 
-Use `autotouch agents ...` for recurring signal-based discovery. Scheduled agents support `--target ACCOUNTS` for company/account output and `--target LEADS` for people output. Every agent writes a source/signal table for the evidence it used; lead agents then write `candidate_research.candidates[]` on source rows and list-sync those candidates into the lead/candidate output table. See the agent playbook for the full source-table and candidate-sync contract.
+Use `autotouch agents ...` for recurring signal-based discovery. Scheduled agents support `--target ACCOUNTS` for company/account output and `--target LEADS` for people output. Every agent writes a source/signal table for the evidence it used; lead agents then write `candidate_research.candidates[]` on source rows and list-sync those candidates into the lead/candidate output table. LinkedIn engagement lead agents screen all harvested engagers by headline/title before company resolution and final lead scoring; company agents can keep matches in review or auto-promote qualified matches into the Companies workspace. See the agent playbook for the full source-table, candidate-sync, and company-promotion contract.
 
 ## Workflow Plans
 
@@ -198,7 +203,7 @@ discover -> plan -> scaffold -> run primitives -> inspect
 - `autotouch workflows scaffold --type <TYPE> --out-dir <DIR>` writes payload files and a command runbook.
 - `autotouch columns recipe` and `autotouch sequences recipe` remain leaf-level templates.
 
-Goal-level workflow types include `bulk-outreach`, `company-table-to-people`, `table-to-outreach`, `research-to-sequence`, `account-research`, `signal-outreach`, `website-visitors`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, Autotouch Sequences, webhooks, visitor sources, and external intent sources as sources/destinations inside one organized workflow layer instead of creating one-off top-level commands.
+Goal-level workflow types include `bulk-outreach`, `company-table-to-people`, `table-to-outreach`, `research-to-sequence`, `agent-to-sequence`, `account-research`, `signal-outreach`, `website-visitors`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, Autotouch Sequences, scheduled agents, webhooks, visitor sources, and external intent sources as sources/destinations inside one organized workflow layer instead of creating one-off top-level commands.
 
 ## Sources And Destinations
 
@@ -268,10 +273,11 @@ For automation or agent-driven setup, use:
 - `autotouch cli-manifest --output json` for the local machine-readable command contract
 - `autotouch cli-reference` for the shipped parser-generated reference
 - `autotouch capabilities --output json` for provider/workflow contracts
-- `autotouch --version` should be `0.2.100` or newer for structured company list builds without user-supplied keywords, stored list-build input lookup, research-workspace list-build guidance, the cleaned single LinkedIn-sourced list-build path, Exa Company Search up to 100 results, scheduled agent `--target ACCOUNTS|LEADS`, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee config, backend-owned directional source/destination helpers, goal-level workflow plans, and website visitor/external intent webhook workflow guidance
+- `autotouch --version` should be `0.2.102` or newer for structured company list builds without user-supplied keywords, stored list-build input lookup, research-workspace list-build guidance, the cleaned single LinkedIn-sourced list-build path, Exa Company Search up to 100 results, scheduled agent `--target ACCOUNTS|LEADS`, `agents signals --target`, the `agent-to-sequence` workflow scaffold, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee and active-sequence-conflict guard config, backend-owned directional source/destination helpers, goal-level workflow plans, and website visitor/external intent webhook workflow guidance
 - `autotouch capabilities --output json --select list_builds` for documented list-build inputs such as geography IDs, company size buckets, profile language, and company IDs
 - `autotouch integrations list` and `autotouch integrations status --provider <provider>` before choosing source/destination workflows
 - `autotouch workflows plan --type bulk-outreach` and `autotouch workflows scaffold --type bulk-outreach --out-dir workflow` for goal-level workflow planning
+- `autotouch workflows plan --type agent-to-sequence` and `autotouch workflows scaffold --type agent-to-sequence --out-dir workflow` for scheduled agent discovery into Autotouch Sequence tasks
 - `autotouch workflows plan --type website-visitors` and `autotouch workflows scaffold --type website-visitors --out-dir workflow` for website visitor or external intent provider webhook workflows
 - `autotouch integrations recipe --type from_crm --provider hubspot` for CRM-to-research-table imports
 - `autotouch columns recipe --type to_crm|to_outreach|to_leads|to_sequence` for research-table destination workflows

{autotouch_cli-0.2.100 → autotouch_cli-0.2.102}/README.md

@@ -66,6 +66,11 @@ autotouch auth bootstrap \
 autotouch auth check
 ```
 
+Demo accounts:
+
+- For a brand-new demo org plus developer key, use `autotouch auth bootstrap` as shown above.
+- For a demo login inside an existing seeded demo org, create the org with `apps/api/scripts/create_demo_org.py`, then add the user through the invite/register flow in `docs/operations/demo-accounts.md`.
+
 Config precedence:
 - Explicit flags win over environment variables.
 - Environment variables win over saved config.
@@ -158,7 +163,7 @@ For structured company builds, start with industry IDs plus geo/company-size fil
 
 For account-first prospecting from LinkedIn/Sales Navigator, build companies/accounts first, inspect the returned company IDs, then pass those IDs to `autotouch list-build leads --current-company-id ...`. Do not use Exa company search as a default pre-step for every LinkedIn list build; use it when the user's target is genuinely semantic, niche, competitor-based, or not meant to be LinkedIn-sourced.
 
-Use `autotouch agents ...` for recurring signal-based discovery. Scheduled agents support `--target ACCOUNTS` for company/account output and `--target LEADS` for people output. Every agent writes a source/signal table for the evidence it used; lead agents then write `candidate_research.candidates[]` on source rows and list-sync those candidates into the lead/candidate output table. See the agent playbook for the full source-table and candidate-sync contract.
+Use `autotouch agents ...` for recurring signal-based discovery. Scheduled agents support `--target ACCOUNTS` for company/account output and `--target LEADS` for people output. Every agent writes a source/signal table for the evidence it used; lead agents then write `candidate_research.candidates[]` on source rows and list-sync those candidates into the lead/candidate output table. LinkedIn engagement lead agents screen all harvested engagers by headline/title before company resolution and final lead scoring; company agents can keep matches in review or auto-promote qualified matches into the Companies workspace. See the agent playbook for the full source-table, candidate-sync, and company-promotion contract.
 
 ## Workflow Plans
 
@@ -173,7 +178,7 @@ discover -> plan -> scaffold -> run primitives -> inspect
 - `autotouch workflows scaffold --type <TYPE> --out-dir <DIR>` writes payload files and a command runbook.
 - `autotouch columns recipe` and `autotouch sequences recipe` remain leaf-level templates.
 
-Goal-level workflow types include `bulk-outreach`, `company-table-to-people`, `table-to-outreach`, `research-to-sequence`, `account-research`, `signal-outreach`, `website-visitors`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, Autotouch Sequences, webhooks, visitor sources, and external intent sources as sources/destinations inside one organized workflow layer instead of creating one-off top-level commands.
+Goal-level workflow types include `bulk-outreach`, `company-table-to-people`, `table-to-outreach`, `research-to-sequence`, `agent-to-sequence`, `account-research`, `signal-outreach`, `website-visitors`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, Autotouch Sequences, scheduled agents, webhooks, visitor sources, and external intent sources as sources/destinations inside one organized workflow layer instead of creating one-off top-level commands.
 
 ## Sources And Destinations
 
@@ -243,10 +248,11 @@ For automation or agent-driven setup, use:
 - `autotouch cli-manifest --output json` for the local machine-readable command contract
 - `autotouch cli-reference` for the shipped parser-generated reference
 - `autotouch capabilities --output json` for provider/workflow contracts
-- `autotouch --version` should be `0.2.100` or newer for structured company list builds without user-supplied keywords, stored list-build input lookup, research-workspace list-build guidance, the cleaned single LinkedIn-sourced list-build path, Exa Company Search up to 100 results, scheduled agent `--target ACCOUNTS|LEADS`, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee config, backend-owned directional source/destination helpers, goal-level workflow plans, and website visitor/external intent webhook workflow guidance
+- `autotouch --version` should be `0.2.102` or newer for structured company list builds without user-supplied keywords, stored list-build input lookup, research-workspace list-build guidance, the cleaned single LinkedIn-sourced list-build path, Exa Company Search up to 100 results, scheduled agent `--target ACCOUNTS|LEADS`, `agents signals --target`, the `agent-to-sequence` workflow scaffold, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee and active-sequence-conflict guard config, backend-owned directional source/destination helpers, goal-level workflow plans, and website visitor/external intent webhook workflow guidance
 - `autotouch capabilities --output json --select list_builds` for documented list-build inputs such as geography IDs, company size buckets, profile language, and company IDs
 - `autotouch integrations list` and `autotouch integrations status --provider <provider>` before choosing source/destination workflows
 - `autotouch workflows plan --type bulk-outreach` and `autotouch workflows scaffold --type bulk-outreach --out-dir workflow` for goal-level workflow planning
+- `autotouch workflows plan --type agent-to-sequence` and `autotouch workflows scaffold --type agent-to-sequence --out-dir workflow` for scheduled agent discovery into Autotouch Sequence tasks
 - `autotouch workflows plan --type website-visitors` and `autotouch workflows scaffold --type website-visitors --out-dir workflow` for website visitor or external intent provider webhook workflows
 - `autotouch integrations recipe --type from_crm --provider hubspot` for CRM-to-research-table imports
 - `autotouch columns recipe --type to_crm|to_outreach|to_leads|to_sequence` for research-table destination workflows

{autotouch_cli-0.2.100 → autotouch_cli-0.2.102}/autotouch_cli/commands/agents.py

@@ -297,6 +297,8 @@ def cmd_agents_update(args: argparse.Namespace, *, runtime: AgentCommandRuntime)
         payload: Dict[str, Any] = {}
         if getattr(args, "name", None):
             payload["name"] = args.name
+        if getattr(args, "assigned_user", None):
+            payload["assignedUserId"] = args.assigned_user
         if getattr(args, "status", None):
             payload["status"] = args.status
         if getattr(args, "auto_find_email", None) is not None:
@@ -548,10 +550,15 @@ def cmd_agents_generate_job_signal(args: argparse.Namespace, *, runtime: AgentCo
 
 def cmd_agents_signals(args: argparse.Namespace, *, runtime: AgentCommandRuntime) -> None:
     token = runtime.resolve_token(args.token, required=True)
+    params = None
+    target = str(getattr(args, "target", "") or "").strip()
+    if target:
+        params = {"targetType": target}
     data = runtime.request_api(
         "GET", "/api/agents/skill-packs",
         base_url=args.base_url, token=token,
         use_x_api_key=args.use_x_api_key,
+        params=params,
         timeout=args.timeout, verbose=args.verbose,
     )
     runtime.print_json(data, args.compact)
@@ -631,7 +638,10 @@ def register_agents_subcommands(
     pac.add_argument(
         "--auto-sequence-id",
         dest="auto_sequence_id",
-        help="Sequence ID — discovered leads get auto-enrolled. Triggers outreach automatically.",
+        help=(
+            "Sequence ID — enroll discovered leads after lead sync; sequence step settings control "
+            "manual vs automated execution."
+        ),
     )
     pac.add_argument("--status", choices=["DRAFT", "ACTIVE", "PAUSED"], help="Initial status")
     pac.add_argument("--from-file", dest="from_file", help="Path to JSON payload file")
@@ -643,6 +653,7 @@ def register_agents_subcommands(
     pau = agents_sub.add_parser("update", help="Update an existing agent")
     pau.add_argument("agent_id", help="Agent ID")
     pau.add_argument("--name", help="New agent name")
+    pau.add_argument("--assigned-user", dest="assigned_user", help="Assigned user ID")
     pau.add_argument("--status", choices=["DRAFT", "ACTIVE", "PAUSED"], help="New status")
     pau.add_argument("--auto-find-email", dest="auto_find_email", type=_bool_arg, default=None, help="Enable/disable auto email finder")
     pau.add_argument("--auto-find-phone", dest="auto_find_phone", type=_bool_arg, default=None, help="Enable/disable auto phone finder")
@@ -656,7 +667,10 @@ def register_agents_subcommands(
     pau.add_argument(
         "--auto-sequence-id",
         dest="auto_sequence_id",
-        help="Sequence ID for auto-enrollment. Pass empty string to clear.",
+        help=(
+            "Sequence ID for enrollment after lead sync; sequence step settings control manual vs "
+            "automated execution. Pass empty string to clear."
+        ),
     )
     pau.add_argument("--schedule-time", dest="schedule_time", help="Time of day (HH:MM) — used by daily/weekly")
     pau.add_argument("--schedule-tz", dest="schedule_tz", help="Timezone")
@@ -765,6 +779,7 @@ def register_agents_subcommands(
 
     # -- signals --
     pass_ = agents_sub.add_parser("signals", help="List available signal skill packs")
+    pass_.add_argument("--target", choices=AGENT_TARGET_CHOICES, help="Filter signals to a target type")
     add_api_common_arguments(pass_)
     pass_.set_defaults(func=handlers["signals"])
 

{autotouch_cli-0.2.100 → autotouch_cli-0.2.102}/autotouch_cli/data/CLI_REFERENCE.md

@@ -1,6 +1,6 @@
 # Autotouch CLI Reference
 
-Generated from the installed parser for `autotouch-cli` `0.2.100`.
+Generated from the installed parser for `autotouch-cli` `0.2.102`.
 Manifest schema version: `2`.
 
 ## Output Modes
@@ -69,7 +69,7 @@ Create a new agent
   - `--auto-find-phone` (kind=boolean; when omitted=False; when present=True): Enable auto phone finder
   - `--auto-broaden` (kind=boolean; when omitted=False; when present=True): Enable auto broaden search
   - `--auto-create-lead-mode` (kind=string; choices=qualified_only,everyone,manual_only): Which discovered prospects become leads (default: qualified_only)
-  - `--auto-sequence-id` (kind=string): Sequence ID — discovered leads get auto-enrolled. Triggers outreach automatically.
+  - `--auto-sequence-id` (kind=string): Sequence ID — enroll discovered leads after lead sync; sequence step settings control manual vs automated execution.
   - `--status` (kind=string; choices=DRAFT,ACTIVE,PAUSED): Initial status
   - `--from-file` (kind=file; input=file): Path to JSON payload file
   - `--generate` (kind=boolean; when omitted=False; when present=True): Auto-generate persona, topics, and job signal config
@@ -353,12 +353,14 @@ List available signal skill packs
 - Destructive: `no`
 - Output modes: `json, ndjson, human`
 - Example:
-  - `autotouch agents signals [-h] [--base-url BASE_URL] [--token TOKEN]
+  - `autotouch agents signals [-h] [--target {LEADS,ACCOUNTS}]
+                                [--base-url BASE_URL] [--token TOKEN]
                                 [--use-x-api-key] [--timeout TIMEOUT]
                                 [--output {json,ndjson,human}] [--compact]
                                 [--select SELECT |
                                 --json-pointer JSON_POINTER] [--verbose]`
 - Options:
+  - `--target` (kind=string; choices=LEADS,ACCOUNTS): Filter signals to a target type
   - `--base-url` (kind=string; default=https://app.autotouch.ai): API base URL (default: https://app.autotouch.ai)
   - `--token` (kind=string; sensitive): Developer API key / JWT token
   - `--use-x-api-key` (kind=boolean; when omitted=False; when present=True): Send token via X-API-Key header
@@ -379,6 +381,7 @@ Update an existing agent
 - Output modes: `json, ndjson, human`
 - Example:
   - `autotouch agents update [-h] [--name NAME]
+                               [--assigned-user ASSIGNED_USER]
                                [--status {DRAFT,ACTIVE,PAUSED}]
                                [--auto-find-email AUTO_FIND_EMAIL]
                                [--auto-find-phone AUTO_FIND_PHONE]
@@ -401,12 +404,13 @@ Update an existing agent
                                agent_id`
 - Options:
   - `--name` (kind=string): New agent name
+  - `--assigned-user` (kind=string): Assigned user ID
   - `--status` (kind=string; choices=DRAFT,ACTIVE,PAUSED): New status
   - `--auto-find-email` (kind=string): Enable/disable auto email finder
   - `--auto-find-phone` (kind=string): Enable/disable auto phone finder
   - `--auto-broaden` (kind=string): Enable/disable auto broaden search
   - `--auto-create-lead-mode` (kind=string; choices=qualified_only,everyone,manual_only): Which discovered prospects become leads
-  - `--auto-sequence-id` (kind=string): Sequence ID for auto-enrollment. Pass empty string to clear.
+  - `--auto-sequence-id` (kind=string): Sequence ID for enrollment after lead sync; sequence step settings control manual vs automated execution. Pass empty string to clear.
   - `--schedule-time` (kind=string): Time of day (HH:MM) — used by daily/weekly
   - `--schedule-tz` (kind=string): Timezone
   - `--schedule-frequency` (kind=string; choices=hourly,every_6h,every_12h,daily,weekly): Run cadence
@@ -6062,7 +6066,7 @@ Use workflows for full user goals. Recipes are leaf templates; workflow plans de
 - Example:
   - `autotouch workflows list`
   - `autotouch workflows plan --type bulk-outreach`
-  - `autotouch workflows scaffold --type research-to-sequence --out-dir workflow`
+  - `autotouch workflows scaffold --type agent-to-sequence --out-dir workflow`
 
 #### `autotouch workflows list`
 
@@ -6097,13 +6101,13 @@ Plan the workflow before creating files or running side effects. Use this to cho
 - Output modes: `json, ndjson, human`
 - Example:
   - `autotouch workflows plan [-h]
-                                --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}
+                                --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}
                                 [--out-file OUT_FILE]
                                 [--output {json,ndjson,human}] [--compact]
                                 [--select SELECT |
                                 --json-pointer JSON_POINTER]`
 - Options:
-  - `--type` (required; kind=string; choices=bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table): Workflow blueprint type
+  - `--type` (required; kind=string; choices=bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table): Workflow blueprint type
   - `--out-file` (kind=file; input=file): Save raw workflow payload to file
   - `--output` (kind=string; choices=json,ndjson,human; default=json): Output mode
   - `--compact` (kind=boolean; when omitted=False; when present=True): Print compact JSON
@@ -6121,13 +6125,13 @@ Alias for `workflows plan`
 - Output modes: `json, ndjson, human`
 - Example:
   - `autotouch workflows recipe [-h]
-                                  --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}
+                                  --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}
                                   [--out-file OUT_FILE]
                                   [--output {json,ndjson,human}] [--compact]
                                   [--select SELECT |
                                   --json-pointer JSON_POINTER]`
 - Options:
-  - `--type` (required; kind=string; choices=bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table): Workflow blueprint type
+  - `--type` (required; kind=string; choices=bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table): Workflow blueprint type
   - `--out-file` (kind=file; input=file): Save raw workflow payload to file
   - `--output` (kind=string; choices=json,ndjson,human; default=json): Output mode
   - `--compact` (kind=boolean; when omitted=False; when present=True): Print compact JSON
@@ -6145,13 +6149,13 @@ Emit ordered workflow files and commands for a blueprint
 - Output modes: `json, ndjson, human`
 - Example:
   - `autotouch workflows scaffold [-h]
-                                    --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}
+                                    --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}
                                     [--out-dir OUT_DIR]
                                     [--output {json,ndjson,human}] [--compact]
                                     [--select SELECT |
                                     --json-pointer JSON_POINTER]`
 - Options:
-  - `--type` (required; kind=string; choices=bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table): Workflow blueprint type
+  - `--type` (required; kind=string; choices=bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table): Workflow blueprint type
   - `--out-dir` (kind=string): Directory to save scaffold payload files
   - `--output` (kind=string; choices=json,ndjson,human; default=json): Output mode
   - `--compact` (kind=boolean; when omitted=False; when present=True): Print compact JSON

{autotouch_cli-0.2.100 → autotouch_cli-0.2.102}/autotouch_cli/data/cli-manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.2.100",
+  "version": "0.2.102",
   "manifest_schema_version": 2,
   "entry_points": {
     "autotouch": "autotouch_cli.cli:main",
@@ -8983,7 +8983,7 @@
       "examples": [
         "autotouch workflows list",
         "autotouch workflows plan --type bulk-outreach",
-        "autotouch workflows scaffold --type research-to-sequence --out-dir workflow"
+        "autotouch workflows scaffold --type agent-to-sequence --out-dir workflow"
       ],
       "stability": "stable",
       "handler": null
@@ -9133,6 +9133,7 @@
             "company-table-to-people",
             "table-to-outreach",
             "research-to-sequence",
+            "agent-to-sequence",
             "account-research",
             "signal-outreach",
             "website-visitors",
@@ -9242,7 +9243,7 @@
       },
       "availability": null,
       "examples": [
-        "autotouch workflows plan [-h]\n                                --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}\n                                [--out-file OUT_FILE]\n                                [--output {json,ndjson,human}] [--compact]\n                                [--select SELECT |\n                                --json-pointer JSON_POINTER]"
+        "autotouch workflows plan [-h]\n                                --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}\n                                [--out-file OUT_FILE]\n                                [--output {json,ndjson,human}] [--compact]\n                                [--select SELECT |\n                                --json-pointer JSON_POINTER]"
       ],
       "stability": "stable",
       "handler": "_fn"
@@ -9274,6 +9275,7 @@
             "company-table-to-people",
             "table-to-outreach",
             "research-to-sequence",
+            "agent-to-sequence",
             "account-research",
             "signal-outreach",
             "website-visitors",
@@ -9383,7 +9385,7 @@
       },
       "availability": null,
       "examples": [
-        "autotouch workflows recipe [-h]\n                                  --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}\n                                  [--out-file OUT_FILE]\n                                  [--output {json,ndjson,human}] [--compact]\n                                  [--select SELECT |\n                                  --json-pointer JSON_POINTER]"
+        "autotouch workflows recipe [-h]\n                                  --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}\n                                  [--out-file OUT_FILE]\n                                  [--output {json,ndjson,human}] [--compact]\n                                  [--select SELECT |\n                                  --json-pointer JSON_POINTER]"
       ],
       "stability": "stable",
       "handler": "_fn"
@@ -9415,6 +9417,7 @@
             "company-table-to-people",
             "table-to-outreach",
             "research-to-sequence",
+            "agent-to-sequence",
             "account-research",
             "signal-outreach",
             "website-visitors",
@@ -9523,7 +9526,7 @@
       },
       "availability": null,
       "examples": [
-        "autotouch workflows scaffold [-h]\n                                    --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}\n                                    [--out-dir OUT_DIR]\n                                    [--output {json,ndjson,human}] [--compact]\n                                    [--select SELECT |\n                                    --json-pointer JSON_POINTER]"
+        "autotouch workflows scaffold [-h]\n                                    --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}\n                                    [--out-dir OUT_DIR]\n                                    [--output {json,ndjson,human}] [--compact]\n                                    [--select SELECT |\n                                    --json-pointer JSON_POINTER]"
       ],
       "stability": "stable",
       "handler": "_fn"
@@ -36058,7 +36061,7 @@
         {
           "dest": "auto_sequence_id",
           "required": false,
-          "help": "Sequence ID \u2014 discovered leads get auto-enrolled. Triggers outreach automatically.",
+          "help": "Sequence ID \u2014 enroll discovered leads after lead sync; sequence step settings control manual vs automated execution.",
           "kind": "string",
           "action": "store",
           "flags": [
@@ -36301,6 +36304,17 @@
           ],
           "takes_value": true
         },
+        {
+          "dest": "assigned_user",
+          "required": false,
+          "help": "Assigned user ID",
+          "kind": "string",
+          "action": "store",
+          "flags": [
+            "--assigned-user"
+          ],
+          "takes_value": true
+        },
         {
           "dest": "status",
           "required": false,
@@ -36369,7 +36383,7 @@
         {
           "dest": "auto_sequence_id",
           "required": false,
-          "help": "Sequence ID for auto-enrollment. Pass empty string to clear.",
+          "help": "Sequence ID for enrollment after lead sync; sequence step settings control manual vs automated execution. Pass empty string to clear.",
           "kind": "string",
           "action": "store",
           "flags": [
@@ -36654,7 +36668,7 @@
       },
       "availability": null,
       "examples": [
-        "autotouch agents update [-h] [--name NAME]\n                               [--status {DRAFT,ACTIVE,PAUSED}]\n                               [--auto-find-email AUTO_FIND_EMAIL]\n                               [--auto-find-phone AUTO_FIND_PHONE]\n                               [--auto-broaden AUTO_BROADEN]\n                               [--auto-create-lead-mode {qualified_only,everyone,manual_only}]\n                               [--auto-sequence-id AUTO_SEQUENCE_ID]\n                               [--schedule-time SCHEDULE_TIME]\n                               [--schedule-tz SCHEDULE_TZ]\n                               [--schedule-frequency {hourly,every_6h,every_12h,daily,weekly}]\n                               [--schedule-days {all,weekdays}]\n                               [--schedule-day-of-week 0-6]\n                               [--schedule-window-start SCHEDULE_WINDOW_START]\n                               [--schedule-window-end SCHEDULE_WINDOW_END]\n                               [--from-file FROM_FILE] [--dry-run]\n                               [--base-url BASE_URL] [--token TOKEN]\n                               [--use-x-api-key] [--timeout TIMEOUT]\n                               [--output {json,ndjson,human}] [--compact]\n                               [--select SELECT | --json-pointer JSON_POINTER]\n                               [--verbose]\n                               agent_id"
+        "autotouch agents update [-h] [--name NAME]\n                               [--assigned-user ASSIGNED_USER]\n                               [--status {DRAFT,ACTIVE,PAUSED}]\n                               [--auto-find-email AUTO_FIND_EMAIL]\n                               [--auto-find-phone AUTO_FIND_PHONE]\n                               [--auto-broaden AUTO_BROADEN]\n                               [--auto-create-lead-mode {qualified_only,everyone,manual_only}]\n                               [--auto-sequence-id AUTO_SEQUENCE_ID]\n                               [--schedule-time SCHEDULE_TIME]\n                               [--schedule-tz SCHEDULE_TZ]\n                               [--schedule-frequency {hourly,every_6h,every_12h,daily,weekly}]\n                               [--schedule-days {all,weekdays}]\n                               [--schedule-day-of-week 0-6]\n                               [--schedule-window-start SCHEDULE_WINDOW_START]\n                               [--schedule-window-end SCHEDULE_WINDOW_END]\n                               [--from-file FROM_FILE] [--dry-run]\n                               [--base-url BASE_URL] [--token TOKEN]\n                               [--use-x-api-key] [--timeout TIMEOUT]\n                               [--output {json,ndjson,human}] [--compact]\n                               [--select SELECT | --json-pointer JSON_POINTER]\n                               [--verbose]\n                               agent_id"
       ],
       "stability": "stable",
       "handler": "_fn"
@@ -38300,6 +38314,21 @@
       "required_flags": [],
       "positionals": [],
       "options": [
+        {
+          "dest": "target",
+          "required": false,
+          "help": "Filter signals to a target type",
+          "kind": "string",
+          "action": "store",
+          "choices": [
+            "LEADS",
+            "ACCOUNTS"
+          ],
+          "flags": [
+            "--target"
+          ],
+          "takes_value": true
+        },
         {
           "dest": "base_url",
           "required": false,
@@ -38453,7 +38482,7 @@
       },
       "availability": null,
       "examples": [
-        "autotouch agents signals [-h] [--base-url BASE_URL] [--token TOKEN]\n                                [--use-x-api-key] [--timeout TIMEOUT]\n                                [--output {json,ndjson,human}] [--compact]\n                                [--select SELECT |\n                                --json-pointer JSON_POINTER] [--verbose]"
+        "autotouch agents signals [-h] [--target {LEADS,ACCOUNTS}]\n                                [--base-url BASE_URL] [--token TOKEN]\n                                [--use-x-api-key] [--timeout TIMEOUT]\n                                [--output {json,ndjson,human}] [--compact]\n                                [--select SELECT |\n                                --json-pointer JSON_POINTER] [--verbose]"
       ],
       "stability": "stable",
       "handler": "_fn"

{autotouch_cli-0.2.100 → autotouch_cli-0.2.102}/autotouch_cli/parser.py

@@ -488,7 +488,7 @@ def build_parser(
     pw._codex_examples = [
         "autotouch workflows list",
         "autotouch workflows plan --type bulk-outreach",
-        "autotouch workflows scaffold --type research-to-sequence --out-dir workflow",
+        "autotouch workflows scaffold --type agent-to-sequence --out-dir workflow",
     ]
     workflows_sub = pw.add_subparsers(dest="workflows_cmd", required=True)
 

{autotouch_cli-0.2.100 → autotouch_cli-0.2.102}/autotouch_cli/templates.py

@@ -51,6 +51,7 @@ COLUMN_RECIPE_ALIASES: Dict[str, Dict[str, Any]] = {
             "Directional alias: Autotouch Leads -> Autotouch Sequence.",
             "Use this after leads exist and the user wants Autotouch sequence enrollment.",
             "Set config.assignedToUserId so generated sequence tasks are assigned to the intended user.",
+            "Keep config.skipActiveSequenceConflicts=true unless the user explicitly wants parallel enrollment for people already active in another sequence.",
         ],
     },
     "to_crm": {
@@ -1649,6 +1650,7 @@ def _to_sequence_payload(*, source_lead_column: str = "sync_to_leads") -> Dict[s
         "sequenceId": "<SEQUENCE_ID>",
         "sourceLeadColumn": source_lead_column,
         "assignedToUserId": "<USER_ID>",
+        "skipActiveSequenceConflicts": True,
     }
     return payload
 
@@ -1737,6 +1739,7 @@ def _workflow_scaffold_research_to_sequence() -> Dict[str, Any]:
             table_scope="source",
             notes=[
                 "Set sequenceId and assignedToUserId before creating the column.",
+                "Keep skipActiveSequenceConflicts=true unless the user explicitly wants parallel enrollment for people already active in another sequence.",
                 "AI-draft sequence steps should default to manual review until users trust the outputs.",
             ],
         ),
@@ -1759,6 +1762,108 @@ def _workflow_scaffold_research_to_sequence() -> Dict[str, Any]:
     }
 
 
+def _agent_to_sequence_payload() -> Dict[str, Any]:
+    return {
+        "name": "<AGENT_NAME>",
+        "targetType": "LEADS",
+        "assignedUserId": "<USER_ID>",
+        "personaConfig": {
+            "brief": "<ICP_BRIEF>",
+            "industries": ["Software Development"],
+            "companySizes": ["11-50", "51-200"],
+            "locations": ["United States"],
+            "companyExclusions": [],
+            "candidatesPerCompany": 2,
+            "additionalContext": (
+                "Find people who are likely to own or influence the outreach motion. "
+                "Return none when the company or person fit is weak."
+            ),
+        },
+        "selectedSignals": [
+            {
+                "key": "hiring-signals",
+                "config": {
+                    "jobTitles": ["Sales Development Representative", "Business Development Representative", "SDR", "BDR"],
+                    "keywords": ["outbound", "prospecting", "cold email", "cold calling"],
+                    "remoteOnly": False,
+                    "lookbackWindow": "24h",
+                },
+            }
+        ],
+        "schedule": {
+            "timezone": "America/New_York",
+            "timeOfDay": "09:00",
+            "frequency": "daily",
+            "days": "weekdays",
+        },
+        "autoFindEmail": True,
+        "autoCreateLeadMode": "qualified_only",
+        "autoSequenceId": "<SEQUENCE_ID>",
+        "status": "ACTIVE",
+    }
+
+
+def _sequence_task_query_payload() -> Dict[str, Any]:
+    return {
+        "filters": [
+            {"field": "sequence_id", "operator": "eq", "value": "<SEQUENCE_ID>"},
+            {"field": "assigned_to", "operator": "eq", "value": "<USER_ID>"},
+            {"field": "task_status", "operator": "eq", "value": "pending"},
+        ],
+        "sort": {"field": "due_date", "direction": "asc"},
+        "include_skipped": False,
+        "include_total_count": True,
+        "include_research_values": True,
+    }
+
+
+def _workflow_scaffold_agent_to_sequence() -> Dict[str, Any]:
+    artifacts = [
+        _workflow_artifact(
+            step=1,
+            kind="agent_payload",
+            provider="agents",
+            filename="01-agent-to-sequence.json",
+            payload=_agent_to_sequence_payload(),
+            table_scope="agent",
+            notes=[
+                "Use this payload when you want explicit signal/persona config instead of --generate.",
+                "Keep targetType=LEADS and autoCreateLeadMode=qualified_only for sequence handoffs unless the user asks otherwise.",
+            ],
+        ),
+        _workflow_artifact(
+            step=2,
+            kind="task_query",
+            provider="tasks",
+            filename="02-sequence-task-query.json",
+            payload=_sequence_task_query_payload(),
+            table_scope="sequence",
+            notes=["Set SEQUENCE_ID and USER_ID before querying the visible tasks created by the run."],
+        ),
+    ]
+    return {
+        "artifacts": artifacts,
+        "commands": [
+            "autotouch auth status --output json",
+            "autotouch agents signals --target LEADS --output json",
+            "autotouch sequences list --status ACTIVE --include-stats --output json",
+            "autotouch sequences get --sequence-id <SEQUENCE_ID> --output json",
+            "autotouch agents create --name '<AGENT_NAME>' --target LEADS --assigned-user <USER_ID> --generate --auto-find-email --auto-create-lead-mode qualified_only --auto-sequence-id <SEQUENCE_ID> --status ACTIVE --output json",
+            "autotouch agents update <AGENT_ID> --assigned-user <USER_ID> --auto-find-email true --auto-create-lead-mode qualified_only --auto-sequence-id <SEQUENCE_ID> --status ACTIVE --output json",
+            "autotouch agents watch <AGENT_ID> --interval 10 --max-wait 900 --output json",
+            "autotouch agents runs <AGENT_ID> --limit 5 --output json",
+            "autotouch sequences stats --sequence-id <SEQUENCE_ID> --output json",
+            "autotouch tasks query --data-file 02-sequence-task-query.json --output json",
+        ],
+        "notes": [
+            "Use an existing ACTIVE Autotouch Sequence. The sequence's own step settings control manual review versus automated execution.",
+            "For demos, prefer manual-review or AI-draft manual sequence steps so the created tasks are visible before any send/execute action.",
+            "Use the --generate create command for a fast demo path, or edit 01-agent-to-sequence.json when the signal/persona config must be deterministic.",
+            "Do not default to LinkedIn signals unless the user asks for LinkedIn or the signal catalog indicates that LinkedIn is connected and appropriate.",
+        ],
+    }
+
+
 def _workflow_scaffold_company_table_to_people() -> Dict[str, Any]:
     artifacts = [
         _workflow_artifact(
@@ -1874,7 +1979,7 @@ def _workflow_scaffold_signal_outreach() -> Dict[str, Any]:
             "autotouch agents --help",
             "autotouch agents generate-persona --target LEADS --output json",
             "autotouch agents create --help",
-            "autotouch workflows scaffold --type research-to-sequence --out-dir sequence-handoff",
+            "autotouch workflows scaffold --type agent-to-sequence --out-dir sequence-handoff",
             "autotouch workflows scaffold --type table-to-outreach --out-dir outreach-handoff",
         ],
         "notes": [
@@ -2260,6 +2365,7 @@ def _workflow_scaffold_bundle(workflow_type: str) -> Dict[str, Any]:
         "company-table-to-people": _workflow_scaffold_company_table_to_people,
         "table-to-outreach": _workflow_scaffold_table_to_outreach,
         "research-to-sequence": _workflow_scaffold_research_to_sequence,
+        "agent-to-sequence": _workflow_scaffold_agent_to_sequence,
         "account-research": _workflow_scaffold_account_research,
         "signal-outreach": _workflow_scaffold_signal_outreach,
         "website-visitors": _workflow_scaffold_website_visitors,

{autotouch_cli-0.2.100 → autotouch_cli-0.2.102}/autotouch_cli/workflows/registry.py

@@ -97,6 +97,33 @@ _GOAL_WORKFLOW_BLUEPRINTS: Dict[str, Dict[str, Any]] = {
             {"provider": "to_sequence", "purpose": "enroll Leads into an active sequence and assign generated tasks"},
         ],
     },
+    "agent-to-sequence": {
+        "goal": "Run a lead-target scheduled agent, create qualified Leads, and enroll them into an active Autotouch Sequence.",
+        "use_case": "scheduled_agent_sequence_handoff",
+        "supported_starting_points": ["scheduled_agent", "signal_catalog", "active_sequence"],
+        "recommended_when": [
+            "the user wants Autotouch to find signal-qualified people and create visible sequence tasks",
+            "the destination is an Autotouch Sequence rather than Instantly, Smartlead, or an external CRM",
+            "the demo or workflow should show agent discovery, lead sync, sequence enrollment, and task inspection end to end",
+        ],
+        "default_safety": {
+            "target_type": "LEADS",
+            "auto_create_lead_mode": "qualified_only",
+            "assigned_user_required": True,
+            "sequence_must_be_active": True,
+            "ai_draft_steps": "manual_review",
+            "skip_active_sequence_conflicts": True,
+            "sample_first": True,
+        },
+        "steps": [
+            {"provider": "auth", "purpose": "confirm API key, organization, user, and remaining credits"},
+            {"provider": "agents.signals", "purpose": "list lead-compatible signal packs for this organization"},
+            {"provider": "sequences", "purpose": "choose an existing ACTIVE sequence with manual-review tasks for demos"},
+            {"provider": "agents", "purpose": "create or update a LEADS agent with auto email, qualified-only lead creation, assignee, and autoSequenceId"},
+            {"provider": "agents.watch", "purpose": "run the agent and wait for a terminal run state"},
+            {"provider": "sequences|tasks", "purpose": "inspect sequence stats and visible assigned tasks"},
+        ],
+    },
     "account-research": {
         "goal": "Research accounts for rep enablement, optionally discover leads, and hand off to manual AI-draft sequences.",
         "use_case": "rep_enablement",

{autotouch_cli-0.2.100 → autotouch_cli-0.2.102}/autotouch_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: autotouch-cli
-Version: 0.2.100
+Version: 0.2.102
 Summary: Autotouch Smart Table CLI
 Project-URL: Homepage, https://app.autotouch.ai
 Project-URL: Documentation, https://github.com/nicolonic/autotouch_main/tree/main/docs/research-table/reference
@@ -91,6 +91,11 @@ autotouch auth bootstrap \
 autotouch auth check
 ```
 
+Demo accounts:
+
+- For a brand-new demo org plus developer key, use `autotouch auth bootstrap` as shown above.
+- For a demo login inside an existing seeded demo org, create the org with `apps/api/scripts/create_demo_org.py`, then add the user through the invite/register flow in `docs/operations/demo-accounts.md`.
+
 Config precedence:
 - Explicit flags win over environment variables.
 - Environment variables win over saved config.
@@ -183,7 +188,7 @@ For structured company builds, start with industry IDs plus geo/company-size fil
 
 For account-first prospecting from LinkedIn/Sales Navigator, build companies/accounts first, inspect the returned company IDs, then pass those IDs to `autotouch list-build leads --current-company-id ...`. Do not use Exa company search as a default pre-step for every LinkedIn list build; use it when the user's target is genuinely semantic, niche, competitor-based, or not meant to be LinkedIn-sourced.
 
-Use `autotouch agents ...` for recurring signal-based discovery. Scheduled agents support `--target ACCOUNTS` for company/account output and `--target LEADS` for people output. Every agent writes a source/signal table for the evidence it used; lead agents then write `candidate_research.candidates[]` on source rows and list-sync those candidates into the lead/candidate output table. See the agent playbook for the full source-table and candidate-sync contract.
+Use `autotouch agents ...` for recurring signal-based discovery. Scheduled agents support `--target ACCOUNTS` for company/account output and `--target LEADS` for people output. Every agent writes a source/signal table for the evidence it used; lead agents then write `candidate_research.candidates[]` on source rows and list-sync those candidates into the lead/candidate output table. LinkedIn engagement lead agents screen all harvested engagers by headline/title before company resolution and final lead scoring; company agents can keep matches in review or auto-promote qualified matches into the Companies workspace. See the agent playbook for the full source-table, candidate-sync, and company-promotion contract.
 
 ## Workflow Plans
 
@@ -198,7 +203,7 @@ discover -> plan -> scaffold -> run primitives -> inspect
 - `autotouch workflows scaffold --type <TYPE> --out-dir <DIR>` writes payload files and a command runbook.
 - `autotouch columns recipe` and `autotouch sequences recipe` remain leaf-level templates.
 
-Goal-level workflow types include `bulk-outreach`, `company-table-to-people`, `table-to-outreach`, `research-to-sequence`, `account-research`, `signal-outreach`, `website-visitors`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, Autotouch Sequences, webhooks, visitor sources, and external intent sources as sources/destinations inside one organized workflow layer instead of creating one-off top-level commands.
+Goal-level workflow types include `bulk-outreach`, `company-table-to-people`, `table-to-outreach`, `research-to-sequence`, `agent-to-sequence`, `account-research`, `signal-outreach`, `website-visitors`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, Autotouch Sequences, scheduled agents, webhooks, visitor sources, and external intent sources as sources/destinations inside one organized workflow layer instead of creating one-off top-level commands.
 
 ## Sources And Destinations
 
@@ -268,10 +273,11 @@ For automation or agent-driven setup, use:
 - `autotouch cli-manifest --output json` for the local machine-readable command contract
 - `autotouch cli-reference` for the shipped parser-generated reference
 - `autotouch capabilities --output json` for provider/workflow contracts
-- `autotouch --version` should be `0.2.100` or newer for structured company list builds without user-supplied keywords, stored list-build input lookup, research-workspace list-build guidance, the cleaned single LinkedIn-sourced list-build path, Exa Company Search up to 100 results, scheduled agent `--target ACCOUNTS|LEADS`, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee config, backend-owned directional source/destination helpers, goal-level workflow plans, and website visitor/external intent webhook workflow guidance
+- `autotouch --version` should be `0.2.102` or newer for structured company list builds without user-supplied keywords, stored list-build input lookup, research-workspace list-build guidance, the cleaned single LinkedIn-sourced list-build path, Exa Company Search up to 100 results, scheduled agent `--target ACCOUNTS|LEADS`, `agents signals --target`, the `agent-to-sequence` workflow scaffold, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee and active-sequence-conflict guard config, backend-owned directional source/destination helpers, goal-level workflow plans, and website visitor/external intent webhook workflow guidance
 - `autotouch capabilities --output json --select list_builds` for documented list-build inputs such as geography IDs, company size buckets, profile language, and company IDs
 - `autotouch integrations list` and `autotouch integrations status --provider <provider>` before choosing source/destination workflows
 - `autotouch workflows plan --type bulk-outreach` and `autotouch workflows scaffold --type bulk-outreach --out-dir workflow` for goal-level workflow planning
+- `autotouch workflows plan --type agent-to-sequence` and `autotouch workflows scaffold --type agent-to-sequence --out-dir workflow` for scheduled agent discovery into Autotouch Sequence tasks
 - `autotouch workflows plan --type website-visitors` and `autotouch workflows scaffold --type website-visitors --out-dir workflow` for website visitor or external intent provider webhook workflows
 - `autotouch integrations recipe --type from_crm --provider hubspot` for CRM-to-research-table imports
 - `autotouch columns recipe --type to_crm|to_outreach|to_leads|to_sequence` for research-table destination workflows

{autotouch_cli-0.2.100 → autotouch_cli-0.2.102}/autotouch_shared/provider_registry.py

@@ -1017,12 +1017,14 @@ _PROVIDER_CONTRACTS: Tuple[ResearchTableProviderContract, ...] = (
                 "sequenceId": "<SEQUENCE_ID>",
                 "sourceLeadColumn": "sync_to_leads",
                 "assignedToUserId": "<USER_ID>",
+                "skipActiveSequenceConflicts": True,
             },
         },
         recipe_notes=(
             "sourceLeadColumn should reference the source column key that stores lead IDs (for example sync_to_leads), not the provider name add_to_crm.",
             "Set sequenceId to the target workflow sequence ID.",
             "Set assignedToUserId to choose who owns the generated sequence tasks.",
+            "skipActiveSequenceConflicts defaults to true for table-driven sequence handoffs so people already active in another sequence are skipped. Set it false only when the user explicitly wants parallel sequence enrollment.",
             "The target sequence must already be ACTIVE for real enrollment.",
             "Common tail order after contact rows or lead IDs exist is email_finder -> Sync to Leads (`add_to_crm`) -> create/activate sequence -> add_to_sequence.",
             "Creating add_to_sequence after lead IDs already exist does not replay those older updates; run add_to_sequence explicitly or rerun the lead-id source column.",

{autotouch_cli-0.2.100 → autotouch_cli-0.2.102}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "autotouch-cli"
-version = "0.2.100"
+version = "0.2.102"
 description = "Autotouch Smart Table CLI"
 readme = "README.md"
 requires-python = ">=3.9"