loop-tracklisted

# /loop-track — register an external cron into the history ## When to use this - A loop was created via raw `/loop <interval> <prompt>` and no history entry exists for it (i.e. it predates this toolkit OR was spawned outside the loop-* skills). - The user wants to attach a `label` to an existing loop so it shows up nicely in `/loops` output. - Auditing: the user wants every active loop to have a `created` or `discovered` history event so the audit trail is complete. `/loops` does an automatic untracked-cron detection pass and logs `discovered` events as a side effect. `/loop-track` is the explicit manual version when the user wants to add a label or specific metadata. ## Argument parsing ``` /loop-track <job-id> [label: "<label>"] [created-at: "<ISO-8601>"] ``` - `<job-id>` — the cron job ID from `CronList`. Required. - `label:` — optional short label (informational only) - `created-at:` — optional historical timestamp (default: now, marked as `discovered` event) If no args: list current `CronList` IDs and ask which to track. ## Steps 1. `CronList` — verify the job-id exists. If not: error out. 2. Pull the cron's cron expression + prompt from CronList output. **Note**: CronList truncates the prompt to ~80 chars. If truncated, refuse to register without the full prompt OR ask the user to paste it. 3. Read `~/.claude/loop-history.jsonl`. If a `created`, `resumed`, or `discovered` event with this `id_original`, `id_new`, or matching `cron + pr