@aitne-sh/aitne 0.1.8 → 0.1.10

package/agent-assets/skills/external-services/SKILL.delegated.claude.md

@@ -128,7 +128,7 @@ curl -s -X POST http://localhost:8321/api/integrations/google_calendar/exec \
 `needsConfirmation` plan, or skip the dance for self-only events you
 already greenlit.)
 
-`outputSchema` is **required** (4 KB cap). Defaults: `maxToolCalls=7`,
+`outputSchema` is **required** (4 KB cap). Defaults: `maxToolCalls=8`,
 `maxBudgetUsd=0.05`, `timeoutMs=60000`. Bump up to 15 / 0.50 / 300000
 for genuinely larger intents.
 
@@ -176,32 +176,7 @@ freshness matters, and never on a destructive-confirm second call.
   know about, call `POST /api/notify` with a one-line summary. The
   daemon does NOT auto-notify — it's an explicit choice.
 
-### Error envelope
-
-`/exec` extends the direct-mode envelope with delegated-mode fields.
-Discriminator: `body.mode === "delegated"`.
-
-| HTTP | `error` | retry? | What to do |
-|---|---|---|---|
-| 400 | `validation_error` / `schema_too_large` | no | Fix the request body. |
-| 409 | `mode_mismatch` | no | Calendar isn't delegated, OR your DM backend matches `delegatedBackend`. Re-read `integrations.md` and stop. |
-| 409 | `precondition` | no | Mode/backend flipped during the queue wait. Re-check state and re-plan. |
-| 429 | `task_quota_exhausted` | no | Daily cap reached; wait or surface. |
-| 502 | `parse_error` / `schema_violation` | no (daemon already retried once) | Consider a simpler schema. |
-| 502 | `tool_unavailable` | no | No connector tool fits the intent. Surface the gap. |
-| 502 | `tool_failed` | maybe | Connector tool returned an error. Surface `body.message` verbatim; retry only if clearly transient. |
-| 502 | `auth_error` | no | Connector signed out. Tell the user to re-authenticate it. |
-| 502 | `policy_violation` | no | Subprocess attempted a tool outside the per-task allowlist (anti-injection). |
-| 502 | `loop_aborted` | no | `maxToolCalls` exceeded. Bump the cap or simplify. |
-| 502 | `budget_exhausted` | no | `maxBudgetUsd` exceeded. Caller can raise the cap. |
-| 502 | `post_write_format_failure` | no | Write succeeded; formatting failed. Side effect is real — surface with the partial trace. |
-| 503 | `delegated_proxy_busy` | yes | Daemon queue saturated. Backoff a few seconds, try once. |
-| 503 | `task_mode_disabled` | no | Operator turned the kill switch off. Stop. |
-| 504 | `timeout` | yes (1×) | Wall-clock fired. Retry once if intent was simple. |
-| 500 | `subprocess_crashed` | no | Unhandled exception inside the subprocess. Surface and stop. |
-
-Always preserve `body.message` verbatim when reporting to the user — it
-carries the connector's own language.
+{{> ref:exec-errors }}
 <!-- /service:calendar -->
 
 ---
@@ -212,7 +187,7 @@ carries the connector's own language.
 **Scope**: this skill targets a **separate** Obsidian vault the user
 maintains alongside this app — e.g. a personal knowledge base. It is
 **not** the agent's own primary management store. The agent's primary
-files (`today.md`, `roadmap.md`, `projects/`, `rules/`, `routines/`,
+files (`state/today.md`, `plans/roadmap.md`, `projects/`, `rules/`, `routines/`,
 `user/`, `agent/`, …) live in the primary vault and are reached via
 `/api/context/*` (see the `context` skill). **Never** use this skill to
 read or write the primary vault.
@@ -257,10 +232,10 @@ skill and the `/api/context/*` endpoints instead.
 
 ```bash
 curl -s http://localhost:8321/api/github/repos                              # list watched repos
-curl -s "http://localhost:8321/api/github/pulls?state=open"                  # list PRs
+curl -s "http://localhost:8321/api/github/pulls?owner=user&repo=repo&state=open" # list PRs
 curl -s -X POST http://localhost:8321/api/github/pulls/comment \
   -H 'Content-Type: application/json' \
-  -d '{"owner": "user", "repo": "repo", "pullNumber": 42, "body": "LGTM"}' # comment — Autonomous
+  -d '{"owner": "user", "repo": "repo", "pull_number": 42, "comment": "LGTM"}' # comment — Autonomous
 ```
 <!-- /service:github -->
 
@@ -276,92 +251,20 @@ update, archive).
 
 ---
 
-## Recurring Schedules
+## Recurring tasks
 
-CRUD for repeating agent tasks. Timezone auto-filled from daemon config.
-
-```bash
-curl -s -X POST http://localhost:8321/api/recurring-schedules \
-  -H 'Content-Type: application/json' \
-  -d '{"taskType": "wake", "description": "Morning inbox triage.", "recurrenceRule": {"frequency": "daily", "time": "09:00"}}'
-curl -s "http://localhost:8321/api/recurring-schedules?enabled=true"         # list
-curl -s -X PATCH http://localhost:8321/api/recurring-schedules/1 \
-  -H 'Content-Type: application/json' \
-  -d '{"recurrenceRule": {"frequency": "weekly", "time": "10:00", "daysOfWeek": [1,3,5]}}'
-curl -s -X PATCH http://localhost:8321/api/recurring-schedules/1 \
-  -H 'Content-Type: application/json' -d '{"enabled": false}'              # disable
-curl -s -X DELETE http://localhost:8321/api/recurring-schedules/1           # delete
-```
-`recurrenceRule`: `frequency` (daily/weekly/monthly), `time` (HH:MM), `daysOfWeek` (0=Sun..6=Sat, weekly), `daysOfMonth` (1-31, monthly). → Full guide: load `schedule` skill.
-
----
-
-## One-Shot Scheduling
-
-Schedule a future DM or agent task. Use `<current_time>` to resolve relative times into absolute ISO 8601 with offset.
-
-### DM vs Agent Task
-
-| Criterion | `/api/schedule/dm` (free) | `/api/schedule` (~$0.03) |
-|---|---|---|
-| Message text knowable now? | Yes | No — needs lookup/decision at execution |
-| Needs API data at execution? | No | Yes |
-| Multi-step action? | No | Yes |
-| Conditional on state that may change? | No | Yes |
-
-**Default to DM** — every agent wake-up costs money and context.
-
-### Context-loss warning
-
-> The wake-up agent has NO memory of why it was scheduled — the `description` field is its only context.
-
-Include: **What** (verb + object), **Why** (trigger/reason), **Who/What** (names, IDs, URLs), **Expected output** (what success looks like).
-
-Bad: `"Meeting prep"` — which meeting? when? what to prepare? The wake-up agent will skip ambiguous descriptions.
-
-### POST /api/schedule/dm — Pre-composed DM
-```bash
-curl -s -X POST http://localhost:8321/api/schedule/dm \
-  -H 'Content-Type: application/json' \
-  -d '{"time": "2026-04-06T16:00:00-04:00", "message": "Reminder: Design review in 30 min.", "platform": "slack"}'
-```
-
-### POST /api/schedule — Agent task
-```bash
-curl -s -X POST http://localhost:8321/api/schedule \
-  -H 'Content-Type: application/json' \
-  -d '{"time": "2026-04-06T16:00:00-04:00", "taskType": "wake", "description": "Check PR #42 status and notify user.", "tier": "medium", "taskContext": {"scheduledBy": "dm_conversation"}}'
-```
-Fields: `time` (required), `taskType` (`wake`), `description` (required, min 20 chars), `tier` (`lite`/`medium`/`high`) **or** `model` (registered id like `claude-opus-4-7`, legacy alias `sonnet`/`opus`, or composite `<backendId>/<modelId>`) — mutually exclusive, `taskContext` (optional metadata). See the `schedule` skill body for the full surface and `/api/schedule/options` for the live model list.
-
-### Manage pending items
-```bash
-curl -s "http://localhost:8321/api/schedule?status=pending"                         # list
-curl -s -X PATCH http://localhost:8321/api/schedule/42 \
-  -H 'Content-Type: application/json' -d '{"time": "2026-04-06T17:00:00-04:00"}'   # edit
-curl -s -X DELETE http://localhost:8321/api/schedule/42                              # cancel
-```
-Editable: `time`, `description`, `message` (dm only), `tier` (or `model`, mutually exclusive — pass `null` to clear), `taskContext`. Only `pending` items.
-
-### Time discipline
-- Absolute ISO 8601 with offset required — no relative times.
-- Do not schedule during quiet hours (default 22:00–08:00, configurable) unless critical.
-- Maximum 5 wake-ups per execution.
+Recurring autonomous **work** (fetch / check / act on a cadence) is an **Agent** —
+create one with the `agent-create` skill (`POST /api/agents`), managed on `/agents`.
+Recurring scheduled **DMs / briefings** stay on `POST /api/recurring-schedules`
+with `taskType: "dm_session"`. `GET /api/recurring-schedules?enabled=true` lists
+existing rows (dedup). → Full guide: load the `agent-create` or `schedule` skill.
 
 ---
 
-## Skills Management
+## Scheduling & Skills CRUD
 
-User-authored skills: `~/.personal-agent/skills/{slug}/SKILL.md`. Built-in skills are read-only (403). Slug: lowercase kebab-case `[a-z0-9][a-z0-9-]*`, 1–64 chars.
-
-```bash
-curl -s http://localhost:8321/api/skills                                            # list all
-curl -s http://localhost:8321/api/skills/todo-digest                                # read one
-curl -s -X POST http://localhost:8321/api/skills \
-  -H 'Content-Type: application/json' \
-  -d '{"name": "todo-digest", "description": "Summarize today.md", "content": "# TODO Digest\n...", "allowedTools": ["Bash(curl *)", "Read"]}'
-curl -s -X PUT http://localhost:8321/api/skills/todo-digest \
-  -H 'Content-Type: application/json' -d '{"description": "New description"}'      # update
-curl -s -X DELETE http://localhost:8321/api/skills/todo-digest                      # delete
-```
-Always `GET /api/skills` before creating (check name collisions). **Omit frontmatter** from `content` — the API injects it.
+One-shot DMs / agent wake-ups (`/api/schedule`, `/api/schedule/dm`) and
+user-authored Skills CRUD (`/api/skills`) work identically to direct
+mode — they are never proxied. Load the `schedule` skill for scheduling
+and the `agent-create` skill for recurring work; this variant does not
+mirror those surfaces.

package/agent-assets/skills/external-services/SKILL.delegated.codex.md

@@ -122,7 +122,7 @@ curl -sS -X POST http://localhost:8321/api/integrations/google_calendar/exec \
   }'
 ```
 
-`outputSchema` is **required** (4 KB cap). Defaults: `maxToolCalls=7`,
+`outputSchema` is **required** (4 KB cap). Defaults: `maxToolCalls=8`,
 `maxBudgetUsd=0.05`, `timeoutMs=60000`. Bump up to 15 / 0.50 / 300000
 for genuinely larger intents.
 
@@ -157,31 +157,7 @@ destructive-confirm second call.
   know about, call `POST /api/notify` with a one-line summary. The
   daemon does NOT auto-notify — it's an explicit choice.
 
-### Error envelope
-
-`/exec` extends the direct-mode envelope with delegated-mode fields.
-Discriminator: `body.mode === "delegated"`.
-
-| HTTP | `error` | retry? | What to do |
-|---|---|---|---|
-| 400 | `validation_error` / `schema_too_large` | no | Fix the request body. |
-| 409 | `mode_mismatch` | no | Calendar isn't delegated, OR your DM backend matches `delegatedBackend`. Re-read `integrations.md`. |
-| 409 | `precondition` | no | Mode/backend flipped during queue wait. Re-check state. |
-| 429 | `task_quota_exhausted` | no | Daily cap reached. Wait or surface. |
-| 502 | `parse_error` / `schema_violation` | no (daemon already retried once) | Simplify schema. |
-| 502 | `tool_unavailable` | no | No connector tool fits. Surface the gap. |
-| 502 | `tool_failed` | maybe | Connector tool returned an error. Surface verbatim. |
-| 502 | `auth_error` | no | Connector signed out. Re-authenticate. |
-| 502 | `policy_violation` | no | Subprocess attempted an out-of-allowlist tool (anti-injection). |
-| 502 | `loop_aborted` | no | `maxToolCalls` exceeded. Bump or simplify. |
-| 502 | `budget_exhausted` | no | `maxBudgetUsd` exceeded. Caller can raise the cap. |
-| 502 | `post_write_format_failure` | no | Write succeeded; formatting failed. Surface with partial trace. |
-| 503 | `delegated_proxy_busy` | yes | Queue saturated. Backoff and retry once. |
-| 503 | `task_mode_disabled` | no | Operator killed it. Stop. |
-| 504 | `timeout` | yes (1×) | Wall-clock fired. Retry once. |
-| 500 | `subprocess_crashed` | no | Daemon-side defect. Surface and stop. |
-
-Always preserve `body.message` verbatim when reporting to the user.
+{{> ref:exec-errors }}
 <!-- /service:calendar -->
 
 ---
@@ -192,7 +168,7 @@ Always preserve `body.message` verbatim when reporting to the user.
 **Scope**: this skill targets a **separate** Obsidian vault the user
 maintains alongside this app — e.g. a personal knowledge base. It is
 **not** the agent's own primary management store. The agent's primary
-files (`today.md`, `roadmap.md`, `projects/`, `rules/`, `routines/`,
+files (`state/today.md`, `plans/roadmap.md`, `projects/`, `rules/`, `routines/`,
 `user/`, `agent/`, …) live in the primary vault and are reached via
 `/api/context/*` (see the `context` skill). **Never** use this skill to
 read or write the primary vault.
@@ -237,10 +213,10 @@ skill and the `/api/context/*` endpoints instead.
 
 ```bash
 curl -s http://localhost:8321/api/github/repos                              # list watched repos
-curl -s "http://localhost:8321/api/github/pulls?state=open"                  # list PRs
+curl -s "http://localhost:8321/api/github/pulls?owner=user&repo=repo&state=open" # list PRs
 curl -s -X POST http://localhost:8321/api/github/pulls/comment \
   -H 'Content-Type: application/json' \
-  -d '{"owner": "user", "repo": "repo", "pullNumber": 42, "body": "LGTM"}' # comment — Autonomous
+  -d '{"owner": "user", "repo": "repo", "pull_number": 42, "comment": "LGTM"}' # comment — Autonomous
 ```
 <!-- /service:github -->
 
@@ -256,92 +232,20 @@ update, archive).
 
 ---
 
-## Recurring Schedules
+## Recurring tasks
 
-CRUD for repeating agent tasks. Timezone auto-filled from daemon config.
-
-```bash
-curl -s -X POST http://localhost:8321/api/recurring-schedules \
-  -H 'Content-Type: application/json' \
-  -d '{"taskType": "wake", "description": "Morning inbox triage.", "recurrenceRule": {"frequency": "daily", "time": "09:00"}}'
-curl -s "http://localhost:8321/api/recurring-schedules?enabled=true"         # list
-curl -s -X PATCH http://localhost:8321/api/recurring-schedules/1 \
-  -H 'Content-Type: application/json' \
-  -d '{"recurrenceRule": {"frequency": "weekly", "time": "10:00", "daysOfWeek": [1,3,5]}}'
-curl -s -X PATCH http://localhost:8321/api/recurring-schedules/1 \
-  -H 'Content-Type: application/json' -d '{"enabled": false}'              # disable
-curl -s -X DELETE http://localhost:8321/api/recurring-schedules/1           # delete
-```
-`recurrenceRule`: `frequency` (daily/weekly/monthly), `time` (HH:MM), `daysOfWeek` (0=Sun..6=Sat, weekly), `daysOfMonth` (1-31, monthly). → Full guide: load `schedule` skill.
-
----
-
-## One-Shot Scheduling
-
-Schedule a future DM or agent task. Use `<current_time>` to resolve relative times into absolute ISO 8601 with offset.
-
-### DM vs Agent Task
-
-| Criterion | `/api/schedule/dm` (free) | `/api/schedule` (~$0.03) |
-|---|---|---|
-| Message text knowable now? | Yes | No — needs lookup/decision at execution |
-| Needs API data at execution? | No | Yes |
-| Multi-step action? | No | Yes |
-| Conditional on state that may change? | No | Yes |
-
-**Default to DM** — every agent wake-up costs money and context.
-
-### Context-loss warning
-
-> The wake-up agent has NO memory of why it was scheduled — the `description` field is its only context.
-
-Include: **What** (verb + object), **Why** (trigger/reason), **Who/What** (names, IDs, URLs), **Expected output** (what success looks like).
-
-Bad: `"Meeting prep"` — which meeting? when? what to prepare? The wake-up agent will skip ambiguous descriptions.
-
-### POST /api/schedule/dm — Pre-composed DM
-```bash
-curl -s -X POST http://localhost:8321/api/schedule/dm \
-  -H 'Content-Type: application/json' \
-  -d '{"time": "2026-04-06T16:00:00-04:00", "message": "Reminder: Design review in 30 min.", "platform": "slack"}'
-```
-
-### POST /api/schedule — Agent task
-```bash
-curl -s -X POST http://localhost:8321/api/schedule \
-  -H 'Content-Type: application/json' \
-  -d '{"time": "2026-04-06T16:00:00-04:00", "taskType": "wake", "description": "Check PR #42 status and notify user.", "tier": "medium", "taskContext": {"scheduledBy": "dm_conversation"}}'
-```
-Fields: `time` (required), `taskType` (`wake`), `description` (required, min 20 chars), `tier` (`lite`/`medium`/`high`) **or** `model` (registered id like `claude-opus-4-7`, legacy alias `sonnet`/`opus`, or composite `<backendId>/<modelId>`) — mutually exclusive, `taskContext` (optional metadata). See the `schedule` skill body for the full surface and `/api/schedule/options` for the live model list.
-
-### Manage pending items
-```bash
-curl -s "http://localhost:8321/api/schedule?status=pending"                         # list
-curl -s -X PATCH http://localhost:8321/api/schedule/42 \
-  -H 'Content-Type: application/json' -d '{"time": "2026-04-06T17:00:00-04:00"}'   # edit
-curl -s -X DELETE http://localhost:8321/api/schedule/42                              # cancel
-```
-Editable: `time`, `description`, `message` (dm only), `tier` (or `model`, mutually exclusive — pass `null` to clear), `taskContext`. Only `pending` items.
-
-### Time discipline
-- Absolute ISO 8601 with offset required — no relative times.
-- Do not schedule during quiet hours (default 22:00–08:00, configurable) unless critical.
-- Maximum 5 wake-ups per execution.
+Recurring autonomous **work** (fetch / check / act on a cadence) is an **Agent** —
+create one with the `agent-create` skill (`POST /api/agents`), managed on `/agents`.
+Recurring scheduled **DMs / briefings** stay on `POST /api/recurring-schedules`
+with `taskType: "dm_session"`. `GET /api/recurring-schedules?enabled=true` lists
+existing rows (dedup). → Full guide: load the `agent-create` or `schedule` skill.
 
 ---
 
-## Skills Management
+## Scheduling & Skills CRUD
 
-User-authored skills: `~/.personal-agent/skills/{slug}/SKILL.md`. Built-in skills are read-only (403). Slug: lowercase kebab-case `[a-z0-9][a-z0-9-]*`, 1–64 chars.
-
-```bash
-curl -s http://localhost:8321/api/skills                                            # list all
-curl -s http://localhost:8321/api/skills/todo-digest                                # read one
-curl -s -X POST http://localhost:8321/api/skills \
-  -H 'Content-Type: application/json' \
-  -d '{"name": "todo-digest", "description": "Summarize today.md", "content": "# TODO Digest\n...", "allowedTools": ["Bash(curl *)", "Read"]}'
-curl -s -X PUT http://localhost:8321/api/skills/todo-digest \
-  -H 'Content-Type: application/json' -d '{"description": "New description"}'      # update
-curl -s -X DELETE http://localhost:8321/api/skills/todo-digest                      # delete
-```
-Always `GET /api/skills` before creating (check name collisions). **Omit frontmatter** from `content` — the API injects it.
+One-shot DMs / agent wake-ups (`/api/schedule`, `/api/schedule/dm`) and
+user-authored Skills CRUD (`/api/skills`) work identically to direct
+mode — they are never proxied. Load the `schedule` skill for scheduling
+and the `agent-create` skill for recurring work; this variant does not
+mirror those surfaces.

package/agent-assets/skills/external-services/SKILL.delegated.gemini.md

@@ -121,7 +121,7 @@ curl -sS -X POST http://localhost:8321/api/integrations/google_calendar/exec \
   }'
 ```
 
-`outputSchema` is **required** (4 KB cap). Defaults: `maxToolCalls=7`,
+`outputSchema` is **required** (4 KB cap). Defaults: `maxToolCalls=8`,
 `maxBudgetUsd=0.05`, `timeoutMs=60000`.
 
 ### Destructive-confirm two-step (`allowDestructive`)
@@ -155,31 +155,7 @@ destructive-confirm second call.
   know about, call `POST /api/notify` with a one-line summary. The
   daemon does NOT auto-notify — it's an explicit choice.
 
-### Error envelope
-
-`/exec` extends the direct-mode envelope with delegated-mode fields.
-Discriminator: `body.mode === "delegated"`.
-
-| HTTP | `error` | retry? | What to do |
-|---|---|---|---|
-| 400 | `validation_error` / `schema_too_large` | no | Fix the request body. |
-| 409 | `mode_mismatch` | no | Calendar isn't delegated. Re-read `integrations.md`. |
-| 409 | `precondition` | no | Mode/backend flipped during queue wait. Re-check state. |
-| 429 | `task_quota_exhausted` | no | Daily cap reached. Wait or surface. |
-| 502 | `parse_error` / `schema_violation` | no (daemon already retried once) | Simplify schema. |
-| 502 | `tool_unavailable` | no | No connector tool fits. Surface the gap. |
-| 502 | `tool_failed` | maybe | Connector tool returned an error. Surface verbatim. |
-| 502 | `auth_error` | no | Connector signed out. Re-authenticate. |
-| 502 | `policy_violation` | no | Subprocess attempted an out-of-allowlist tool (anti-injection). |
-| 502 | `loop_aborted` | no | `maxToolCalls` exceeded. Bump or simplify. |
-| 502 | `budget_exhausted` | no | `maxBudgetUsd` exceeded. Caller can raise the cap. |
-| 502 | `post_write_format_failure` | no | Write succeeded; formatting failed. Surface with partial trace. |
-| 503 | `delegated_proxy_busy` | yes | Queue saturated. Backoff and retry once. |
-| 503 | `task_mode_disabled` | no | Operator killed it. Stop. |
-| 504 | `timeout` | yes (1×) | Wall-clock fired. Retry once. |
-| 500 | `subprocess_crashed` | no | Daemon-side defect. Surface and stop. |
-
-Always preserve `body.message` verbatim when reporting to the user.
+{{> ref:exec-errors }}
 <!-- /service:calendar -->
 
 ---
@@ -190,7 +166,7 @@ Always preserve `body.message` verbatim when reporting to the user.
 **Scope**: this skill targets a **separate** Obsidian vault the user
 maintains alongside this app — e.g. a personal knowledge base. It is
 **not** the agent's own primary management store. The agent's primary
-files (`today.md`, `roadmap.md`, `projects/`, `rules/`, `routines/`,
+files (`state/today.md`, `plans/roadmap.md`, `projects/`, `rules/`, `routines/`,
 `user/`, `agent/`, …) live in the primary vault and are reached via
 `/api/context/*` (see the `context` skill). **Never** use this skill to
 read or write the primary vault.
@@ -235,10 +211,10 @@ skill and the `/api/context/*` endpoints instead.
 
 ```bash
 curl -s http://localhost:8321/api/github/repos                              # list watched repos
-curl -s "http://localhost:8321/api/github/pulls?state=open"                  # list PRs
+curl -s "http://localhost:8321/api/github/pulls?owner=user&repo=repo&state=open" # list PRs
 curl -s -X POST http://localhost:8321/api/github/pulls/comment \
   -H 'Content-Type: application/json' \
-  -d '{"owner": "user", "repo": "repo", "pullNumber": 42, "body": "LGTM"}' # comment — Autonomous
+  -d '{"owner": "user", "repo": "repo", "pull_number": 42, "comment": "LGTM"}' # comment — Autonomous
 ```
 <!-- /service:github -->
 
@@ -254,92 +230,20 @@ update, archive).
 
 ---
 
-## Recurring Schedules
+## Recurring tasks
 
-CRUD for repeating agent tasks. Timezone auto-filled from daemon config.
-
-```bash
-curl -s -X POST http://localhost:8321/api/recurring-schedules \
-  -H 'Content-Type: application/json' \
-  -d '{"taskType": "wake", "description": "Morning inbox triage.", "recurrenceRule": {"frequency": "daily", "time": "09:00"}}'
-curl -s "http://localhost:8321/api/recurring-schedules?enabled=true"         # list
-curl -s -X PATCH http://localhost:8321/api/recurring-schedules/1 \
-  -H 'Content-Type: application/json' \
-  -d '{"recurrenceRule": {"frequency": "weekly", "time": "10:00", "daysOfWeek": [1,3,5]}}'
-curl -s -X PATCH http://localhost:8321/api/recurring-schedules/1 \
-  -H 'Content-Type: application/json' -d '{"enabled": false}'              # disable
-curl -s -X DELETE http://localhost:8321/api/recurring-schedules/1           # delete
-```
-`recurrenceRule`: `frequency` (daily/weekly/monthly), `time` (HH:MM), `daysOfWeek` (0=Sun..6=Sat, weekly), `daysOfMonth` (1-31, monthly). → Full guide: load `schedule` skill.
-
----
-
-## One-Shot Scheduling
-
-Schedule a future DM or agent task. Use `<current_time>` to resolve relative times into absolute ISO 8601 with offset.
-
-### DM vs Agent Task
-
-| Criterion | `/api/schedule/dm` (free) | `/api/schedule` (~$0.03) |
-|---|---|---|
-| Message text knowable now? | Yes | No — needs lookup/decision at execution |
-| Needs API data at execution? | No | Yes |
-| Multi-step action? | No | Yes |
-| Conditional on state that may change? | No | Yes |
-
-**Default to DM** — every agent wake-up costs money and context.
-
-### Context-loss warning
-
-> The wake-up agent has NO memory of why it was scheduled — the `description` field is its only context.
-
-Include: **What** (verb + object), **Why** (trigger/reason), **Who/What** (names, IDs, URLs), **Expected output** (what success looks like).
-
-Bad: `"Meeting prep"` — which meeting? when? what to prepare? The wake-up agent will skip ambiguous descriptions.
-
-### POST /api/schedule/dm — Pre-composed DM
-```bash
-curl -s -X POST http://localhost:8321/api/schedule/dm \
-  -H 'Content-Type: application/json' \
-  -d '{"time": "2026-04-06T16:00:00-04:00", "message": "Reminder: Design review in 30 min.", "platform": "slack"}'
-```
-
-### POST /api/schedule — Agent task
-```bash
-curl -s -X POST http://localhost:8321/api/schedule \
-  -H 'Content-Type: application/json' \
-  -d '{"time": "2026-04-06T16:00:00-04:00", "taskType": "wake", "description": "Check PR #42 status and notify user.", "tier": "medium", "taskContext": {"scheduledBy": "dm_conversation"}}'
-```
-Fields: `time` (required), `taskType` (`wake`), `description` (required, min 20 chars), `tier` (`lite`/`medium`/`high`) **or** `model` (registered id like `claude-opus-4-7`, legacy alias `sonnet`/`opus`, or composite `<backendId>/<modelId>`) — mutually exclusive, `taskContext` (optional metadata). See the `schedule` skill body for the full surface and `/api/schedule/options` for the live model list.
-
-### Manage pending items
-```bash
-curl -s "http://localhost:8321/api/schedule?status=pending"                         # list
-curl -s -X PATCH http://localhost:8321/api/schedule/42 \
-  -H 'Content-Type: application/json' -d '{"time": "2026-04-06T17:00:00-04:00"}'   # edit
-curl -s -X DELETE http://localhost:8321/api/schedule/42                              # cancel
-```
-Editable: `time`, `description`, `message` (dm only), `tier` (or `model`, mutually exclusive — pass `null` to clear), `taskContext`. Only `pending` items.
-
-### Time discipline
-- Absolute ISO 8601 with offset required — no relative times.
-- Do not schedule during quiet hours (default 22:00–08:00, configurable) unless critical.
-- Maximum 5 wake-ups per execution.
+Recurring autonomous **work** (fetch / check / act on a cadence) is an **Agent** —
+create one with the `agent-create` skill (`POST /api/agents`), managed on `/agents`.
+Recurring scheduled **DMs / briefings** stay on `POST /api/recurring-schedules`
+with `taskType: "dm_session"`. `GET /api/recurring-schedules?enabled=true` lists
+existing rows (dedup). → Full guide: load the `agent-create` or `schedule` skill.
 
 ---
 
-## Skills Management
+## Scheduling & Skills CRUD
 
-User-authored skills: `~/.personal-agent/skills/{slug}/SKILL.md`. Built-in skills are read-only (403). Slug: lowercase kebab-case `[a-z0-9][a-z0-9-]*`, 1–64 chars.
-
-```bash
-curl -s http://localhost:8321/api/skills                                            # list all
-curl -s http://localhost:8321/api/skills/todo-digest                                # read one
-curl -s -X POST http://localhost:8321/api/skills \
-  -H 'Content-Type: application/json' \
-  -d '{"name": "todo-digest", "description": "Summarize today.md", "content": "# TODO Digest\n...", "allowedTools": ["Bash(curl *)", "Read"]}'
-curl -s -X PUT http://localhost:8321/api/skills/todo-digest \
-  -H 'Content-Type: application/json' -d '{"description": "New description"}'      # update
-curl -s -X DELETE http://localhost:8321/api/skills/todo-digest                      # delete
-```
-Always `GET /api/skills` before creating (check name collisions). **Omit frontmatter** from `content` — the API injects it.
+One-shot DMs / agent wake-ups (`/api/schedule`, `/api/schedule/dm`) and
+user-authored Skills CRUD (`/api/skills`) work identically to direct
+mode — they are never proxied. Load the `schedule` skill for scheduling
+and the `agent-create` skill for recurring work; this variant does not
+mirror those surfaces.

package/agent-assets/skills/external-services/SKILL.md

@@ -15,7 +15,7 @@ Base URL: `http://localhost:8321`. All calls via `curl -s` with `Content-Type: a
 Two adjacent files declare where the user's data lives — read both before
 routing any external-service call.
 
-1. **`rules/management.md` → `## Source of Truth`** carries durable
+1. **`policies/management.md` → `## Source of Truth`** carries durable
    user-authored answers ("Schedule = Google Calendar", "Tasks = Notion",
    etc.). This is the authoritative routing table.
 2. **`~/.personal-agent/integrations.md` → `## Note Sources`** is the
@@ -33,7 +33,7 @@ integrations DB. Treat it as a routing hint, not a knob.
 
 ### Calendar provider routing
 
-The user's calendar provider lives in `rules/management.md` → `## Source of Truth` → Schedule row. Read it before every calendar call.
+The user's calendar provider lives in `policies/management.md` → `## Source of Truth` → Schedule row. Read it before every calendar call.
 
 | Schedule value in management rules | Use this base path | Backed by |
 |---|---|---|
@@ -43,7 +43,7 @@ The user's calendar provider lives in `rules/management.md` → `## Source of Tr
 
 **Hard rule**: NEVER cross-call. Calling `/api/calendar/*` while Schedule = Apple Calendar does NOT return empty — it queries the user's separate Google account if one exists, returning the wrong day. Calling `/api/apple-calendar/*` while Schedule = Google Calendar returns 503. Both failure modes are silent at the agent level — only the user notices, in the form of wrong answers.
 
-If `rules/management.md` is missing, ambiguous, or names a provider not listed here, **stop and ask the user** rather than guessing. Do not default to Google.
+If `policies/management.md` is missing, ambiguous, or names a provider not listed here, **stop and ask the user** rather than guessing. Do not default to Google.
 
 The endpoint sets are intentionally near-identical in shape (same JSON for events, same query parameters for listing) so the rest of this skill body documents both at once. Provider-specific differences are flagged inline with **[Apple only]** or **[Google only]**.
 

package/agent-assets/skills/external-services/SKILL.native.claude.md

@@ -37,14 +37,14 @@ in the session preamble.
 The same two files documented in the direct-mode body are still
 authoritative for non-Calendar routing:
 
-1. **`rules/management.md` → `## Source of Truth`** — durable
+1. **`policies/management.md` → `## Source of Truth`** — durable
    user-authored answers ("Schedule = Google Calendar", "Tasks =
    Notion", etc.).
 2. **`~/.personal-agent/integrations.md` → `## Note Sources`** — the
    daemon-rendered snapshot for the user's external Obsidian vault path
    plus Notion's mode.
 
-If `rules/management.md` Schedule = Apple Calendar or Outlook Calendar,
+If `policies/management.md` Schedule = Apple Calendar or Outlook Calendar,
 the user's chosen provider is **not** Google Calendar and the
 native-Claude binding is irrelevant — route to `/api/apple-calendar/*`
 or `/api/calendar/outlook/*` exactly as the direct-mode body documents.
@@ -149,7 +149,7 @@ the window and intersect.
 <!-- service:apple-calendar -->
 ## Apple Calendar (iCloud CalDAV) — direct, unchanged
 
-If `rules/management.md` Schedule = Apple Calendar, use the
+If `policies/management.md` Schedule = Apple Calendar, use the
 `/api/apple-calendar/*` routes documented in the base body. Apple
 Calendar has no MCP connector; native-mode gating does not apply.
 
@@ -165,7 +165,7 @@ native binding above is Google-only.
 <!-- service:outlook-calendar -->
 ## Outlook Calendar (Microsoft Graph) — direct, unchanged
 
-If `rules/management.md` Schedule = Outlook Calendar, use
+If `policies/management.md` Schedule = Outlook Calendar, use
 `/api/calendar/outlook/*` per the direct-mode body. Microsoft does not
 ship a hosted Outlook Calendar connector for Claude / Codex / Gemini
 today; native-mode gating does not apply.
@@ -178,7 +178,7 @@ today; native-mode gating does not apply.
 
 **Scope**: this skill targets the **separate** Obsidian vault the user
 maintains alongside this app — never the agent's primary management
-store (`today.md`, `roadmap.md`, `projects/`, `rules/`, `routines/`,
+store (`state/today.md`, `plans/roadmap.md`, `projects/`, `rules/`, `routines/`,
 `user/`, `agent/`). Those are reached via `/api/context/*` (see the
 `context` skill).
 
@@ -241,7 +241,7 @@ session's integration state.
 When the hourly_check native flow's Step 0b fetches imminent-window
 events, POST each materialised event to `/api/observations` so
 subsequent runs can dedup. The daemon computes `contentHash`
-server-side via `@personal-agent/shared/observations-hash.ts` — pass
+server-side via `@aitne/shared/observations-hash` — pass
 the raw `payload`.
 
 **Batch when you have more than one event.** Use
@@ -284,7 +284,7 @@ schedule surface (scheduling is daemon-internal, not an integration).
 
 ## Skills Management — direct, unchanged
 
-User-authored skills: `~/.personal-agent/skills/{slug}/SKILL.md`.
+User-authored skills: `<contextDir>/policies/skills/{slug}/SKILL.md`.
 Built-in skills are read-only (403). Native-mode gating does not apply.
 
 ```bash