@aitne-sh/aitne 0.1.7 → 0.1.8

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

@@ -101,38 +101,13 @@ curl -s "http://localhost:8321/api/profile-questions/slot-filled?path=user/profi
 This wraps the canonical TS helper. Use it — do NOT re-derive the rule
 in prose. URL-encode `section` and `anchor` if they contain spaces.
 
-## Operation 1 — Pick a question (morning routine Step 7.5)
+## Operation 1 — Pick a question (Morning Routine Step 7.5)
 
-```
-1. GET agent/profile-questions.md.
-2. Skip the entire step if any of:
-     - ## In Progress is non-empty.
-     - ## Pending is empty.
-     - User has not sent a DM in the last 24h.
-     - Day-type focus for [personal] on line 2 of <today> is `off`.
-     - The current run is the initial morning routine
-       (`routine.morning_routine_initial`) — it lands during setup; piling
-       on a question is bad UX.
-3. Walk Pending rows in priority order (HIGH → MID → LOW, then file
-   order). For each candidate:
-     a. If the row carries `<!-- last_attempted=YYYY-MM-DD -->` and that
-        date is within the last 7 days, skip — cooldown.
-     b. Call /api/profile-questions/slot-filled for the row's target. If
-        the slot turns out to be filled (Layer 2 catches drift since
-        last sweep), tick the row [x] (read-rebuild + replace) and
-        append `- [x] <today> → <id> (reconciled:morning)` to ## Answered.
-        Continue to the next candidate.
-     c. Otherwise, this is the chosen row. Stop walking.
-4. Append a single line to today.md ## Agent Notes (latent-question
-   flavor, see "Today.md surfacing" below):
-     `- Profile question (latent): <id> — wait for natural opportunity`
-5. Append to ## In Progress in the queue file (PATCH replace, read-rebuild):
-     `- <id> :: state=latent :: since=<today>`
-   The `since=` date is load-bearing — the evening sweep needs it to
-   compute the 3-day fallback threshold.
-6. Do NOT POST /api/schedule for this row. Latent rows are NOT
-   scheduled DMs — they wait for an opportunity.
-```
+Morning-routine-only. The full skip gates (5 conditions), walk order,
+drift-tick recovery, today.md mirror line, and no-schedule rule are in
+the op-morning reference below.
+
+{{> ref:op-morning }}
 
 ## Operation 2 — Latent opportunity check (DM handler)
 
@@ -190,34 +165,12 @@ composing the reply.
 
 ## Operation 3 — Latent piggyback (morning briefing composition)
 
-Mirror of Operation 2, run inside the `## Morning briefing` sub-flow of
-`scheduled.dm.md`. The briefing is already an outgoing DM the agent
-composes; it is one of the few naturally-occurring opportunities to
-slip in a question.
+Scheduled.dm-only. Mirror of Operation 2 but run inside the
+`## Morning briefing` sub-flow of `scheduled.dm.md`. Slot-filled
+pre-check, domain-overlap judgment, and the two PATCHes are in the
+op-briefing reference below.
 
-```
-1. GET agent/profile-questions.md ## In Progress.
-2. If no entry has state=latent, skip.
-2.5 Slot-filled pre-check (MANDATORY). Same recipe as Operation 2 step 2.5:
-   GET /api/profile-questions/slot-filled. If `filled: true`, resolve
-   the row (tick Pending, remove In Progress, append
-   `- [x] <today> → <id> (reconciled:opportunity)` to Answered, remove
-   the matching `Profile question (latent):` line from today.md ## Agent Notes) and
-   skip the piggyback — DO NOT weave the question.
-3. Decide whether the briefing's main content overlaps with the
-   question's domain (work questions when the day is calendar-heavy
-   with work meetings; personal questions when the day is light /
-   personal). If yes, weave one question into the briefing as a 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 —
-     flip the entry to
-     `state=asked :: since=<unchanged> :: asked_at=<current_time>`.
-   - `PATCH /api/context/today` section=agent_notes — flip the matching
-     `Profile question (latent):` line by changing the parenthetical to
-     `(asked HH:MM)`.
-```
+{{> ref:op-briefing }}
 
 ## Operation 4 — Capture the answer (DM handler queue reconcile)
 
@@ -315,7 +268,7 @@ curl -s -X PATCH http://localhost:8321/api/context/agent/profile-questions \
 # Fallback DM scheduling (Operation 5B only)
 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>","model":"sonnet","taskContext":{"scheduledBy":"user_profile_sweep_fallback","queueId":"<id>","importance":"low"}}'
+  -d '{"time":"<ISO>","taskType":"dm_session","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

@@ -0,0 +1,51 @@
+---
+kind: reference
+name: op-briefing
+description: Operation 3 — weave a latent profile question into the morning briefing inside scheduled.dm's ## Morning briefing sub-flow. Slot-filled pre-check, domain overlap, two PATCHes.
+---
+
+# Operation 3 — Latent piggyback (morning briefing composition)
+
+Run this inside the `## Morning briefing` sub-flow of
+`scheduled.dm.md`. The briefing is already an outgoing DM the agent
+composes; it is one of the few naturally-occurring opportunities to
+slip in a question without surfacing a cold standalone DM.
+
+```
+1. GET agent/profile-questions.md ## In Progress.
+2. If no entry has state=latent, skip.
+2.5 Slot-filled pre-check (MANDATORY). Same recipe as Operation 2
+   step 2.5: GET /api/profile-questions/slot-filled. If
+   `filled: true`, resolve the row (tick Pending, remove In Progress,
+   append `- [x] <today> → <id> (reconciled:opportunity)` to Answered,
+   remove the matching `Profile question (latent):` line from
+   today.md ## Agent Notes) and skip the piggyback — DO NOT weave the
+   question.
+3. Decide whether the briefing's main content overlaps with the
+   question's domain (work questions when the day is calendar-heavy
+   with work meetings; personal questions when the day is light /
+   personal). If yes, weave one question into the briefing as a
+   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 —
+     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
+     matching `Profile question (latent):` line by changing the
+     parenthetical to `(asked HH:MM)`.
+```
+
+## What "natural piggyback" means in this sub-flow
+
+The briefing already enumerates today's calendar items, deltas since
+yesterday, and any flagged inbound from the overnight window. A
+piggyback question should feel like a side comment on one of those —
+"the design review is at 14:00 — what's your usual ramp-up before
+those?" — not a separate `## Question:` paragraph.
+
+If the briefing's main content does not have any natural anchor for
+the latent question's domain, do not force it. Leave the entry
+`state=latent` and let Operation 2 catch it on the next DM the user
+sends.

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

@@ -0,0 +1,59 @@
+---
+kind: reference
+name: op-morning
+description: Operation 1 — pick a profile-interview question during Morning Routine Step 7.5. Skip gates, walk order, drift-tick recovery, today.md mirror, no-schedule rule.
+---
+
+# Operation 1 — Pick a question (Morning Routine Step 7.5)
+
+Run this only inside `routine.morning_routine` (and its split
+variants `routine.morning_routine_today`). DM handlers, scheduled.dm
+briefings, and hourly checks do not run this operation — they use
+Operation 2 / 3 / 4 instead.
+
+```
+1. GET agent/profile-questions.md.
+2. Skip the entire step if any of:
+     - ## In Progress is non-empty.
+     - ## Pending is empty.
+     - User has not sent a DM in the last 24h.
+     - Day-type focus for [personal] on line 2 of <today> is `off`.
+     - This is the first-run morning routine (`<yesterday>` is absent
+       from your prompt context — the wizard just finished setup and a
+       profile question on day 1 piles onto an already busy onboarding
+       surface). Pre-Phase-4 this was keyed off the
+       `routine.morning_routine_initial` process key, which the
+       dispatcher no longer emits — both branches now route through
+       `routine.morning_routine` and the cue is `<yesterday>` absence.
+3. Walk Pending rows in priority order (HIGH → MID → LOW, then file
+   order). For each candidate:
+     a. If the row carries `<!-- last_attempted=YYYY-MM-DD -->` and
+        that date is within the last 7 days, skip — cooldown.
+     b. Call /api/profile-questions/slot-filled for the row's target.
+        If the slot turns out to be filled (Layer 2 catches drift
+        since last sweep), tick the row [x] (read-rebuild + replace)
+        and append `- [x] <today> → <id> (reconciled:morning)` to
+        ## Answered. Continue to the next candidate.
+     c. Otherwise, this is the chosen row. Stop walking.
+4. Append a single line to today.md ## Agent Notes (latent-question
+   flavor, see "Today.md surfacing" in the skill body):
+     `- Profile question (latent): <id> — wait for natural opportunity`
+5. Append to ## In Progress in the queue file (PATCH replace,
+   read-rebuild):
+     `- <id> :: state=latent :: since=<today>`
+   The `since=` date is load-bearing — the evening sweep needs it to
+   compute the 3-day fallback threshold.
+6. Do NOT POST /api/schedule for this row. Latent rows are NOT
+   scheduled DMs — they wait for an opportunity.
+```
+
+## Why no schedule?
+
+A cold scheduled DM that asks "what's your timezone?" out of nowhere
+is exactly the failure mode the queue exists to avoid. The latent row
+sits in `## In Progress` until either Operation 2 (DM-handler
+opportunity match) or Operation 3 (morning briefing piggyback)
+naturally weaves it in. Only the evening sweep's Operation 5B fallback
+(3 days latent without an opportunity, user still active) escalates to
+a scheduled DM — and that's the design's safety valve, not the
+primary path.

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

@@ -31,7 +31,7 @@ B. LATENT FALLBACK PROMOTION.
          {time: tomorrow @ 14:00 local (or quiet_hours_end + 2h),
           taskType: "dm_session",
           description: "profile_interview:<id> — <ask-hint>",
-          model: "sonnet",
+          tier: "medium",
           taskContext: {scheduledBy: "user_profile_sweep_fallback",
                         queueId: "<id>", importance: "low"}}
        Update the In Progress entry to

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

@@ -8,12 +8,7 @@ allowed-tools:
 
 # User Profile Update Guide
 
-Output language: follow `<output_language_policy>`. `user/profile.md`
-and `user/*.md` are Policy B — template H2 headers (`## Identity`,
-`## Work Pattern`, `## Platforms`, `## Expertise`, `## Notification
-Preferences`, `## Learned Context`, `## Raw Signals`) are skeleton and
-stay English; the facts you write under them are in
-`<settings primary_language>`. Preserve user-customized headers verbatim.
+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.
 
 `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).
 
@@ -42,7 +37,7 @@ Detailed, dictionary-like background belongs under `user/*.md`. Read `user/_inde
 - "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.
 
-See the `message.received.dm.md` / `message.received.dm_first.md` **Capture user info** block for the full decision rule (profile.md vs `user/<topic>.md` tie-breakers, `section_not_found` → `append_to_file` first-write fallback, and a worked `curl` example).
+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.
 
 ## Section ownership
 
@@ -74,6 +69,21 @@ All `user/*.md` files must keep YAML frontmatter with `type: user`,
 section-level PATCH, preserve the existing frontmatter. When doing a
 full-file PUT, update `updated` to today's date.
 
+**Bullet key convention — load-bearing.** Bullets under each H2 use
+**English label keys**, any-language values:
+
+```
+- Name: Alex
+- Timezone: America/New_York
+- Working hours: Weekdays 09:00–18:00
+```
+
+The `user-interview` skill's queue (`agent/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
+`user-interview/SKILL.md` §"Anchor convention — load-bearing".
+
 ## Notification Preferences format
 
 Morning Routine reads this daily to derive today.md's day-type filter. Keep bullets machine-parseable:
@@ -92,31 +102,17 @@ If the user says "I don't want work notifications on weekends", paraphrase into
 
 ## Tone / character preferences
 
-**Tone, style, voice, formality, emoji, verbosity, language preferences 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`.
-
-Triggers: "always reply in English", "shorter please", "no emojis", "speak casually", "be more concise", "more formal please", "end every reply with a period".
-
-**Read-before-write still applies.** Do this in one turn:
+**Tone, style, voice, formality, emoji, verbosity, language
+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`.
 
-```bash
-# 1. Read current character
-curl -s http://localhost:8321/api/config/character | jq -r .character
-
-# 2. Merge the new preference into the existing value, then PATCH:
-curl -s -X PATCH http://localhost:8321/api/config/character \
-  -H 'Content-Type: application/json' \
-  -d '{"character": "Speak casually. Tight bullets. No emojis. End every reply with a period."}'
-```
+Full recipe — triggers, merge rules, endpoint note, cap-handling, and
+where the value ends up — is in the character-preferences reference
+below.
 
-**Endpoint note.** Use `/api/config/character` (narrow, agent-callable),
-not `/api/config` — the general config surface is dashboard-only (Approve
-tier) and will return 401 from an agent curl. The narrow endpoint accepts
-only the `character` field, runs the same Zod validation, and fans the
-new value out to active sessions identically.
-
-**Observe the 1000-char cap.** If the merged value would exceed 1000 characters, surface the excess to the user ("Your style guide is 1180 characters, over the 1000 limit — shall I trim?") rather than silently truncating. Zod rejects over-cap writes with 400 at the API.
-
-The character value is written verbatim into every session's `CLAUDE.md` / `AGENTS.md` / `GEMINI.md` between the safety preamble and the profile body. It applies across Claude, Codex, and Gemini uniformly — no separate injection per backend.
+{{> ref:character-preferences }}
 
 ## Read-before-write — mandatory for PATCH replace
 
@@ -134,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), see the **Capture user info** block in `message.received.dm.md` / `message.received.dm_first.md` for the decision rule, the `section_not_found` → `append_to_file` first-write fallback, and a worked `curl` example against `user/people.md`. The read-before-write rule above 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 `user/people.md`). The read-before-write rule applies identically when merging into an existing `user/<topic>.md` section.
 
 ## Learned Context entry format
 
@@ -167,42 +163,26 @@ Populate `user/profile.md` (Identity, Work Pattern, Platforms, Expertise summary
 
 ## API Reference
 
-### Read
-```bash
-curl -s http://localhost:8321/api/context/user/profile              # Full profile
-curl -s http://localhost:8321/api/context/user/_index               # Topic index
-curl -s http://localhost:8321/api/context/user/people               # Specific topic
-```
+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
+summary file) and `/api/context/user/:topic` (one of `people` /
+`work` / `expertise` / `personal` / `goals`).
 
-### PATCH /api/context/user/profile — Section-level edit
-```bash
-curl -s -X PATCH http://localhost:8321/api/context/user/profile \
-  -H 'Content-Type: application/json' \
-  -d '{"section": "learned_context", "mode": "append", "content": "- [YYYY-MM-DD] ..."}'
-```
+Two user-profile-specific notes layered on top of the generic surface:
 
-| Field | Type | Description |
-|---|---|---|
-| `section` | string | snake_case of heading (e.g. `learned_context`) |
-| `mode` | `append` \| `replace` \| `clear` \| `clear_before` | Default `append` |
-| `content` | string | Ignored for `clear` / `clear_before` |
-| `cutoff` | string | `clear_before` only: entries with `[timestamp] ≤ cutoff` are removed (race-safe consumption for Raw Signals) |
-| `maxEntries` | number | `append` only: trims oldest entries to cap (SignalDetector uses cap=20) |
+- **`clear_before` on `## Raw Signals`** is the race-safe consumption
+  path Evening Review uses to drain Raw Signals without dropping
+  concurrent appends. Pass a SQLite-format `cutoff`:
 
-`clear_before` example (Evening Review consuming Raw Signals without dropping concurrent appends):
-```bash
-curl -s -X PATCH http://localhost:8321/api/context/user/profile \
-  -H 'Content-Type: application/json' \
-  -d '{"section": "raw_signals", "mode": "clear_before", "cutoff": "2026-04-10 02:33:00"}'
-```
+  ```bash
+  curl -s -X PATCH http://localhost:8321/api/context/user/profile \
+    -H 'Content-Type: application/json' \
+    -d '{"section": "raw_signals", "mode": "clear_before", "cutoff": "2026-04-10 02:33:00"}'
+  ```
 
-### PATCH /api/context/user/:topic
-Same shape. Target a section within a topic file:
-```bash
-curl -s -X PATCH http://localhost:8321/api/context/user/people \
-  -H 'Content-Type: application/json' \
-  -d '{"section": "colleagues", "mode": "append", "content": "- Alice: PM on Project X"}'
-```
+- **`maxEntries`** on `## Raw Signals` append is the SignalDetector's
+  cap (= 20). Other writers do not set it.
 
 ## Knowledge map — topic files (auto-curated)
 

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

@@ -0,0 +1,83 @@
+---
+kind: reference
+name: character-preferences
+description: Tone / style / voice / language preferences are agent directives — route to PATCH /api/config/character (read-before-write, 1000-char cap, narrow endpoint).
+---
+
+# Tone / character preferences
+
+**Tone, style, voice, formality, emoji, verbosity, language preferences
+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`.
+
+## Triggers
+
+The user is asking for a character change when they say things like:
+
+- "always reply in English" / "speak Japanese from now on"
+- "shorter please" / "be more concise" / "stop padding"
+- "no emojis" / "drop the emojis"
+- "speak casually" / "be more formal please"
+- "end every reply with a period"
+- "don't ask follow-up questions, just answer"
+- "stop with the disclaimers"
+
+If the phrasing reads as a behavioral preference for *how* the agent
+speaks rather than a fact about the user, it belongs in
+`character`, not in profile.md.
+
+## Read-before-write — mandatory
+
+`PATCH /api/config/character` replaces the value wholesale. If you write
+just the new preference, you lose every preference the user previously
+set. Do this in one turn:
+
+```bash
+# 1. Read current character
+curl -s http://localhost:8321/api/config/character | jq -r .character
+
+# 2. Merge the new preference into the existing value, then PATCH:
+curl -s -X PATCH http://localhost:8321/api/config/character \
+  -H 'Content-Type: application/json' \
+  -d '{"character": "Speak casually. Tight bullets. No emojis. End every reply with a period."}'
+```
+
+Merge rules: if the new preference conflicts with an existing one
+(e.g. user used to ask for "formal" and now asks for "casual"), drop
+the old one. If it is additive (a new "no emojis" on top of an
+existing "tight bullets"), append.
+
+## Endpoint note — use the narrow path
+
+Use `/api/config/character` (narrow, agent-callable), **not** `/api/config`.
+The general config surface is dashboard-only (Approve tier) and will
+return 401 from an agent curl. The narrow endpoint accepts only the
+`character` field, runs the same Zod validation, and fans the new value
+out to active sessions identically.
+
+## 1000-char cap
+
+If the merged value would exceed 1000 characters, **surface the excess
+to the user** ("Your style guide is 1180 characters, over the 1000
+limit — shall I trim?") rather than silently truncating. Zod rejects
+over-cap writes with HTTP 400 at the API.
+
+A character value over the cap usually means the user added a
+preference that *replaces* an older one rather than extending it —
+offer to drop the obsoleted bullet as the first trim candidate.
+
+## Where the value ends up
+
+The character value is written verbatim into every session's
+`CLAUDE.md` / `AGENTS.md` / `GEMINI.md` between the safety preamble
+and the profile body. It applies across Claude, Codex, and Gemini
+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
+`character`. The split is: `character` says *how* the agent speaks;
+`user/*` says *who the user is*.

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

@@ -22,6 +22,34 @@
         { "heading": "## Colleagues", "contains": "current and recent coworkers" },
         { "heading": "## Friends", "contains": "social ties" }
       ]
+    },
+    {
+      "path": "user/work.md",
+      "purpose": "workplace, team, tech stack",
+      "sections": [
+        { "heading": "## Stack", "contains": "tools, languages, services used at work" }
+      ]
+    },
+    {
+      "path": "user/expertise.md",
+      "purpose": "domains, tools, skill levels",
+      "sections": [
+        { "heading": "## Tools", "contains": "tools the user uses habitually" }
+      ]
+    },
+    {
+      "path": "user/personal.md",
+      "purpose": "hobbies, health, habits",
+      "sections": [
+        { "heading": "## Habits", "contains": "routines, lifestyle, health" }
+      ]
+    },
+    {
+      "path": "user/goals.md",
+      "purpose": "developmental goals and learning targets",
+      "sections": [
+        { "heading": "## Learning", "contains": "skills the user wants to build" }
+      ]
     }
   ]
 }

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

@@ -3,7 +3,6 @@ name: wiki-ask
 description: Load for wiki.ask. Answers a question from the wiki and records the answer under 30_outputs.
 allowed-tools:
   - Bash(curl *)
-  - Bash(jq *)
 ---
 
 # Wiki Ask

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

@@ -3,7 +3,6 @@ name: wiki-compile
 description: Load for wiki.compile. Synthesizes 10_raw notes into 20_wiki notes via the daemon Wiki API and updates the wiki index.
 allowed-tools:
   - Bash(curl *)
-  - Bash(jq *)
 ---
 
 # Wiki Compile

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

@@ -3,7 +3,6 @@ name: wiki-connect
 description: Load for wiki.connect. Bridges two domains by surfacing shared terms, references, and structural analogies; writes a cited connection report to 30_outputs/.
 allowed-tools:
   - Bash(curl *)
-  - Bash(jq *)
 ---
 
 # Wiki Connect

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

@@ -3,7 +3,6 @@ name: wiki-graduate
 description: Load alongside wiki-compile. Promotes ready inbox material into a real wiki note with the canonical schema; never invents content beyond the source.
 allowed-tools:
   - Bash(curl *)
-  - Bash(jq *)
 ---
 
 # Wiki Graduate

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

@@ -4,7 +4,6 @@ description: Load for wiki.ingest_url. Captures one URL into 10_raw/<slug>.md by
 allowed-tools:
   - WebFetch
   - Bash(curl *)
-  - Bash(jq *)
 ---
 
 # Wiki URL Ingestion

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

@@ -3,7 +3,6 @@ name: wiki-lint
 description: Load for wiki.lint. Audits the wiki for orphans, broken links, schema drift, taxonomy candidates, and stale notes; writes a dated health report.
 allowed-tools:
   - Bash(curl *)
-  - Bash(jq *)
 ---
 
 # Wiki Lint

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

@@ -3,7 +3,6 @@ name: wiki-trace
 description: Load for wiki.trace. Reconstructs the chronological evolution of an idea across raw, wiki, and outputs; writes a cited timeline to 30_outputs/.
 allowed-tools:
   - Bash(curl *)
-  - Bash(jq *)
 ---
 
 # Wiki Trace

package/agent-assets/skills/wiki/wiki-vault-rules/SKILL.md

@@ -3,7 +3,6 @@ name: wiki-vault-rules
 description: Load for every wiki.* process. Defines wiki vault layout, layer ownership, and the daemon Wiki API call convention (endpoints + canonical curl shape).
 allowed-tools:
   - Bash(curl *)
-  - Bash(jq *)
   - Read
 ---
 

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

@@ -0,0 +1,68 @@
+You are Claude Code, Anthropic's official CLI for Claude. This session is the
+**routine.fetch_window pre-pass** dispatched by the Aitne daemon: a short,
+mechanical fetch session whose only job is to materialise the rows in the
+`<acquisition-plan>` block of your prompt into fresh `/api/observations`
+rows. The parent routine session is spawned immediately after you terminate.
+
+## Operating principles
+
+- **Fetch, don't think.** The daemon already resolved the
+  `(integration, mode, window, account?)` routing. Trust it. Do not probe
+  MCP registries, do not list "common tool names", do not guess. The
+  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.
+- **No interpretation.** Do not summarize, rank, filter, or annotate
+  payloads. The async summarizer worker drains `/api/observations` after
+  you return.
+- **Emit exactly one JSON line on stdout, then terminate.** The shape is
+  `{"fetched":<int>,"posted":<int>,"duplicates":<int>,"errors":[<{type,...}>]}`.
+  No prose, no markdown fences. The dispatcher reads the last
+  JSON-shaped object on stdout — a malformed line surfaces as
+  `pre-pass-failed`.
+
+## 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`.
+- **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
+  `ToolSearch` — fetch the schema before calling.
+- **ToolSearch**: load deferred MCP schemas by name or keyword. Use it
+  before calling an MCP tool whose schema is not yet visible.
+- **No other tools are needed.** Do not invoke Skill, Read, Write, Edit,
+  Glob, Grep, NotebookEdit, WebFetch, WebSearch, Task, EnterPlanMode,
+  ScheduleWakeup, or sub-agents. Even if a tool is not explicitly
+  forbidden, the boundary above is enforced by the SDK allowlist.
+
+## Boundaries
+
+- Do NOT spawn sub-tasks or sub-agents — keep the run flat so the
+  dispatcher can clamp turn / budget cleanly.
+- Do NOT exceed `max_turns` / `max_budget_usd`. If you hit the cap,
+  record `{"type":"budget-exhausted","remaining":[…]}` in `errors` and
+  print the JSON line.
+- `actor` on every observations element MUST be `"agent"`. Do NOT
+  compute `contentHash` — the server derives it.
+- The pre-pass is invisible to the owner by contract. No notifications,
+  no DMs, no file writes outside the observations API.
+
+## Output
+
+When every `<fetch>` row has been processed (success, duplicate, or
+recorded error), emit exactly one JSON line on stdout in the shape
+above and terminate. The user prompt below carries the full
+`<acquisition-plan>` and the integration partial that names the
+endpoint / argument shapes. Follow that partial verbatim — do not
+transfer argument names across integration boundaries.