@aitne-sh/aitne 0.1.11 → 0.1.13

package/agent-assets/docs/features/wiki/dashboard.md

@@ -23,8 +23,6 @@ section: wiki
 tags:
   - wiki
   - dashboard
-  - reference
-  - core
 status: stable
 ask_examples:
   - What does the /wiki page show?
@@ -37,7 +35,7 @@ ask_examples:
   - What does the Enable Wiki button do?
 locale: en-US
 created: 2026-05-21
-updated: 2026-06-07
+updated: 2026-07-01
 keywords:
   - /wiki
   - /wiki/timeline
@@ -82,12 +80,12 @@ process_keys:
 
 # Wiki Dashboard Surfaces
 
-The wiki has three distinct pages in the dashboard. The split mirrors
-Aitne's broader IA: content browsing lives under **My Life**,
-configuration lives under **Setup → Settings**. The pages share a
-single read path through the daemon's `/api/wiki/*` routes — every
+The wiki has three separate pages in the dashboard. The split mirrors
+how the rest of Aitne is organized: content you browse lives under
+**My Life**, and configuration lives under **Setup → Settings**. All
+three pages read through the same daemon routes (`/api/wiki/*`). Every
 request carries an `x-process-key: wiki.ask` header so the safety
-layer can attribute reads correctly.
+layer can record who is reading what.
 
 ## `/wiki` — workspace home
 
@@ -112,13 +110,13 @@ Two action buttons at the bottom of the card: **Timeline & health**
 
 ### 2. Index
 
-Renders the latest `20_wiki/_index.md`, the LLM-maintained catalogue
-of wiki pages. The agent rewrites this file at the end of every
-`!compile` run.
+Renders the latest `20_wiki/_index.md`, the running catalogue of wiki
+pages that the agent keeps up to date. The agent rewrites this file at
+the end of every `!compile` run.
 
 States:
-- **Empty** — no `_index.md` yet; the CTA tells you to run `!compile`
-  from a DM.
+- **Empty** — no `_index.md` yet; the card's call-to-action button
+  tells you to run `!compile` from a DM.
 - **Loaded** — the file is rendered verbatim as a monospaced code
   block (the index uses wikilink syntax, so rendering as markdown
   would lose information).
@@ -139,10 +137,10 @@ error toast.
 ### Disabled state
 
 When no `active=1` workspace exists in `wiki_workspaces`, the page
-shows an **Enable Wiki** CTA that jumps to `/settings/wiki`. The
-sidebar entry is always visible (gated only on the workspace
-catalogue being reachable), so this disabled state is reachable via
-the sidebar, a deep link, or browser history.
+shows an **Enable Wiki** button that jumps to `/settings/wiki`. The
+sidebar entry is always visible (it shows as long as the workspace
+list can be loaded), so you can still land on this disabled page from
+the sidebar, a shared link, or browser history.
 
 ## `/wiki/timeline` — full chronological history + health
 
@@ -172,9 +170,9 @@ log plus an **All commands** default. Entries render the same way
 they do in the `/wiki` recent-activity card — process-key badge,
 operation, path, timestamp.
 
-Both surfaces read live from the wiki API; the timeline page is a
-pure rendering pass over files the wiki skills already produce — no
-extra daemon-side schema backs them.
+Both surfaces read live from the wiki API. The timeline page simply
+displays files the wiki skills already write to disk — there is no
+separate database table behind it.
 
 ## `/settings/wiki` — configuration
 
@@ -186,9 +184,9 @@ A two-card chooser:
 
 - **Internal** (recommended) — managed by Aitne inside the context
   vault (default `<contextDir>/knowledge/wiki`, i.e.
-  `~/.personal-agent/context/knowledge/wiki`), schema seeded
-  automatically. The **Enable internal wiki** button turns it on with
-  nothing else to configure.
+  `~/.personal-agent/context/knowledge/wiki`), with the folder
+  structure set up for you. The **Enable internal wiki** button turns
+  it on with nothing else to configure.
 - **Existing Obsidian vault** (external) — point Aitne at a folder you
   already own via the path picker, then confirm with **Use this
   folder**.
@@ -222,7 +220,7 @@ The full configuration:
   model, turn limit, and per-run budget on each `wiki.*` process key
   (`wiki.ingest_url`, `wiki.compile`, `wiki.ask`, `wiki.lint`,
   `wiki.trace`, `wiki.connect`). All six default to the medium tier
-  (Claude Sonnet 4.6) with a sensible `maxTurns` / `maxBudgetUsd`; you
+  (Claude Sonnet 5) with a sensible `maxTurns` / `maxBudgetUsd`; you
   can override per key.
 - **Archive / delete** — archive keeps the row but flips `active=0`;
   delete drops the row (data on disk is untouched on external mode).

package/agent-assets/docs/features/wiki/overview.md

@@ -17,7 +17,6 @@ section: wiki
 tags:
   - wiki
   - knowledge
-  - core
 status: stable
 ask_examples:
   - What is the wiki?
@@ -26,7 +25,7 @@ ask_examples:
   - Can I point the wiki at my Obsidian vault?
 locale: en-US
 created: 2026-05-12
-updated: 2026-06-07
+updated: 2026-07-01
 keywords:
   - wiki
   - wiki workspace
@@ -88,10 +87,10 @@ and questions you ask it.
 The three commands you reach for daily:
 
 - **URL ingest**: send `!ingest <url>` from a paired DM channel; the wiki
-  agent fetches the source, summarises it, and stores a raw note.
+  agent fetches the source, summarizes it, and stores a raw note.
 - **Compile**: `!compile` (incremental) and `!compile full` (full
-  rebuild) turn raw notes into synthesised wiki articles with
-  cross-links and an `_index.md` catalogue.
+  rebuild) turn raw notes into synthesized wiki articles with
+  cross-links and an `_index.md` catalog.
 - **Ask**: `!ask <question>` searches the wiki and writes a cited
   answer under `30_outputs/`.
 
@@ -110,8 +109,9 @@ competes for budget with daily reactive memory.
 Aitne offers two modes:
 
 - **Internal** (recommended starting point) — the daemon owns the
-  vault at `$PA_DATA_DIR/context/knowledge/wiki`. No sandbox issues,
-  daemon-managed snapshots, isolated from iCloud sync conflicts.
+  vault at `$PA_DATA_DIR/context/knowledge/wiki`. No sandbox
+  permission issues, snapshots are managed for you, and it stays clear
+  of iCloud sync conflicts.
 - **External** — you point the wiki at an existing Obsidian vault on
   disk. The daemon writes directly when the filesystem allows, and
   falls back to the official Obsidian CLI when the vault sits in a
@@ -126,7 +126,7 @@ workspaces may not nest.
 - `00_inbox/` — human-only capture (the agent has read access but
   cannot write here).
 - `10_raw/` — source-faithful raw notes (append-only).
-- `20_wiki/` — synthesised wiki articles + `_index.md` catalogue.
+- `20_wiki/` — synthesized wiki articles + `_index.md` catalog.
 - `30_outputs/` — answer / report artifacts written by `!ask`.
 - `90_meta/` — taxonomy, schemas, lint reports, and the
   `import-<date>.md` migration record.
@@ -138,31 +138,23 @@ process keys can write wiki layers.
 ## Cost Safety
 
 `!compile full` rebuilds the entire wiki from raw notes and is the
-most expensive command. Before you run it, the dashboard shows a
-bracketed estimate — the optimistic (0.5×) and pessimistic (2×)
-multiples of the assumed input-token spend. If the pessimistic
-estimate exceeds the per-workspace threshold (default $2.00), the
-command escalates to the approval queue and requires your explicit
-confirmation before the compile starts. The pending-approval card
-surfaces on the dashboard home page (`/`), where you Approve or Deny
-it.
-
-On a git-tracked external vault, Aitne also runs
-`git add -A && git commit -m "aitne wiki: pre-compile snapshot <ts>"`
-on a clean working tree before the compile so you can roll back if
-the run produces a surprise. A dirty tree refuses the operation —
-commit or stash first.
+most expensive command, so Aitne guards it: the dashboard shows a cost
+estimate before you run it, a large run needs your approval (the
+per-workspace threshold defaults to $2.00), and a git-tracked external
+vault gets a snapshot commit first so you can roll back a surprising
+run. See [Cost estimation and approval](cost-and-approval.md) for the
+exact estimate math, the approval flow, and the pre-compile snapshot.
 
 ## Where it lives in the dashboard
 
 The wiki has two distinct surfaces in the dashboard. The split mirrors
-how Aitne organises the rest of the app — configuration lives under
+how Aitne organizes the rest of the app — configuration lives under
 **Setup → Settings**, day-to-day content browsing lives under **My
 Life** next to Knowledge / Reading / Git.
 
 | Page | Section | Use it for |
 |---|---|---|
-| `/wiki` | My Life | Workspace summary, the compiled `_index.md` catalogue, and the latest activity log. The page you open most often. |
+| `/wiki` | My Life | Workspace summary, the compiled `_index.md` catalog, and the latest activity log. The page you open most often. |
 | `/wiki/timeline` | My Life | Full chronological activity log plus the latest `!lint` health report. Linked from `/wiki` and from settings. |
 | `/settings/wiki` | Setup → Settings | Enable / archive a workspace, switch between internal and external mode, pick an external vault path, language, dispatch mode, write strategy, git auto-commit, approval threshold, per-command model selectors. |
 
@@ -196,7 +188,7 @@ This page is a high-level tour. For depth on a specific surface:
 - **[Commands reference](commands.md)** — every wiki bang command
   (`!ingest`, `!compile`, `!ask`, `!lint`, `!trace`, `!connect`,
   `!wiki`), the `@<workspace>` addressing token, dispatch modes, and
-  the disabled-state behaviour.
+  the disabled-state behavior.
 - **[Dashboard surfaces](dashboard.md)** — what `/wiki`,
   `/wiki/timeline`, and `/settings/wiki` actually render, where each
   card reads from on disk, and how the contextual help button maps

package/agent-assets/docs/features/wiki/search.md

@@ -21,9 +21,7 @@ summary: |
 section: wiki
 tags:
   - wiki
-  - search
-  - fts
-  - reference
+  - knowledge
 status: stable
 ask_examples:
   - How does !ask find the right wiki pages?
@@ -36,7 +34,7 @@ ask_examples:
   - What is fts_wiki?
 locale: en-US
 created: 2026-05-21
-updated: 2026-06-07
+updated: 2026-07-01
 keywords:
   - wiki search
   - fts_wiki
@@ -83,9 +81,9 @@ The wiki exposes two read paths the skills use to find content:
    A short, human-readable list with one bullet per wiki page, kept
    current by every `!compile` run. Good for "give me the lay of the
    land" queries.
-2. **`fts_wiki`** — a content-less SQLite FTS5 virtual table the
-   daemon syncs on every successful disk write. Good for "find any
-   page that mentions X" queries.
+2. **`fts_wiki`** — a full-text search index (a content-less SQLite
+   FTS5 virtual table) the daemon syncs on every successful disk
+   write. Good for "find any page that mentions X" queries.
 
 Both surfaces are read-only consumers; only `!compile` writes the
 catalogue, and only the wiki API write endpoints update `fts_wiki`.
@@ -139,9 +137,9 @@ CREATE VIRTUAL TABLE IF NOT EXISTS fts_wiki USING fts5(
 ```
 
 The `unicode61` tokenizer with `remove_diacritics 2` matches the
-mail FTS table for consistency. CJK content is handled by code-point
-breaking — searches work for Japanese, Chinese, Korean, and
-mixed-script wikis.
+mail FTS table for consistency. CJK (Chinese, Japanese, Korean)
+content is handled by code-point breaking, so searches work across
+those scripts and mixed-script wikis.
 
 ### Layer prefixes
 
@@ -157,9 +155,9 @@ The path classifier maps each on-disk file to one of six layers:
 Only four of these are actually indexed. `upsertWikiFulltextRow`
 **drops `log` and `inbox` rows** before insert: `log.md` is an
 append-only audit trail and `00_inbox/` is human-only, so indexing
-them would bury wiki and raw matches under log noise. So the values
-you ever see in `fts_wiki.layer` are `raw`, `wiki`, `output`, and
-`meta`.
+them would bury wiki and raw matches under log noise. So the only
+values you ever see in `fts_wiki.layer` are `raw`, `wiki`, `output`,
+and `meta`.
 
 Searches can filter by layer to restrict the result set — e.g.
 `layer=wiki` for only canonical pages, not raw notes.
@@ -173,7 +171,7 @@ evidence. The query supports:
 
 - `q` — the search query. Each whitespace-separated token is quoted
   and joined by implicit AND, so a multi-word query narrows the
-  result set. (Tokens are quoted to neutralise FTS5's `AND`/`OR`/
+  result set. (Tokens are quoted to neutralize FTS5's `AND`/`OR`/
   `NOT`/`NEAR` operator vocabulary — typing literally `rust AND go`
   matches those words, it does not parse as a boolean.)
 - `layer` — restrict to a single indexed layer (`raw` / `wiki` /
@@ -187,8 +185,8 @@ evidence. The query supports:
 
 Each result row carries `path`, `layer`, `title`, a body `snippet`
 (FTS5 `snippet()` output, `<mark>`-wrapped), `mtime` so the caller
-can rank by recency, and a BM25 `rank` (lower is better, `title`
-weighted above `body`).
+can rank by recency, and a BM25 relevance `rank` (lower is better,
+`title` weighted above `body`).
 
 There is no dashboard content-search bar today — the FTS surface is
 used by the agent, not the user UI. The dashboard timeline
@@ -222,7 +220,7 @@ A simplified flow for `!ask <question>`:
    question's key terms.
 2. It reads `10_raw/` notes only when the wiki pages need source
    verification.
-3. The LLM synthesises an answer from the pages it pulled.
+3. The LLM synthesizes an answer from the pages it pulled.
 4. The answer is written to
    `30_outputs/<YYYY-MM-DD>-<slug>.md` (the date-prefixed output
    shape the `OUTPUT_RE` path check enforces). The file records the

package/agent-assets/docs/features/wiki/workspaces.md

@@ -24,7 +24,6 @@ tags:
   - wiki
   - workspaces
   - config
-  - core
 status: stable
 ask_examples:
   - What is a wiki workspace?
@@ -37,7 +36,7 @@ ask_examples:
   - Can two wikis live in nested folders?
 locale: en-US
 created: 2026-05-21
-updated: 2026-06-07
+updated: 2026-07-01
 keywords:
   - wiki workspace
   - workspace
@@ -87,10 +86,10 @@ config_keys:
 # Wiki Workspaces, Vaults, and Write Strategy
 
 A **wiki workspace** is one row in the `wiki_workspaces` table plus
-the directory tree it points at. Aitne ships with no active
-workspace; the first run of the Enable flow creates one named
-`default`. Phase 5 unlocked multi-workspace — you can run as many
-side-by-side wikis as you have distinct knowledge domains.
+the directory tree it points at. Aitne starts with no active
+workspace. The first run of the Enable flow creates one named
+`default`. You can run as many side-by-side wikis as you have
+distinct knowledge domains — one per subject is a common setup.
 
 ## Internal vs external mode
 
@@ -109,8 +108,8 @@ Path-collision rules apply to both modes:
 - Two wiki workspaces may not nest — neither root can be inside the other.
 
 The dashboard probe (`POST /api/wiki/workspaces/probe`) runs these
-checks live before the workspace row is written and surfaces a
-human-readable error if any rule trips.
+checks live before the workspace row is written, and shows a
+plain-language error if any rule is broken.
 
 ## The layered layout
 
@@ -126,19 +125,19 @@ top-level subdirectories plus a workspace-root `log.md`:
 | `90_meta/` | Wiki agent | Taxonomy (`taxonomy.md`), schemas, health reports (`90_meta/health/<date>.md`), migration records (`90_meta/health/pre-migrate-<date>/`). |
 | `log.md` | Wiki agent (append-only) | One line per write. Drives the dashboard timeline. |
 
-The DM agent can read wiki search and index routes, but only the
+The DM agent can read the wiki search and index routes, but only the
 wiki process keys (`wiki.ingest_url`, `wiki.compile`, `wiki.ask`,
-`wiki.lint`, `wiki.trace`, `wiki.connect`) can write into these
-layers. The chokepoint is `POST /api/wiki/:workspace/files/:path` —
-the route validates the layer the path resolves into and rejects
-writes to `00_inbox/` unconditionally.
+`wiki.lint`, `wiki.trace`, `wiki.connect`) may write into these
+layers. Every write funnels through one route,
+`POST /api/wiki/:workspace/files/:path`, which checks which layer the
+path lands in and always rejects writes to `00_inbox/`.
 
 ## Multi-workspace addressing
 
-Every wiki bang command accepts an optional `@<name>` token
-immediately after the bang to target a specific workspace. The token
-is parsed before the command's own argument parser sees the rest, so
-multi-word topics and comma-separated arguments work as normal:
+Every wiki bang command takes an optional `@<name>` token right
+after the bang to aim at a specific workspace. Aitne reads this token
+before the command parses the rest of the line, so multi-word topics
+and comma-separated arguments still work as usual:
 
 ```
 !compile @research full
@@ -146,15 +145,15 @@ multi-word topics and comma-separated arguments work as normal:
 !connect @research diffusion models, score matching
 ```
 
-Omit the token and the command targets the **default** workspace —
-in practice the oldest active workspace (lowest id), which is the one
-named `default` on a fresh install, or the next-oldest active
-workspace if `default` has been archived.
+Leave the token off and the command targets the **default**
+workspace — in practice the oldest active workspace (lowest id). That
+is the one named `default` on a fresh install, or the next-oldest
+active workspace if `default` has been archived.
 
-A workspace name after `@` must start with a letter or digit and then
-contain only letters, digits, `.`, `_`, or `-` (max 64 chars). An
-invalid token is rejected with a usage error rather than silently
-falling back to the default.
+A workspace name after `@` must start with a letter or digit, and the
+rest may contain only letters, digits, `.`, `_`, or `-` (max 64
+chars). An invalid token gets a usage error rather than a silent
+fall-back to the default.
 
 See [guides/multiple-wikis-for-multiple-domains](../../guides/multiple-wikis-for-multiple-domains.md)
 for a walkthrough.
@@ -172,18 +171,18 @@ write. Three values:
   running). Used for external vaults that live in sandboxed
   locations (typically iCloud-synced vaults) where direct fs writes
   fail with `EPERM` / `EACCES` / `EROFS` / `EBUSY`.
-- **`auto`** — the resolver tries `fs` first, falls back to `cli`
-  on those sandbox error codes, and persists the resolved value back
-  to the row so subsequent writes skip the probe.
+- **`auto`** — tries `fs` first, falls back to `cli` on those
+  sandbox error codes, and saves the value it settled on back to the
+  row so later writes skip the check.
 
 Internal workspaces are pinned to `fs`. External workspaces start in
-`auto` and self-tune. You can override the resolved value from
-`/settings/wiki` if you need to force one path or the other (e.g. to
-test the CLI path on a non-sandboxed vault).
+`auto` and tune themselves. You can override the resolved value from
+`/settings/wiki` if you need to force one path or the other (for
+example, to test the CLI path on a non-sandboxed vault).
 
-The resolved strategy is surfaced in the workspace API response and
-on the `/settings/wiki` row, so you can always see which path
-(`fs` or `cli`) `auto` settled on. The full design is in
+The resolved strategy shows up in the workspace API response and on
+the `/settings/wiki` row, so you can always see which path (`fs` or
+`cli`) `auto` settled on. The full design is in
 WIKI_BUILDER_DESIGN.md §P2.B / §8.
 
 ## Dispatch mode (`parallel` / `serial`)
@@ -191,13 +190,13 @@ WIKI_BUILDER_DESIGN.md §P2.B / §8.
 `!ingest` honours the per-workspace **dispatch mode** in
 `/settings/wiki`:
 
-- **Parallel** (default): all URLs fan out simultaneously up to the
-  per-URL concurrency cap (`wiki_workspaces.concurrency_cap`, default
-  `3`, valid range 1–10). Fastest; small risk of bursting rate
-  limits at the URL host.
-- **Serial**: URLs are enqueued in submitted order; each agent
-  session starts only after the previous one completes. Slower but
-  predictable budget and rate.
+- **Parallel** (default): all URLs run at once, up to the per-URL
+  concurrency cap (`wiki_workspaces.concurrency_cap`, default `3`,
+  valid range 1–10). Fastest, with a small risk of tripping rate
+  limits at the URL's host.
+- **Serial**: URLs run in the order you submitted them; each agent
+  session starts only after the previous one finishes. Slower, but
+  the budget and request rate stay predictable.
 
 The acknowledgement DM tells you which mode ran
 (`in parallel` / `serially`).
@@ -205,10 +204,10 @@ The acknowledgement DM tells you which mode ran
 ## Language
 
 `wiki_workspaces.language` is the workspace's content language. It
-defaults to `en` and is independent of `runtimeSettings.primaryLanguage`
-— see WIKI_BUILDER_DESIGN.md §14 Q2 for the reasoning. You can pick
-any language tag from the picker in `/settings/wiki`; the value is
-passed to the wiki skills as the target language for compiled
+defaults to `en` and is separate from `runtimeSettings.primaryLanguage`
+— see WIKI_BUILDER_DESIGN.md §14 Q2 for the reasoning. Pick any
+language tag from the picker in `/settings/wiki`; Aitne passes that
+value to the wiki skills as the target language for compiled
 articles, ask answers, and trace / connect outputs.
 
 The wiki language does **not** cascade from your primary language at
@@ -217,16 +216,16 @@ wiki in English, and vice versa.
 
 ## Archive vs delete
 
-- **Archive** — flips `active=0` on the row but keeps the on-disk
+- **Archive** — sets `active=0` on the row but keeps the on-disk
   data and the row's metadata. Bang commands cannot target an
-  archived workspace; the dashboard hides it from the active list
-  but surfaces it in an "Archived" collapsible. You can unarchive by
-  re-enabling the workspace.
-- **Delete** — drops the row. On-disk data is **not** removed for
-  external workspaces (the daemon never deletes the user's vault).
-  For internal workspaces, the disk tree is also left in place under
-  `$PA_DATA_DIR/context/knowledge/wiki/<name>` — recover by re-creating
-  a workspace at the same name.
+  archived workspace; the dashboard hides it from the active list and
+  tucks it into an "Archived" collapsible. Re-enable the workspace to
+  unarchive it.
+- **Delete** — drops the row. The on-disk data is **not** removed for
+  external workspaces (the daemon never deletes your vault). For
+  internal workspaces, the disk tree is also left in place under
+  `$PA_DATA_DIR/context/knowledge/wiki/<name>` — to recover, create a
+  workspace again with the same name.
 
 ## Fields and defaults reference
 
@@ -250,5 +249,5 @@ Quick map between the dashboard knobs and the `wiki_workspaces` row:
 | Active | `active` | `1` |
 
 `dm_agent_write_enabled=0` is the safe default — the DM agent can
-only call the read-side wiki routes; writes happen inside dedicated
-`wiki.*` sessions spawned by bang commands.
+only call the read-side wiki routes. Writes happen inside dedicated
+`wiki.*` sessions that bang commands spawn.

package/agent-assets/docs/getting-started/01-what-is-this.md

@@ -18,7 +18,6 @@ summary: |
   Markdown files.
 section: getting-started
 tags:
-  - core
   - getting-started
   - backends
 status: stable
@@ -42,7 +41,7 @@ keywords:
   - markdown memory
   - backends
 created: 2026-04-25
-updated: 2026-05-28
+updated: 2026-07-01
 context_files:
   - state/today.md
   - plans/roadmap.md
@@ -59,7 +58,7 @@ related:
 # What is Aitne?
 
 Aitne is a local-first personal AI agent. It runs as a long-running
-daemon on your own machine, drives Claude Code, Codex CLI, Gemini
+background program (a daemon) on your own machine, drives Claude Code, Codex CLI, Gemini
 CLI, or OpenCode (`@opencode-ai/sdk` server) via provider API keys
 you register (with the CLI's local subscription login as a
 fallback), and keeps all of its memory as plain Markdown files under
@@ -122,7 +121,7 @@ decides what (if anything) is worth telling you about.
 
 - [Mail](../features/integrations/mail.md) — Gmail, Outlook, Yahoo,
   iCloud, or any IMAP server. Searches your messages locally via
-  FTS5. Auto-classifies into
+  FTS5 (SQLite's built-in full-text search). Auto-classifies into
   [reading list](../features/lifestyle/reading.md),
   [receipts](../features/lifestyle/receipts.md), and
   [travel bookings](../features/lifestyle/travel-bookings.md).
@@ -181,7 +180,7 @@ dashboard surfaces a warning whenever a backend is running on
 subscription auth.
 
 Each kind of work is mapped to a backend and a tier — most work runs
-on medium (Claude Sonnet 4.6 by default) and quick triage on lite
+on medium (Claude Sonnet 5 by default) and quick triage on lite
 (Claude Haiku 4.5). The high tier (Claude Opus 4.8) is registered but
 left unseeded; you opt into it per task from the dashboard. You can
 change any of this mapping at any time.

package/agent-assets/docs/getting-started/02-first-steps.md

@@ -14,7 +14,6 @@ summary: |
   pair a messaging app, and arrive at a green health pill.
 section: getting-started
 tags:
-  - core
   - getting-started
   - setup
 status: stable
@@ -31,7 +30,7 @@ keywords:
   - dashboard onboarding
   - health pill
 created: 2026-04-27
-updated: 2026-06-07
+updated: 2026-07-01
 related:
   - getting-started/01-what-is-this
   - getting-started/03-what-can-this-do
@@ -70,19 +69,19 @@ skippable in the wizard. Run through it once, top to bottom.
    the daemon claims you as the owner. See
    [Messaging Overview](../features/messaging/overview.md) for the
    list of supported apps and what each one does well.
-3. **Pick a main backend and register an API key.** Pick the LLM
+3. **Pick a main backend and register an API key.** This is the LLM
    the agent uses for "think hard" turns (Claude / Codex / Gemini /
-   OpenCode) and paste a provider API key — the supported way to run
-   a headless agent. If you skip the key, the daemon falls back to
-   whatever subscription login the matching CLI already has on your
-   machine; the dashboard surfaces a warning when this happens
-   because most providers do not support running agents on a
-   personal subscription. The same picker also lets you point the
+   OpenCode). Paste a provider API key — that is the supported way
+   to run the agent unattended (with no human signed in). If you skip
+   the key, the daemon falls back to whatever subscription login the
+   matching CLI already has on your machine, and the dashboard shows
+   a warning, because most providers do not support running agents on
+   a personal subscription. The same picker can instead point the
    backend at a cloud provider (Bedrock / Vertex / Foundry / Azure
-   OpenAI / Gemini-Vertex) instead of the direct API key — the
-   provider dropdown on `/settings/models` is the single surface for
-   both direct keys and cloud-provider credentials. Defaults are
-   sensible and can be changed later from `/settings/models`.
+   OpenAI / Gemini-Vertex) rather than a direct API key — the provider
+   dropdown on `/settings/models` is the single place for both direct
+   keys and cloud-provider credentials. The defaults are sensible, and
+   you can change them later from `/settings/models`.
    Background: [Backends and Tiers](../concepts/backends-and-tiers.md).
 4. **Skip integrations you do not need yet.** Mail, calendar, git,
    Notion, Obsidian are all optional and re-runnable any time from

package/agent-assets/docs/getting-started/03-what-can-this-do.md

@@ -14,7 +14,6 @@ summary: |
   granularity, with a link to the detailed feature doc for each.
 section: getting-started
 tags:
-  - core
   - getting-started
   - routines
   - messaging
@@ -35,7 +34,7 @@ keywords:
   - wiki
   - lifestyle
 created: 2026-04-27
-updated: 2026-05-28
+updated: 2026-07-01
 related:
   - getting-started/01-what-is-this
   - getting-started/02-first-steps
@@ -110,16 +109,17 @@ them — the agent reads what's there next time it runs.
 
 ## Build a personal wiki from what you DM
 
-A workspace-scoped builder turns URLs, pastes, and notes you send into a
-linked Markdown wiki. The raw capture, the synthesised article, and the
-cited answer all stay on disk and the agent only writes via the daemon
-API so the layout invariants hold.
+Send the agent URLs, pastes, or notes and it builds them into a linked
+Markdown wiki inside a dedicated workspace. The raw capture, the
+synthesized article, and any cited answer all stay as files on disk. The
+agent writes only through the daemon API, which keeps the folder layout
+consistent.
 
 - [Wiki Overview](../features/wiki/overview.md) — the workspace concept,
   the `00_inbox` / `10_raw` / `20_wiki` / `30_outputs` layers, and the
   approval gate on full rebuilds.
 - [Wiki Commands](../features/wiki/commands.md) — `!ingest` (capture
-  URLs), `!compile` (synthesise), `!ask` (cited Q&A), `!lint` /
+  URLs), `!compile` (synthesize), `!ask` (cited Q&A), `!lint` /
   `!trace` / `!connect` (audit, history, bridges), `!wiki` (status).
 - [Build Your Wiki](../guides/build-your-wiki.md) — the first-day
   walkthrough from empty workspace to first answered question.

package/agent-assets/docs/getting-started/04-first-day.md

@@ -15,7 +15,6 @@ aliases:
   - day zero
 section: getting-started
 tags:
-  - core
   - getting-started
   - setup
   - integrations
@@ -52,7 +51,7 @@ context_files:
 api_endpoints:
   - POST /api/knowledge/import
 created: 2026-04-25
-updated: 2026-06-10
+updated: 2026-07-01
 related:
   - getting-started/02-first-steps
   - getting-started/03-what-can-this-do
@@ -119,9 +118,9 @@ Send 3–5 DMs that read like introductions to a new assistant:
 
 The agent appends each fact to the right `identity/*.md` file (work
 facts → `identity/work.md`, people → `identity/people.md`, preferences →
-`identity/personal.md`, and so on). Identity-class facts (legal name,
-primary timezone) are deferred for your explicit confirmation
-rather than auto-written.
+`identity/personal.md`, and so on). Identity-class facts (your legal
+name, your primary timezone) wait for you to confirm them instead of
+being written automatically.
 
 ### Bootstrap from ChatGPT, Gemini, or anywhere else