fix(skills): repair butler endpoint drift + add cron scheduling (#550)

## Why

Routine drift audit of the AionUi Butler assistant (`aionui-assistant`)
against current `aioncore` source. Two of its documented endpoints were
dead (would silently fail when an agent followed the skill), and the
cron backend gained a full REST surface the butler wasn't using.

## What

**Breaking fixes (`aionui-config`)**
- `GET /api/agents` → removed; the path 404s
(`legacy_agents_endpoint_is_not_found`). The live engine list is `GET
/api/agents/management`, returning `AgentManagementRow`s with
`installed`/`status` instead of the old `available`/`handshake` shape.
`handshake`/`available` now documented as living on `POST
/api/agents/refresh`.
- `GET /api/skills/builtin-auto` → removed; the route 405s
(`builtin_auto_skill_list_get_is_not_registered`). `GET /api/skills`
already lists every skill with its source.

**New capability (`aionui-config`)**
- Added a "Scheduled tasks (cron)" section: natural-language schedule →
`POST /api/cron/jobs`, with the three `schedule` shapes
(`at`/`every`/`cron`), required/optional fields, and the
list/get/update/run-now/delete endpoints. Captured the non-obvious
contract (5-field crontab auto-prepends seconds, `created_by` is
`user|agent`, `conversation_id` always required,
`agent_config.assistant_id` required in practice,
`deny_unknown_fields`).
- Removed the stale "cron is out of scope" note; added a cron
verification step and cron to the frontmatter description for
auto-trigger.

**Doc fix (`aionui-troubleshooting`)**
- Corrected the "no REST API for crons" claim — `/api/cron/jobs` exists;
SQLite stays the diagnostic read path.

**Rule (`aionui-assistant`, all three locales)**
- Removed the "I don't create / configure scheduled tasks" disclaimer;
advertised scheduled-task creation in the Configuration intro and the
skills table. zh-CN uses full-width punctuation.

## How verified

Every change traced to source before editing:
- `crates/aionui-ai-agent/src/routes/agent.rs`,
`registry.rs::list_management_rows` (route table + field projection)
- `crates/aionui-api-types/src/agent_discovery.rs` (`AgentManagementRow`
vs `AgentMetadata`)
- `crates/aionui-extension/src/skill_routes.rs` (skill route table, the
405 test)
- `crates/aionui-cron/src/{routes.rs,service.rs,scheduler.rs,types.rs}`
+ `crates/aionui-api-types/src/cron.rs` (cron contract)
- The 404/405 assertions in `crates/aionui-app/tests/acp_e2e.rs` and
`skill_routes.rs`

## Deploy path

Asset-only change — no `.rs` modifications. Ships via `include_dir!` on
the next `aioncore` binary build.

Author: IceyLiu

crates/aionui-app/assets/builtin-assistants/rules/aionui-assistant.en-US.md

@@ -19,12 +19,13 @@ Be proactive, helpful, and keep things easy for the user.
 - Configure MCP servers
 - Add an LLM model / API key, switch the default model
 - Change UI settings (language, theme, font size, zoom, notifications)
+- Schedule recurring or one-off tasks ("every morning at 9", "remind me in 2 hours")
 
 **Troubleshooting (diagnose problems)**
 
 - A conversation is stuck or errored
 - A model / provider call is failing
-- Why a scheduled (cron) task didn't run (I can diagnose this, but I don't create / configure scheduled tasks)
+- Why a scheduled (cron) task didn't run
 - An MCP server has no tools, a team member is hung
 
 **Remote access (use it from elsewhere)**
@@ -40,7 +41,7 @@ What would you like me to help with?"
 
 | Skill | Purpose | Nature |
 | --- | --- | --- |
-| **aionui-config** | Create/edit assistants, import & attach skills, configure MCP, add LLM providers & API keys, change app/UI settings | **Write** (affects the live app) |
+| **aionui-config** | Create/edit assistants, import & attach skills, configure MCP, add LLM providers & API keys, change app/UI settings, create & manage scheduled tasks | **Write** (affects the live app) |
 | **aionui-troubleshooting** | Inspect conversations/runtime, read aioncore logs, check provider health, cron / team / MCP status | **Read-only** diagnosis |
 | **aionui-webui-public** | Set up remote access to the local AionUi and produce an external access link | **Execute** (runs commands on the user's machine, opens a connection) |
 

crates/aionui-app/assets/builtin-assistants/rules/aionui-assistant.ru-RU.md

@@ -19,12 +19,13 @@
 - Настройка серверов MCP
 - Добавление модели LLM / API-ключа, смена модели по умолчанию
 - Изменение настроек интерфейса (язык, тема, размер шрифта, масштаб, уведомления)
+- Планирование периодических или разовых задач («каждое утро в 9», «напомни через 2 часа»)
 
 **Диагностика (найду проблему)**
 
 - Разговор завис или выдал ошибку
 - Сбой вызова модели / провайдера
-- Почему запланированная задача (cron) не выполнилась (я могу это диагностировать, но не создаю / не настраиваю запланированные задачи)
+- Почему запланированная задача (cron) не выполнилась
 - У сервера MCP нет инструментов, участник команды завис
 
 **Удалённый доступ (чтобы пользоваться откуда угодно)**
@@ -40,7 +41,7 @@
 
 | Навык | Назначение | Характер |
 | --- | --- | --- |
-| **aionui-config** | Создание/редактирование ассистентов, импорт и подключение навыков, настройка MCP, добавление провайдеров LLM и API-ключей, изменение настроек приложения/интерфейса | **Запись** (влияет на работающее приложение) |
+| **aionui-config** | Создание/редактирование ассистентов, импорт и подключение навыков, настройка MCP, добавление провайдеров LLM и API-ключей, изменение настроек приложения/интерфейса, создание и управление запланированными задачами | **Запись** (влияет на работающее приложение) |
 | **aionui-troubleshooting** | Просмотр разговоров/состояния выполнения, чтение логов aioncore, проверка здоровья провайдеров, состояние cron / команд / MCP | **Только чтение**, диагностика |
 | **aionui-webui-public** | Настроить удалённый доступ к локальному AionUi и выдать внешнюю ссылку доступа | **Выполнение** (запускает команды на машине пользователя, открывает соединение) |
 

crates/aionui-app/assets/builtin-assistants/rules/aionui-assistant.zh-CN.md

@@ -19,12 +19,13 @@
 - 配置 MCP 服务器
 - 添加 LLM 模型 / API Key，切换默认模型
 - 调整界面设置（语言、主题、字号、缩放、通知）
+- 安排定时任务（如"每天早上9点""2小时后提醒我"）
 
 **排查类（帮你诊断）**
 
 - 会话卡住、报错
 - 模型 / Provider 调用失败
-- 定时任务（cron）为什么没执行（我能诊断，但不负责创建/配置定时任务）
+- 定时任务（cron）为什么没执行
 - MCP 服务器没有工具、团队成员卡住
 
 **远程访问（帮你在外面也能用）**
@@ -40,7 +41,7 @@
 
 | 技能 | 用途 | 性质 |
 | --- | --- | --- |
-| **aionui-config** | 创建/编辑助手、导入并绑定技能、配置 MCP、添加 LLM Provider 与 API Key、改应用/界面设置 | **写**（会改动用户的实时应用） |
+| **aionui-config** | 创建/编辑助手、导入并绑定技能、配置 MCP、添加 LLM Provider 与 API Key、改应用/界面设置、创建与管理定时任务 | **写**（会改动用户的实时应用） |
 | **aionui-troubleshooting** | 查会话/运行状态、读 aioncore 日志、查 Provider 健康、cron / team / MCP 状态 | **只读**诊断 |
 | **aionui-webui-public** | 把本机 AionUi 配置成可远程访问，生成外网访问链接 | **执行**（在用户机器上跑命令、建连接） |
 

crates/aionui-app/assets/builtin-skills/aionui-config/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: aionui-config
 description: >-
-  Configure AionUi itself through its backend API — create and edit assistants (name, avatar, system prompt, quick-start prompts, engine), import and attach skills, manage MCP servers, configure LLM providers (add/edit a model endpoint, set the API key, fetch the model list, pick the default model), and change app/UI settings (language, theme, font size, zoom, notifications). Use when the user wants you to set up an AionUi assistant, sink a skill into AionUi's skill registry, attach skills to an assistant, change an assistant's avatar or system prompt, add or configure an MCP server, add an LLM/model provider or API key, switch the default model, change the theme or language, or otherwise configure their AionUi installation. This is "Agent-assisted AionUi configuration": you act on the user's behalf via the local backend.
+  Configure AionUi itself through its backend API — create and edit assistants (name, avatar, system prompt, quick-start prompts, engine), import and attach skills, manage MCP servers, configure LLM providers (add/edit a model endpoint, set the API key, fetch the model list, pick the default model), change app/UI settings (language, theme, font size, zoom, notifications), and create or manage scheduled tasks (cron jobs) from a natural-language schedule. Use when the user wants you to set up an AionUi assistant, sink a skill into AionUi's skill registry, attach skills to an assistant, change an assistant's avatar or system prompt, add or configure an MCP server, add an LLM/model provider or API key, switch the default model, change the theme or language, schedule a recurring or one-off task ("every morning at 9", "remind me in 2 hours", "run this daily"), or otherwise configure their AionUi installation. This is "Agent-assisted AionUi configuration": you act on the user's behalf via the local backend.
 ---
 
 > **⚠️ Platform note — read before running any command.** The shell snippets in this skill are written for **macOS / Linux** (bash/zsh). Always check which OS you are on first. On **Windows** do **not** run them verbatim — the underlying tool/CLI commands are usually cross-platform, but the surrounding shell syntax is not. Translate it to PowerShell before running:
@@ -265,7 +265,6 @@ Three sources: `builtin` (`~/.aionui/builtin-skills/`), `custom`
 ```bash
 python3 scripts/aionui_api.py get /api/skills
 python3 scripts/aionui_api.py get /api/skills/paths          # where skills live on disk
-python3 scripts/aionui_api.py get /api/skills/builtin-auto   # auto-injected builtin skills
 python3 scripts/aionui_api.py post /api/skills/info '{"skill_path":"/abs/path/to/skill-folder"}'  # read a SKILL.md's name/description WITHOUT importing
 ```
 
@@ -534,15 +533,106 @@ python3 scripts/aionui_api.py put /api/settings/client '{"ui.zoomFactor": 1.0}'
 
 ## Engines (agents)
 
-`GET /api/agents` lists the available engines (`aionrs`, `claude`, `codex`, …).
-Each entry carries `enabled` (toggled on), `available` (installed & reachable),
-`team_capable` (can run in a team), and a `handshake` object describing what the
-engine supports — `agent_capabilities`, `auth_methods`, `config_options`,
-`available_modes`, `available_models`, `available_commands`. Check `available`
-before binding an assistant to that engine (via its `agent_id` — see *Picking the
-engine* above), and inspect `handshake` to see which models/modes that engine
-offers. `POST /api/agents/refresh` re-scans custom
-agents.
+`GET /api/agents/management` lists the available engines (`aionrs`, `claude`,
+`codex`, …). There is **no** bare `GET /api/agents` — that path 404s; always use
+the `/management` sub-path. Each row carries `id`, `enabled` (toggled on),
+`installed` (spawn command resolvable on `$PATH`), `team_capable` (can run in a
+team), `backend`, `agent_type`, and a `status` of `online` / `offline` /
+`missing`. Check `installed` (and `status`) before binding an assistant to that
+engine (via its `agent_id` — see *Picking the engine* above).
+
+> The management row does **not** include the engine `handshake` (its
+> `agent_capabilities` / `auth_methods` / `config_options` / `available_modes` /
+> `available_models` / `available_commands`) — those live on the fuller agent
+> metadata returned by `POST /api/agents/refresh`, which re-scans custom agents
+> and returns each agent's `available` + `handshake`. Use `refresh` when you need
+> the modes/models an engine offers; use `management` for the at-a-glance
+> enabled/installed/status list.
+
+---
+
+## Scheduled tasks (cron)
+
+Create and manage scheduled tasks ("run this every morning at 9", "remind me in
+two hours", "every 30 minutes do X") over the REST API — `/api/cron/*` is a
+full, verified CRUD surface. Translate the user's natural-language schedule into
+one of three `schedule` shapes, then `POST /api/cron/jobs`.
+
+### The schedule (`schedule` is a tagged union — the `kind` field picks the shape)
+
+| Natural language | `schedule` body |
+| --- | --- |
+| "at 3pm today / on this exact date" (one-shot) | `{"kind":"at","at_ms":<unix-ms>}` |
+| "every 30 minutes / every 2 hours" (fixed interval) | `{"kind":"every","every_ms":<ms>}` |
+| "every day at 9am / every Monday" (calendar) | `{"kind":"cron","expr":"0 9 * * *","tz":"Asia/Shanghai"}` |
+
+- **`cron.expr` takes a standard 5-field crontab** (`min hour day month weekday`).
+  The backend auto-prepends the seconds field, so `0 9 * * *` means 09:00 daily.
+  (A 6-field `sec min hour day month weekday` is also accepted as-is.)
+- **`cron.tz`** is an IANA timezone name (`Asia/Shanghai`, `America/New_York`,
+  `UTC`). Omit it and the expression runs in UTC — always set it to the user's
+  zone for "9am" to mean their 9am.
+- **`every.every_ms`** must be `> 0`. There is no documented lower bound, but be
+  sensible — don't schedule a sub-minute loop unless asked.
+- **`at.at_ms`** is a Unix timestamp in **milliseconds**. A past time is accepted
+  by the API but will not run, so compute it from "now" in the user's zone.
+- An optional `description` can go inside any schedule variant for a
+  human-readable label.
+
+### Required fields on `POST /api/cron/jobs`
+
+```bash
+python3 scripts/aionui_api.py post /api/cron/jobs '{
+  "name": "每日早报",
+  "schedule": {"kind": "cron", "expr": "0 9 * * *", "tz": "Asia/Shanghai"},
+  "message": "总结今天的科技新闻",
+  "conversation_id": "<conv-id>",
+  "created_by": "agent",
+  "execution_mode": "new_conversation",
+  "agent_config": {"name": "AionUi Butler", "assistant_id": "<assistant-id>"}
+}'
+```
+
+| Field | Required | Meaning |
+| --- | --- | --- |
+| `name` | ✅ | display name of the task |
+| `schedule` | ✅ | one of the three shapes above |
+| `conversation_id` | ✅ | the conversation the task is tied to — get one from `GET /api/conversations` (or create one). Even `new_conversation` jobs need this set |
+| `created_by` | ✅ | `"agent"` when you create it on the user's behalf, `"user"` for a user-initiated one. **Only these two values** |
+| `message` (or `prompt`) | — | the instruction sent on each run. `message` wins if both are given; with neither, the run sends an empty prompt |
+| `execution_mode` | — | `"existing"` (default) reuses `conversation_id` every run; `"new_conversation"` spins up a fresh conversation each run |
+| `agent_config` | — | which assistant runs the task. **In practice required for a new job**: omit it and the API 400s with *"assistant_id is required for new cron jobs"*. Pass `{"name":"<label>","assistant_id":"<id>"}` |
+| `description` | — | optional longer description |
+
+> `agent_config` is strict (`deny_unknown_fields`): only `name`, `assistant_id`,
+> `cli_path`, `mode`, `model_id`, `model`, `config_options`, `workspace` are
+> accepted. Legacy keys `backend`, `agent_type`, `custom_agent_id`, `is_preset`
+> are **rejected** — don't send them. Get the `assistant_id` from
+> `GET /api/assistants`.
+
+The response is the created job (HTTP 201) with its generated `id` (prefixed
+`cron_…`), resolved `agent_type`, and a `state` block (`next_run_at_ms`,
+`run_count`, …).
+
+### List / inspect / change / run / delete
+
+```bash
+python3 scripts/aionui_api.py get    /api/cron/jobs                       # all jobs
+python3 scripts/aionui_api.py get    "/api/cron/jobs?conversation_id=<id>"  # jobs for one conversation
+python3 scripts/aionui_api.py get    /api/cron/jobs/<id>                   # one job
+python3 scripts/aionui_api.py put    /api/cron/jobs/<id> '{"enabled": false}'   # partial update (pause)
+python3 scripts/aionui_api.py post   /api/cron/jobs/<id>/run              # run it once right now
+python3 scripts/aionui_api.py delete /api/cron/jobs/<id>                  # remove it
+```
+
+`PUT` is a partial update — send only what changes (`name`, `description`,
+`enabled`, `schedule`, `message`, `execution_mode`, `agent_config`,
+`conversation_title`, `max_retries`). Read the job back to confirm its
+`schedule` and `state.next_run_at_ms` after any change.
+
+> Note: an `existing`-mode job can't have its assistant changed after creation
+> (`agent_config` on update is rejected for ongoing-conversation jobs) — that's
+> by design, the ongoing conversation keeps its original assistant.
 
 ---
 
@@ -557,7 +647,9 @@ After a configuration task, confirm with reads:
 5. MCP server in `get /api/mcp/servers`, enabled, right transport?
 6. Provider in `get /api/providers`, enabled, right `models`? (redact the key)
 7. Settings changed? `get /api/settings/client` shows the new value.
-8. Tell the user to refresh / reopen the AionUi view to see changes.
+8. Scheduled task created? `get /api/cron/jobs` lists it, `enabled: true`, with
+   the expected `schedule` and a non-null `state.next_run_at_ms`.
+9. Tell the user to refresh / reopen the AionUi view to see changes.
 
 ## Out of scope (handled elsewhere)
 
@@ -568,11 +660,9 @@ API here:
 - **Teams** (`/api/teams/*`) — create Teams through the Team UI or REST API.
   Once a Team session is active, Team agents use the `team_*` MCP tools
   provided by the per-Team `aionui-team` server.
-- **Cron / scheduled jobs** (`/api/cron/*`) — created and managed through their
-  own flow (scheduling tools / the AionUi cron UI), not this skill.
 
 This skill stays focused on *configuration*: assistants, skills, MCP servers,
-LLM providers, and app settings.
+LLM providers, app settings, and scheduled tasks.
 
 ## Not yet covered
 

crates/aionui-app/assets/builtin-skills/aionui-troubleshooting/SKILL.md

@@ -140,9 +140,11 @@ python3 scripts/aion_diag.py logs --errors --lines 100
 python3 scripts/aion_diag.py crons
 ```
 
-There is **no REST API for crons** — this reads the `cron_jobs` table from the
-SQLite store directly (read-only). It surfaces a `failing` list (jobs whose
-`last_status` is `error` or `missed`) plus every job's `schedule_*`,
+This reads the `cron_jobs` table from the SQLite store directly (read-only). A
+REST API for crons does exist (`/api/cron/jobs`, used by the `aionui-config`
+skill to *create/manage* jobs), but for diagnosis the table read is more direct
+and surfaces the run-state columns in one shot. It surfaces a `failing` list
+(jobs whose `last_status` is `error` or `missed`) plus every job's `schedule_*`,
 `last_status`, `last_error`, `next_run_at`, `last_run_at`, `run_count`,
 `retry_count`. Check `enabled`, compare `next_run_at` to now, and read
 `last_error` for failed jobs.
@@ -203,7 +205,7 @@ python3 scripts/aion_diag.py logs [--lines N] [--errors] [--conv <id>]
 | Conversation list + runtime state | `GET /api/conversations[/{id}]` | REST |
 | Conversation messages / errors | `messages` table (by `conversation_id`) | SQLite (read-only) |
 | LLM provider health | `GET /api/providers` → `model_health` | REST (api_key redacted) |
-| Scheduled jobs | `cron_jobs` table | SQLite (no REST API) |
+| Scheduled jobs | `cron_jobs` table (REST `/api/cron/jobs` exists too) | SQLite (read-only) |
 | Teams + members | `GET /api/teams` | REST |
 | MCP servers | `GET /api/mcp/servers` | REST |
 | Logs | `*.aioncore.log` in `--log-dir` | File tail |