@aitne-sh/aitne 0.1.4 → 0.1.5

package/agent-assets/agent-profiles/_safety.md

@@ -24,3 +24,17 @@
 - **Read-before-write**: PATCH `mode=replace` replaces the entire section.
   Always GET first, merge your changes into the existing content, then PATCH.
   Prefer `mode=append` when simply adding new entries.
+- **Daemon-API body submission** (`curl -d` on `/api/context/*`,
+  `/api/observations`, `/api/schedule`, etc.). Two safe shapes:
+  - Inline JSON — `-d '{"key":"value"}'`. Use for small / single-line
+    bodies. Escape internal newlines as `\n`.
+  - Stdin heredoc — `-d @- <<'JSON' … JSON`. Use for multi-line or
+    large bodies. `@-` is curl's stdin marker (a literal two-character
+    token), distinct from the file-read forms below.
+
+  Never use `-d @<filepath>` / `--data-raw '@<filepath>'` /
+  `-F field=@<filepath>`. They are file-read shapes — safe mode
+  hook-blocks them, and a request that slips through sends the literal
+  `@/path/...` text as the body, which the daemon rejects with
+  `invalid_json_body`. There is no agent-facing reason to read a body
+  off the filesystem; pipe stdin via `@-` instead.

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

@@ -26,8 +26,10 @@ the update.
    - Update `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:
-   `curl -s -X POST http://localhost:8321/api/observations/consume -H 'Content-Type: application/json' -d '{"ids":[1,2],"correlationId":"<event-correlation-id>"}'`
+6. Mark processed observations consumed via the bulk endpoint
+   (`POST /api/observations/consume`) — see "POST /api/observations/consume"
+   in the API Reference below for the exact body shape and the
+   `correlationId` rule. There is no per-id variant.
 
 ## Skip Criteria
 
@@ -133,13 +135,29 @@ etc.) and are picked up by the prefix match on the GET route.
 
 ### 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.
+
+Copy the `correlationId` value verbatim from the
+`<event_correlation_id>…</event_correlation_id>` tag in your turn
+context — do not paste the angle-bracket placeholder.
+
 ```bash
+# Example: <event_correlation_id>hourly-2026-04-23T15:00:00Z-7af3</event_correlation_id>
+# arrived in context, and observations 14 and 17 were processed.
 curl -s -X POST http://localhost:8321/api/observations/consume \
   -H 'Content-Type: application/json' \
-  -d '{"ids": [1, 2, 3], "correlationId": "<event_correlation_id>"}'
+  -d '{"ids":[14,17],"correlationId":"hourly-2026-04-23T15:00:00Z-7af3"}'
 ```
 
-Response: `{ "consumed": 3 }`
+| Field | Type | Required | Notes |
+|---|---|---|---|
+| `ids` | `number[]` | yes | Integers, not strings. `["14"]` is rejected. |
+| `correlationId` | `string` | yes | Verbatim from the `<event_correlation_id>` context tag. Non-string or missing → 400. |
+
+Response: `{ "consumed": <count> }`. Validation failures return 400
+`{"error":"validation_error"}`.
 
 ### GET /api/observations/stats
 

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

@@ -246,6 +246,12 @@ mid-session refresh is not interleaved with a DM handler PATCH.
 
 ## roadmap.md API
 
+Body submission follows `_safety.md` "Daemon-API body submission":
+small POST / PATCH bodies use inline `-d '{...}'`; the full-file PUT
+runs multi-KB and uses the stdin heredoc `-d @- <<'JSON'` shape.
+Include `X-Lock-Id: <roadmap_write_lock_id>` on every PUT / PATCH
+when that tag is in your context.
+
 ```bash
 # Read
 curl -s http://localhost:8321/api/context/roadmap
@@ -254,19 +260,21 @@ curl -s http://localhost:8321/api/context/roadmap
 curl -s -X POST http://localhost:8321/api/context/roadmap/id \
   -H 'Content-Type: application/json' \
   -H 'X-Lock-Id: <roadmap_write_lock_id>' \
-  -d '{"creationDate": "YYYY-MM-DD"}'
+  -d '{"creationDate":"YYYY-MM-DD"}'
 
-# Full replace (roadmap refresh — include X-Lock-Id if context provides one)
+# Full replace (roadmap refresh) — multi-KB body, use heredoc.
 curl -s -X PUT http://localhost:8321/api/context/roadmap \
   -H 'Content-Type: application/json' \
   -H 'X-Lock-Id: <roadmap_write_lock_id>' \
-  -d '{"content": "# Roadmap\n..."}'
+  -d @- <<'JSON'
+{"content":"# Roadmap\n> Last synced: 2026-04-23\n\n## Annual Goals\n- ...\n\n## Quarterly Focus\n- ...\n\n## Long-term Plans\n- [2026-Q3] ...  <!-- id: rm-20260419-b8e7d4 -->\n\n## Agent Action Plan\n\n## Recurring\n- Every Friday: weekly review\n"}
+JSON
 
 # Section PATCH
 curl -s -X PATCH http://localhost:8321/api/context/roadmap \
   -H 'Content-Type: application/json' \
   -H 'X-Lock-Id: <roadmap_write_lock_id>' \
-  -d '{"section": "long_term_plans", "mode": "append", "content": "- [2026-Q3] ...\n"}'
+  -d '{"section":"long_term_plans","mode":"append","content":"- [2026-Q3] ...\n"}'
 ```
 
 Snapshotting, mtime updates, and path validation are handled by the

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

@@ -186,15 +186,34 @@ PUT today.md must contain the H1 date line, day-type header quote, and all six s
 
 ## today.md API (subset of context API)
 
+Body submission follows the rule in `_safety.md` "Daemon-API body
+submission": small section PATCHes use inline `-d '{...}'`; full-file
+PUT uses the stdin heredoc `-d @- <<'JSON'` shape because the body
+runs multi-KB. Add `X-Lock-Id: <today_write_lock_id>` on every
+PUT / PATCH when that tag is in your context.
+
 ```bash
-curl -s http://localhost:8321/api/context/today                    # Read
-curl -s -X PUT http://localhost:8321/api/context/today \            # Full replace (Morning only)
-  -H 'Content-Type: application/json' -d '{"content": "# 2026-04-02 (Thu)\n..."}'
-curl -s -X PATCH http://localhost:8321/api/context/today \          # Section operation
-  -H 'Content-Type: application/json' -d '{"section": "agent_log", "mode": "append", "content": "- 09:35 ..."}'
+# Read
+curl -s http://localhost:8321/api/context/today
+
+# Full replace — Morning Routine only. Multi-KB body → heredoc.
+curl -s -X PUT http://localhost:8321/api/context/today \
+  -H 'Content-Type: application/json' \
+  -H 'X-Lock-Id: <today_write_lock_id>' \
+  -d @- <<'JSON'
+{"content":"# 2026-04-02 (Thursday)\n> Day type: Weekday | Work focus: on | Study focus: on | Personal focus: on\n\n## User Schedule\n- 14:00–15:00 Design review [work]\n\n## User Tasks\n- [ ] 11:00 Finalize Q2 draft [work]\n\n## Agent Plan\n- [ ] 08:55 DM reminder: standup [work] →DM\n\n## Agent Notes\n\n## Agent Log\n- 04:00 Morning Routine completed (day-type: Weekday)\n\n## Handoff\n- (none)\n"}
+JSON
+
+# Section operation — small body, inline `-d` is fine.
+curl -s -X PATCH http://localhost:8321/api/context/today \
+  -H 'Content-Type: application/json' \
+  -H 'X-Lock-Id: <today_write_lock_id>' \
+  -d '{"section":"agent_log","mode":"append","content":"- 09:35 ..."}'
 ```
 
-Add `X-Lock-Id` header if `<today_write_lock_id>` is in context. See context skill for full API reference.
+The H1 date and the `> Day type:` quote line are validated by exact
+regex on PUT — keep both English-shaped exactly as the template. See
+context skill for the full endpoint reference.
 
 ## Knowledge map — section shape (auto-curated)
 

package/agent-assets/task-flows/routine.roadmap_refresh.md

@@ -176,11 +176,15 @@ coordinates the high-level gather → analyze → write loop.
    consult that ID before emitting a new entry or matching by text.
 
 7. Consume the observations whose candidate was incorporated or
-   deliberately dropped — always pass the event correlation id:
-   ```
+   deliberately dropped. Copy the `correlationId` value verbatim from
+   the `<event_correlation_id>…</event_correlation_id>` tag in your
+   turn context — do not paste the placeholder. Bulk-only; the per-id
+   form does not exist. Field contract is in the `observations`
+   skill ("POST /api/observations/consume").
+   ```bash
    curl -s -X POST http://localhost:8321/api/observations/consume \
      -H 'Content-Type: application/json' \
-     -d '{"ids":[<id>, ...], "correlationId": "<event_correlation_id>"}'
+     -d '{"ids":[<id>, ...],"correlationId":"<copied-from-event_correlation_id-tag>"}'
    ```
    Observations left pending here will re-appear on the next refresh.
 

package/agent-assets/task-flows/setup.initial.md

@@ -7,8 +7,9 @@ Vault step already captured `settings.primary_language` (BCP-47 tag, e.g.
 `en` or `es`) and `settings.vault_mode` (`plain` or `obsidian`) — the
 latter controls how the **primary management vault** is laid out, not the
 separate external Obsidian integration. Do NOT re-ask those questions.
-Output language for user-editable prose (profile, today, daily journal):
-follow `<output_language_policy>`.
+Output language for everything written to disk in this flow
+(`user/profile.md`, `user/*.md`, `rules/management.md` body): follow
+`<output_language_policy>`.
 
 SETUP-FLOW-REDESIGN-PLAN §5.8 — the legacy "tool selections" form was
 removed. Steps 4–6 of the wizard (Mail, Calendar, Note) already
@@ -68,6 +69,15 @@ about all four rows rather than fabricating defaults. Do not retry
 with a curl.
 
 ### Instructions
+
+Steps 3–8 all happen in the same agent turn. They are ordered to match
+the actual emission sequence: the two staged code blocks (rules then
+character) land in the stream first; the silent curl writes follow. The
+dashboard reveals the preview as soon as the rules block lands but
+keeps "Save & Finish" disabled until the whole turn ends, so emitting
+blocks before curls minimizes how long the user waits on a disabled
+button.
+
 1. Run Step 0 silently. Greet the user in one line, introducing
    yourself by the name in `<agent_identity>` display_name. Then
    present the derived Source-of-Truth table and ask any remaining
@@ -78,28 +88,30 @@ with a curl.
    - Project-management method preferences (anything you want the agent
      to follow when handling your projects?)
    Either answer may be "no preference" / "skip" — accept that cleanly.
-3. Once the user has answered, generate rules/management.md inside a
-   ```management-rules code block. This triggers the dashboard preview.
-4. If the user requests changes, revise. Complete within **at most 2
-   revision rounds**.
+3. Generate rules/management.md inside a ```management-rules code
+   block. This is the FIRST thing emitted in the turn — the dashboard
+   reveals the preview as soon as it lands.
+4. If the user requests changes, revise (return to step 3). Complete
+   within **at most 2 revision rounds**.
 5. **Do NOT put communication style inside rules/management.md, and do NOT
    put it inside `user/profile.md` either.** Tone / style / voice / emoji
    / language preferences live in the `character` runtime-config field
-   only — emitted as a ```character``` code block (see step 6.5). See
+   only — emitted as a ```character``` code block (see step 6). See
    `docs/design/15-character.md` for the split rule.
-6. In the same turn as the management-rules block, silently call
-   PUT /api/context/user/profile using the template in "user/profile.md
-   Format" below. Working hours and quiet hours are pre-populated with
-   defaults (Weekdays 09:00–18:00, Quiet hours 22:00–08:00) — do not
-   ask about them. Fill Platforms from the **derived Source-of-Truth
-   table** (Step 0) — the row values you confirmed with the user.
-   Leave Identity blank — setup does not collect name or timezone.
-6.5. If the user stated a communication-style preference in step 2,
-   emit a ```character``` code block in the same turn (see "Character
-   code block format" below). If the user skipped, omit the block.
-7. If the conversation surfaced detail-heavy facts that belong in the
-   detailed profile layer, also PATCH the matching user/*.md file in the
-   same turn. Typical Q&A → file mappings:
+6. If the user stated a communication-style preference in step 2, emit
+   a ```character``` code block immediately after the rules block (see
+   "Character code block format" below). If the user skipped, omit the
+   block.
+7. After the staged blocks, silently call PUT /api/context/user/profile
+   using the template in "user/profile.md Format" below. Working hours
+   and quiet hours are pre-populated with defaults (Weekdays 09:00–18:00,
+   Quiet hours 22:00–08:00) — do not ask about them. Fill Platforms
+   from the **derived Source-of-Truth table** (Step 0) — the row values
+   you confirmed with the user. Leave Identity blank — setup does not
+   collect name or timezone.
+8. If the conversation surfaced detail-heavy facts that belong in the
+   detailed profile layer, also PATCH the matching user/*.md file (still
+   the same turn, after step 7). Typical Q&A → file mappings:
      - Named colleagues, family, friends → user/people.md
      - Current company, role specifics, ongoing projects → user/work.md
      - Specific frameworks, years of experience → user/expertise.md
@@ -109,7 +121,7 @@ with a curl.
    Only seed what the user actually stated — do not invent or infer. If
    nothing came up for a given file, do not touch it. See the user-profile
    skill for the read-before-write PATCH recipe.
-8. Keep the updates in steps 6–7 silent — the dashboard handles saving
+9. Keep steps 7–8 silent — the dashboard handles saving
    rules/management.md separately when the user approves the preview. Do
    not create or modify any other context files; the daemon seeds the
    rest of the primary-vault scaffold automatically.
@@ -218,6 +230,18 @@ write tone/style preferences into user/profile.md.
 
 ### rules/management.md Format
 
+Output language: follow `<output_language_policy>`. rules/management.md
+is Policy B — the section headers (`## Agent Identity`, `## Source of
+Truth`, `## Autonomy Levels`, `## Notification Rules`, `## Schedule`,
+`## Project Management`) are skeleton and stay English; the descriptive
+bullets under `## Autonomy Levels`, `## Notification Rules`, `## Schedule`,
+and `## Project Management` are written in `<settings primary_language>`.
+File-specific carve-outs that also stay English: the `## Agent Identity`
+field labels (`- AI name:`, `- WhatsApp label:`) — the daemon parses and
+rewrites this section; the Source of Truth table column headers and
+Domain-column row labels; and product/brand cells (`Google Calendar`,
+`Obsidian`, `Notion`, `today.md`, `projects/*.md`).
+
 Fill the Source of Truth table from the **derived rows you confirmed
 with the user in Step 0** (Schedule / Tasks / Notes / Projects).
 Generate using this format:
@@ -274,5 +298,8 @@ heading onto the end of the previous list item (e.g. `- Label:
 <value>## Next Section` on one line). Copy user-provided values as-is,
 then newline, blank line, then the next heading.
 
-**Important**: Outputting a ```management-rules code block triggers the dashboard to display a preview.
-The dashboard handles saving when the user approves, so you do NOT need to save via curl.
+**Important**: Do NOT curl-write rules/management.md to disk yourself.
+The dashboard persists it via `POST /setup/save-rules` when the user
+clicks Save & Finish. (The silent curl PUT to /api/context/user/profile
+in step 7 and the user/*.md PATCHes in step 8 ARE required — only the
+rules file is saved by the dashboard.)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aitne-sh/aitne",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "Aitne — a local-first, proactive personal AI agent. A long-running TypeScript daemon is the nervous system; Claude Code (or Codex / Gemini CLI) is the brain. All persistent memory lives in local Markdown files.",
   "keywords": [
     "ai",
@@ -31,16 +31,39 @@
   },
   "files": [
     "bin",
-    "scripts",
     "personal-agent.mjs",
     "agent-assets",
+    "scripts/start.mjs",
+    "scripts/run-node.mjs",
+    "scripts/browser.mjs",
+    "scripts/rm-paths.mjs",
+    "scripts/lib/",
+    "scripts/commands/*.mjs",
     "LICENSE",
     "README.md"
   ],
+  "scripts": {
+    "build": "turbo run build",
+    "start": "node bin/aitne.mjs start",
+    "stop": "node bin/aitne.mjs stop",
+    "restart": "node bin/aitne.mjs restart",
+    "status": "node bin/aitne.mjs status",
+    "logs": "node bin/aitne.mjs logs",
+    "dev": "node bin/aitne.mjs dev",
+    "doctor": "node bin/aitne.mjs doctor",
+    "audit": "node bin/aitne.mjs audit",
+    "test": "node scripts/check-redaction-coverage.mjs && vitest run --coverage",
+    "test:watch": "vitest",
+    "check:redaction": "node scripts/check-redaction-coverage.mjs",
+    "lint": "turbo run lint",
+    "typecheck:tests": "turbo run typecheck:tests",
+    "clean": "turbo run clean && node scripts/rm-paths.mjs node_modules .buildstamp",
+    "prepublishOnly": "pnpm run build"
+  },
   "dependencies": {
-    "@aitne/daemon": "0.1.4",
-    "@aitne/dashboard": "0.1.4",
-    "@aitne/shared": "0.1.4"
+    "@aitne/daemon": "workspace:*",
+    "@aitne/dashboard": "workspace:*",
+    "@aitne/shared": "workspace:*"
   },
   "devDependencies": {
     "@typescript-eslint/eslint-plugin": "^8.58.1",
@@ -52,27 +75,28 @@
     "typescript-eslint": "^8.58.1",
     "vitest": "^3.2.0"
   },
+  "packageManager": "pnpm@10.12.1",
+  "pnpm": {
+    "onlyBuiltDependencies": [
+      "esbuild",
+      "better-sqlite3",
+      "ffmpeg-static",
+      "onnxruntime-node",
+      "protobufjs"
+    ],
+    "overrides": {
+      "dompurify": ">=3.4.0",
+      "vite": "7.3.2",
+      "@anthropic-ai/sdk": ">=0.81.0",
+      "protobufjs": ">=7.5.5",
+      "axios": ">=1.16.0",
+      "fast-uri": ">=3.1.2"
+    }
+  },
   "publishConfig": {
     "access": "public"
   },
   "engines": {
     "node": ">=22.0.0"
-  },
-  "scripts": {
-    "build": "turbo run build",
-    "start": "node bin/aitne.mjs start",
-    "stop": "node bin/aitne.mjs stop",
-    "restart": "node bin/aitne.mjs restart",
-    "status": "node bin/aitne.mjs status",
-    "logs": "node bin/aitne.mjs logs",
-    "dev": "node bin/aitne.mjs dev",
-    "doctor": "node bin/aitne.mjs doctor",
-    "audit": "node bin/aitne.mjs audit",
-    "test": "node scripts/check-redaction-coverage.mjs && vitest run --coverage",
-    "test:watch": "vitest",
-    "check:redaction": "node scripts/check-redaction-coverage.mjs",
-    "lint": "turbo run lint",
-    "typecheck:tests": "turbo run typecheck:tests",
-    "clean": "turbo run clean && node scripts/rm-paths.mjs node_modules .buildstamp"
   }
-}
+}

package/scripts/check-redaction-coverage.mjs

@@ -1,109 +0,0 @@
-#!/usr/bin/env node
-// Roadmap §2.5 / §9.2 — redaction static guard.
-//
-// Fails (exit 1) if any production source file outside the single
-// permitted module (`auth-health-monitor.ts`) contains a raw SQL
-// assignment to `auth_detail` or `last_error`. The permitted module
-// owns the `writeAuthFailureDetail` / `writeAuthOkDetail` helpers,
-// which apply `redactSensitiveString` unconditionally — every other
-// caller is required to go through them.
-//
-// Exemptions:
-//   - test files (*.test.ts)         — they seed raw fixtures, not
-//                                       production writes
-//   - `auth-health-monitor.ts`        — the helpers themselves
-//
-// A match prints file:line:matching-line and exits non-zero. The full
-// scan runs in well under a second; it is intended to be wired into
-// `pnpm test`'s preamble (or a CI step) so that a new offending write
-// cannot silently land alongside a green test suite.
-
-import { execFileSync } from "node:child_process";
-import { fileURLToPath } from "node:url";
-import { dirname, relative, resolve } from "node:path";
-import { existsSync } from "node:fs";
-
-const here = dirname(fileURLToPath(import.meta.url));
-const root = resolve(here, "..");
-const searchRoot = resolve(root, "packages/daemon/src");
-
-if (!existsSync(searchRoot)) {
-  console.error(`check-redaction-coverage: ${searchRoot} does not exist`);
-  process.exit(1);
-}
-
-// Pattern matches any assignment target `auth_detail =` or
-// `last_error =`, regardless of placeholder style (`?` / `@name` /
-// `:name` / `NULL` / literal). The rg -P flag uses PCRE so we can
-// write a single union.
-const PATTERN = String.raw`(auth_detail|last_error)\s*=`;
-
-const EXEMPT_PATHS = new Set([
-  "packages/daemon/src/core/backends/auth-health-monitor.ts",
-  // `mail_accounts.last_error` is a separate column from the `backends`
-  // table's `last_error` that the redaction helpers guard. The redaction
-  // helper enforces scrubbing of model-auth detail strings; mail-poll
-  // errors are IMAP/Graph status messages that never carry secrets
-  // (credentials live in the encrypted blob store and are never inlined
-  // into error text — see mail-poller.ts `handlePollError`).
-  "packages/daemon/src/services/mail/account-registry.ts",
-]);
-
-let rgOutput = "";
-try {
-  rgOutput = execFileSync(
-    "rg",
-    [
-      "--no-heading",
-      "--line-number",
-      "--with-filename",
-      "--glob",
-      "!**/*.test.ts",
-      "--glob",
-      "!**/*.d.ts",
-      "-e",
-      PATTERN,
-      searchRoot,
-    ],
-    { encoding: "utf8" },
-  );
-} catch (err) {
-  // rg exits 1 when there are zero matches — that is the success case.
-  if (err.status === 1 && !err.stdout) {
-    process.exit(0);
-  }
-  // rg exits 2 on actual errors. Surface them.
-  console.error("check-redaction-coverage: rg failed");
-  console.error(err.stderr?.toString() ?? err.message);
-  process.exit(2);
-}
-
-const lines = rgOutput.split("\n").filter((line) => line.length > 0);
-const offenders = [];
-for (const line of lines) {
-  // Each rg line is `absolute-path:line:content`. Convert to a repo
-  // relative path so the exemption check is stable.
-  const firstColon = line.indexOf(":");
-  const secondColon = line.indexOf(":", firstColon + 1);
-  if (firstColon < 0 || secondColon < 0) continue;
-  const absPath = line.slice(0, firstColon);
-  const relPath = relative(root, absPath).replace(/\\/g, "/");
-  if (EXEMPT_PATHS.has(relPath)) continue;
-  offenders.push(`${relPath}:${line.slice(firstColon + 1)}`);
-}
-
-if (offenders.length > 0) {
-  console.error(
-    "check-redaction-coverage: found raw auth_detail / last_error writes outside the helper module.",
-  );
-  console.error(
-    "All writes must go through writeAuthFailureDetail / writeAuthOkDetail in packages/daemon/src/core/backends/auth-health-monitor.ts (roadmap §9.2).",
-  );
-  console.error("");
-  for (const line of offenders) {
-    console.error(`  ${line}`);
-  }
-  process.exit(1);
-}
-
-process.exit(0);