@aitne-sh/aitne 0.1.12 → 0.1.13

package/agent-assets/docs/features/routines/weekly-review.md

@@ -19,7 +19,6 @@ tags:
   - routines
   - autonomous
   - journal
-  - reflection
 status: stable
 ask_examples:
   - When does the weekly review run?
@@ -27,7 +26,7 @@ ask_examples:
   - Where do weekly retros get stored?
 locale: en-US
 created: 2026-04-25
-updated: 2026-06-10
+updated: 2026-07-01
 keywords:
   - weekly review
   - Friday review
@@ -58,49 +57,54 @@ context_files:
 
 ## In One Sentence
 
-A medium-tier weekly retro fires every Friday evening and writes a
-synthesis into `journal/weekly/YYYY-Www.md` (ISO week), whose
-**Carry Over / Next Week Focus / Lessons** sections are then lifted
-into every morning routine of the following ISO week.
+Every Friday evening, a medium-tier weekly retrospective (a look back
+over the week) runs and writes a summary into
+`journal/weekly/YYYY-Www.md` — one file per ISO week (the standard
+Mon–Sun week numbering). Its **Carry Over / Next Week Focus /
+Lessons** sections are then copied into every morning routine of the
+following ISO week.
 
 ## What It Does
 
 - Reads each `journal/daily/YYYY-MM-DD.md` for the current ISO week,
   the week's calendar retrospective, the roadmap, and active projects.
-- Synthesizes three axes — Outcomes, Forward items, Behavioral
-  Lessons — and writes the user-facing snapshot.
-- Appends an agent-internal block to `journal/agent.md` for
+- Pulls this together along three lines — Outcomes, Forward items,
+  and Behavioral Lessons — and writes the summary you read.
+- Adds a private, agent-only block to `journal/agent.md` covering
   self-critique, filter quality, and improvement ideas.
-- Feeds the learning loop: for each concrete, actionable system
-  improvement idea it identifies, it also posts a `source=self_critique`
-  feedback signal (in addition to the `journal/agent.md` prose), so the
-  idea is consolidated into the [agent lessons](../memory-files/agent-lessons.md)
-  rather than only living in the journal.
-- Judges the daemon's self-tuning recommendations: when the weekly
-  pre-step finds a cost knob worth changing (e.g. raising the mail
-  pre-pass freshness window because most fetches came back empty), it
-  injects up to three bounded proposals and the review records an
-  apply / reject / defer verdict for each. While `selfTuningEnabled` is
-  `false` (the default) nothing is ever changed automatically — verdicts
-  are recorded for the owner to review (shadow mode). With the flag on,
-  an apply verdict is actuated immediately by the daemon within hard
-  per-key bounds; the owner gets a one-line DM per applied change
-  (`!revert tuning` undoes the latest one) and a daily monitor
-  auto-reverts any change whose 7-day follow-up metrics regressed.
-- Sends a brief Friday-evening notification by default (the silence
-  gate triggers only on an essentially blank week).
-- Refreshes `identity/reading-taste.md` and Book Candidates when
-  enough new highlights have accumulated.
+- Feeds the learning loop: for each concrete, actionable improvement
+  idea it finds, it also posts a `source=self_critique` feedback
+  signal (on top of the `journal/agent.md` note), so the idea gets
+  folded into the [agent lessons](../memory-files/agent-lessons.md)
+  instead of only living in the journal.
+- Reviews the daemon's self-tuning suggestions: when the weekly
+  pre-step spots a cost setting worth changing (for example, widening
+  the mail pre-pass freshness window because most fetches came back
+  empty), it puts forward up to three bounded proposals, and the
+  review records an apply / reject / defer verdict for each. While
+  `selfTuningEnabled` is `false` (the default), nothing changes
+  automatically — the verdicts are only recorded for the owner to
+  review (this is called shadow mode). With the flag on, an apply
+  verdict takes effect immediately, kept inside hard per-key limits;
+  the owner gets a one-line DM for each applied change
+  (`!revert tuning` undoes the most recent one), and a daily monitor
+  automatically rolls back any change whose 7-day follow-up metrics
+  got worse.
+- Sends a short Friday-evening notification by default. It stays quiet
+  (the silence gate) only when the week was essentially blank.
+- Refreshes `identity/reading-taste.md` and your Book Candidates once
+  enough new highlights have piled up.
 
 ## When It Runs / How It Is Triggered
 
-Every **Friday at 19:00 local time** (one hour after `evening_review`).
-The schedule is fixed in `packages/daemon/src/core/scheduler.ts` and is
-not operator-configurable. If the Friday fire misses (daemon outage),
-the **Fri / Sat / Sun catch-up window** in `schedule-helpers.ts` fires
-the retro when the daemon recovers, before the new ISO week begins —
-a Mon–Thu catch-up is intentionally out of scope so the next week's
-`<previous_week>` injection stays stable Mon–Sun.
+It runs every **Friday at 19:00 local time**, one hour after
+`evening_review`. The schedule is fixed in
+`packages/daemon/src/core/scheduler.ts` and can't be changed. If the
+Friday run is missed (say, the daemon was down), the **Fri / Sat / Sun
+catch-up window** in `schedule-helpers.ts` runs the retro as soon as
+the daemon recovers, before the new ISO week begins. A Mon–Thu
+catch-up is left out on purpose, so the next week's `<previous_week>`
+injection stays a stable Mon–Sun.
 
 ## What It Outputs
 
@@ -111,25 +115,27 @@ a Mon–Thu catch-up is intentionally out of scope so the next week's
 
 ## Configuration
 
-The fire time (Friday 19:00 local) and day-of-week are fixed in code
-and are not operator-tunable. The backend and model that handle this
-routine, however, are configurable: `routine.weekly_review` is a
-configurable process key (default **medium** tier — Sonnet on Claude)
-that you can repoint from **Settings → Models**. The weekly rulebook
+The run time (Friday 19:00 local) and the day of the week are fixed in
+code and can't be changed. What you *can* change is the backend and
+model behind this routine: `routine.weekly_review` is a configurable
+process key (default **medium** tier — Sonnet on Claude) that you can
+repoint from **Settings → Models**. The weekly rulebook
 (`policies/routines/weekly.md`) is edited on the weekly-review agent's
-Rulebook tab (`/agents/weekly-review?tab=rulebook`), where the agent
-can also be enabled or disabled.
+Rulebook tab (`/agents/weekly-review?tab=rulebook`), where you can also
+enable or disable the agent.
 
 ## When Something Goes Wrong
 
-- The retro **doesn't fire on Friday**: the Fri–Sun catch-up window
-  retries on Saturday and Sunday agent-days. A full Fri–Sun outage
-  results in a missing weekly file; the next week's morning routines
-  proceed without the `<previous_week>` block.
-- The retro **runs but the file is empty** (silence gate): legitimate
-  for a blank week — the file is still written with empty sections,
-  and the next week's morning routine sees `(none recorded)` sub-
-  blocks, which is the deliberate downstream signal.
+- The retro **doesn't run on Friday**: the Fri–Sun catch-up window
+  retries on the Saturday and Sunday agent-days (the agent's own day,
+  which rolls over at `dayBoundaryHour` rather than at midnight). If
+  the daemon is down for the whole Fri–Sun window, the weekly file is
+  never written, and the next week's morning routines simply carry on
+  without the `<previous_week>` block.
+- The retro **runs but the file is empty** (the silence gate): this is
+  fine for a genuinely blank week — the file is still written, just
+  with empty sections, and the next week's morning routine sees
+  `(none recorded)` sub-blocks. That is the intended signal, not a bug.
 
 ## Related
 

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

@@ -21,8 +21,6 @@ summary: |
 section: wiki
 tags:
   - wiki
-  - bang-commands
-  - core
 status: stable
 ask_examples:
   - How do I send a URL to the wiki?
@@ -34,7 +32,7 @@ ask_examples:
   - How do I bridge two domains with `!connect`?
 locale: en-US
 created: 2026-05-12
-updated: 2026-06-07
+updated: 2026-07-01
 keywords:
   - !ingest
   - !compile
@@ -48,6 +46,7 @@ keywords:
 related:
   - features/wiki/overview
   - features/messaging/bang-commands
+  - features/wiki/cost-and-approval
   - guides/budget-and-cost-for-wiki
   - guides/maintain-wiki-health
   - guides/explore-with-trace-and-connect
@@ -67,9 +66,10 @@ ui_anchors:
 
 # Wiki Commands
 
-Use these from a paired DM channel after enabling the wiki. Open
+These are bang commands — chat messages that start with `!`. Send
+them from a paired DM channel once the wiki is turned on. Open
 **Settings → Wiki** (`/settings/wiki`) to enable a workspace, then
-browse the result from **My Life → Wiki** (`/wiki`).
+read the results under **My Life → Wiki** (`/wiki`).
 
 | Command | Effect |
 |---|---|
@@ -91,17 +91,17 @@ batch at 10 URLs.
 ## `@<workspace>` — addressing a non-default workspace
 
 If you run more than one wiki workspace (Phase 5), every bang command
-accepts an optional `@<name>` token immediately after the bang. 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:
+accepts an optional `@<name>` token right after the bang. Aitne reads
+this token first and removes it before the command parses the rest of
+your message, so multi-word topics and comma-separated arguments still
+work as usual:
 
     !compile @research full
     !ask @parenting what did the pediatrician recommend?
     !connect @research diffusion models, score matching
 
 Omit the token and the command targets the **default** workspace.
-See `agent-assets/docs/guides/multiple-wikis-for-multiple-domains.md`
+See [guides/multiple-wikis-for-multiple-domains](../../guides/multiple-wikis-for-multiple-domains.md)
 for a walkthrough.
 
 ## `!compile --preview` — the dry run
@@ -119,14 +119,15 @@ Use `!compile --preview` (or `--dry-run`) when you want to see what
 - **est. duration** — Rough wall-clock estimate (intentionally
   pessimistic).
 
-The preview is an upper bound. The compile is an LLM and may
-merge or skip pages inside the agent loop; the preview cannot
-predict that exactly, but it will not undercount the touch set.
-Reply `!compile` (or `!compile full`) to actually run the compile.
+Treat the preview as an upper bound. The real compile runs an LLM,
+which may merge or skip pages as it works, so the preview cannot
+predict the outcome exactly — but it will never undercount the pages
+it touches. Reply `!compile` (or `!compile full`) to run the compile
+for real.
 
 ## Dispatch Mode for `!ingest`
 
-`!ingest` honours the per-workspace **dispatch mode** in
+`!ingest` follows the per-workspace **dispatch mode** set in
 Settings → Wiki:
 
 - **Parallel** (default): all URLs fan out simultaneously up to the
@@ -142,8 +143,8 @@ The acknowledgement DM names the mode that ran (`in parallel` /
 
 ## `!compile full` — the Cost Gate
 
-Full rebuilds touch every wiki note and are the most expensive
-command in the wiki surface. The flow:
+Full rebuilds touch every wiki note, so they are the most expensive
+command in the wiki surface. Here is what happens when you run one:
 
 1. The bang handler estimates the cost (per raw note, an on-disk
    char→token approximation × Sonnet 5 input price, bracketed
@@ -160,15 +161,20 @@ command in the wiki surface. The flow:
 4. Otherwise, the run starts autonomously and you receive a
    completion DM with actual spend.
 
-The same estimate is shown live in **Settings → Wiki** so you can
-see what the next `!compile full` will cost before you run it.
+The same estimate is shown live in **Settings → Wiki**, so you can
+see what the next `!compile full` will cost before you run it. See
+[features/wiki/cost-and-approval](cost-and-approval.md) for the full
+cost-estimation and approval reference.
 
 ## Operational Triad — `!lint`, `!trace`, `!connect`
 
 These three commands round out the wiki surface for ongoing
 maintenance and exploration. None of them write to the content
 layers (`10_raw/`, `20_wiki/`); they only produce health reports
-(`90_meta/health/`) or output documents (`30_outputs/`).
+(`90_meta/health/`) or output documents (`30_outputs/`). This
+section is the command reference; for the step-by-step workflows,
+see [guides/maintain-wiki-health](../../guides/maintain-wiki-health.md)
+and [guides/explore-with-trace-and-connect](../../guides/explore-with-trace-and-connect.md).
 
 ### `!lint`
 
@@ -197,7 +203,7 @@ Timeline & health** (`/wiki/timeline`).
 ### `!trace <topic>`
 
 Reconstructs the chronological evolution of an idea across every
-wiki layer. Use a free-form topic — the skill canonicalises against
+wiki layer. Use a free-form topic — the skill matches it against
 `90_meta/taxonomy.md` before deriving the output slug:
 
 ```

package/agent-assets/docs/features/wiki/cost-and-approval.md

@@ -25,7 +25,6 @@ tags:
   - cost
   - approval
   - safety
-  - core
 status: stable
 ask_examples:
   - How does !compile full estimate cost?
@@ -39,7 +38,7 @@ ask_examples:
   - Can I see the cost before running !compile full?
 locale: en-US
 created: 2026-05-21
-updated: 2026-06-07
+updated: 2026-07-01
 keywords:
   - cost estimate
   - cost bracket
@@ -106,26 +105,30 @@ The same estimator backs four surfaces so the numbers cannot drift:
 
 ## How the estimator works
 
-Pure JS, no agent session, no SDK call. The estimator
-(`packages/daemon/src/core/wiki/cost-estimate.ts`) opens each raw
-note under `10_raw/`, approximates its token count from on-disk
-content, then multiplies the total by the tier unit cost and
-brackets with 0.5×/2× multipliers.
+The estimate is plain JavaScript math — it never starts an agent or
+calls the model, so it costs nothing and returns instantly. The
+estimator (`packages/daemon/src/core/wiki/cost-estimate.ts`) opens
+each raw note under `10_raw/`, approximates its token count from the
+text on disk, then multiplies the total by the tier unit cost and
+wraps it in a 0.5×/2× bracket (a low/high range).
 
 ### Character → token approximation
 
-- **Latin / English content** — ~4 chars per token. The well-known
-  OpenAI rule-of-thumb; matches Anthropic's tokenizer within ±15%
-  for prose; confirmed against the gpt-tokenizer dist.
-- **CJK content** — ~1.5 chars per token. BPE merges short CJK runs
-  but not as aggressively as Latin word fragments.
-
-The classifier counts Unicode code points whose script is one of
-Han, Hiragana, Katakana, Hangul, Bopomofo. If the document is
-majority-CJK we apply the CJK divisor to the entire file; otherwise
-Latin. A per-script split per file would be marginally more accurate
-but adds 30% code for a sub-percent gain on typical mixed-script
-files.
+- **Latin / English content** — about 4 characters per token. This
+  is the well-known OpenAI rule-of-thumb; it matches Anthropic's
+  tokenizer within ±15% for prose, confirmed against the
+  gpt-tokenizer package.
+- **CJK content** (Chinese, Japanese, Korean) — about 1.5 characters
+  per token. The tokenizer merges short CJK runs, but not as
+  aggressively as it merges Latin word fragments, so each character
+  carries more weight.
+
+To pick a ratio, the classifier counts the Unicode code points whose
+script is one of Han, Hiragana, Katakana, Hangul, or Bopomofo. If a
+file is majority-CJK, the CJK ratio applies to the whole file;
+otherwise the Latin ratio does. Splitting each file script-by-script
+would be slightly more accurate, but it adds 30% more code for a
+sub-percent gain on typical mixed-script files, so we don't.
 
 ### The 0.5×/2× bracket
 
@@ -188,7 +191,8 @@ estimate landed to the actual cost.
 
 ## The pre-compile git snapshot
 
-Only meaningful on an **external + git-tracked** vault. The gate
+This only matters for an **external + git-tracked** vault — a vault
+stored outside Aitne whose folder is a git repository. The gate
 decides:
 
 | Workspace state | Outcome |
@@ -202,9 +206,10 @@ decides:
 The snapshot is your rollback target if `!compile full` produces a
 surprise — `git reset --hard <snapshot-commit>` puts the vault back.
 
-The pre-compile commit uses no special author identity; it lands
-under whatever git is configured to use. If you co-author with
-Aitne, you'll want to set that up at the git config level.
+The pre-compile commit uses no special author identity — it lands
+under whatever name and email your git is already configured to use.
+If you want to credit Aitne as a co-author, set that up in your git
+config.
 
 ## The `--preview` dry-run
 

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**.

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