@aitne-sh/aitne 0.1.7 → 0.1.8

package/agent-assets/docs/guides/setup-wizard.md

@@ -12,16 +12,22 @@ summary: |
   Walks through the setup wizard step by step: profile, time axis,
   backend selection and API-key registration, messaging pairing,
   integrations, execution mode.
+section: setup-wizard
 tags:
+  - core
+  - guide
+  - getting-started
   - setup
+  - backends
 status: stable
 ask_examples:
   - What does each setup step do?
   - Can I rerun the setup wizard?
   - Do I have to connect every integration to start?
+  - Where do I paste my API key?
 locale: en-US
 created: 2026-04-25
-updated: 2026-05-04
+updated: 2026-05-15
 keywords:
   - setup
   - wizard
@@ -29,12 +35,16 @@ keywords:
   - cloud providers
   - bedrock
   - vertex
+  - foundry
+  - azure-openai
+  - opencode
+  - execution mode
 related:
   - getting-started/01-what-is-this
   - getting-started/02-first-steps
   - getting-started/04-first-day
   - concepts/safety-and-execution
-  - guides/use-cloud-providers
+  - concepts/backends-and-tiers
 ui_anchors:
   - /setup
 ---
@@ -49,7 +59,7 @@ the steps you have already filled in.
 
 ## Prerequisites
 
-- The daemon is launched (`pa start` or `pnpm start`).
+- The daemon is launched (`aitne start` or `pnpm start`).
 - The dashboard is reachable at `http://localhost:3000`.
 
 ## Steps
@@ -85,9 +95,10 @@ The provider dropdown picks one of:
   (Vertex AI).
 
 For non-direct providers, the form re-renders with the cloud-specific
-fields (region, project ID, AWS auth mode, deployment names, …). See
-[Use a Cloud Provider for Models](use-cloud-providers.md) for the
-full per-provider field reference.
+fields (region, project ID, AWS auth mode, deployment names, …). Refer
+to your cloud provider's enterprise / Vertex / Bedrock documentation
+for the value of each field; the daemon stores them in the OS keychain
+and mirrors the matching env vars into the backend subprocess.
 
 API key (or cloud-provider) registration is the recommended path
 because it is what Anthropic, OpenAI, and Google document for
@@ -120,8 +131,8 @@ Each integration is independently re-runnable from `/connections`.
 
 ### Step 7 — Routines
 
-Toggle which routines are enabled (morning, evening, weekly, monthly,
-hourly check) and pick the hours.
+Toggle which routines are enabled (morning, evening, weekly, hourly
+check) and pick the hours.
 
 ## Verification
 
@@ -131,7 +142,7 @@ hourly check) and pick the hours.
 
 ## If It Fails
 
-- A step that errors: check `pa logs` for the underlying daemon
+- A step that errors: check `aitne logs` for the underlying daemon
   message. Most failures are credential shape issues.
 - A backend that won't authenticate: see [Auth Failed](../troubleshooting/auth-failed.md).
 

package/agent-assets/docs/guides/switch-default-backend.md

@@ -3,6 +3,10 @@ schema_version: 1
 slug: guides/switch-default-backend
 title: Switch the Default Backend
 id: switch-default-backend
+aliases:
+  - switch backend
+  - change main backend
+  - switch claude codex gemini opencode
 category: guides
 summary: |
   Change the main backend the agent uses for most ProcessKeys, plus
@@ -12,6 +16,7 @@ section: switch-default-backend
 tags:
   - guide
   - backends
+  - operations
 status: stable
 ask_examples:
   - How do I switch from Claude to Codex?
@@ -19,11 +24,15 @@ ask_examples:
 locale: en-US
 created: 2026-04-25
 updated: 2026-05-04
+keywords:
+  - main backend
+  - switch backend
+  - default backend
+  - PUT /api/backends/main
 related:
   - concepts/backends-and-tiers
   - features/operations/backend-routing
   - guides/change-which-model-handles-x
-  - guides/use-cloud-providers
 ---
 
 # Switch the Default Backend

package/agent-assets/docs/guides/use-an-existing-obsidian-vault.md

@@ -25,6 +25,11 @@ ask_examples:
 locale: en-US
 created: 2026-05-12
 updated: 2026-05-12
+keywords:
+  - external vault
+  - existing obsidian vault
+  - point at vault
+  - wiki external
 related:
   - features/wiki/overview
   - guides/build-your-wiki

package/agent-assets/docs/reference/api.md

@@ -3,6 +3,11 @@ schema_version: 1
 slug: reference/api
 title: API Reference
 id: api-ref
+aliases:
+  - api reference
+  - rest api
+  - http api
+  - daemon api
 category: reference
 summary: |
   Aitne's daemon serves a Hono HTTP API on PA_API_PORT
@@ -12,13 +17,24 @@ section: api
 tags:
   - reference
   - api
+  - core
+  - operations
 status: stable
 ask_examples:
   - What endpoints does the daemon expose?
   - How do I read context files via API?
 locale: en-US
 created: 2026-04-25
-updated: 2026-04-25
+updated: 2026-05-16
+keywords:
+  - API
+  - REST
+  - endpoint
+  - Hono
+  - PA_API_PORT
+  - bearer token
+  - /api
+  - /api/wiki
 related:
   - reference/config
 ---
@@ -39,6 +55,7 @@ related:
 | Reading | `/api/books` | Reading list CRUD. |
 | Lifestyle | `/api/receipts`, `/api/travel-bookings`, `/api/travel-time` | Lifestyle data. |
 | Docs | `/api/docs/*` | Docs corpus + QA pipeline. |
+| Wiki | `/api/wiki/*` | Wiki workspaces, files, search (FTS5), index, estimate, compile preview, reindex. |
 | Dashboard | `/api/dashboard/*` | Dashboard config + state. |
 | SSE | `/api/chat/stream`, `/api/events/stream` | SSE streams. |
 | Health | `/api/health`, `/api/metrics` | Daemon liveness / metrics. |
@@ -46,6 +63,17 @@ related:
 
 Auth: bearer token written to the OS keychain at first launch.
 
+## Wiki — Phase 4 endpoints
+
+All wiki routes require an `x-process-key` header. Search and read endpoints accept DM-tier keys (`message.dm`, `message.mention`, `dashboard.chat`); writes and operator-level endpoints require `wiki.*` keys.
+
+| Method | Path | Purpose |
+|---|---|---|
+| GET | `/api/wiki/:ws/search?q=<term>&kind=fts\|grep&layer=<l>&limit=<n>` | Search the workspace. Default `kind=fts` (SQLite FTS5). `kind=grep` is the legacy substring fallback; empty queries automatically fall back to grep so callers can enumerate the vault. |
+| POST | `/api/wiki/:ws/reindex` | Operator escape hatch: rebuild the FTS5 index from disk. Requires a wiki-tier process key. |
+| GET | `/api/wiki/:ws/compile/preview?mode=incremental\|full` | Dry-run preview of `!compile`. Returns the predicted touch set (added / modified / unchanged), scaled cost estimate, and estimated duration. No agent session runs. |
+| GET | `/api/wiki/:ws/estimate?strategy=per-file\|flat` | Cost estimate for `!compile full`. Default `per-file` returns a token-level estimate (script-aware char→token approximation) with a top-N breakdown; `flat` returns the legacy P2 heuristic. |
+
 ## Related
 
 - [Config](config.md)

package/agent-assets/docs/reference/cli-commands.md

@@ -3,13 +3,21 @@ schema_version: 1
 slug: reference/cli-commands
 title: CLI Commands
 id: cli-commands
+aliases:
+  - cli
+  - commands
+  - aitne cli
+  - pnpm scripts
 category: reference
 summary: |
   Lookup table for the aitne / pnpm commands that drive the daemon and
   dashboard, plus the environment variables that override defaults.
+section: cli
 tags:
-  - cli
+  - core
   - reference
+  - cli
+  - operations
 status: stable
 ask_examples:
   - What command starts the daemon?
@@ -17,17 +25,25 @@ ask_examples:
   - How do I tail the daemon log?
   - Where does Aitne put its data?
   - How do I see what the agent has been doing?
+  - How do I check my install with aitne doctor?
 locale: en-US
 created: 2026-04-27
-updated: 2026-04-27
+updated: 2026-05-15
 keywords:
   - aitne start
   - aitne stop
+  - aitne restart
+  - aitne status
   - aitne logs
   - aitne doctor
   - aitne audit
+  - aitne setup
+  - aitne open
+  - aitne update
+  - aitne uninstall
   - pnpm start
   - PA_DATA_DIR
+  - PA_API_PORT
 related:
   - guides/install-and-run
   - guides/reinstall-cleanly
@@ -126,11 +142,14 @@ lives under `PA_DATA_DIR`, **not** inside the repo.
 ~/.personal-agent/
 ├── data/personal_agent.db    # SQLite (sessions, actions, observations, FTS)
 ├── context/                  # Markdown memory the agent reads and writes
-│   ├── user.md
+│   ├── user/profile.md       # user identity + topic slices alongside
 │   ├── today.md
 │   ├── roadmap.md
+│   ├── agent/journal.md
 │   ├── projects/
 │   ├── schedule/
+│   ├── daily/                # Per-day archives (YYYY-MM-DD.md)
+│   ├── rules/                # Management registry + policies index
 │   └── …
 ├── logs/                     # Daemon and dashboard logs
 └── pids/                     # Process IDs for aitne start/stop

package/agent-assets/docs/reference/config.md

@@ -3,23 +3,45 @@ schema_version: 1
 slug: reference/config
 title: Config Reference
 id: config-ref
+aliases:
+  - config
+  - AgentConfig
+  - settings keys
+  - runtime config
 category: reference
 summary: |
   All AgentConfig fields, their types, and where each is set
   (environment, database settings table, or in-process default).
 section: config
 tags:
+  - core
   - reference
   - config
+  - operations
 status: stable
 ask_examples:
   - What configuration keys does the agent expose?
   - Where does config get loaded from?
+  - How do I change the day boundary?
+  - Which config keys are runtime-editable from the dashboard?
 locale: en-US
+keywords:
+  - AgentConfig
+  - applyConfigUpdates
+  - dayBoundaryHour
+  - hourlyCheckIntervalMinutes
+  - quietHoursStart
+  - quietHoursEnd
+  - executeTimeoutMinutes
+  - autonomousDailyCostCapUsd
+  - allowedToolsOverride
+  - PA_DATA_DIR
+  - PA_API_PORT
 created: 2026-04-25
-updated: 2026-04-25
+updated: 2026-05-15
 related:
   - reference/api
+  - reference/cli-commands
 ---
 
 # Config Reference
@@ -49,22 +71,32 @@ A subset listed in `applyConfigUpdates` is mutable at runtime via
 | `disallowedTools` | string[] | absolute-block defaults |
 | `allowedToolsOverride` | string[] | empty |
 | `autonomousDailyCostCapUsd` | number | `0` (off) |
+| `hourlyCheckPrePassFreshnessMinutes` | number | freshness window for the hourly_check `harvestForGate` pre-pass (Layer 1) — skips per-integration fetch if `runtime_state.pre_pass_last_run:<key>` is fresher than this |
+| `monthlyReviewEnabled` | boolean | `false` (kill switch — routine.monthly_review stays registered but does not fire by default) |
+| `delegatedTaskHeavyEnabled` | boolean | `false` (Approve-tier opt-in — gates `delegated_task_heavy` ProcessKey) |
+| `voiceTranscriptionEnabled` | boolean | `false` (Whisper local transcription for voice attachments) |
+| `voiceTranscriptionPrimaryLanguage` | string | Whisper language code (see VOICE_LANGUAGE_FULL list) |
+| `claudeExecutionPermissionMode` | `"safe"`/`"allow"` | per-backend Safe/Allow posture set in the setup wizard |
+| `codexExecutionPermissionMode` | `"safe"`/`"allow"` | same; absolute-block layer overlays both modes |
+| `geminiExecutionPermissionMode` | `"safe"`/`"allow"` | same |
+| `opencodeExecutionPermissionMode` | `"safe"`/`"allow"` | per-backend mode for the OpenCode backend |
+| `opencodeBaseUrl` | URL string | OpenCode server URL (when self-hosted) |
+| `opencodeServerUsername` | string | OpenCode server username, default `"opencode"` |
 
 The runtime-mutable subset can be edited from `/settings/*`. Restart-only
-fields (e.g. `apiPort`) require `pa restart`.
+fields (e.g. `apiPort`) require `aitne restart`.
 
 ### Routine schedule keys do not exist
 
-Morning, evening, weekly, and monthly routines fire at fixed times in
+Morning, evening, and weekly routines fire at fixed times in
 `packages/daemon/src/core/scheduler.ts`. There is no `morningRoutineHour`,
-`eveningReviewHour`, `weeklyReviewDay`, or `monthlyReviewHour` config key.
+`eveningReviewHour`, or `weeklyReviewDay` config key.
 
 | Routine | Trigger |
 |---|---|
 | `routine.morning_routine` | daily at `dayBoundaryHour` |
 | `routine.evening_review` | daily at `18:00` local |
 | `routine.weekly_review` | Friday `18:00` local |
-| `routine.monthly_review` | last day of month at `18:00` local |
 
 Only the hourly check has a configurable cadence (`hourlyCheckIntervalMinutes`)
 and an active window (`hourlyCheckActiveStartHour` / `…ActiveEndHour`).

package/agent-assets/docs/reference/disallowed-tools.md

@@ -3,6 +3,11 @@ schema_version: 1
 slug: reference/disallowed-tools
 title: Disallowed Tools (Reference)
 id: disallowed-tools-ref
+aliases:
+  - disallowed tools
+  - blocked tools
+  - deny list
+  - absolute block
 category: reference
 summary: |
   The absolute-block tool patterns. Cannot be widened by config or
@@ -11,6 +16,7 @@ section: disallowed-tools
 tags:
   - reference
   - safety
+  - core
 status: stable
 ask_examples:
   - What can the agent never run?
@@ -18,6 +24,13 @@ ask_examples:
 locale: en-US
 created: 2026-04-25
 updated: 2026-04-26
+keywords:
+  - disallowedTools
+  - deniedTools
+  - absolute block
+  - always-disallowed
+  - Bash(rm -rf)
+  - PreToolUse
 related:
   - concepts/safety-and-execution
 ---

package/agent-assets/docs/reference/keyboard-shortcuts.md

@@ -3,6 +3,10 @@ schema_version: 1
 slug: reference/keyboard-shortcuts
 title: Keyboard Shortcuts
 id: keyboard-shortcuts
+aliases:
+  - keyboard shortcuts
+  - hotkeys
+  - key bindings
 category: reference
 summary: |
   Keyboard shortcuts available in the dashboard. The set is small by
@@ -11,12 +15,21 @@ section: keyboard-shortcuts
 tags:
   - reference
   - dashboard
+  - core
 status: stable
 ask_examples:
   - What keyboard shortcuts work in the dashboard?
 locale: en-US
 created: 2026-04-25
 updated: 2026-04-25
+keywords:
+  - shortcut
+  - hotkey
+  - Cmd+K
+  - Ctrl+K
+  - keyboard
+  - cmdk
+  - command palette
 related:
   - features/messaging/dashboard-chat
 ---

package/agent-assets/docs/reference/process-keys.md

@@ -6,49 +6,99 @@ id: process-keys-ref
 aliases:
   - process key list
   - dispatch keys
+  - processkey reference
+  - routine keys
 category: reference
 summary: |
   The full list of ProcessKeys, what triggers each, and the default
   tier. Mirrors packages/shared/src/process-key.ts.
 section: process-keys
 tags:
+  - core
   - reference
   - dispatch
+  - backends
+  - routing
 status: stable
 ask_examples:
   - List all the ProcessKeys
   - What is the default tier for hourly check?
+  - Which ProcessKeys are configurable from the dashboard?
+  - What is routine.fetch_window used for?
 locale: en-US
+keywords:
+  - processkey
+  - ProcessKey
+  - dispatch
+  - tier
+  - lite
+  - medium
+  - high
+  - routine.morning_routine
+  - routine.fetch_window
+  - message.dm
+  - calendar.change
+  - delegated_task
+  - gmail_classify
 created: 2026-04-25
-updated: 2026-04-25
+updated: 2026-05-15
 related:
   - concepts/process-keys
+  - concepts/backends-and-tiers
+  - features/operations/backend-routing
 ---
 
 # ProcessKeys
 
 | ProcessKey | Trigger | Default tier | Configurable |
 |---|---|---|---|
-| `routine.morning_routine` | Daily at `dayBoundaryHour` (default 04:00) | heavy | yes |
-| `routine.morning_routine_initial` | One-shot, fired once during the setup wizard's first day | heavy | no |
-| `routine.evening_review` | Daily at 18:00 local (fixed) | light | yes |
-| `routine.weekly_review` | Friday 18:00 local (fixed) | light | yes |
-| `routine.monthly_review` | Last day of month, 18:00 local (fixed) | light | yes |
-| `routine.hourly_check` | Every `hourlyCheckIntervalMinutes` (default 60) inside the active window | light | yes |
-| `routine.user_profile_sweep` | Periodic agent-day summarization pass | light | no |
-| `routine.today_refresh` | Mid-day re-check of `today.md` | light | no |
-| `routine.roadmap_refresh` | Periodic roadmap re-derivation | light | no |
+| `routine.morning_routine` | Daily at `dayBoundaryHour` (default 04:00). Parent envelope; LLM dispatch flows through the two stage keys below. | medium | yes |
+| `routine.morning_routine_today` | Stage A of the morning-routine pipeline — today.md synthesis, schedule fan-out, profile-question pick, user-editable checks. Stage A also populates roadmap.md from a daemon-prepared `<roadmap_skeleton>` block on the first-run branch (Phase 7 retired the heavy-tier `routine.morning_routine_initial`). | medium | yes |
+| `routine.morning_routine_journal` | Stage B of the morning-routine pipeline — authors `daily/<yesterday>.md` from the daemon-prepared journal skeleton. | lite | yes |
+| `routine.today_refresh` | Every 4h inside the active window — drift-refresh of `today.md` | medium | yes |
+| `routine.evening_review` | Daily at 18:00 local (fixed) | medium | yes |
+| `routine.weekly_review` | Friday 18:00 local (fixed) | medium | yes |
+| `routine.monthly_review` | Monthly cadence (gated OFF by default — kill switch `monthlyReviewEnabled` in runtime settings) | medium | no |
+| `routine.hourly_check` | Every `hourlyCheckIntervalMinutes` (default 60) inside the active window | medium | yes |
+| `routine.hourly_check.triage` | Stage 2 triage gate of every hourly check | lite | yes |
+| `routine.fetch_window` | Pre-pass fetcher spawned before each main routine | lite | yes |
+| `routine.user_profile_sweep` | Periodic agent-day profile summarization pass | medium | no |
+| `routine.roadmap_refresh` | Periodic roadmap re-derivation (NOT in `ROUTINE_WINDOWS` — no `routine.fetch_window` pre-pass; the synthesis session itself drives the native-mode MCP fan-out) | medium | yes |
+| `routine.skill_curation` | Background skill-curation / overlay refinement loop (cron cadence picked at `/settings/self-learning`) | medium | yes |
 | `routine.custom.<slug>` | Operator-defined recurrence (see [Custom Routines](../features/routines/custom-routines.md)) | configurable | yes |
-| `message.dm` | Owner DM | light | yes |
-| `message.mention` | @-mention in shared channel | light | yes |
-| `dashboard.chat` | `/chat` send | light | yes |
-| `dashboard.docs_qa` | Docs QA panel | light (forced) | yes (within forced light) |
-| `agent.task` | Future-dated agent action (recurring schedules) | light | yes |
-| `agent.dm_task` | DM-tone scheduled session (e.g. morning briefing) | light | yes |
-| `schedule.approaching` | Pre-event reminder | light | no |
-| `calendar.change` | Calendar event added / moved / cancelled | light | yes |
-| `gmail_classify` | Mail classifier inference | light | yes |
-| `setup` | Setup wizard one-shot | heavy | no |
+| `message.dm` | Owner DM | medium | yes |
+| `message.mention` | @-mention in a paired Slack channel where the agent is invited (DMs are `message.dm`; Telegram/WhatsApp groups are filtered out) | medium | yes |
+| `dashboard.chat` | `/chat` send | medium | yes |
+| `dashboard.docs_qa` | Docs QA panel — tier is hard-forced to medium regardless of any `message.dm` override; backend choice still inherits | medium (forced) | yes (backend only) |
+| `agent.task` | Future-dated agent action (recurring schedules) | medium | yes |
+| `agent.dm_task` | DM-tone scheduled session (e.g. morning briefing) | medium | yes |
+| `schedule.approaching` | Pre-event reminder | medium | no |
+| `calendar.change` | Calendar event added / moved / cancelled | lite | yes |
+| `gmail_classify` | Mail classifier inference | lite | yes |
+| `delegated_task` | Generic delegated sub-job invocation | lite | no (server-resolved) |
+| `delegated_task_heavy` | Opt-in heavy variant gated by `delegatedTaskHeavyEnabled` (Approve-tier) | high | no (server-resolved) |
+| `observation.summarize` | Per-observation summarizer (cost-reduction §A) | lite | yes |
+| `integration_drift_sync` | Periodic drift-reconciler across connected integrations | lite | no |
+| `knowledge.import` | One-shot heavy session that ingests an owner-uploaded knowledge file | medium | no |
+| `setup` | One-shot setup wizard backend probe / write | medium | no |
+| `git.lifecycle.poll` | Git repo poll observer | lite | yes |
+| `git.push.detected` | New push on a watched git repo | lite | yes |
+| `git.push.force_pushed` | Force-push detected on a watched repo | lite | yes |
+| `git.branch.created` | New branch on a watched repo | lite | yes |
+| `git.tag.created` | New tag on a watched repo | lite | yes |
+| `git.merge_to_default` | Merge into the default branch | lite | yes |
+| `git.local_ahead.stale` | Local branch ahead of remote for too long | lite | yes |
+| `git.project.{init,update,refresh_architecture,retemplate}` | Project-doc lifecycle hooks for watched repos (one-shot, generative — Sonnet by default) | medium | yes |
+| `github.assigned` | Issue / PR assigned to the operator | lite | yes |
+| `github.pull_request.review_requested` | PR review requested | lite | yes |
+| `github.workflow_run.failed` | CI run failed on a tracked repo | lite | yes |
+| `github.security_alert` | Dependabot / security alert raised | lite | yes |
+| `wiki.ingest_url` | URL → vault ingest (WIKI_BUILDER_DESIGN P1) | medium | yes |
+| `wiki.compile` | Raw → wiki synthesis (P1) | medium | yes |
+| `wiki.ask` | Q&A against the compiled wiki (P1) | medium | yes |
+| `wiki.lint` | Health pass over the wiki — writes `90_meta/health/<date>.md` | medium | yes |
+| `wiki.trace` | Chronological evolution of an idea across raw / wiki / outputs | medium | yes |
+| `wiki.connect` | Bridges two domains — writes `30_outputs/<date>-connect-<slug>.md` | medium | yes |
 
 "Configurable" = the operator can override the backend / tier on
 `/settings/models` (i.e. the key appears in `CONFIGURABLE_PROCESS_KEYS`).

package/agent-assets/docs/reference/skills.md

@@ -3,48 +3,67 @@ schema_version: 1
 slug: reference/skills
 title: Skills (Reference)
 id: skills-ref
+aliases:
+  - skill index
+  - built-in skills
+  - skill registry
 category: reference
 summary: |
   Index of built-in skills bundled with Aitne. Each maps to
   a SKILL.md under agent-assets/skills/<slug>/.
 section: skills
 tags:
+  - core
   - reference
   - skills
 status: stable
 ask_examples:
   - List all the built-in skills
   - What does the docs-search skill do?
+  - What does the wiki skill do?
+  - How is each skill scoped?
 locale: en-US
+keywords:
+  - skill
+  - skills
+  - SKILL.md
+  - skill registry
+  - overlay
+  - context skill
+  - mail skill
+  - wiki skill
+  - notify skill
 created: 2026-04-25
-updated: 2026-05-04
+updated: 2026-05-15
 related:
   - concepts/skills
-  - features/operations/skill-self-optimization
 ---
 
 # Built-in Skills
 
 | Slug | Purpose |
 |---|---|
+| `agent-actions` | Read the agent action log (`agent_actions` table) for retrospective audits. |
 | `attach` | Attach a generated or downloaded file to the agent's reply when the user expects a file artifact. |
-| `context` | Read / write context Markdown — projects, weekly/monthly summaries, agent journal, generic context files. |
+| `context` | Read / write context Markdown — projects, weekly summaries, agent journal, generic context files. |
 | `docs-search` | Read-only search and fetch over the operator-facing docs corpus. Used for `dashboard.docs_qa`. |
 | `external-services` | Call Google Calendar, the user's Obsidian vault, GitHub, or the agent Skills-management routes through the daemon proxy. |
-| `mail` | Unified multi-provider mail interface (Gmail, Outlook, Yahoo, iCloud) — search, label, classify. |
+| `mail` | Unified multi-provider mail interface (Gmail, Outlook, Yahoo, iCloud, generic IMAP) — search, label, classify. |
+| `gmail-lifestyle` | Conditional skill (gated by `gmailLifestyleActive` / `gmailLifestyleActiveForDm`). Merges travel-booking queries, calendar-event commute calculations, and receipt save-to-external-vault. |
+| `managed-tasks` | Register, modify, stop, or one-off-run a Managed Task (`mt_<n>`) — a recurring agent fetch against a third-party app (Zoom / Gmail / Drive / Notion / custom MCP). Conditional skill gated by `managedTasksActive` / `managedTasksActiveForDm`. |
 | `management-policy` | Capture a durable management rule from a DM ("every morning X", "from now on when Y, do Z"). Persists to the management policy store. |
 | `notify` | Send a notification through the paired messaging app and decide whether notifying is warranted. |
 | `notion` | Read, query, search, create, update, and archive Notion pages and databases. |
 | `observations` | Drain the pending-observations queue and inspect raw external-source change records. |
+| `project-doc` | Read / write per-project markdown files under `projects/<slug>.md`. |
 | `reading` | Query reading history and highlights; owns the reading-taste profile via the `books` and `reading_highlights` tables. |
-| `receipts` | Query and manage receipt / invoice attachments detected from Gmail; download and save to the external Obsidian vault. |
 | `roadmap` | Read / write `roadmap.md` (cross-request write lock). |
 | `schedule` | Schedule future agent wake-ups and DMs via the daemon (writes `agent_schedule` and `recurring_schedules` rows). |
+| `scheduled-managed-task` | Surface and act on Managed Tasks that are due now. |
 | `today` | Read or write `today.md` — morning routines, hourly checks, DMs that need a today snapshot. |
-| `travel` | Query the travel-bookings store (flights, hotels, restaurants, trains). |
-| `travel-time` | Estimate door-to-door travel time via Google Maps; calculate departure times. |
 | `user-interview` | Manage the profile-interview queue at `agent/profile-questions.md`; ask one question at a time. |
 | `user-profile` | Record user facts — identity, people, work, expertise, habits, goals — into the `user/*` slices. |
+| `wiki` | Build and maintain the personal wiki workspace — `!ingest` / `!compile` / `!ask` / `!lint` / `!trace` / `!connect`. |
 
 The source of truth is each skill's `SKILL.md` under
 `agent-assets/skills/<slug>/`. The `description` field in that file's
@@ -55,5 +74,4 @@ tables, search recipes, etc.) is also refined at runtime through
 JSON **overlays** maintained by the skill-curation loop. The seed
 files in `agent-assets/skills/` are never rewritten — overlays are
 applied at session-init by the SkillsCompiler and live under
-`<dataDir>/overlays/<skill>/<section-id>.json`. See
-[Skill Self-Optimization](../features/operations/skill-self-optimization.md).
+`<dataDir>/overlays/<skill>/<section-id>.json`.

package/agent-assets/docs/troubleshooting/auth-failed.md

@@ -22,6 +22,11 @@ ask_examples:
 locale: en-US
 created: 2026-04-25
 updated: 2026-05-04
+keywords:
+  - auth failed
+  - auth error
+  - subscription warning
+  - API key invalid
 related:
   - concepts/auth-health
   - concepts/costs-and-quotas
@@ -59,8 +64,8 @@ related:
    daemon mirrors it into `process.env` and re-probes immediately.
 4. If on the subscription fallback, the recommended fix is to
    register an API key on `/settings/models` (or one of the cloud-
-   provider options — see
-   [Use a Cloud Provider for Models](../guides/use-cloud-providers.md)).
+   provider options exposed on the same picker — Bedrock / Vertex /
+   Foundry / Azure OpenAI / Gemini-Vertex).
    If you cannot or do not want to, run the corresponding CLI login
    (`claude`, `codex login`, `gemini auth`) and the daemon picks up
    the new credentials on the next probe. Note that this fallback