@aitne-sh/aitne 0.1.8 → 0.1.9

package/agent-assets/skills/user-interview/SKILL.md

@@ -16,12 +16,12 @@ morning briefing). This skill is how every callsite touches that queue.
 
 ## Source-of-truth file
 
-**`agent/profile-questions.md`** — agent-internal markdown. Three
+**`state/profile-questions.md`** — agent-internal markdown. Three
 top-level sections: `## Pending`, `## In Progress`, `## Answered`.
 Never auto-injected into prompts; load only when this skill is in use.
 
 ```bash
-curl -s http://localhost:8321/api/context/agent/profile-questions
+curl -s http://localhost:8321/api/context/state/profile-questions
 ```
 
 ### Pending row format
@@ -34,7 +34,7 @@ curl -s http://localhost:8321/api/context/agent/profile-questions
 |---|---|
 | `PRIO`        | `HIGH` / `MID` / `LOW` — selection priority |
 | `<id>`        | snake_case unique. Doubles as the correlation id in any scheduled DM description (`profile_interview:<id> — <hint>`) |
-| `target_path` | which user file the answer should land in, e.g. `user/profile.md` |
+| `target_path` | which user file the answer should land in, e.g. `identity/profile.md` |
 | `## Section`  | optional — narrows to a section within the target file |
 | `match=<anchor>` | optional — bullet key (English, like `Name`, `Timezone`, `Sleep`, `Working hours`). Required when multiple rows share a section, or when setup pre-seeds the section with an unrelated bullet |
 | `ask-hint`    | English brief of WHAT to ask (agent-internal, Policy A). Render the actual DM per `<output_language_policy>` — this skill intentionally splits the two surfaces |
@@ -150,11 +150,11 @@ composing the reply.
      b. After the reply is ready (final assistant text already includes
         the question), issue **two PATCH replaces** (separate calls —
         they target different files):
-        - `PATCH /api/context/agent/profile-questions` section=in_progress
+        - `PATCH /api/context/state/profile-questions` section=in_progress
           — flip the entry to
           `state=asked :: since=<unchanged> :: asked_at=<current_time>`
           (preserve the original `since=` date).
-        - `PATCH /api/context/today` section=agent_notes — replace the
+        - `PATCH /api/context/state/today` section=agent_notes — replace the
           parenthetical from `(latent)` to `(asked HH:MM)` and append
           `(asked HH:MM)` to the same line; preserve every other Agent
           Notes line byte-for-byte.
@@ -231,7 +231,7 @@ The heuristic anchor lookup matches against bullet keys written by the
 - Sleep: 23:00–07:00
 ```
 
-Anchors in `agent/profile-questions.md` MUST match these English keys —
+Anchors in `state/profile-questions.md` MUST match these English keys —
 not the user's primary-language phrasing. If a future `user-profile`
 schema change introduces non-English keys, Layers 1–3 silently miss
 those bullets and the system degrades to Layer-4-only protection
@@ -255,20 +255,23 @@ those bullets and the system degrades to Layer-4-only protection
 
 ```bash
 # Read the queue
-curl -s http://localhost:8321/api/context/agent/profile-questions
+curl -s http://localhost:8321/api/context/state/profile-questions
 
 # Slot-filled probe
 curl -s "http://localhost:8321/api/profile-questions/slot-filled?path=user/profile.md&section=Identity&anchor=Name"
 
 # Section-level edit (queue file uses the standard context API)
-curl -s -X PATCH http://localhost:8321/api/context/agent/profile-questions \
+curl -s -X PATCH http://localhost:8321/api/context/state/profile-questions \
   -H 'Content-Type: application/json' \
   -d '{"section": "in_progress", "mode": "replace", "content": "- name :: state=latent"}'
 
 # Fallback DM scheduling (Operation 5B only)
+# `prompt` is REQUIRED (the wake-up session has NO memory — it is the only
+# instruction). `description` stays as the short label whose
+# `profile_interview:<id>` prefix triggers the Operation 6 sub-flow.
 curl -s -X POST http://localhost:8321/api/schedule \
   -H 'Content-Type: application/json' \
-  -d '{"time":"<ISO>","taskType":"dm_session","description":"profile_interview:<id> — <hint>","tier":"medium","taskContext":{"scheduledBy":"user_profile_sweep_fallback","queueId":"<id>","importance":"low"}}'
+  -d '{"time":"<ISO>","taskType":"dm_session","prompt":"profile_interview:<id> — run the scheduled.dm ## Profile interview sub-flow (Operation 6): fire-time slot-filled abort check, then compose one short natural DM around <hint>.","description":"profile_interview:<id> — <hint>","tier":"medium","taskContext":{"scheduledBy":"user_profile_sweep_fallback","queueId":"<id>","importance":"low"}}'
 ```
 
 The PATCH `section` argument is snake_case of the heading: `pending`,

package/agent-assets/skills/user-interview/references/op-briefing.md

@@ -28,11 +28,11 @@ slip in a question without surfacing a cold standalone DM.
    closing side note. Same naturalness rules as Operation 2 — no
    preamble, no separate paragraph.
 4. After composing, issue two PATCH replaces (separate calls):
-   - `PATCH /api/context/agent/profile-questions` section=in_progress —
+   - `PATCH /api/context/state/profile-questions` section=in_progress —
      flip the entry to
      `state=asked :: since=<unchanged> :: asked_at=<current_time>`
      (preserve the original `since=` date).
-   - `PATCH /api/context/today` section=agent_notes — flip the
+   - `PATCH /api/context/state/today` section=agent_notes — flip the
      matching `Profile question (latent):` line by changing the
      parenthetical to `(asked HH:MM)`.
 ```

package/agent-assets/skills/user-interview/references/sweep-and-fallback.md

@@ -30,10 +30,18 @@ B. LATENT FALLBACK PROMOTION.
        state=scheduled. Register POST /api/schedule with:
          {time: tomorrow @ 14:00 local (or quiet_hours_end + 2h),
           taskType: "dm_session",
+          prompt: "profile_interview:<id> — run Operation 6 (the
+                   scheduled.dm ## Profile interview sub-flow): fire-time
+                   slot-filled abort check, then compose one short natural
+                   DM around <ask-hint>.",
           description: "profile_interview:<id> — <ask-hint>",
           tier: "medium",
           taskContext: {scheduledBy: "user_profile_sweep_fallback",
                         queueId: "<id>", importance: "low"}}
+       NOTE: `prompt` is REQUIRED by POST /api/schedule (the wake-up
+       session has NO memory — the prompt is its only instruction).
+       `description` is the short list label whose `profile_interview:<id>`
+       prefix triggers Operation 6; keep both fields.
        Update the In Progress entry to
        `state=scheduled :: since=<unchanged> :: scheduled_at=<tomorrow 14:00>`.
        Remove the matching `Profile question (latent): <id>` line from

package/agent-assets/skills/user-profile/SKILL.md

@@ -8,21 +8,21 @@ allowed-tools:
 
 # User Profile Update Guide
 
-Output language: `user/profile.md` and `user/*.md` are Policy B — see `<output_language_policy>`. Template H2 headers stay English skeleton; the facts under them are in `<settings primary_language>`. Preserve user-customized headers verbatim.
+Output language: `identity/profile.md` and `user/*.md` are Policy B — see `<output_language_policy>`. Template H2 headers stay English skeleton; the facts under them are in `<settings primary_language>`. Preserve user-customized headers verbatim.
 
-`user/profile.md` stores the user's identity, preferences, and learned behavioral patterns. It is injected into every agent session via `<user>` tags — keep it concise (target: under ~600 tokens total).
+`identity/profile.md` stores the user's identity, preferences, and learned behavioral patterns. It is injected into every agent session via `<user>` tags — keep it concise (target: under ~600 tokens total).
 
-Detailed, dictionary-like background belongs under `user/*.md`. Read `user/_index.md` first, then fetch only the topic file you need.
+Detailed, dictionary-like background belongs under `user/*.md`. Read `identity/_index.md` first, then fetch only the topic file you need.
 
 ## When to Update
 
 **Immediately (same turn) when the user shares:**
 - Identity or role — "I'm a …", "I work at …", "my title is …" → `profile.md ## Identity`
-- People they know — names + relationship, e.g. "my sister", "my manager Sarah" → `user/people.md`
-- Workplace specifics — company, team, tech stack, tools — "I use Postgres at work" → `user/work.md`
-- Expertise or tools they use habitually — "I've been writing Go for ten years", "I'm new to React" → `user/expertise.md` (add a one-line summary in `profile.md ## Expertise` when the fact also shapes how the agent should explain things)
-- Hobbies, habits, health, lifestyle (factual) — "I run every morning", "I don't eat meat" → `user/personal.md`
-- Goals or learning targets — "I want to get better at Rust", "I want to read 20 books this year" → `user/goals.md`
+- People they know — names + relationship, e.g. "my sister", "my manager Sarah" → `identity/people.md`
+- Workplace specifics — company, team, tech stack, tools — "I use Postgres at work" → `identity/work.md`
+- Expertise or tools they use habitually — "I've been writing Go for ten years", "I'm new to React" → `identity/expertise.md` (add a one-line summary in `profile.md ## Expertise` when the fact also shapes how the agent should explain things)
+- Hobbies, habits, health, lifestyle (factual) — "I run every morning", "I don't eat meat" → `identity/personal.md`
+- Goals or learning targets — "I want to get better at Rust", "I want to read 20 books this year" → `identity/goals.md`
 - A notification or day-type preference — "no work notifications on weekends" → `profile.md ## Notification Preferences`
 - A self-reported behavioral pattern the agent should adapt to — "I'm not a morning person", "I tend to skim long messages" → `profile.md ## Learned Context` with today's `[YYYY-MM-DD]` prefix
 
@@ -35,7 +35,7 @@ Detailed, dictionary-like background belongs under `user/*.md`. Read `user/_inde
 **Routing edge cases** (for shapes the trigger list above doesn't disambiguate):
 - "my name is Alex" — explicit identity statement goes to `profile.md ## Identity`, not a topic file.
 - "user has been unusually curt over the last week" — a pattern inferred across multiple turns with no single user statement. Written to `profile.md ## Learned Context` by Evening Review Step 3a only; the DM handler and sweep do not write inferred patterns.
-- "my sister just had a baby" → `user/people.md ## Family`. If the section doesn't exist yet (fresh topic file with only the H1), the PATCH returns `section_not_found` — retry with `mode: "append_to_file"` and include `"\n## Family\n- <bullet>"` in `content`. The next write to that section succeeds normally.
+- "my sister just had a baby" → `identity/people.md ## Family`. If the section doesn't exist yet (fresh topic file with only the H1), the PATCH returns `section_not_found` — retry with `mode: "append_to_file"` and include `"\n## Family\n- <bullet>"` in `content`. The next write to that section succeeds normally.
 
 The decision rule (profile.md vs `user/<topic>.md` tie-breakers, `section_not_found` → `append_to_file` first-write fallback, and the read-before-write `curl` recipe) is documented in full in this skill — see §"Section ownership", §"File schema", and §"Worked example" below.
 
@@ -78,7 +78,7 @@ full-file PUT, update `updated` to today's date.
 - Working hours: Weekdays 09:00–18:00
 ```
 
-The `user-interview` skill's queue (`agent/profile-questions.md`)
+The `user-interview` skill's queue (`state/profile-questions.md`)
 matches against these English keys. If you introduce a non-English
 label here, the queue's slot-filled probe silently misses the bullet
 and re-asks the same question on the next opportunity. See
@@ -106,7 +106,7 @@ If the user says "I don't want work notifications on weekends", paraphrase into
 preferences are NOT profile content.** Route them to the `character`
 runtime-config field via `PATCH /api/config/character` (narrow
 endpoint, 1000-char cap, read-before-write). Never write tone /
-style preferences into `user/profile.md` or any `user/*.md`.
+style preferences into `identity/profile.md` or any `user/*.md`.
 
 Full recipe — triggers, merge rules, endpoint note, cap-handling, and
 where the value ends up — is in the character-preferences reference
@@ -122,7 +122,7 @@ See _safety.md "Common Patterns" for the general rule. Section name in PATCH is
 
 User: `"I want to read 20 books this year."` → GET user/profile.md (or topic file), merge new bullet into the right section. For a top-level goal summary bullet:
 ```bash
-curl -s -X PATCH http://localhost:8321/api/context/user/profile \
+curl -s -X PATCH http://localhost:8321/api/context/identity/profile \
   -H 'Content-Type: application/json' \
   -d '{"section": "learned_context", "mode": "append", "content": "- [2026-04-23] Reading goal: 20 books/year"}'
 ```
@@ -130,7 +130,7 @@ For a full-section replace, GET first, merge with existing bullets, then PATCH w
 
 **WRONG** (erases existing bullets): `curl -s -X PATCH ... -d '{"section": "learned_context", "mode": "replace", "content": "- [2026-04-23] Reading goal: ..."}'` when the section already held other bullets.
 
-For writes to `user/<topic>.md` (people / work / expertise / personal / goals), the same decision rule applies — §"Routing edge cases" above documents the `section_not_found` → `append_to_file` first-write fallback (with a worked `curl` example against `user/people.md`). The read-before-write rule applies identically when merging into an existing `user/<topic>.md` section.
+For writes to `user/<topic>.md` (people / work / expertise / personal / goals), the same decision rule applies — §"Routing edge cases" above documents the `section_not_found` → `append_to_file` first-write fallback (with a worked `curl` example against `identity/people.md`). The read-before-write rule applies identically when merging into an existing `user/<topic>.md` section.
 
 ## Learned Context entry format
 
@@ -155,9 +155,9 @@ Review can prune entries older than 30 days:
 
 ## Initial Setup
 
-Populate `user/profile.md` (Identity, Work Pattern, Platforms, Expertise summary, Notification Preferences — leave Learned Context/Raw Signals empty). Read skeleton first → prefer `mode: "append"` → `mode: "replace"` only for full merged body. Tone / style preferences do NOT go into profile.md — see §"Tone / character preferences".
+Populate `identity/profile.md` (Identity, Work Pattern, Platforms, Expertise summary, Notification Preferences — leave Learned Context/Raw Signals empty). Read skeleton first → prefer `mode: "append"` → `mode: "replace"` only for full merged body. Tone / style preferences do NOT go into profile.md — see §"Tone / character preferences".
 
-*During setup, seed `user/profile.md` only. The topic files (`user/people.md`, `work.md`, `expertise.md`, `personal.md`, `goals.md`) stay empty and grow from lived conversation via the DM handler and `routine.user_profile_sweep`.*
+*During setup, seed `identity/profile.md` only. The topic files (`identity/people.md`, `work.md`, `expertise.md`, `personal.md`, `goals.md`) stay empty and grow from lived conversation via the DM handler and `routine.user_profile_sweep`.*
 
 ---
 
@@ -165,7 +165,7 @@ Populate `user/profile.md` (Identity, Work Pattern, Platforms, Expertise summary
 
 The generic GET / PATCH surface (modes, fields, error envelopes) is
 documented in the **context** skill `references/api.md`. user-profile
-writes target the two paths `/api/context/user/profile` (the injected
+writes target the two paths `/api/context/identity/profile` (the injected
 summary file) and `/api/context/user/:topic` (one of `people` /
 `work` / `expertise` / `personal` / `goals`).
 
@@ -176,7 +176,7 @@ Two user-profile-specific notes layered on top of the generic surface:
   concurrent appends. Pass a SQLite-format `cutoff`:
 
   ```bash
-  curl -s -X PATCH http://localhost:8321/api/context/user/profile \
+  curl -s -X PATCH http://localhost:8321/api/context/identity/profile \
     -H 'Content-Type: application/json' \
     -d '{"section": "raw_signals", "mode": "clear_before", "cutoff": "2026-04-10 02:33:00"}'
   ```

package/agent-assets/skills/user-profile/curation.json

@@ -7,7 +7,7 @@
       "anchor": "<!-- CURATION:knowledge_layout id=\"topic-files\" -->",
       "human_label": "Topic file layout",
       "description": "Which user/* file owns which kind of fact",
-      "scope_paths": ["user/profile.md", "user/*.md"]
+      "scope_paths": ["identity/profile.md", "user/*.md"]
     },
     {
       "id": "routing-table",
@@ -23,7 +23,7 @@
       "anchor": "<!-- CURATION:convention_notes id=\"learned-context-format\" -->",
       "human_label": "Learned Context bullet conventions",
       "description": "Date-prefix rule, prune cadence, refresh-on-merge",
-      "scope_paths": ["user/profile.md"]
+      "scope_paths": ["identity/profile.md"]
     }
   ]
 }

package/agent-assets/skills/user-profile/references/character-preferences.md

@@ -10,7 +10,7 @@ description: Tone / style / voice / language preferences are agent directives
 are NOT profile content** — they are agent directives, not user facts.
 Route them to the `character` runtime-config field via `PATCH
 /api/config/character` (see `docs/design/15-character.md`), never to
-`user/profile.md` or any `user/*.md`.
+`identity/profile.md` or any `user/*.md`.
 
 ## Triggers
 
@@ -78,6 +78,6 @@ uniformly — no separate injection per backend.
 ## What does NOT belong here
 
 Facts about the user — identity, role, expertise, hobbies, people,
-goals — go to `user/profile.md` or `user/<topic>.md`, not to
+goals — go to `identity/profile.md` or `user/<topic>.md`, not to
 `character`. The split is: `character` says *how* the agent speaks;
 `user/*` says *who the user is*.

package/agent-assets/skills/user-profile/seeds/routing-table.seed.json

@@ -3,49 +3,49 @@
   "rules": [
     {
       "trigger_pattern": "user states identity or role (I'm a, I work at, my title is)",
-      "destination_path": "user/profile.md",
+      "destination_path": "identity/profile.md",
       "destination_section": "## Identity",
       "destination_mode": "replace"
     },
     {
       "trigger_pattern": "user mentions a person they know with a name plus relationship",
-      "destination_path": "user/people.md",
+      "destination_path": "identity/people.md",
       "destination_section": "## Family",
       "destination_mode": "append_to_file"
     },
     {
       "trigger_pattern": "user mentions a workplace specific (company, team, tech stack)",
-      "destination_path": "user/work.md",
+      "destination_path": "identity/work.md",
       "destination_section": "## Stack",
       "destination_mode": "append_to_file"
     },
     {
       "trigger_pattern": "user describes hobbies, habits, health, or lifestyle facts",
-      "destination_path": "user/personal.md",
+      "destination_path": "identity/personal.md",
       "destination_section": "## Habits",
       "destination_mode": "append_to_file"
     },
     {
       "trigger_pattern": "user states a goal or learning target",
-      "destination_path": "user/goals.md",
+      "destination_path": "identity/goals.md",
       "destination_section": "## Learning",
       "destination_mode": "append_to_file"
     },
     {
       "trigger_pattern": "user states expertise level or tools they use habitually",
-      "destination_path": "user/expertise.md",
+      "destination_path": "identity/expertise.md",
       "destination_section": "## Tools",
       "destination_mode": "append_to_file"
     },
     {
       "trigger_pattern": "user states a notification or day-type preference",
-      "destination_path": "user/profile.md",
+      "destination_path": "identity/profile.md",
       "destination_section": "## Notification Preferences",
       "destination_mode": "replace"
     },
     {
       "trigger_pattern": "user reports a behavioral pattern the agent should adapt to",
-      "destination_path": "user/profile.md",
+      "destination_path": "identity/profile.md",
       "destination_section": "## Learned Context",
       "destination_mode": "append"
     }

package/agent-assets/skills/user-profile/seeds/topic-files.seed.json

@@ -2,7 +2,7 @@
   "kind": "knowledge_layout",
   "files": [
     {
-      "path": "user/profile.md",
+      "path": "identity/profile.md",
       "purpose": "identity, preferences, learned context",
       "sections": [
         { "heading": "## Identity", "contains": "name, role, time zone" },
@@ -15,7 +15,7 @@
       ]
     },
     {
-      "path": "user/people.md",
+      "path": "identity/people.md",
       "purpose": "people the user knows",
       "sections": [
         { "heading": "## Family", "contains": "household members" },
@@ -24,28 +24,28 @@
       ]
     },
     {
-      "path": "user/work.md",
+      "path": "identity/work.md",
       "purpose": "workplace, team, tech stack",
       "sections": [
         { "heading": "## Stack", "contains": "tools, languages, services used at work" }
       ]
     },
     {
-      "path": "user/expertise.md",
+      "path": "identity/expertise.md",
       "purpose": "domains, tools, skill levels",
       "sections": [
         { "heading": "## Tools", "contains": "tools the user uses habitually" }
       ]
     },
     {
-      "path": "user/personal.md",
+      "path": "identity/personal.md",
       "purpose": "hobbies, health, habits",
       "sections": [
         { "heading": "## Habits", "contains": "routines, lifestyle, health" }
       ]
     },
     {
-      "path": "user/goals.md",
+      "path": "identity/goals.md",
       "purpose": "developmental goals and learning targets",
       "sections": [
         { "heading": "## Learning", "contains": "skills the user wants to build" }

package/agent-assets/skills/wiki/wiki-compile/SKILL.md

@@ -29,7 +29,7 @@ Therefore:
 | `GET`   | `/api/wiki/{{workspace_name}}/search?q=<query>` | Body-substring search for duplicate detection. |
 | `GET`   | `/api/wiki/{{workspace_name}}/files/<path>` | Read raw notes, existing wiki notes, taxonomy, log. |
 | `POST`  | `/api/wiki/{{workspace_name}}/files/20_wiki/<slug>.md` | Create a new wiki note. |
-| `PATCH` | `/api/wiki/{{workspace_name}}/files/20_wiki/<slug>.md` | Rewrite an existing wiki note (`mode: "replace"`). |
+| `POST`  | `/api/wiki/{{workspace_name}}/files/20_wiki/<slug>.md` | Rewrite an existing wiki note — re-POST to the same path overwrites in place (a `.snapshots/` backup is taken first). |
 | `PATCH` | `/api/wiki/{{workspace_name}}/files/20_wiki/_index.md` | Append a new wiki note's entry (`mode: "append"`). |
 | `PATCH` | `/api/wiki/{{workspace_name}}/files/log.md` | Append the per-run summary (`mode: "append"`). |
 
@@ -52,7 +52,7 @@ Every request must include `-H 'x-process-key: wiki.compile'`. The `wiki-vault-r
    - Use `90_meta/taxonomy.md` for canonical slugs.
    - Preserve source URLs and quoted passages verbatim. Mark conflicts and unknowns explicitly.
    - Each note's frontmatter MUST list every source raw under a `sources:` array and the synthesis date under `compiled_at:`.
-   - Write via `POST` (new slug) or `PATCH mode: "replace"` (existing slug). Read-before-write any slug you `PATCH`-replace so you preserve material that the new raws didn't cover.
+   - Write via `POST` for both new and existing slugs — re-POSTing to an existing `20_wiki/<slug>.md` overwrites it in place (the daemon snapshots the prior version to `.snapshots/` first). Read-before-write any slug you overwrite so you preserve material that the new raws didn't cover. (`PATCH` on `20_wiki/<slug>.md` only supports `mode: "append"` / `"prepend"` — there is no `replace` mode.)
 6. **Append `20_wiki/_index.md`** with one bullet per newly created or modified wiki note (`PATCH mode: "append"`). Skip notes that were unchanged.
 7. **Append `log.md`** with one operational line summarising the run: `[<ISO>] wiki.compile (<mode>): compiled <N> notes from <M> raws — added <A>, updated <B>, unchanged <C>`.
 
@@ -98,7 +98,7 @@ Inside `<<'JSON'` (single-quoted marker) the body is verbatim — only JSON's ow
 - `curl ... -d @/some/path` — `@<filepath>` is blocked by the security hook and the shim. The only acceptable `@…` value is the literal stdin marker `@-`.
 - `curl http://example.com/...` (non-loopback) — only `http://localhost:8321/api/*` is permitted.
 - POST to a non-existent path (`/api/send-message`, `/api/notify-user`, `/api/dm`, etc.) — not daemon routes; calls return 401/404 and DO NOT notify anyone. Your completion DM (final assistant text) is what the daemon forwards.
-- Re-POSTing to `/api/wiki/.../20_wiki/<slug>.md` to update — POST is create-only; the second call returns 409. Use `PATCH mode: "replace"` to overwrite, or pick a different slug.
+- Assuming POST to `/api/wiki/.../20_wiki/<slug>.md` is create-only — it is NOT. Re-POSTing to an existing `20_wiki/<slug>.md` overwrites it in place (with a `.snapshots/` backup first); the `wiki` layer has no create-only guard. The `409 append_only` guard only fires for the `10_raw/` and `log.md` layers. There is no `PATCH mode: "replace"` — PATCH only supports `append` / `prepend`.
 
 ## Common error codes
 
@@ -108,7 +108,7 @@ Inside `<<'JSON'` (single-quoted marker) the body is verbatim — only JSON's ow
 | 400 | `invalid_path` / `invalid_layer` | Slug shape or layer prefix rejected | Path must be exactly `20_wiki/<slug>.md`. Slug matches `^[a-z0-9][a-z0-9-]*$`. |
 | 403 | `missing_process_key` | Header missing | Add `-H 'x-process-key: wiki.compile'`. |
 | 403 | `wiki_write_denied` | Trying to write outside `20_wiki/` (or the `_index.md` / `log.md` exceptions) under `wiki.compile` | Fix the target path. Use `wiki-graduate` for inbox-to-wiki promotion (same process key, different source layer). |
-| 409 | `append_only` | POST to an existing slug | Use `PATCH mode: "replace"` or pick a different slug. |
+| 409 | `append_only` | POST to an existing `10_raw/` file or `log.md` (those two layers are create-only). Does NOT apply to `20_wiki/<slug>.md` — re-POSTing there overwrites in place. | For `log.md` use `PATCH mode: "append"`. `10_raw/` files cannot be overwritten by design. |
 | 413 | — | Body exceeds 512 KB | Split the note or trim verbatim extracts. |
 | 5xx | — | Daemon error | Append a failure line to `log.md`, classify the run as partial, do not retry inside the same turn. |
 

package/agent-assets/system-prompts/routine-fetch-window.md

@@ -12,12 +12,16 @@ rows. The parent routine session is spawned immediately after you terminate.
   inlined integration partial in your user prompt states the call shape;
   your bound tools resolve it. If no surface is bound for a row, record a
   `no-surface` error and move on.
-- **One window → one curl → one JSON body.** Each acquired window is sent
-  as a single `POST /api/observations/batch` call (up to 200 items in
-  `observations[]`). Do NOT loop over items in a shell `for`. Do NOT write
-  a script under `/tmp/` and pipe / source / bash it. Do NOT chain
-  multiple `curl` calls in one Bash invocation. The daemon's hooks block
-  those shapes.
+- **One window → one observations call.** Each acquired window is posted
+  as a single batch (up to 200 items in `observations[]`). On a Claude
+  session, post via the `mcp__aitne-observations__submit_observations`
+  MCP tool the integration partial names — structured transport that
+  never goes through the bash preflight, so Unicode-bearing titles /
+  subjects can't trip it. On Codex/Gemini, post via one
+  `POST /api/observations/batch` curl. Either way: Do NOT loop over items
+  in a shell `for`. Do NOT write a script under `/tmp/` and pipe / source
+  / bash it. Do NOT chain multiple `curl` calls in one Bash invocation.
+  The daemon's hooks block those shapes.
 - **No interpretation.** Do not summarize, rank, filter, or annotate
   payloads. The async summarizer worker drains `/api/observations` after
   you return.
@@ -29,12 +33,18 @@ rows. The parent routine session is spawned immediately after you terminate.
 
 ## Tool conventions
 
-- **Bash**: only `curl` against `http://localhost:<apiPort>/*` to call the
-  daemon's REST API. The localhost-only check, secret-flag scrubber, and
-  pipe-chain block are enforced as PreToolUse hooks at runtime — the
-  policy layer is authoritative, not this prompt. One curl per Bash
-  call; heredoc bodies are fine. **Do not** read or write context MD
-  files via `/api/context/*`, do not call `/api/notify`.
+- **Bash**: `curl` against `http://localhost:<apiPort>/*` to call the
+  daemon's REST API — the `<fetch>` reads, and (Codex/Gemini only) the
+  `/api/observations/batch` write. On a Claude session the curl
+  observations-write path is NOT in your allowlist — post observations
+  through the `submit_observations` MCP tool instead; a Unicode-bearing
+  `-d @-` body would trip the SDK bash preflight and be denied (which
+  cascades to a wasted retry and `budget-cap`). The localhost-only check,
+  secret-flag scrubber, and pipe-chain block are enforced as PreToolUse
+  hooks at runtime — the policy layer is authoritative, not this prompt.
+  One curl per Bash call; heredoc bodies are fine for the Codex/Gemini
+  curl write. **Do not** read or write context MD files via
+  `/api/context/*`, do not call `/api/notify`.
 - **MCP tools (`mcp__<server>__<tool>`)**: when the integration partial
   routes through `native` or `delegated-same`, the tool surface is
   whatever your session has bound. Their schemas may be deferred behind

package/agent-assets/task-flows/_partials/calendar-acquire.google_calendar.md

@@ -19,8 +19,10 @@ windows for the pre-pass.
 
 Submit every returned event — for a whole window in **one** call — via the
 `mcp__aitne-observations__submit_observations` MCP tool when it is in your
-allowed tools (preferred — bypasses the SDK bash preflight). Build the
-tool input as `{"observations":[…]}` with one entry per event.
+allowed tools (preferred — the structured MCP transport carries
+Unicode-bearing titles / attendee names that would deterministically trip
+`curl … -d '{…}'` on the SDK's bash preflight). Build the tool input as
+`{"observations":[…]}` with one entry per event.
 
 If the MCP tool is unavailable (non-Claude session backend), fall back to
 `POST http://localhost:8321/api/observations/batch` with the same envelope:

package/agent-assets/task-flows/_partials/calendar-acquire.outlook_calendar.md

@@ -30,8 +30,10 @@ only ships drift / retrospective / imminent windows.
 
 Submit every returned event — for a whole window in **one** call — via the
 `mcp__aitne-observations__submit_observations` MCP tool when it is in your
-allowed tools (preferred — bypasses the SDK bash preflight). Build the
-tool input as `{"observations":[…]}` with one entry per event.
+allowed tools (preferred — the structured MCP transport carries
+Unicode-bearing titles / attendee names that would deterministically trip
+`curl … -d '{…}'` on the SDK's bash preflight). Build the tool input as
+`{"observations":[…]}` with one entry per event.
 
 If the MCP tool is unavailable (non-Claude session backend), fall back to
 `POST http://localhost:8321/api/observations/batch` with the same envelope:

package/agent-assets/task-flows/_partials/capture-user-info.md

@@ -17,8 +17,8 @@ Scan for declarative user facts or imperative tone/style directives. If matched,
 
 **Declarative facts about the user** → route through the user-profile skill. The skill owns the trigger shapes, the file split (`profile.md` vs `user/<topic>.md`), the read-before-write contract, the `section_not_found` → `append_to_file` first-write fallback, and the Learned-Context-vs-personal.md disambiguator. Key calls:
 
-- Top-level identity / platform / notification fact → `user/profile.md`.
+- Top-level identity / platform / notification fact → `identity/profile.md`.
 - Detail-heavy fact (specific person, workplace, hobby, tool, goal) → matching `user/<topic>.md` (`people` / `work` / `expertise` / `personal` / `goals`).
-- Self-reported behavioral pattern the agent should adapt to ("I'm not a morning person") → `user/profile.md ## Learned Context` with today's `[YYYY-MM-DD]` prefix.
+- Self-reported behavioral pattern the agent should adapt to ("I'm not a morning person") → `identity/profile.md ## Learned Context` with today's `[YYYY-MM-DD]` prefix.
 
 Never invent facts the user did not state. Never re-write a fact a paraphrase of which already exists in the target file.

package/agent-assets/task-flows/_partials/dm-intent.long-horizon.md

@@ -21,7 +21,7 @@ current day so the DM handler can route them into roadmap.
 **Not signals:**
 - Speculative language (*"maybe"*, *"someday"*, *"might"*, *"perhaps"*,
   *"thinking about"*) without a concrete anchor
-- Current-week commitments (those belong in `today.md`)
+- Current-week commitments (those belong in `state/today.md`)
 - Opinions, preferences, taste statements
   (those belong in `user/*.md` via the `user-profile` skill)
 

package/agent-assets/task-flows/_partials/dm-intent.project.md

@@ -51,9 +51,9 @@ can copy the same pattern into their own skills.
      writing.
    - **Decline-marker pre-check (Goal 3 — never ask twice).** Before
      classifying a no-match as new, compute the candidate slug and
-     read `agent/journal.md ## Declined Intents`:
+     read `journal/agent.md ## Declined Intents`:
      ```bash
-     curl -s "http://localhost:8321/api/context/agent/journal" \
+     curl -s "http://localhost:8321/api/context/journal/agent" \
        | jq -r '.content // ""' \
        | awk '/^## Declined Intents/{f=1;next} f && /^## /{exit} f'
      ```
@@ -175,7 +175,7 @@ can copy the same pattern into their own skills.
        "confirm_defer_count": 0,
        "confirm_max_defers": 3,
        "confirm_decline_marker": {
-         "path": "agent/journal.md",
+         "path": "journal/agent.md",
          "section": "declined_intents",
          "match": "create_project:<slug>"
        },
@@ -270,14 +270,14 @@ can copy the same pattern into their own skills.
      decline, do NOT write the project file. Two mandatory writes:
 
      a. **Write the decline marker** to
-        `agent/journal.md ## Declined Intents`. Three cases — file
+        `journal/agent.md ## Declined Intents`. Three cases — file
         missing entirely, file present but section missing, file +
         section both present — are handled in one read-then-branch
         sequence:
 
         ```bash
         # 1. GET. HTTP 404 means the journal file does not yet exist.
-        body=$(curl -sS -w '\n%{http_code}' "http://localhost:8321/api/context/agent/journal")
+        body=$(curl -sS -w '\n%{http_code}' "http://localhost:8321/api/context/journal/agent")
         status=$(printf '%s\n' "$body" | tail -n1)
         content=$(printf '%s\n' "$body" | sed '$d' | jq -r '.content // ""' 2>/dev/null)
 
@@ -287,19 +287,19 @@ can copy the same pattern into their own skills.
           # Case A — file missing. CREATE_ONLY_PUT is enabled for
           # agent/journal, so PUT creates the file in a single call.
           # Include both the H1 and the Declined Intents section.
-          curl -s -X PUT "http://localhost:8321/api/context/agent/journal" \
+          curl -s -X PUT "http://localhost:8321/api/context/journal/agent" \
             -H 'Content-Type: application/json' \
             -d "$(jq -n --arg m "$marker_line" '{content: "# Agent Journal\n\n## Declined Intents\n\($m)\n"}')"
         elif printf '%s' "$content" | grep -q '^## Declined Intents'; then
           # Case B — file + section present. Append a bullet to the
           # existing section.
-          curl -s -X PATCH "http://localhost:8321/api/context/agent/journal" \
+          curl -s -X PATCH "http://localhost:8321/api/context/journal/agent" \
             -H 'Content-Type: application/json' \
             -d "$(jq -n --arg m "$marker_line" '{section:"declined_intents",mode:"append",content:$m}')"
         else
           # Case C — file present but section missing. append_to_file
           # adds the section header + bullet to the end of the file.
-          curl -s -X PATCH "http://localhost:8321/api/context/agent/journal" \
+          curl -s -X PATCH "http://localhost:8321/api/context/journal/agent" \
             -H 'Content-Type: application/json' \
             -d "$(jq -n --arg m "$marker_line" '{mode:"append_to_file",content:"\n## Declined Intents\n\($m)\n"}')"
         fi
@@ -326,7 +326,7 @@ can copy the same pattern into their own skills.
    inline in a fresh DM (the carve-out in Step 1) or as a reply to a
    confirm DM — run this recipe instead of skipping:
 
-   1. GET `agent/journal.md`, parse the `## Declined Intents`
+   1. GET `journal/agent.md`, parse the `## Declined Intents`
       section, drop the line whose bracketed dedup_key matches
       `create_project:<slug>`, and PATCH the section with
       `mode: "replace"` carrying the rebuilt body (the other lines

package/agent-assets/task-flows/_partials/mail-acquire.outlook_mail.md

@@ -32,8 +32,9 @@ The four non-disabled branches therefore split into two real flows:
 
 Submit every returned message — for a whole window in **one** call — via the
 `mcp__aitne-observations__submit_observations` MCP tool when it is in your
-allowed tools (preferred — bypasses the SDK bash preflight which denies
-Unicode-whitespace-bearing bodies). Build the tool input as
+allowed tools (preferred — the structured MCP transport carries
+Unicode-bearing subjects / snippets that would deterministically trip
+`curl … -d '{…}'` on the SDK's bash preflight). Build the tool input as
 `{"observations":[…]}` with one entry per message.
 
 If the MCP tool is unavailable (non-Claude session backend), fall back to