schedule-list

# /schedule-list — Show scheduled entries ## Purpose Display a formatted summary of all entries currently registered in the `schedule:` block of onebrain.yml. Both skill-mode entries (`skill: /daily`) and command-mode entries (`command: onebrain` + `args: [...]`) are shown side by side, with installed-on-disk status from launchd. --- ## Skill flow ### Step 1: Read onebrain.yml Read onebrain.yml from the vault root. Locate the `schedule:` block. If onebrain.yml does not exist or has no `schedule:` block, or the block is empty: ``` No scheduled entries found. → Run /schedule-add to set one up. ``` Stop. ### Step 2: Fetch status Read the `schedule:` block from onebrain.yml directly to get the cron/at expression and `skill`/`command` field for each entry. Optionally run from the vault root: ``` onebrain schedule register --status ``` This emits plain text (not JSON). Each line is one entry with the `[cron]` or `[once]` tag, the cron/at value, and either `skill: /name (k=v, k2=v2)` (skill mode with optional args) or `cmd: binary arg1 arg2` (command mode with positional argv). The `✓` / `✗` prefix indicates whether the plist file exists on disk. The CLI does not track last-run, next-run, or last-status — that detail is in `[logs_folder]/scheduler/YYYY/MM/`. If `onebrain schedule register --status` is unavailable or fails: fall back to checking launchd plist existence in `~/Library/LaunchAgents/` for each entry. Compute the plist filename as `com.onebrain.<labelSafe>...