setup-cronlisted

# Setup-cron - Schedule Daily Automation Installs an OS-scheduler entry that runs `/daily-cycle <project>` headless on a daily schedule. One entry per project: re-running for the same project replaces its entry; entries for different projects coexist. **Before starting:** `Read` `${CLAUDE_PLUGIN_ROOT}/references/workspace-conventions.md` and follow the cross-cutting conventions there. ## Prerequisites — verify, and abort with the fix if missing - At least one project exists. None -> "Run `/leadace <your-homepage-URL>` first." - `claude` CLI on PATH (`which claude`; capture the absolute path). Missing -> offer the `/loop` alternative. - Headless runs cannot answer permission prompts: any tool without a stored allow rule is denied, and repeated denials abort the run. The user should have run `/daily-cycle` interactively at least once from this directory, answering "always allow" for its tools; if they haven't, warn that scheduled runs may abort until they do. Never compensate with permission-bypass flags — denying un-allowed tools is the intended fail-safe. - The MCP OAuth token is reused from interactive sessions and expires after ~30 days of inactivity; scheduled runs then fail until the user signs in interactively again. ## 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. 2. **Method**: the OS scheduler matching `uname -s`, or