setup-cronlisted

# Setup-cron - Schedule Daily Automation Sets up an unattended daily run of `/daily-cycle <project>`. One schedule per project; schedules for different projects coexist. **Before starting:** `Read` `${CLAUDE_PLUGIN_ROOT}/references/workspace-conventions.md` and follow the cross-cutting conventions there. ## Prerequisites - At least one project exists. None -> "Run `/leadace <your-homepage-URL>` first." ## Confirm with the user Use `AskUserQuestion` for enumerable choices, plain text for free-form input. 1. **Project**: `$0` if given; else `list_projects` — exactly one -> use it, several -> ask. `<PROJECT_SLUG>` = the project name lowercased, every character outside `[a-z0-9]` replaced by `-` (collapse runs, trim leading/trailing `-`). 2. **Method**, offered in this order; state what each can run before the user picks: - **Server-side schedule** — default, and the only one that needs neither a machine nor a Claude session. LeadAce itself runs the instruction; email outreach, replies, evaluation and list building all work. It has no browser, so contact forms, SNS DMs and platform channels are out. Set it up in the Web app (Project settings -> Scheduled runs) or by asking in the Web chat; `list_schedules` shows what is already registered. Registering it is not possible from here — say where to go and what to write. - **Claude Cowork scheduled task** — for browser channels, or a self-host without a model key on the server. Runs in the cloud with no machine on; browse