bot-bootlisted

# Bot Boot Skill Boot orchestrator for Pilot Bot. Runs on every bot session start via `pilot bot`. The bot is an automation agent — scheduled tasks, background jobs, 24/7 operation. Telegram integration is optional (auto-detected). Environment variables available: - `PILOT_BOT_MODE=1` — confirms bot context - `PILOT_BOT_DIR` — path to `~/.pilot/bot/` (contains JOBS.yaml) ## Execution **Phase 1** — Single message with parallel tool calls (foreground + background agents): | # | Type | Action | |---|------|--------| | 1 | **Foreground** | Read `$PILOT_BOT_DIR/JOBS.yaml` to understand current job configuration. | | 2 | **Background Agent** | **MCP health check** — silent check, no greeting (see below) | **Phase 2** — After Phase 1 completes, register crons in the **main session** (Cron tools are not available to subagents): | # | Action | |---|--------| | 3 | **Heartbeat registration** — First load tools: `ToolSearch(query="select:CronList,CronCreate")`. Then use CronList to check if a heartbeat cron already exists (look for 'bot-heartbeat' in prompt text). If it already exists, do nothing. If not found, use CronCreate with `cron='*/30 * * * *'` and `prompt='Run /bot-heartbeat skill (invoke Skill tool with skill=bot-heartbeat)'`. | | 4 | **Jobs registration** — Read JOBS.yaml from `$PILOT_BOT_DIR`. If missing or empty (`jobs: {}`), skip. Otherwise use CronList to get existing crons, then for each job with `active: true`, register via CronCreate with `cron='<schedule>'` an