@aitne-sh/aitne 0.1.7 → 0.1.8

package/agent-assets/docs/troubleshooting/dashboard-shows-degraded.md

@@ -3,6 +3,11 @@ schema_version: 1
 slug: troubleshooting/dashboard-shows-degraded
 title: Dashboard Shows Degraded
 id: dashboard-shows-degraded
+aliases:
+  - dashboard degraded
+  - degraded pill
+  - health pill red
+  - health degraded
 category: troubleshooting
 summary: |
   The DegradedBanner appears at the top of every page when the daemon
@@ -12,6 +17,7 @@ section: dashboard-shows-degraded
 tags:
   - troubleshooting
   - operations
+  - health
 status: stable
 ask_examples:
   - Why is the dashboard showing a degraded banner?
@@ -19,6 +25,12 @@ ask_examples:
 locale: en-US
 created: 2026-04-25
 updated: 2026-04-25
+keywords:
+  - degraded
+  - health pill
+  - /health
+  - auth health
+  - indexer degraded
 related:
   - troubleshooting/auth-failed
   - features/memory-files/today
@@ -41,7 +53,7 @@ related:
 
 ## Diagnostic Steps
 
-1. `pa logs` — search for the most recent error.
+1. `aitne logs` — search for the most recent error.
 2. Confirm `df -h` shows free space on the data directory.
 3. Check for a stale lock file in `~/.personal-agent/`.
 

package/agent-assets/docs/troubleshooting/fallback-keeps-firing.md

@@ -3,6 +3,10 @@ schema_version: 1
 slug: troubleshooting/fallback-keeps-firing
 title: Fallback Keeps Firing
 id: fallback-keeps-firing
+aliases:
+  - fallback firing
+  - backend fallback
+  - main backend down
 category: troubleshooting
 summary: |
   The router transitioned main → fallback for several runs in a row.
@@ -11,6 +15,7 @@ section: fallback-keeps-firing
 tags:
   - troubleshooting
   - backends
+  - routing
 status: stable
 ask_examples:
   - Why does the fallback keep running?
@@ -18,6 +23,11 @@ ask_examples:
 locale: en-US
 created: 2026-04-25
 updated: 2026-04-25
+keywords:
+  - fallback
+  - BackendQuotaError
+  - BackendDecisiveFailure
+  - router fallover
 related:
   - troubleshooting/auth-failed
   - troubleshooting/quota-exhausted

package/agent-assets/docs/troubleshooting/messaging-not-pairing.md

@@ -3,6 +3,10 @@ schema_version: 1
 slug: troubleshooting/messaging-not-pairing
 title: Messaging Not Pairing
 id: messaging-not-pairing
+aliases:
+  - pairing failed
+  - magic phrase not working
+  - messaging not paired
 category: troubleshooting
 summary: |
   The magic phrase isn't pairing your messaging account. Usually the
@@ -12,6 +16,7 @@ section: messaging-not-pairing
 tags:
   - troubleshooting
   - messaging
+  - pairing
 status: stable
 ask_examples:
   - Why isn't my magic phrase pairing?
@@ -19,6 +24,12 @@ ask_examples:
 locale: en-US
 created: 2026-04-25
 updated: 2026-04-25
+keywords:
+  - magic phrase
+  - owner channel
+  - pairing
+  - bot token
+  - OAuth
 related:
   - features/messaging/pairing-and-magic-phrase
   - features/messaging/overview

package/agent-assets/docs/troubleshooting/morning-routine-didnt-run.md

@@ -15,7 +15,8 @@ summary: |
 section: morning-routine-didnt-run
 tags:
   - troubleshooting
-  - routine
+  - routines
+  - autonomous
 status: stable
 ask_examples:
   - Why didn't my morning routine fire?
@@ -23,6 +24,10 @@ ask_examples:
 locale: en-US
 created: 2026-04-25
 updated: 2026-04-25
+keywords:
+  - morning routine didn't run
+  - morning routine skipped
+  - morning routine gate
 related:
   - features/routines/morning-routine
   - troubleshooting/auth-failed
@@ -39,7 +44,7 @@ related:
 
 ## Most Likely Causes (in probability order)
 
-1. **Daemon was stopped at the trigger time.** Check `pa status`.
+1. **Daemon was stopped at the trigger time.** Check `aitne status`.
 2. **Fallback failed too.** Look for a `fallback-failed` notification.
 3. **Heavy-tier quota exhausted on both backends.** See
    [Quota Exhausted](quota-exhausted.md).
@@ -53,11 +58,11 @@ related:
 
 ## Diagnostic Steps
 
-1. `pa status` — daemon up?
+1. `aitne status` — daemon up?
 2. `/activity` — any row for `routine.morning_routine`?
 3. `/settings/routines` — the routine list shows the next scheduled
    fire and recent runs.
-4. `pa logs` — search for `morning_routine`.
+4. `aitne logs` — search for `morning_routine`.
 
 ## Confirming the Fix
 

package/agent-assets/docs/troubleshooting/observation-not-detected.md

@@ -3,6 +3,11 @@ schema_version: 1
 slug: troubleshooting/observation-not-detected
 title: Observation Not Detected
 id: observation-not-detected
+aliases:
+  - observation missing
+  - no observations
+  - polling broken
+  - hourly check empty
 category: troubleshooting
 summary: |
   An expected change (commit, note, calendar move) didn't surface in
@@ -12,6 +17,7 @@ section: observation-not-detected
 tags:
   - troubleshooting
   - observations
+  - polling
 status: stable
 ask_examples:
   - Why didn't the agent notice my new commit?
@@ -19,6 +25,12 @@ ask_examples:
 locale: en-US
 created: 2026-04-25
 updated: 2026-04-25
+keywords:
+  - observation
+  - polling
+  - observer
+  - AgentWriteTracker
+  - hourly check
 related:
   - concepts/observations
   - features/integrations/git

package/agent-assets/docs/troubleshooting/quota-exhausted.md

@@ -24,10 +24,16 @@ ask_examples:
 locale: en-US
 created: 2026-04-25
 updated: 2026-05-04
+keywords:
+  - quota
+  - BackendQuotaError
+  - rate limit
+  - fallback fired
+  - 5h window
 related:
   - concepts/costs-and-quotas
   - concepts/auth-health
-  - guides/use-cloud-providers
+  - guides/switch-default-backend
 ---
 
 # Quota Exhausted

package/agent-assets/docs/troubleshooting/wiki-ingest-full-blocked.md

@@ -26,6 +26,11 @@ ask_examples:
 locale: en-US
 created: 2026-05-12
 updated: 2026-05-12
+keywords:
+  - wiki ingest blocked
+  - ingest cost gate
+  - ingest approval
+  - full rebuild blocked
 related:
   - features/wiki/commands
   - guides/budget-and-cost-for-wiki

package/agent-assets/docs/troubleshooting/wiki-write-failed.md

@@ -25,6 +25,11 @@ ask_examples:
 locale: en-US
 created: 2026-05-12
 updated: 2026-05-12
+keywords:
+  - wiki write failed
+  - wiki API failure
+  - wiki write lock
+  - external vault write
 related:
   - features/wiki/overview
   - guides/use-an-existing-obsidian-vault

package/agent-assets/optimizer-skills/drift-analysis/SKILL.md

@@ -16,7 +16,7 @@ Each is one row from `skill_curation_signals`:
   "skill_slug": "user-profile",
   "section_id": "topic-files",
   "signal_type": "structure_diff",
-  "payload": { "sub_kind": "heading_add", "target": "user/personal.md#健康記録" },
+  "payload": { "sub_kind": "heading_add", "target": "user/personal.md#health-log" },
   "observed_at": 1717000000000
 }
 ```

package/agent-assets/optimizer-skills/skill-curation/SKILL.md

@@ -37,7 +37,7 @@ Body:
   "skill_slug": "user-profile",
   "section_id": "topic-files",
   "payload": { "kind": "knowledge_layout", "files": [...] },
-  "rationale": "structure_diff observed `## 健康記録` heading on user/personal.md last week",
+  "rationale": "structure_diff observed `## Health Log` heading on user/personal.md last week",
   "signal_ids": [42, 47]
 }
 ```
@@ -65,7 +65,7 @@ Free-text fields (`convention_notes.rule`, `routing_table.note`,
 action. Examples:
 
 - ❌ "When the user mentions a doctor visit, write to user/personal.md"
-- ✅ "Doctor visits are recorded under `user/personal.md ## 健康記録`"
+- ✅ "Doctor visits are recorded under `user/personal.md ## Health Log`"
 - ❌ "Always include the date with the entry"
 - ✅ "Entries carry a `[YYYY-MM-DD]` prefix"
 - ❌ "Never use spaces in slugs"

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

@@ -0,0 +1,122 @@
+---
+name: agent-actions
+description: Load when the running session needs to write structured metadata into its own `agent_actions` row so daemon-side consumers (morning-routine AgentJournalAppender, anomaly surfacing, audit log) read structured data instead of parsing prose.
+allowed-tools:
+  - Bash(curl *)
+  - Read
+---
+
+# Agent self-reporting structured metadata
+
+The running session can patch structured metadata into the `agent_actions`
+row that records its own run. The daemon's morning-routine pipeline
+consumes that metadata to assemble `agent/journal.md` without parsing
+your final-text output — see `docs/design/appendices/morning-routine-
+optimization.md` §"Data-flow principle: prose vs structured".
+
+## When to call this
+
+Call exactly once near the end of your turn, after you have produced
+every other output. The endpoint is shallow-merge so repeated PATCHes
+within the same session accumulate — but the morning-routine task-flow
+expects a single consolidated call so the audit row reads cleanly.
+
+## Authentication
+
+<a id="self-write-auth"></a>
+
+The endpoint resolves your `agent_actions` row from two headers that
+the daemon's pa-api / curl shim auto-attaches inside a
+dispatcher-spawned session:
+
+- `x-pa-event-correlation-id` (from `PA_EVENT_CORRELATION_ID`) —
+  matches `agent_actions.event_id`.
+- `x-process-key` (from `PA_PROCESS_KEY`) — matches
+  `agent_actions.action_type`.
+
+When you call this from skill prose using `curl`, the shim handles
+header attachment for you — you do not type them. The endpoint returns
+`agent_actions.session_identity_missing` if either header is absent
+(the session is misconfigured) and `agent_actions.session_row_not_found`
+if no in-flight row matches your session — typically because the row
+has already settled to a terminal `result`, or because the dispatcher
+spawned the session without the pre-insert step that the morning
+routine's pipeline orchestrator owns. Surface as anomaly and continue.
+
+## Metadata shape
+
+<a id="metadata-shape"></a>
+
+The morning-routine Stage A is the primary caller. Its expected shape:
+
+| Field | Type | Purpose |
+|---|---|---|
+| `dayType` | `"weekday" \| "weekend" \| "focus" \| "off"` | The day-type Stage A derived. ⑥ AgentJournalAppender writes this into agent/journal.md's header line. |
+| `anomalies` | `string[]` | Free-form anomalies you encountered (e.g. "AgentPlan cardinality mismatch: today.md has 6 rows, batch had 5"). ⑥ surfaces these in agent/journal.md and `pnpm audit` filters on them. |
+| `filesTouched` | `string[]` | Paths your turn wrote to (e.g. `context/today.md`, `context/roadmap.md`). |
+| `inboxStats` | `{triaged, movedToScratch, dmConfirmsSent, secretsSkipped}` | Inbox triage counts from Step 4. All keys integers >= 0. `secretsSkipped` is collected but NOT rendered by ⑥; surface secret-skip events through `anomalies` as well so they reach the audit trail. |
+| `morningChecks` | `string[]` | Short labels for every Step 8 `routines/morning.md` extension check executed (e.g. `"water bottle filled"`). ⑥ joins these with `, ` into the `Checks from routines/morning.md:` bullet. Empty array → renders as `(none)`. |
+| `scheduleBatchSize` | `number` | Cardinality you observed when posting to `/api/schedule/batch`. Mirrors what was POSTed so ⑥ can detect cardinality mismatches against today.md. |
+
+The endpoint accepts any well-formed JSON object — these are the keys
+the morning-routine pipeline consumes. Skills can extend the shape
+informally; the daemon does not constrain field set.
+
+## Call shape
+
+```bash
+curl -s -X PATCH http://localhost:8321/api/agent-actions/self \
+  -H 'Content-Type: application/json' \
+  -d '{
+    "metadata": {
+      "dayType": "weekday",
+      "anomalies": [],
+      "filesTouched": ["context/today.md", "context/roadmap.md"],
+      "inboxStats": { "triaged": 4, "movedToScratch": 4, "dmConfirmsSent": 1, "secretsSkipped": 0 },
+      "morningChecks": ["water bottle filled", "calendar synced"],
+      "scheduleBatchSize": 5
+    }
+  }'
+```
+
+Success (200):
+```json
+{ "ok": true, "id": 1234, "metadata": { ...merged result... } }
+```
+
+## Errors
+
+Every error response uses the **agent-consumable envelope**:
+
+```jsonc
+{
+  "ok": false,
+  "summary": "Request rejected: agent_actions.session_identity_missing on headers.x-pa-event-correlation-id.",
+  "errors": [
+    {
+      "rowIndex": null,
+      "code": "agent_actions.session_identity_missing",
+      "field": "headers.x-pa-event-correlation-id",
+      "received": "<missing>",
+      "expected": "x-pa-event-correlation-id and x-process-key headers identifying the running session",
+      "hint": "The pa-api shim auto-injects these from PA_EVENT_CORRELATION_ID and PA_PROCESS_KEY when running inside a dispatcher-spawned session.",
+      "skillAnchor": "agent-actions#self-write-auth",
+      "severity": "error"
+    }
+  ],
+  "retryable": false
+}
+```
+
+### Codes the endpoint can emit
+
+| Code | When | Fix |
+|---|---|---|
+| `agent_actions.session_identity_missing` | `x-pa-event-correlation-id` or `x-process-key` header is absent / empty. | Running inside a dispatcher-spawned session the pa-api shim attaches both headers from env. If you see this, the session is misconfigured — surface it as an anomaly via `<safety_violation>` and stop. Not retryable in the same turn. |
+| `agent_actions.session_row_not_found` | No in-flight `agent_actions` row matches `(event_id, action_type)`. | Either the row has already settled to a terminal result (success/failed/partial) and your PATCH arrived late, or the dispatcher spawned this session without the orchestrator-side pre-insert that the morning-routine pipeline relies on. Either way, the PATCH cannot land — surface as anomaly and continue. Not retryable. |
+| `agent_actions.body_not_object` | Request body is not a JSON object. | POST `{"metadata":{…}}`. |
+| `agent_actions.metadata_field_invalid` | `metadata` slot is missing, not an object, an array, or carries non-JSON-serialisable values (functions, Symbols, BigInts). | Pass a plain JSON object literal. Arrays go inside named keys (e.g. `anomalies:[…]`). |
+
+`retryable:false` means the agent should NOT retry the same call; it
+should surface the failure as a structured anomaly (via this endpoint's
+`anomalies` field when accessible) or DM the operator.

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

@@ -1,7 +1,6 @@
 ---
 name: attach
 description: Load when the reply should embed a file (generated md/PDF/CSV, chart image, modified upload) — `Write` to disk alone is not delivery.
-when_to_use: The only channel that delivers a file alongside chat. Skip if the user only needs the path mentioned, not the bytes attached.
 allowed-tools:
   - Bash(curl *)
   - Write
@@ -85,7 +84,7 @@ Per-turn total across all attachments is capped at **100 MB**; the endpoint retu
 ## Workflow
 
 1. Decide the filename and caption up front (literal strings — no shell interpolation).
-2. Generate the content and write it with the `Write` tool. Use `/tmp/<name>` as the path; never write into the session workdir or the context dir.
+2. Generate the content and write it with the `Write` tool. Use `/tmp/<name>` as the path only — every other path (`~/`, session workdir, context dir, `/var/`, `/Users/...`) is denied by the absolute-block layer (`packages/daemon/src/safety/always-disallowed.ts`). Never write into the session workdir or the context dir.
 3. Issue the single curl POST shown above. One file per call.
 4. Branch on the response:
    - Success (`{"id": "..."}`) — mention the attachment in your reply, e.g. `"Attached: weekly-summary.md"`. You may discard the id; the daemon links it to your message automatically.