@aitne-sh/aitne 0.1.8 → 0.1.9

package/agent-assets/skills/management-policy/SKILL.md

@@ -11,17 +11,17 @@ allowed-tools:
 A **management policy** is a durable, ongoing rule the user wants the
 agent to keep applying. It is NOT a one-off task.
 
-Each policy lives at `rules/policies/<slug>.md` and may link to:
+Each policy lives at `policies/management-captures/<slug>.md` and may link to:
 
-- `routines/custom/<slug>.md` — the cron-driven execution rulebook
-- `dossiers/<topic>.md` — where the policy's accumulating data lands
+- `policies/routines/custom/<slug>.md` — the cron-driven execution rulebook
+- `knowledge/dossiers/<topic>.md` — where the policy's accumulating data lands
 
-A readable summary of every policy lives at `rules/policies/_index.md`,
+A readable summary of every policy lives at `policies/management-captures/_index.md`,
 which the daemon's policy-index reconciler **auto-maintains** from the
-policy files on disk. The directory listing under `rules/policies/` is
+policy files on disk. The directory listing under `policies/management-captures/` is
 the source of truth; `_index.md` is a derived snapshot — **do not
 PATCH or PUT it by hand**. The same reconciler also re-renders the
-`## Active Policies` section in `rules/management.md` so it stays in
+`## Active Policies` section in `policies/management.md` so it stays in
 sync. Both files refresh within ~10 s of any policy file write.
 
 ## When to use this skill
@@ -42,7 +42,7 @@ Use when the user expresses a **durable, ongoing management rule**:
 | "Reply more tersely from now on" / tone, voice, style | `user-profile` (routes to `character`) |
 | "I'm an NYC-based dev" / single user fact | `user-profile` |
 | "Add a project for the Q3 roadmap" | `context` (`projects/*.md`) |
-| Pure data write — "log this transaction" | direct context write to the relevant `dossiers/<topic>.md` |
+| Pure data write — "log this transaction" | direct context write to the relevant `knowledge/dossiers/<topic>.md` |
 
 If the user's request is **a recurring task with no need for a recorded
 reason** (e.g. "ping me every Monday at 9 to start standup prep"), use
@@ -60,12 +60,12 @@ the directory listing if you need authoritative state.
 ```bash
 # Auto-maintained by the daemon — fastest read for slug / status /
 # cadence / linked routine + dossier / one-line why.
-curl -s "http://localhost:8321/api/context/rules/policies/_index"
+curl -s "http://localhost:8321/api/context/policies/management-captures/_index"
 
 # Directory listing — authoritative source of truth. Use this if a
 # specific policy file looks newer than the index (the reconciler
 # debounces ~10 s; fresh writes may not be reflected yet).
-curl -s "http://localhost:8321/api/context/list/rules"
+curl -s "http://localhost:8321/api/context/list/policies"
 ```
 
 If the listing and `_index.md` rows disagree, **prefer the listing**
@@ -103,14 +103,14 @@ wait again.
 
 ### Step 4 — Build the policy file
 
-Emit the full `rules/policies/<slug>.md` content as a fenced markdown
+Emit the full `policies/management-captures/<slug>.md` content as a fenced markdown
 block in the DM **before** writing, so the user sees what's about to be
 saved. The slug must:
 
 - equal the filename stem
 - match `^[a-z0-9][a-z0-9-]*[a-z0-9]$` (or a single `[a-z0-9]`)
 - be ≤ 64 chars
-- equal the linked `routines/custom/<slug>.md` slug (if any) — keep
+- equal the linked `policies/routines/custom/<slug>.md` slug (if any) — keep
   them aligned in v1
 
 ### Step 5 — Wire the dependencies (strict order; on failure, roll back in reverse)
@@ -152,7 +152,7 @@ the active policies first and ask.
    `updated: <today>`, PUT back. (The frontmatter parser is
    line-scalar so a per-field PATCH section call would not target a
    frontmatter key — always GET-merge-PUT for frontmatter edits.)
-2. If `linked.routine` is set: GET `routines/custom/<slug>`, flip
+2. If `linked.routine` is set: GET `policies/routines/custom/<slug>`, flip
    frontmatter `enabled: false`, PUT back. The reload hook flips the
    cron job off automatically.
 
@@ -173,7 +173,7 @@ Same fan-out, with `status: active` and `enabled: true`.
 1. GET the policy file, flip frontmatter `status: removed` and
    `updated: <today>`, PUT back.
 2. If `linked.routine` is set: `DELETE
-   /api/context/routines/custom/<slug>` (whitelisted).
+   /api/context/policies/routines/custom/<slug>` (whitelisted).
 
 The reconciler moves the row from `## Active` to `## Removed`
 automatically — the `removedAt` cell is read from the policy file's
@@ -185,10 +185,10 @@ is intentionally not whitelisted (see MANAGEMENT-POLICY-CAPTURE-PLAN
 
 ## What this skill does NOT do
 
-- Does NOT touch `rules/management.md` body sections (Source of Truth
+- Does NOT touch `policies/management.md` body sections (Source of Truth
   table, Notification Rules, Schedule, etc.). Those are wizard-only.
 - Does NOT create rows in the `recurring_schedules` DB table — defer to
-  `routines/custom/` for cron, which gives the user a visible MD file
+  `policies/routines/custom/` for cron, which gives the user a visible MD file
   to edit.
 - Does NOT migrate existing custom routines into policy files
   retroactively. Migration is a separate one-time operation.
@@ -197,11 +197,12 @@ is intentionally not whitelisted (see MANAGEMENT-POLICY-CAPTURE-PLAN
 
 - **Need a one-off wake-up?** Use `schedule` (`/api/schedule` or
   `/api/schedule/dm`) — no policy file needed.
-- **Need a recurring DB-driven task with no recorded `## Why`?** Use
-  `schedule`'s `/api/recurring-schedules` — supports hourly / daily /
-  weekly / monthly cadences. Default to `tier:"medium"`; pin a
-  specific model id (`claude-opus-4-7`, `gpt-5.4`, …) only when the
-  rule needs to outlive a `/settings/models` re-route.
+- **Need a recurring task with no recorded `## Why`?** Recurring autonomous
+  **work** → create an Agent via the `agent-create` skill (`POST /api/agents`);
+  recurring scheduled **DM / briefing** → `schedule`'s
+  `/api/recurring-schedules` with `taskType: "dm_session"`. Default to
+  `tier:"medium"`; pin a specific model id only when the rule needs to
+  outlive a `/settings/models` re-route.
 - **Tone / voice / language preference?** Belongs in `user-profile`
   (which routes to `PATCH /api/config/character`), NOT a policy file.
   Full recipe in `user-profile/references/character-preferences.md`.
@@ -212,17 +213,17 @@ All writes go through `/api/context/*` — see the **context** skill's
 `references/api.md` for verb / mode / error envelope details. This
 skill targets these paths:
 
-- `GET /api/context/rules/policies/_index` (Step 1 summary)
-- `GET /api/context/list/rules` (Step 1 authoritative — entries prefixed `policies/`)
-- `GET /api/context/rules/policies/<slug>` (read before pause / resume / remove)
-- `PUT /api/context/dossiers/<topic>` (Step 5.1 — if new)
-- `PUT /api/context/routines/custom/<slug>` (Step 5.2 — if scheduling)
-- `PUT /api/context/rules/policies/<slug>` (Step 5.3)
-- `PATCH /api/context/rules/policies/<slug>` (pause / resume / remove; frontmatter via GET-merge-PUT only — line-scalar parser)
-- `DELETE /api/context/routines/custom/<slug>` (remove only)
-
-`rules/policies/_index.md` and the `## Active Policies` section in
-`rules/management.md` are written by the daemon's policy-index
+- `GET /api/context/policies/management-captures/_index` (Step 1 summary)
+- `GET /api/context/list/policies` (Step 1 authoritative — entries prefixed `management-captures/`)
+- `GET /api/context/policies/management-captures/<slug>` (read before pause / resume / remove)
+- `PUT /api/context/knowledge/dossiers/<topic>` (Step 5.1 — if new)
+- `PUT /api/context/policies/routines/custom/<slug>` (Step 5.2 — if scheduling)
+- `PUT /api/context/policies/management-captures/<slug>` (Step 5.3)
+- `PATCH /api/context/policies/management-captures/<slug>` (pause / resume / remove; frontmatter via GET-merge-PUT only — line-scalar parser)
+- `DELETE /api/context/policies/routines/custom/<slug>` (remove only)
+
+`policies/management-captures/_index.md` and the `## Active Policies` section in
+`policies/management.md` are written by the daemon's policy-index
 reconciler — they are NOT in the agent's write surface for this skill.
 
 Frontmatter validation enforces `kind: policy`, `owner: agent`, and

package/agent-assets/skills/management-policy/curation.json

@@ -7,7 +7,7 @@
       "anchor": "<!-- CURATION:knowledge_layout id=\"policy-file-shape\" -->",
       "human_label": "Policy file section shape",
       "description": "Required sections inside rules/policies/<slug>.md and what each holds",
-      "scope_paths": ["rules/policies/*.md"]
+      "scope_paths": ["policies/management-captures/*.md"]
     }
   ]
 }

package/agent-assets/skills/management-policy/references/policy-workflow.md

@@ -13,7 +13,7 @@ steps `N-1 … 1` in reverse before reporting the failure to the user.
 
 ```bash
 # Optional — only if the policy accumulates data into a new topic.
-curl -sS -X PUT http://localhost:8321/api/context/dossiers/<topic> \
+curl -sS -X PUT http://localhost:8321/api/context/knowledge/dossiers/<topic> \
   -H 'Content-Type: application/json' \
   -d @- <<'JSON'
 {"content":"---\ntype: dossier\nowner: agent\nupdated: 2026-04-24\n---\n# <Topic>\n\n## Daily Log\n"}
@@ -27,7 +27,7 @@ when the rest of the flow rolls back.
 ## 5.2 Create the custom routine (only if scheduling is needed)
 
 ```bash
-curl -sS -X PUT http://localhost:8321/api/context/routines/custom/<slug> \
+curl -sS -X PUT http://localhost:8321/api/context/policies/routines/custom/<slug> \
   -H 'Content-Type: application/json' \
   -d @- <<'JSON'
 {"content":"---\ntype: rule\nslug: <slug>\nprocess_key: routine.custom.<slug>\ncron: \"0 7 * * *\"\nbackend_tier: light\nmax_budget_usd: 0.20\nenabled: true\n---\n# <Title>\n\n## Checks\n\n### <step label>\n**Action**: …\n"}
@@ -52,7 +52,7 @@ line, write a short summary in `origin` and put the verbatim quote in
 a body section called `## Captured From`.
 
 ```bash
-curl -sS -X PUT http://localhost:8321/api/context/rules/policies/<slug> \
+curl -sS -X PUT http://localhost:8321/api/context/policies/management-captures/<slug> \
   -H 'Content-Type: application/json' \
   -d @- <<'JSON'
 {"content":"---\ntype: rule\nkind: policy\nowner: agent\nupdated: 2026-04-24\nslug: <slug>\nstatus: active\ncreated_at: 2026-04-24\ncreated_via: dm\norigin: \"User DM 2026-04-24T14:30Z: <one-line summary or short quote>\"\nlinked:\n  routine: <slug>\n  dossier: <topic>\ntemplate_version: 1\n---\n# <Title>\n\n## Why\n<one short paragraph>\n\n## How\n1. …\n\n## Source of Truth\n- Authoritative: …\n- Local cache: dossiers/<topic>.md\n\n## Captured From\n> <verbatim DM quote, only when too long for the origin line>\n\n## Notes\n- …\n"}
@@ -62,7 +62,7 @@ JSON
 The global FS-watch reconciler picks this up within ~1 s and the
 policy appears in `context-index.md` automatically. The policy-index
 reconciler also fires on the same FS event (chained off the same
-debounce), so `rules/policies/_index.md` and `rules/management.md`'s
+debounce), so `policies/management-captures/_index.md` and `policies/management.md`'s
 `## Active Policies` section refresh within ~10 s — no manual PATCH
 needed.
 
@@ -76,14 +76,14 @@ reconciler can resolve them.
 
 ## 5.4 _(no manual step required)_
 
-`rules/policies/_index.md` is auto-maintained by the daemon's
+`policies/management-captures/_index.md` is auto-maintained by the daemon's
 policy-index reconciler — it re-renders within ~10 s of step 5.3's
 write. Same for the `## Active Policies` section in
-`rules/management.md`. **Do not PATCH or PUT either path manually**;
+`policies/management.md`. **Do not PATCH or PUT either path manually**;
 doing so just races the reconciler and creates snapshot churn.
 
 If you need to confirm the index is up to date before replying to the
-user, GET `rules/policies/_index` after a short wait. The
+user, GET `policies/management-captures/_index` after a short wait. The
 reconciler's last-run record lives at `runtime_state` key
 `reconciler.policy_index.last_run` for diagnostics.
 
@@ -91,8 +91,8 @@ reconciler's last-run record lives at `runtime_state` key
 
 | Failure at | Roll back |
 |---|---|
-| 5.2 | undo 5.1 (`DELETE` the dossier file you just created — only if you created it; do not delete a pre-existing dossier) |
-| 5.3 | undo 5.2 (PUT routines file back to `enabled: false` and the next reconcile clears the cron job; or `DELETE` if you created it new), then undo 5.1 as above |
+| 5.2 | undo 5.1 — the dossier path does **not** accept `DELETE` (`knowledge/dossiers/*` is PUT/PATCH only; a `DELETE` returns `403 context.write_forbidden`). If you created it new, PUT it to empty content / `status: removed`; an empty dossier is harmless (per 5.1). Leave a pre-existing dossier untouched. |
+| 5.3 | undo 5.2 (PUT routines file back to `enabled: false` and the next reconcile clears the cron job; or `DELETE` if you created it new — `policies/routines/custom/*` is DELETE-whitelisted), then undo 5.1 as above |
 | 5.4 | none required — there is no manual 5.4. If the reconciler does not pick the change up within ~30 s, surface the diagnostics record (`runtime_state` key above) to the user rather than rolling back. |
 
 If any rollback step itself fails, **report the partial state to the

package/agent-assets/skills/management-policy/seeds/policy-file-shape.seed.json

@@ -2,7 +2,7 @@
   "kind": "knowledge_layout",
   "files": [
     {
-      "path": "rules/policies/*.md",
+      "path": "policies/management-captures/*.md",
       "purpose": "Durable management policy capturing why a recurring rule exists, how it runs, and where data lands",
       "sections": [
         { "heading": "## Why", "contains": "one short paragraph stating the motivation behind the policy" },

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

@@ -48,7 +48,7 @@ these in any language also fail the positive rule.
 
 ### No internal mechanism names
 
-Never mention `today.md`, `user/profile.md`, `roadmap.md`, `## Agent
+Never mention `state/today.md`, `identity/profile.md`, `plans/roadmap.md`, `## Agent
 Plan`, `## Agent Log`, `## Handoff`, `did-not-fire`, "Morning
 Routine", "Evening Review", "scheduled.task", "scheduled.dm",
 "dm_session", "sub_flow", or any other internal mechanism in
@@ -71,7 +71,7 @@ rule above bars *introducing* such enumeration in any other surface.)
 ### Language and style
 
 Output language: follow `<output_language_policy>`. Tone: follow
-`user/profile.md` Communication Style and the Character block in your
+`identity/profile.md` Communication Style and the Character block in your
 system prompt. Keep technical terms in original form.
 
 ### Compactness
@@ -91,13 +91,13 @@ Notify when **all three** are true: (1) **actionable** or requires awareness, (2
   `[cal] ... — reminder sent` referencing the same item within the
   last 4 hours. If the injected log is truncated (`[...N earlier
   entries omitted ...]` marker) and you can't rule out a prior
-  notification, `GET /api/context/today` for the full log before
+  notification, `GET /api/context/state/today` for the full log before
   firing. Duplicate notifications are the #1 cause of noise.
 - **A pending Agent Plan row / scheduled DM is already set to fire
   for this item within the next 2 hours** — let the planned channel
   deliver; don't pre-empt it.
 - **Quiet hours (default 22:00-08:00, configurable)** unless `critical` — schedule for after instead
-- **Rate-limited (429)** — do NOT retry; log skip to Agent Log. If time-critical, upgrade priority at next opportunity
+- **Over the rate-limit caps (3/hour, 12/day; `critical` bypasses both)** — do NOT spam-retry. The endpoint does NOT signal this: `/api/notify` returns `200 {status:"sent"}` even when quiet-hours or the rate-limit silently drops the message, so a `"sent"` response is not proof of delivery. Self-throttle by checking `<today>` `## Agent Log` before firing; if you suspect suppression, log the skip rather than re-posting. If time-critical, upgrade priority at next opportunity
 - **Routine file changes** or **agent internal state** — use Agent Log instead
 - **When in doubt — prefer silence**
 

package/agent-assets/skills/notify/references/priority.md

@@ -54,7 +54,12 @@ The agent CANNOT query `notification_log` directly (Approve-tier). Use
 `<today>` `## Agent Log` as the authoritative dedup source (look for
 `notify sent` / `DM sent` lines).
 
-A 429 response is final for this attempt — do NOT retry. Log `notify
-skipped (rate_limited)` to Agent Log. If the message is time-critical
-and the next opportunity arises, upgrade to `high` (or `critical` if
-the situation has escalated) rather than re-sending at the same level.
+`/api/notify` does NOT report rate-limit or quiet-hours suppression
+back to you — it returns `200 {status:"sent"}` even when the message is
+silently dropped inside the delivery layer. A `"sent"` response is
+therefore not proof the user saw it. Do NOT re-post the same item
+hoping for delivery; self-throttle by scanning `<today>` `## Agent Log`
+first and log `notify skipped (rate_limited)` when you choose to hold.
+If the message is time-critical and the next opportunity arises,
+upgrade to `high` (or `critical` if the situation has escalated)
+rather than re-sending at the same level.

package/agent-assets/skills/notion/SKILL.delegated.claude.md

@@ -53,7 +53,7 @@ The daemon:
    tool against the per-task allowed-tools envelope, validates the
    final JSON against your `outputSchema`, returns it.
 
-`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.
 

package/agent-assets/skills/notion/SKILL.delegated.codex.md

@@ -48,7 +48,7 @@ The daemon:
    tool against the per-task allowed-tools envelope, validates the
    final JSON against your `outputSchema`, returns it.
 
-`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.
 

package/agent-assets/skills/notion/SKILL.delegated.gemini.md

@@ -48,7 +48,7 @@ The daemon:
    tool against the per-task allowed-tools envelope, validates the
    final JSON against your `outputSchema`, returns it.
 
-`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.
 

package/agent-assets/skills/notion/SKILL.native.claude.md

@@ -11,12 +11,16 @@ allowed-tools:
 > **Refusal directive — read first.** Notion is in `native` mode bound
 > to Claude. Do **NOT** call any of:
 >
-> - `POST /api/integrations/notion/exec` (returns `410` with
->   `X-Integration-Mode: native`)
-> - `POST /api/integrations/notion/reconcile` (410)
-> - `/api/notion/query`, `/api/notion/search`, `/api/notion/pages`,
->   `/api/notion/pages/<id>/content` (each route-prefix 410 in native
+> - `POST /api/integrations/notion/exec` (returns `409 mode_mismatch`
+>   in native mode — this route is NOT route-gated and carries no
+>   `X-Integration-Mode` header; `/exec` only succeeds in `delegated`
 >   mode)
+> - `POST /api/integrations/notion/reconcile` (not route-gated either;
+>   an LLM-issued notion reconcile returns `400 validation_error` on the
+>   window-key allowlist, which is calendar-only)
+> - `/api/notion/query`, `/api/notion/search`, `/api/notion/pages`,
+>   `/api/notion/pages/<id>/content` (each route-prefix returns `410`
+>   with `X-Integration-Mode: native` — these ARE route-gated)
 >
 > Reach Notion through the in-session Notion connector your harness
 > exposes. Your tool menu lists every available tool at session start
@@ -150,7 +154,7 @@ instead).
 When `routine.hourly_check.native.claude.md`'s Step 0c fetches recent
 Notion edits, POST each materialised page to `/api/observations`. The
 daemon computes `contentHash` server-side via
-`@personal-agent/shared/observations-hash.ts`; pass `payload` verbatim.
+`@aitne/shared/observations-hash.ts`; pass `payload` verbatim.
 
 **Batch when you have more than one page.** Use
 `POST /api/observations/batch` with up to 200 items in one

package/agent-assets/skills/notion/SKILL.native.codex.md

@@ -11,11 +11,16 @@ allowed-tools:
 > **Refusal directive — read first.** Notion is in `native` mode bound
 > to Codex. Do **NOT** call any of:
 >
-> - `POST /api/integrations/notion/exec` (returns `410` with
->   `X-Integration-Mode: native`)
-> - `POST /api/integrations/notion/reconcile` (410)
+> - `POST /api/integrations/notion/exec` (returns `409 mode_mismatch`
+>   in native mode — this route is NOT route-gated and carries no
+>   `X-Integration-Mode` header; `/exec` only succeeds in `delegated`
+>   mode)
+> - `POST /api/integrations/notion/reconcile` (not route-gated either;
+>   an LLM-issued notion reconcile returns `400 validation_error` on the
+>   window-key allowlist, which is calendar-only)
 > - `/api/notion/query`, `/api/notion/search`, `/api/notion/pages`,
->   `/api/notion/pages/<id>/content` (each route-prefix 410)
+>   `/api/notion/pages/<id>/content` (each route-prefix returns `410`
+>   with `X-Integration-Mode: native` — these ARE route-gated)
 >
 > Reach Notion through the in-session Notion connector your harness
 > exposes. Your tool menu lists every available tool at session start

package/agent-assets/skills/notion/SKILL.native.gemini.md

@@ -11,11 +11,16 @@ allowed-tools:
 > **Refusal directive — read first.** Notion is in `native` mode bound
 > to Gemini. Do **NOT** call any of:
 >
-> - `POST /api/integrations/notion/exec` (returns `410` with
->   `X-Integration-Mode: native`)
-> - `POST /api/integrations/notion/reconcile` (410)
+> - `POST /api/integrations/notion/exec` (returns `409 mode_mismatch`
+>   in native mode — this route is NOT route-gated and carries no
+>   `X-Integration-Mode` header; `/exec` only succeeds in `delegated`
+>   mode)
+> - `POST /api/integrations/notion/reconcile` (not route-gated either;
+>   an LLM-issued notion reconcile returns `400 validation_error` on the
+>   window-key allowlist, which is calendar-only)
 > - `/api/notion/query`, `/api/notion/search`, `/api/notion/pages`,
->   `/api/notion/pages/<id>/content` (each route-prefix 410)
+>   `/api/notion/pages/<id>/content` (each route-prefix returns `410`
+>   with `X-Integration-Mode: native` — these ARE route-gated)
 >
 > Reach Notion through the in-session Notion connector your harness
 > exposes (typically a user-installed Notion MCP server registered

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

@@ -17,8 +17,8 @@ Output language: write-ups inherit the destination file's policy via the `today`
 2. Group related observations before acting.
 3. For each group, apply the **fetch decision** (below) — `summary_text` + `novelty_score` are pre-computed by the daemon's per-observation summarizer; only `novelty_score >= 2` warrants full content fetch.
 4. Decide actionability:
-   - Update `today.md` for TODOs, blockers, decisions, or deadlines
-   - Update `roadmap.md` or `projects/*.md` only for material project-state changes
+   - Update `state/today.md` for TODOs, blockers, decisions, or deadlines
+   - Update `plans/roadmap.md` or `projects/*.md` only for material project-state changes
    - Schedule a wake-up if the observation implies a future reminder
 5. Apply the smallest meaningful set of context updates.
 6. Mark processed observations consumed via the bulk endpoint
@@ -138,6 +138,16 @@ that caps each curl invocation at one HTTP request and strips heredoc
 bodies before URL validation. The batch endpoint resolves the
 cardinality mismatch without weakening either hook.
 
+> **If `mcp__aitne-observations__submit_observations` is in your allowed
+> tools (the `routine.fetch_window` pre-pass on Claude), submit the batch
+> through that MCP tool instead of the curl below.** The structured
+> transport never goes through the SDK bash preflight, so Unicode-bearing
+> payloads (NBSP/ZWS in subjects, U+3000 in titles) can't trip its
+> `too-complex` gate and cascade to a denied curl / wasted retry /
+> `budget-cap`. The tool input is the same `{"observations":[…]}` envelope
+> and the response is identical. The curl form below is the fallback for
+> sessions without the MCP tool (the hourly check, Codex/Gemini).
+
 ```bash
 curl -s -X POST http://localhost:8321/api/observations/batch \
   -H 'Content-Type: application/json' \
@@ -190,8 +200,8 @@ Hard limits:
 ### POST /api/observations/consume
 
 Marks one or more observations consumed. **Bulk-only** — there is no
-per-id endpoint (`POST /api/observations/<id>/consume` returns 404).
-Always use this shape, even for a single id.
+per-id endpoint (`POST /api/observations/<id>/consume` returns 405
+`use_bulk_endpoint`). Always use this shape, even for a single id.
 
 Copy the `correlationId` value verbatim from the
 `<event_correlation_id>…</event_correlation_id>` tag in your turn
@@ -230,7 +240,9 @@ you to.**
 
 ### GET /api/observations/stats
 
-`curl -s http://localhost:8321/api/observations/stats` → `{ "total", "pending", "bySource": {...}, "byActor": {...} }`
+`curl -s http://localhost:8321/api/observations/stats` → `{ "totalPending", "oldestPendingObservedAt", "bySource": [{ "source", "pendingCount", "oldestObservedAt" }], "summaryStatusCounts": {...}, "noveltyDistribution": [...] }`
+
+`totalPending` is the single count of unconsumed observations (no separate `total` / `pending` keys). `bySource` is an **array** of per-source rows, not a map. There is no `byActor`. `summaryStatusCounts` / `noveltyDistribution` are summarizer-health telemetry.
 
 ---
 
@@ -267,7 +279,10 @@ current state.
 
 <!-- mode:direct:notion -->
 ```bash
-curl -s "http://localhost:8321/api/notion/query?databaseId=xxx"
+# ?database= takes a database LABEL (default "tasks"), not a UUID.
+# An unrecognized label returns 404 notion.database_not_found with the
+# list of valid labels; an absent param silently uses "tasks".
+curl -s "http://localhost:8321/api/notion/query?database=tasks"
 ```
 <!-- /mode:direct:notion -->
 <!-- mode:delegated-same:notion -->
@@ -331,8 +346,9 @@ names and the canonical search / fetch call shapes. Resolve
 `<databaseId>` first via the un-gated config dump
 (`curl -s http://localhost:8321/api/notion/databases`) and pass the
 UUID to the connector's data-source / search tool. Do NOT call
-`/api/notion/*` (410) or `/api/integrations/notion/exec` (also 410
-in native mode).
+`/api/notion/*` (410) or `/api/integrations/notion/exec` (returns 409
+`mode_mismatch` in native mode — the `/exec` path is not route-gated,
+so it is the handler, not the 410 gate, that rejects it).
 <!-- /mode:native:notion -->
 <!-- mode:disabled:notion -->
 Notion is disabled — there is no live source. Treat the observation

package/agent-assets/skills/project-doc/SKILL.md

@@ -28,7 +28,7 @@ carries (project keeps `## Lifecycle Phases`, repo-only stays light).
 ## Hard rules
 
 - Write only through `/api/context/*`. Never edit files directly on disk.
-- Do not modify `today.md`, `roadmap.md`, `user/*`, `rules/*`, or
+- Do not modify `state/today.md`, `plans/roadmap.md`, `user/*`, `rules/*`, or
   unrelated context files.
 - Preserve valid frontmatter. The overview file uses `type: git-project`,
   the journal file uses `type: git-journal`. Both carry an ISO `updated`

package/agent-assets/skills/project-doc/curation.json

@@ -6,8 +6,8 @@
       "kind": "knowledge_layout",
       "anchor": "<!-- CURATION:knowledge_layout id=\"project-shape\" -->",
       "human_label": "Project / git-repo file shape",
-      "description": "Required sections in projects/*.md and git-repos/*.md, and what each section holds",
-      "scope_paths": ["projects/*.md", "git-repos/*.md"]
+      "description": "Required sections in git/<slug>/overview.md (git-managed repos) and projects/*.md (non-git manual projects), and what each section holds",
+      "scope_paths": ["projects/*.md", "git/*/overview.md"]
     },
     {
       "id": "slug-grammar",
@@ -15,7 +15,7 @@
       "anchor": "<!-- CURATION:convention_notes id=\"slug-grammar\" -->",
       "human_label": "Project slug grammar",
       "description": "Slug format, length cap, reserved stems",
-      "scope_paths": ["projects/*.md", "git-repos/*.md"]
+      "scope_paths": ["projects/*.md", "git/*/overview.md"]
     }
   ]
 }

package/agent-assets/skills/project-doc/seeds/project-shape.seed.json

@@ -14,11 +14,14 @@
       ]
     },
     {
-      "path": "git-repos/*.md",
-      "purpose": "Per-repository context for non-project watched repositories",
+      "path": "git/*/overview.md",
+      "purpose": "Per-repository overview for every git-managed repo (replaces the retired git-repos/*.md layout)",
       "sections": [
-        { "heading": "## Activity", "contains": "summarised recent activity for the watched repo" },
-        { "heading": "## Recent Pushes", "contains": "list of push events with dates and short summaries" }
+        { "heading": "## Summary", "contains": "one-paragraph description of the repo and its current state" },
+        { "heading": "## Architecture", "contains": "structural notes on the repo's layout and components" },
+        { "heading": "## Notable Changes", "contains": "human-readable notes on important commits or decisions" },
+        { "heading": "## Open Threads", "contains": "manual prose; follow-ups and pending questions, preserved verbatim" },
+        { "heading": "## Daily Activity Log", "contains": "rolling 30-day window of summarised activity" }
       ]
     }
   ]

package/agent-assets/skills/project-doc/seeds/slug-grammar.seed.json

@@ -4,17 +4,17 @@
     {
       "topic": "Slug format",
       "rule": "Project and repo slugs are kebab-case, lowercase letters with hyphens between words.",
-      "example": "projects/cost-explorer.md, git-repos/personal-agent.md"
+      "example": "plans/projects/cost-explorer.md, git/personal-agent/overview.md"
     },
     {
       "topic": "Slug length",
       "rule": "Slugs are 32 characters or fewer, including the hyphens but excluding the .md suffix.",
-      "example": "projects/personal-agent-skills.md is at the upper bound"
+      "example": "plans/projects/personal-agent-skills.md is at the upper bound"
     },
     {
       "topic": "Reserved stems",
       "rule": "Stems _index and _archive are reserved for daemon-maintained files and not in use as project slugs.",
-      "example": "projects/_index.md is a directory listing, not a project file"
+      "example": "plans/projects/_index.md is a directory listing, not a project file"
     }
   ]
 }

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

@@ -156,9 +156,19 @@ Response:
 
 Update book status, rating, or notes.
 
+**Approve tier (Bearer required).** This is an operator/dashboard-gated
+write — an autonomous agent curl from a session workdir carries no
+`Authorization: Bearer` header and will be rejected with **401** before
+the handler runs. Do NOT call this autonomously and do NOT assume the
+update landed; book status/rating/notes corrections are made by the user
+via the dashboard. (Body shape, for reference: `status` enum
+`reading|completed|abandoned`, `rating` 1-5, `notes`.)
+
 ```bash
+# Operator/dashboard-only — requires Authorization: Bearer (Approve tier).
 curl -s -X PATCH "http://localhost:8321/api/books/1" \
   -H "Content-Type: application/json" \
+  -H "Authorization: Bearer <operator-token>" \
   -d '{"status": "completed", "rating": 4}'
 ```
 

package/agent-assets/skills/reading/references/reading-taste.md

@@ -146,12 +146,12 @@ the sweep to write the refreshed metadata and YAML `updated` date.
 
 ### First-write registration (_index.md)
 
-The `user/_index.md` file indexes available topic files. When
+The `identity/_index.md` file indexes available topic files. When
 creating `reading-taste.md` for the first time (GET returned 404),
 append a one-line entry to the index so other flows can discover it:
 
 ```bash
-curl -s -X PATCH http://localhost:8321/api/context/user/_index \
+curl -s -X PATCH http://localhost:8321/api/context/identity/_index \
   -H 'Content-Type: application/json' \
   -d '{"section": "topics", "mode": "append", "content": "- reading-taste — derived taste profile + rolling book candidates (updated weekly)"}'
 ```

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

@@ -10,11 +10,11 @@ allowed-tools:
 
 Output language: roadmap.md is Policy B — see `<output_language_policy>`. Section headers stay English skeleton; items, narrative, and preparation-timeline prose are in `<settings primary_language>`. Preserve user-customized headers verbatim.
 
-`roadmap.md` is the single source of truth for **long-horizon user
-intent** — everything that does not belong in `today.md`. It aggregates
+`plans/roadmap.md` is the single source of truth for **long-horizon user
+intent** — everything that does not belong in `state/today.md`. It aggregates
 Calendar events, pending `agent_schedule` rows, DM-captured intent,
 mail-derived bookings, reading goals, and observations; Morning Routine
-consumes it to shape `today.md`.
+consumes it to shape `state/today.md`.
 
 ## Section schema
 
@@ -117,9 +117,9 @@ must carry a daemon-minted HTML comment ID:
 - The `YYYYMMDD` segment is the entry creation date / Source date, not
   the event date. Keep it stable when dates are refined.
 - Do not invent IDs in prose. Before adding a new roadmap entry, call
-  `POST /api/context/roadmap/id`:
+  `POST /api/context/plans/roadmap/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' \
     -d '{"creationDate": "YYYY-MM-DD"}'
   ```

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

@@ -7,7 +7,7 @@
       "anchor": "<!-- CURATION:knowledge_layout id=\"entry-types\" -->",
       "human_label": "Roadmap section schema",
       "description": "Required sections in roadmap.md and what each holds",
-      "scope_paths": ["roadmap.md"]
+      "scope_paths": ["plans/roadmap.md"]
     }
   ]
 }