@aitne-sh/aitne 0.1.8 → 0.1.9

package/agent-assets/skills/context/SKILL.md

@@ -26,33 +26,33 @@ vault**, not this primary store.
 
 | File | Purpose | Owner | Lock? |
 |---|---|---|---|
-| `today.md` | Today's schedule, tasks, agent log, handoff | See `today` skill | Yes (Morning Routine) |
-| `roadmap.md` | Long-horizon agent action plan + Long-term Plans | See `roadmap` skill | Yes (Roadmap Refresh) |
+| `state/today.md` | Today's schedule, tasks, agent log, handoff | See `today` skill | Yes (Morning Routine) |
+| `plans/roadmap.md` | Long-horizon agent action plan + Long-term Plans | See `roadmap` skill | Yes (Roadmap Refresh) |
 | `projects/*.md` | Project state summaries | Any event on material state change | No |
 | `weekly/YYYY-Www.md` | Weekly review snapshots | Friday Weekly Review only (PUT) | No |
 | `monthly/YYYY-MM.md` | Monthly review snapshots | Month-end Monthly Review only (PUT) | No |
 | `rules/*.md` | User-controlled policy files | Explicit user request only | No |
-| `rules/policies/<slug>.md` | Durable management policies captured from DM | `management-policy` skill — **do not write from here** | No |
-| `rules/policies/_index.md` | Readable index of active policies | `management-policy` skill — **do not write from here** | No |
+| `policies/management-captures/<slug>.md` | Durable management policies captured from DM | `management-policy` skill — **do not write from here** | No |
+| `policies/management-captures/_index.md` | Readable index of active policies | `management-policy` skill — **do not write from here** | No |
 | `routines/*.md` | Per-cadence check rulebooks | Explicit user request only | No |
-| `user/profile.md` | User identity and preferences | `user-profile` skill — **do not write from here** | No |
+| `identity/profile.md` | User identity and preferences | `user-profile` skill — **do not write from here** | No |
 | `user/*.md` | Detailed user dictionary | `user-profile` skill — **do not write from here** | No |
 
 Morning Routine scans roadmap daily and processes matching Preparation
-Timeline rows into `today.md` — see the `roadmap` skill for the full
+Timeline rows into `state/today.md` — see the `roadmap` skill for the full
 entry taxonomy and the morning routine task-flow for the scanning rules.
 
 ## projects/*.md
 
 Update on status changes, milestones reached/delayed, or active set changes. Use `GET /api/context/list/projects` to discover files. The source of truth is always the individual `projects/<slug>.md` notes; `_active.base` is only the Obsidian Bases view config, not a narrative summary note.
 
-The canonical frontmatter schema is documented in `projects/_index.md`
-(seeded from `agent-assets/templates/projects/_index.md`). The API
+The canonical frontmatter schema is documented in `plans/projects/_index.md`
+(seeded from `agent-assets/templates/plans/projects/_index.md`). The API
 validates only `type: project`, `owner: shared`, `updated`, and an H1
 (`context-frontmatter.ts`). Conventional but unvalidated fields —
 `slug`, `state`, `start`, `due`, `stakeholders`, `next_milestone`,
 `tags` — should still be written for new files because the
-`projects/_active.base` Obsidian view filters on `state`.
+`plans/projects/_active.base` Obsidian view filters on `state`.
 
 ## Project DM-intent detection
 
@@ -76,8 +76,8 @@ the partial.
 
 Weekly and monthly review snapshots, the user-controlled `rules/*.md`
 policy files, the built-in `routines/<cadence>.md` rulebooks, custom
-routines under `routines/custom/`, and the agent-private
-`agent/journal.md` all have stable per-file conventions (writer event,
+routines under `policies/routines/custom/`, and the agent-private
+`journal/agent.md` all have stable per-file conventions (writer event,
 verb, frontmatter, retention) documented in the snapshot-files
 reference below.
 
@@ -101,7 +101,7 @@ envelope are in the required-frontmatter reference below.
 The full `/api/context/*` surface — read / write / list / lock /
 archive / restore / health / repair / action-log — is organised by
 operation in the reference below. Add `X-Lock-Id` on every PUT / PATCH
-to `today.md` (`<today_write_lock_id>`) or `roadmap.md`
+to `state/today.md` (`<today_write_lock_id>`) or `plans/roadmap.md`
 (`<roadmap_write_lock_id>`) when the matching lock-id tag is in your
 context.
 

package/agent-assets/skills/context/curation.json

@@ -8,8 +8,8 @@
       "human_label": "File responsibilities",
       "description": "Which file owns which area of the context tree (today, roadmap, projects, weekly, rules, user)",
       "scope_paths": [
-        "today.md",
-        "roadmap.md",
+        "state/today.md",
+        "plans/roadmap.md",
         "projects/*.md",
         "weekly/*.md",
         "monthly/*.md",

package/agent-assets/skills/context/references/api.md

@@ -10,8 +10,8 @@ Body submission follows `_safety.md` "Daemon-API body submission":
 small section PATCHes use inline `-d '{...}'`; full-file PUT uses the
 stdin heredoc `-d @- <<'JSON'` shape because the body runs multi-KB.
 
-Add `X-Lock-Id: <today_write_lock_id>` (for `today.md`) or
-`X-Lock-Id: <roadmap_write_lock_id>` (for `roadmap.md`) on every
+Add `X-Lock-Id: <today_write_lock_id>` (for `state/today.md`) or
+`X-Lock-Id: <roadmap_write_lock_id>` (for `plans/roadmap.md`) on every
 PUT / PATCH when the matching lock-id tag is in your context — the
 daemon emits the tag only while the corresponding lock is held by
 this session.
@@ -21,7 +21,7 @@ this session.
 ### GET /api/context/:path
 
 ```bash
-curl -s http://localhost:8321/api/context/roadmap
+curl -s http://localhost:8321/api/context/plans/roadmap
 ```
 
 Response: `{ "content": "...", "lastModified": "ISO8601" }` or `404`.
@@ -41,7 +41,7 @@ enumerate `projects/`, `weekly/`, `monthly/`, `user/`, `rules/`,
 
 ### GET /api/context/today/reconciliation
 
-Returns the Morning Routine's reconciliation report for `today.md`
+Returns the Morning Routine's reconciliation report for `state/today.md`
 (which mail/calendar/Notion sources contributed what to User Tasks /
 Agent Plan). Read-only diagnostic surface; not the place to write
 changes.
@@ -62,40 +62,46 @@ Fields:
 | `content` | string (required) | Full file body, including frontmatter and H1 where the file's validator requires them. |
 | `expectedMtime` | string (optional) | ISO 8601. When present the daemon returns `409` if the current mtime differs — race protection for read-modify-write loops. |
 
-Add `X-Lock-Id: <lock-id>` when writing a locked file (`today.md`,
-`roadmap.md`). Snapshots the prior content for restore.
+Add `X-Lock-Id: <lock-id>` when writing a locked file (`state/today.md`,
+`plans/roadmap.md`). Snapshots the prior content for restore.
 
 Common rejections:
 
 - `400 {error:"validation_error", message, path}` — file-specific
-  validator failed (e.g. `today.md` line-1 date regex, `roadmap.md`
+  validator failed (e.g. `state/today.md` line-1 date regex, `plans/roadmap.md`
   transition guard, required frontmatter missing on `user/*.md` /
   `rules/*.md` / `projects/*.md` / `daily/*.md` / `weekly/*.md` /
   `monthly/*.md`).
-- `409 {error:"lock_held"}` — another session holds the file's write
-  lock. Retry with backoff (30s × 3).
-- `422` — file-specific schema mismatch (e.g. `today.md` line-1
-  agent-day mismatch — the error echoes both the supplied date and
-  the daemon's current agent-day).
-
-`rules/management.md` is user-controlled policy: modify only when the
+- `409 {error:"morning_routine_lock_held"}` — the Morning Routine holds
+  the `state/today.md` write lock; `409 {error:"roadmap_write_lock_held"}`
+  — another session holds the `plans/roadmap.md` lock. Retry with
+  backoff (30s × 3).
+- `400 {error:"validation_error", message, path}` — also covers the
+  `state/today.md` line-1 agent-day mismatch (the message echoes both the
+  supplied date and the daemon's current agent-day). The `422` status is
+  reserved for *frontmatter* validation on globbed files (`user/*.md`,
+  `rules/*.md`, `projects/*.md`, `daily/*.md`, `weekly/*.md`,
+  `monthly/*.md`), not for today.md line-1.
+
+`policies/management.md` is user-controlled policy: modify only when the
 user explicitly asks, and preserve every unrelated section.
 
 ### PATCH /api/context/:path — Section operation
 
 ```bash
-curl -s -X PATCH http://localhost:8321/api/context/today \
+curl -s -X PATCH http://localhost:8321/api/context/state/today \
   -H 'Content-Type: application/json' \
   -d '{"section": "agent_log", "mode": "append", "content": "- 09:35 Processed meeting summary"}'
 ```
 
 | Field | Type | Description |
 |---|---|---|
-| `section` | string | snake_case of the heading (e.g. `learned_context`, `agent_log`, `log`). **Omit for `append_to_file`**; required for every other mode. |
-| `mode` | `append` \| `replace` \| `clear` \| `clear_before` \| `append_to_file` | Default `append`. |
-| `content` | string | Ignored for `clear` / `clear_before`. |
+| `section` | string | snake_case of the heading (e.g. `learned_context`, `agent_log`, `log`). **Omit for `append_to_file` and `frontmatterMerge`**; required for every other mode. |
+| `mode` | `append` \| `replace` \| `clear` \| `clear_before` \| `append_to_file` \| `frontmatterMerge` | Default `append`. |
+| `content` | string | Ignored for `clear` / `clear_before` / `frontmatterMerge`. |
 | `cutoff` | string | **Required when `mode: "clear_before"`.** SQLite format `YYYY-MM-DD HH:MM:SS` (zero-padded). Removes bullet rows whose `- [YYYY-MM-DD HH:MM:SS]` timestamp is ≤ cutoff. |
 | `maxEntries` | number | Optional for `mode: "append"`. After appending, trim oldest bullet entries from the top of the section body so at most `maxEntries` bullets remain. Non-bullet lines are preserved. SignalDetector uses cap = 20. |
+| `frontmatter` | object | **Required when `mode: "frontmatterMerge"`** (and only valid then). Non-empty partial frontmatter object, deep-merged into the file's YAML frontmatter. |
 
 Mode semantics:
 
@@ -103,28 +109,34 @@ Mode semantics:
 - `replace` — replace the entire section body with `content`. **Read-before-write is mandatory** — `replace` does not merge; sending just one bullet erases every sibling. The skill body's "Worked example" shows the GET-merge-PATCH pattern.
 - `clear` — drop the section body, keep the heading.
 - `clear_before` — rolling-log trim, drops bullets with timestamps ≤ `cutoff`. Non-bullet lines preserved. Race-safe consumption shape for `Raw Signals` and similar logs.
-- `append_to_file` — omit `section`, append `content` to the end of the file. The intended first-write path when a section header does not exist yet: include the header inside `content` (`"\n## Section\n- bullet\n"`). Also the only write shape for files with no canonical section schema (`agent/journal.md`).
+- `append_to_file` — omit `section`, append `content` to the end of the file. The intended first-write path when a section header does not exist yet: include the header inside `content` (`"\n## Section\n- bullet\n"`). Also the only write shape for files with no canonical section schema (`journal/agent.md`).
+- `frontmatterMerge` — omit `section`; deep-merge the `frontmatter` object into the file's existing YAML frontmatter (nested objects merge key-by-key; scalars/arrays replace), preserving the body verbatim. The chokepoint-safe way to link entity `sources.<app>.<id>` + set `last_synced_at` without a read-modify-write of the whole file (design 21 §10.4).
 
 Common rejections (informational responses worth knowing):
 
 - `400 {error:"section_not_found", section, availableSections:[…]}` — the section name did not match. `availableSections` lists every snake_cased heading the file actually has; pick the closest match and retry. Do NOT retry the same `section` value.
 - `400 {error:"validation_error", message, path}` — content failed the file-specific validator.
 - `400 {error:"cutoff_required", message}` — `clear_before` was called without a valid `cutoff`.
-- `409 {error:"lock_held"}` — file's write lock is held by another session.
+- `409 {error:"morning_routine_lock_held"}` (PATCH/PUT on `state/today`) or
+  `409 {error:"roadmap_write_lock_held"}` (PATCH/PUT on `plans/roadmap`) —
+  the file's write lock is held by another session. (The generic
+  `lock_held` code is only emitted by `POST /api/context/lock/morning-routine`
+  on contended acquisition, never by a PATCH/PUT.)
 
 ### DELETE /api/context/:path
 
 Removes the file (snapshot first). The daemon only allows DELETE on a
-small set of paths — notably `routines/custom/<slug>` (after the user
+small set of paths — notably `policies/routines/custom/<slug>` (after the user
 asks to retire a custom routine). Most files are NOT delete-eligible
-(e.g. `today.md`, `roadmap.md`, `user/profile.md`); the daemon returns
-`400 {error:"path_not_deletable"}` for those.
+(e.g. `state/today.md`, `plans/roadmap.md`, `identity/profile.md`); the daemon returns
+`403 {error:"forbidden"}` (with `errors[0].code: "context.write_forbidden"`)
+for those.
 
 ## Lifecycle
 
 ### POST /api/context/archive-today
 
-Rotates `today.md` → `yesterday.md` (synthesized `daily/YYYY-MM-DD.md`
+Rotates `state/today.md` → `state/yesterday.md` (synthesized `daily/YYYY-MM-DD.md`
 is now written by the Morning Routine, not this endpoint). Called by
 the Morning Routine during day rotation; other sessions should NOT
 invoke this directly.
@@ -144,7 +156,7 @@ when `GET /api/context/health` reports the file as stubbed.
 
 ## Locks
 
-`today.md` and `roadmap.md` are locked files: `PUT` / `PATCH` requires
+`state/today.md` and `plans/roadmap.md` are locked files: `PUT` / `PATCH` requires
 the lock to be held by the calling session, and the daemon emits an
 `X-Lock-Id` header value that must be echoed on each request via the
 `X-Lock-Id:` header.
@@ -158,7 +170,7 @@ the lock to be held by the calling session, and the daemon emits an
 
 The dispatcher auto-acquires this lock for `routine.morning_routine`
 and surfaces the id via `<today_write_lock_id>` in the prompt context.
-Other sessions get `409 today_write_lock_held` on PUT / PATCH while
+Other sessions get `409 morning_routine_lock_held` on PUT / PATCH while
 the lock is held — back off 30 s and retry up to 3 times.
 
 ### Roadmap lock
@@ -176,8 +188,8 @@ another session — same 30 s × 3 retry pattern.
 **Path-name gotchas** (these return `404 {"error":"unknown_route", …}`
 with a hint pointing at the correct path):
 
-- `POST /api/context/roadmap/lock` — order reversed.
-- `POST /api/context/roadmap/write-lock` — order reversed and wrong noun.
+- `POST /api/context/plans/roadmap/lock` — order reversed.
+- `POST /api/context/plans/roadmap/write-lock` — order reversed and wrong noun.
 - `POST /api/context/lock/roadmap-write` — wrong noun.
 
 A `401 {"error":"unauthorized"}` from a path you believe is correct
@@ -186,13 +198,13 @@ so no bearer token is required).
 
 ## Roadmap-specific writes
 
-### POST /api/context/roadmap/id
+### POST /api/context/plans/roadmap/id
 
 Mints a new stable entry id (`rm-YYYYMMDD-<hash>`) for a roadmap row.
 Requires `X-Lock-Id: <roadmap_write_lock_id>`.
 
 ```bash
-curl -s -X POST http://localhost:8321/api/context/roadmap/id \
+curl -s -X POST http://localhost:8321/api/context/plans/roadmap/id \
   -H 'Content-Type: application/json' \
   -H 'X-Lock-Id: <roadmap_write_lock_id>' \
   -d '{"creationDate":"YYYY-MM-DD"}'
@@ -216,5 +228,5 @@ curl -s -X POST http://localhost:8321/api/action/log \
 ```
 
 Records an entry in `agent_actions` for the dashboard's audit feed.
-Not the same as `today.md ## Agent Log` (that's a markdown surface;
+Not the same as `state/today.md ## Agent Log` (that's a markdown surface;
 this is a SQLite row). Risk tier: Autonomous.

package/agent-assets/skills/context/references/required-frontmatter.md

@@ -50,7 +50,7 @@ on `PUT` (full replace).
 
 ## Files outside the table
 
-`today.md`, `roadmap.md`, `agent/journal.md`, and `rules/policies/*.md`
+`state/today.md`, `plans/roadmap.md`, `journal/agent.md`, and `policies/management-captures/*.md`
 have their own validators (date-line regex, transition guard, append-
 only mode, policy schema). The frontmatter rules in this reference do
 not apply to them — see each owning skill for the specifics.
@@ -60,8 +60,8 @@ not apply to them — see each owning skill for the specifics.
 ```json
 {
   "error": "validation_error",
-  "message": "user/people.md is missing required frontmatter field: updated",
-  "path": "user/people.md"
+  "message": "identity/people.md is missing required frontmatter field: updated",
+  "path": "identity/people.md"
 }
 ```
 

package/agent-assets/skills/context/references/snapshot-files.md

@@ -8,7 +8,7 @@ description: Weekly / monthly review snapshots, rules / routines files — who w
 
 These files live in the primary management vault under
 `weekly/`, `monthly/`, `rules/`, and `routines/`. They are not part
-of the day-to-day context churn (`today.md`, `roadmap.md`,
+of the day-to-day context churn (`state/today.md`, `plans/roadmap.md`,
 `projects/*.md`); they accumulate slowly and are written by routines
 or by explicit user request.
 
@@ -22,7 +22,7 @@ or by explicit user request.
 Notes:
 
 - Monthly files are **user-facing only** — agent-side metrics (cost,
-  retry counts, self-critique) go to `agent/journal.md`, not here.
+  retry counts, self-critique) go to `journal/agent.md`, not here.
 - Weekly file name uses ISO week (`YYYY-Www` — `2026-W19`, not
   `2026-W5`); pad the week to two digits.
 - Never write `weekly/*.md` or `monthly/*.md` on any other day. The
@@ -65,10 +65,10 @@ explicitly asks to change the policy or routine itself.
 
 - Preserve unrelated sections verbatim. PATCH the one section the
   user is changing; do not full-body PUT.
-- `rules/management.md` is the durable management policy file —
+- `policies/management.md` is the durable management policy file —
   modify only when the user explicitly asks.
 
-### `rules/policies/<slug>.md` and `rules/policies/_index.md`
+### `policies/management-captures/<slug>.md` and `policies/management-captures/_index.md`
 
 Route to the `management-policy` skill. It owns the read-before-write,
 similarity-detection, and pause/resume fan-out for durable policies.
@@ -82,7 +82,7 @@ similarity check and the dossier / routine fan-out.
 - Append or edit `### <label>` blocks under `## Checks`; each block
   is one user-authored rule the cadence runs.
 
-### `routines/custom/<slug>.md`
+### `policies/routines/custom/<slug>.md`
 
 Full-file `PUT` is usually safest. Required frontmatter:
 
@@ -98,6 +98,6 @@ max_budget_usd: <number>
 
 The file body must also contain a `## Checks` section.
 
-Deleting a custom routine uses `DELETE /api/context/routines/custom/<slug>`
+Deleting a custom routine uses `DELETE /api/context/policies/routines/custom/<slug>`
 **only** after the user asks to retire it. The daemon snapshots the
 prior content for restore.

package/agent-assets/skills/context/seeds/file-responsibilities.seed.json

@@ -1,13 +1,13 @@
 {
   "kind": "knowledge_layout",
   "files": [
-    { "path": "today.md", "purpose": "today's schedule, tasks, agent log, handoff", "sections": [{ "heading": "## Schedule", "contains": "today's events" }, { "heading": "## Tasks", "contains": "open tasks" }, { "heading": "## Agent Notes", "contains": "agent observations" }] },
-    { "path": "roadmap.md", "purpose": "long-horizon agent action plan + Long-term Plans", "sections": [{ "heading": "## Annual Goals", "contains": "year-scope outcomes" }, { "heading": "## Quarterly Milestones", "contains": "quarter-scope deliverables" }, { "heading": "## Focus Areas", "contains": "current themes of work" }] },
+    { "path": "state/today.md", "purpose": "today's schedule, tasks, agent log, handoff", "sections": [{ "heading": "## Schedule", "contains": "today's events" }, { "heading": "## Tasks", "contains": "open tasks" }, { "heading": "## Agent Notes", "contains": "agent observations" }] },
+    { "path": "plans/roadmap.md", "purpose": "long-horizon agent action plan + Long-term Plans", "sections": [{ "heading": "## Annual Goals", "contains": "year-scope outcomes" }, { "heading": "## Quarterly Milestones", "contains": "quarter-scope deliverables" }, { "heading": "## Focus Areas", "contains": "current themes of work" }] },
     { "path": "projects/*.md", "purpose": "per-project state summaries (slug-named)", "sections": [{ "heading": "## Overview", "contains": "what the project is about" }, { "heading": "## Lifecycle Phases", "contains": "phase ladder for the project" }] },
     { "path": "weekly/*.md", "purpose": "weekly review snapshots (YYYY-Www); Carry Over / Next Week Focus / Lessons are lifted into next week's morning_routine via <previous_week>", "sections": [{ "heading": "## Highlights", "contains": "wins of the week" }, { "heading": "## Open Loops", "contains": "tasks/commitments still pending" }, { "heading": "## Carry Over to Next Week", "contains": "open loops to carry over (max 5) with one-line reason" }, { "heading": "## Next Week Focus", "contains": "top priorities for next week (max 3)" }, { "heading": "## Lessons for Next Week", "contains": "behavioral observation → action (max 3)" }] },
     { "path": "monthly/*.md", "purpose": "monthly review snapshots (YYYY-MM)", "sections": [{ "heading": "## Theme", "contains": "the month's overall theme" }] },
     { "path": "rules/*.md", "purpose": "user-controlled policy files", "sections": [{ "heading": "## Why", "contains": "rationale for the rule" }, { "heading": "## How", "contains": "concrete rule shape" }] },
     { "path": "user/*.md", "purpose": "user identity and preferences dictionary", "sections": [{ "heading": "## Identity", "contains": "name role tz" }] },
-    { "path": "agent/journal.md", "purpose": "agent-owned weekly + monthly self-critique", "sections": [{ "heading": "## Weekly", "contains": "what worked, what slipped, improvements" }] }
+    { "path": "journal/agent.md", "purpose": "agent-owned weekly + monthly self-critique", "sections": [{ "heading": "## Weekly", "contains": "what worked, what slipped, improvements" }] }
   ]
 }

package/agent-assets/skills/docs-search/SKILL.md

@@ -16,7 +16,7 @@ other endpoint is in the allow-list.
 **Daemon URL is not optional.** Every call must go to
 `http://localhost:8321/api/docs/...`. The session's `curl` wrapper
 rejects any other host/port silently (stdout stays empty), so a request
-to `localhost:3000` or a path with no host returns nothing and reads as
+to `localhost:8322` or a path with no host returns nothing and reads as
 "0 results" — exactly the failure mode that masquerades as "the docs
 don't cover this".
 
@@ -74,8 +74,9 @@ wrapper.
 | `curl -s "http://localhost:8321/api/docs"` | Tree listing. Use only when the operator asks "what docs are there?" |
 
 The slug in `by-slug/<slug>` is path-style (e.g.
-`features/routines/morning-routine`), exactly as it appears in the
-search response and inside `[doc:...]` citations.
+`features/routines/morning-routine`, a docs slug — not a vault path), <!-- drift-allow -->
+exactly as it appears in the search response and inside `[doc:...]`
+citations.
 
 ## Search-call budget — at most 3 per turn
 

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

@@ -212,7 +212,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 +257,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,23 +276,13 @@ 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.
+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.
 
 ---
 
@@ -330,9 +320,9 @@ curl -s -X POST http://localhost:8321/api/schedule/dm \
 ```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"}}'
+  -d '{"time": "2026-04-06T16:00:00-04:00", "taskType": "wake", "prompt": "Check PR #42 status and notify user.", "description": "PR #42 status check", "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.
+Fields: `time` (required), `taskType` (`wake`), `prompt` (required — the agent instruction, ≤8000 chars), `description` (optional label, ≤200 chars), `tier` (`lite`/`medium`/`high`) **or** `model` (registered id like `claude-opus-4-8`, 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

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

@@ -192,7 +192,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 +237,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,23 +256,13 @@ 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.
+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.
 
 ---
 
@@ -310,9 +300,9 @@ curl -s -X POST http://localhost:8321/api/schedule/dm \
 ```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"}}'
+  -d '{"time": "2026-04-06T16:00:00-04:00", "taskType": "wake", "prompt": "Check PR #42 status and notify user.", "description": "PR #42 status check", "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.
+Fields: `time` (required), `taskType` (`wake`), `prompt` (required — the agent instruction, ≤8000 chars), `description` (optional label, ≤200 chars), `tier` (`lite`/`medium`/`high`) **or** `model` (registered id like `claude-opus-4-8`, 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

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

@@ -190,7 +190,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 +235,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,23 +254,13 @@ 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.
+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.
 
 ---
 
@@ -308,9 +298,9 @@ curl -s -X POST http://localhost:8321/api/schedule/dm \
 ```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"}}'
+  -d '{"time": "2026-04-06T16:00:00-04:00", "taskType": "wake", "prompt": "Check PR #42 status and notify user.", "description": "PR #42 status check", "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.
+Fields: `time` (required), `taskType` (`wake`), `prompt` (required — the agent instruction, ≤8000 chars), `description` (optional label, ≤200 chars), `tier` (`lite`/`medium`/`high`) **or** `model` (registered id like `claude-opus-4-8`, 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

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]**.