@awebai/oats 0.29.4 → 0.30.1

package/docs/release-notes/v0.27.0.md

@@ -73,16 +73,15 @@ spellings. See [Upgrading from 0.26](#upgrading-from-026).
   and accepts kernels `>=0.25.8 <0.28.0`.
 - **Core capabilities name their origin** (soul, workspace or team) on the soul
   page and the instance sidebar, on a kernel with feature `layers-from`.
-- The unused "the workspace's team settings" origin label is gone (0.26.0's
-  teams amendment K stopped emitting it).
+- The unused "the workspace's team settings" origin label is gone (0.26.0
+  stopped emitting it).
 
 ## Fixed
 
 - **0.26.0's notes said per-workspace personal teams need undeployed aweb
   server support.** The aweb service (0.8.13 and later) and CLI (1.36.8 and
-  later) already carry personal enrollment; what remains is oats.aweb 1.15
-  adopting it. The bundled oats.aweb is still 1.13.1 (the personal team only);
-  the team verbs come with oats.aweb 1.14.1 in a 0.27.x patch.
+  later) already carry personal enrollment; oats.aweb does not use it yet. The
+  bundled oats.aweb is still 1.13.1 (the personal team only).
 
 ## Upgrading from 0.26
 

package/docs/release-notes/v0.27.1.md

@@ -7,8 +7,7 @@
   is given at spawn (`--provider oats.aweb join=<labels>`) or later with
   `oats aweb join <labels>` / the Desktop's Teams controls, and leaves with
   `oats aweb leave <labels>`. Each joined team gets its own identity under the
-  instance home. Joined teams **poll** (their mail is read between tasks); live
-  receive for joined teams is planned for oats.aweb 1.15. Joining needs
+  instance home. Joined teams **poll** (their mail is read between tasks). Joining needs
   **aw 1.36.12 or later** (older aw answers `E_TEAM_AW_FLOOR`; the primary
   identity still mints). A leave removes the local identity only after aweb
   confirms the membership is released, so a failed leave can be retried.
@@ -18,11 +17,10 @@
 
 ## Known limitations
 
-- The bundled oats.okf is still 2.1.5: its harvest worker spawns with `--runtime`, so each harvest answers one `deprecated-runtime-name` warning on 0.27.x. It's harmless; oats.okf 2.1.6 passes `--harness`.
+- The bundled oats.okf is still 2.1.5: its harvest worker spawns with `--runtime`, so each harvest answers one `deprecated-runtime-name` warning on 0.27.x. It's harmless.
 
-- A per-workspace personal team still needs oats.aweb 1.15 (the aweb service
-  and CLI already carry personal enrollment); until then "personal" is the
-  person's active aweb team.
+- There is no per-workspace personal team: "personal" is the person's active
+  aweb team.
 
 ## Upgrading from 0.27.0
 

package/docs/release-notes/v0.27.2.md

@@ -37,7 +37,7 @@
 
 ## Known limitations
 
-- The bundled oats.okf is still 2.1.5 (its harvest answers one `deprecated-runtime-name` warning per spawn; harmless). oats.okf 2.1.6 follows in a later patch.
+- The bundled oats.okf is still 2.1.5 (its harvest answers one `deprecated-runtime-name` warning per spawn; harmless).
 
 - **A `core.attributesFile` or filter driver set in the repository's own
   config is not carried** into a recovery. Merging its patterns would change

package/docs/release-notes/v0.28.0.md

@@ -4,141 +4,74 @@ Package souls, triggers, okf 3.0.0 remote knowledge consult, and the Workspace v
 
 ## Added
 
-- **Package souls** (feature `package-souls`). A package may ship souls as
-  well as capabilities: `souls: ["souls/<name>", …]` in
-  `oats-package/oats-package.json`, each an ordinary soul directory
-  (`soul.yaml`, `AGENTS.md`, `skills/`). One pin in the workspace's
-  `packages:` versions both, so a package soul never drifts the way an
-  `external:` commit pin can. See [packages.md](../packages.md#package-souls).
-  - `oats sync` locks each soul's `name`, `path` and `digest` in the package's
-    lock entry and checks them again on the next sync
-    (`E_PACKAGE_INTEGRITY { why: "souls" }`). A soul without `soul.yaml` or
-    `AGENTS.md` is `E_PACKAGE_MANIFEST`. A lock written by an earlier kernel
-    has its `souls` filled in on the next sync.
-  - `oats souls` lists them with `kind: "package"`, `package`, `version` and
-    `qualifiedName`; `oats sync` and `oats workspace status` list each
-    package's `souls`.
-  - Spawn one by its qualified name `<package>/<soul>`
-    (`oats spawn oats.okf/knowledge-maintainer`), or by its bare name when that
-    is unique. A bare name shared by several souls is `E_SOUL_AMBIGUOUS`, which
-    now names each qualified form (`details.qualified`); a member soul's is
-    `<member name>/<soul>`.
-  - A package soul resolves like any soul: workspace and team defaults apply,
-    `off` and `<slot>: none` work, its `team:` labels must be declared, and
-    `from: here` means its own package at the locked commit.
-  - The spawn fetches the soul at the locked commit and verifies it against the
-    lock's digest (`E_PACKAGE_INTEGRITY { why: "soul-digest" }`). It homes in
-    its own agent directory `agents/<package>--<soul>/`
-    (`agents/oats-okf--knowledge-maintainer/`), its agent name in `oats status`
-    and `OATS_AGENT`, so a member soul of the same bare name never shares its
-    directory or roster row. `instance.json.workspace.soul` records `name`,
-    `qualifiedName` and `package: { id, version, commit, digest, path }`, and
-    the soul id is `package:<id>#<soul>`. `oats status` shows the soul as
-    `moved` once the package pin moves. Two packages whose ids differ only by
-    `.` and `-` (`a.b`, `a-b`) and that ship a same-named soul would share an
-    agent directory: that is an `E_SOUL_AMBIGUOUS` problem in `oats sync` and
-    `oats souls`, and neither spawns.
-
-- **Triggers** (feature `triggers`): event-driven spawns. A trigger says
-  "when a GitHub pull request event matches, spawn a new instance of this soul
-  with this task, in these teams". It is stored beside the schedules
-  (`kind: "trigger"` in `oats-schedules.json`) and evaluated by the same host
-  tick; there is no daemon or webhook. See
-  [schedules.md#triggers](../schedules.md#triggers).
-  - The source `github.pull_request` is polled with the host's `gh` at the
-    trigger's `poll` interval (at least 1m). Events: `opened`, `reopened`,
-    `ready_for_review`, `labeled`, `synchronize`, filtered by `labels` and
-    `base`.
-  - Each event fires once: its key is recorded only after a successful spawn,
-    so a failed spawn is retried on the next poll. Delivery is at least once: a
-    tick that dies between the spawn and recording its key spawns the event
-    again (held while the first instance is live, under the default `perKey: 1`). `concurrency.max` and
-    `perKey` bound the live instances of the trigger and of one PR.
-  - The purpose and task are templated from `{repo} {number} {url} {event}
-    {headSha} {trigger}` only; a PR's title and body never reach the task.
-    `spawn.teams` becomes the messaging capability's `join=`. The instance gets
-    the event as `OATS_TRIGGER_EVENT_FILE` (`<home>/.oats/trigger-event.json`)
-    and records `instance.json.trigger`.
-  - `oats trigger add (--file | --from <package>:<template> --set …) | list |
-    show | enable | disable | remove | test | status`, all with `--json`.
-    `oats trigger test` checks gh auth and where its credential comes from
-    (warning when the host timer cannot reach it, such as a shell-only
-    `GH_TOKEN`), the repository and your push/maintain/admin permissions on it,
-    the soul, the teams, and what would fire now, and spawns nothing.
-    `oats schedule list` counts the triggers it does not list.
-  - A package may ship trigger templates (`triggers: [{ id, file }]` in
-    `oats-package.json`).
-  - `oats spawn --trigger-event <file>` is how a trigger hands the event to the
-    spawn.
+- **Package souls** (feature `package-souls`). A package may ship souls
+  (`souls: ["souls/<name>", …]` in `oats-package/oats-package.json`), versioned
+  by the same `packages:` pin as its capabilities. `oats sync` locks each
+  soul's digest (`E_PACKAGE_INTEGRITY { why: "souls" }` on drift) and `oats
+  souls` lists them with `kind: "package"`. Spawn one as `<package>/<soul>`
+  (`oats spawn oats.okf/knowledge-maintainer`), or by its bare name when
+  unique; an ambiguous bare name is `E_SOUL_AMBIGUOUS`, naming each qualified
+  form. It resolves like any soul, is verified against the lock at spawn,
+  homes in `agents/<package>--<soul>/` (its agent name in `oats status`), and
+  shows as `moved` once the package pin moves. Two packages whose ids differ
+  only by `.` and `-` that ship a same-named soul are an `E_SOUL_AMBIGUOUS`
+  problem, and neither spawns. See [packages.md](../packages.md#package-souls).
+
+- **Triggers** (feature `triggers`): event-driven spawns. When a GitHub pull
+  request event (`opened`, `reopened`, `ready_for_review`, `labeled`,
+  `synchronize`, filtered by `labels` and `base`) matches, a new instance of a
+  soul is spawned with a templated task. Triggers are stored in
+  `oats-schedules.json`, polled with the host's `gh` by the schedule tick (no
+  daemon or webhook), and delivered at least once, bounded by `concurrency.max`
+  and `perKey`. A PR's title and body never reach the task. Commands: `oats
+  trigger add | list | show | enable | disable | remove | test | status`;
+  `oats trigger test` checks gh auth, permissions, the soul and what would
+  fire, and spawns nothing. The instance gets the event as
+  `OATS_TRIGGER_EVENT_FILE` (via `oats spawn --trigger-event <file>`) and
+  records `instance.json.trigger`; `spawn.teams` becomes the messaging
+  capability's `join=`. Packages may ship trigger templates. See
+  [schedules.md](../schedules.md#triggers).
 
 ## Fixed
 
-- **`--flag=value` is read.** Every kernel command ignored the inline form
-  silently: `oats spawn dev --harness=claude` spawned the default harness,
-  and `--name=x`, `--runtime=x`, `--dir=x` and `--server=x` were dropped the
-  same way. A kernel command now reads `--flag=value` exactly as
-  `--flag value`, with the same validation. The value is everything after the
-  first `=`. Two inline forms are refused with `E_BAD_ARGS`: an empty
-  `--flag=`, and a value on a switch. `--yolo=false` is refused and never
-  turns yolo on. A capability command's own flags are its provider's: they
-  are forwarded exactly as typed, and the kernel reads only its dispatch flag
-  (`--soul`) in either form. `oats capture`, `recall` and `setup` parse their
-  own arguments, as before. See
-  [desktop-cli-api.md § Flags](../desktop-cli-api.md#flags).
+- **`--flag=value` is read.** Kernel commands silently ignored the inline
+  form (`oats spawn dev --harness=claude` spawned the default harness). It is
+  now read exactly as `--flag value`; an empty `--flag=` or a value on a switch
+  (`--yolo=false`) is `E_BAD_ARGS`. A capability command's own flags are
+  forwarded as typed. See [desktop-cli-api.md § Flags](../desktop-cli-api.md#flags).
   **On an older kernel:** use the spaced form.
-
-- **`oats-local.yaml` `souls.disabled` is enforced at spawn.** It was documented
-  as "not run on this machine", but only counted souls in the `oats sync`
-  report. A listed soul is now refused with `E_SOUL_DISABLED { name,
-  qualifiedName, entry }`. An entry is a bare name (every soul of that name) or
-  a qualified name (`oats.okf/knowledge-harvester`, `<member>/<soul>`).
+- **`oats-local.yaml` `souls.disabled` is enforced at spawn**
+  (`E_SOUL_DISABLED`). An entry is a bare or a qualified soul name.
 
 ## oats.okf 3.0.0 (catalog pin and bundled mirror)
 
-The official catalog now pins `oats.okf` to `v3.0.0` (tag object `ad2349c7`,
-commit `76f7ccdb`). The copy bundled in this package is its byte mirror. The
-package declares `oats >=0.26.0`.
-
-- **Knowledge is consulted remotely.** An instance reads its soul's knowledge
-  at the accepted state through new commands: `oats okf bases`, `index`,
-  `cat --base <alias> <path>`, `ls`, `links` and `search`. A Git base is served
-  from one host-wide partial clone per base, and a read refetches the accepted
-  branch once the cached commit is older than the `consult-max-age` setting
-  (seconds; default 300; `0` refetches on every read). `--fresh` always
-  refetches. If the fetch fails, the read is served from the cache, with
-  `stale: true` and the reason in its receipt.
-  A directory base is read in place. The new `okf-consultation` skill and the
-  okf injection teach instances to run `oats okf index` at the start of every
-  task.
-- **BREAKING: no `./knowledge/` in homes.** A spawn records the accepted
-  resolution and materializes no `./knowledge/` directory or view. Anything
-  that read `<home>/knowledge/bases/<alias>/…` reads
-  `oats okf cat --base <alias> <path>` instead.
-- **BREAKING: `oats okf refresh` is `E_REMOVED`.** There are no per-instance
-  views to refresh.
-- **`oats okf read --path` still works** in 3.0.0, as an alias of `cat`.
-- **Older homes:** a `./knowledge/` a 2.x spawn left in a home is not touched.
-  3.0.0 ignores it, and `oats okf inspect` reports it as
-  `legacy-local-view`.
-- The memory-harvest worker soul no longer ships a `CLAUDE.md -> AGENTS.md`
-  symlink (npm drops symlinks, and the kernel composes each home's
-  `CLAUDE.md`). The mirror check (`scripts/check-okf-mirror.mjs`) no longer
-  requires one; any symlink a future release ships is mirrored and verified
-  as before.
+The official catalog pins `oats.okf` to `v3.0.0`; the bundled copy is its byte
+mirror. It declares `oats >=0.26.0`.
+
+- **Knowledge is consulted remotely**: `oats okf bases`, `index`, `cat --base
+  <alias> <path>`, `ls`, `links` and `search` read the soul's knowledge at the
+  accepted state. A Git base is served from one host-wide partial clone,
+  refetched once older than `consult-max-age` (default 300 s; `--fresh` always
+  refetches); a failed fetch serves the cache with `stale: true`. The new
+  `okf-consultation` skill teaches instances to run `oats okf index` at the
+  start of every task.
+- **BREAKING: no `./knowledge/` in homes.** Read
+  `oats okf cat --base <alias> <path>` instead of
+  `<home>/knowledge/bases/<alias>/…`. A `./knowledge/` left by a 2.x spawn is
+  ignored and reported by `oats okf inspect` as `legacy-local-view`.
+- **BREAKING: `oats okf refresh` is `E_REMOVED`.** `oats okf read --path`
+  still works as an alias of `cat`.
 
 ## Desktop
 
-- **Workspace v4 redesign** (#206): the Workspace area (Setup, Souls, Capabilities, the soul and capability pages) is rebuilt to the Workspace v4 design. Facts the kernel does not report yet are left out rather than guessed; the Setup screen no longer names kernel files.
+- **Workspace v4 redesign** (#206): Setup, Souls, Capabilities and the soul
+  and capability pages are rebuilt. Facts the kernel does not report yet are
+  left out rather than guessed.
 - **Soul team labels** reach the Souls grid (#208).
 
-## Tests and CI
-
-- A home's resolved view (`resolvedFromHome`) carrying the slot rows its
-  spawn recorded (`layers`, since 0.26.0 layers-from) is now pinned. Before,
-  no test caught reverting it to `{}`.
-- CI runs the suite in six parallel shards (`node --test --test-shard`), plus a gate job with the old check name. Main runs no longer cancel each other.
-
 ## Upgrading
 
-- **okf 3.0.0 is breaking for anything that read `<home>/knowledge/`.** Use `oats okf cat`. Existing homes keep their old view, unused.
-- **Package souls and triggers are additive.** Nothing changes until a package declares `souls:`/`triggers:`, or you add a trigger.
+- **okf 3.0.0 is breaking for anything that read `<home>/knowledge/`.** Use
+  `oats okf cat`. Existing homes keep their old view, unused.
+- **Package souls and triggers are additive.** Nothing changes until a
+  package declares `souls:`/`triggers:`, or you add a trigger.

package/docs/release-notes/v0.29.0.md

@@ -2,239 +2,120 @@
 
 ## Added
 
-- **Workspace triggers and schedules** (feature `automations`). A trigger or a
-  schedule can now be declared in Git, in any confirmed member, and shared with the
-  team. It is named `<member>/<id>`, and a machine's own ones are named
-  `local/<id>`. See
-  [schedules.md#workspace-triggers-and-schedules](../schedules.md#workspace-triggers-and-schedules).
-  - Triggers and schedules stay separate:
-
-    | | triggers | schedules |
-    | --- | --- | --- |
-    | folder | `oats-triggers/` | `oats-schedules/` |
-    | file name anywhere in the member | `*.oats-trigger.yaml` | `*.oats-schedule.yaml` |
-    | `kind:` | `oats-trigger` | `oats-schedule` |
-    | commands and list | `oats trigger …` | `oats schedule …` |
-    | opt-out | `triggers.disabled` | `schedules.disabled` |
-
-    `oats-package/`, `.git/` and `node_modules/` are never scanned.
-  - Every file carries `kind`, `schemaVersion: 1`, `runsOn` (the host that runs it)
-    and `owner` (the GitHub account it acts as). The wrong kind is
-    `E_AUTOMATION_SCHEMA`, and a duplicate id is `E_AUTOMATION_DUPLICATE`.
-  - A host runs one only when `runsOn` is its new `oats-local.yaml` `host.name`
-    **and** its `gh` is logged in as `owner`. Otherwise the item is listed as
-    `assigned-elsewhere`, `owner-mismatch` or `host-unnamed`.
-  - `oats trigger disable <member>/<id>` and `oats schedule disable <member>/<id>`
-    stop it on this host without a commit, by writing `triggers.disabled` or
-    `schedules.disabled` in `oats-local.yaml`.
-  - `oats sync` takes a snapshot of them. The host tick reads the snapshot and
-    refreshes it every ten minutes (`oats automations refresh`).
-  - `oats trigger add … --workspace <member> --runs-on <host> --owner <host>/<login>`
-    writes the file in a checkout of the member, or prints it. `oats schedule add`
-    takes the same options.
-  - `oats trigger list --json` and `oats schedule list --json` answer the Desktop's
-    rows for both levels: the owner, where it runs and why (not), the soul and
-    where it comes from, the task verbatim, the event or cron, and the last and
-    next run. Local schedule rows keep their bare `id` and add `qualifiedId`. See
-    [desktop-cli-api.md](../desktop-cli-api.md).
-  - Each row's `origin` carries `url` (the file on GitHub at its commit) and
-    `localPath` (the file in this machine's clone of the member), each `null` when
-    there is none. Both lists carry `host.ghUser` (who `gh` is logged in as, per
-    GitHub host) and the host `scheduler`. "When it next runs" is `nextDue`
-    everywhere.
-- **Desktop facts** (feature `desktop-facts`): kernel facts the Desktop's Workspace
-  view shows, so it never derives them. Every field is an addition. See
+- **Workspace triggers and schedules** (feature `automations`). A trigger or
+  schedule can be declared in Git in any confirmed member and shared with the
+  team: `oats-triggers/` or `*.oats-trigger.yaml`, and `oats-schedules/` or
+  `*.oats-schedule.yaml`. It is named `<member>/<id>`; a machine's own ones
+  are `local/<id>`. Each file names `runsOn` (the host that runs it) and
+  `owner` (the GitHub account it acts as); a host runs it only when `runsOn` is
+  its new `oats-local.yaml` `host.name` and its `gh` is logged in as `owner`.
+  `oats trigger|schedule disable <member>/<id>` stops one on this host without
+  a commit. `oats sync` snapshots them and the host tick refreshes the
+  snapshot every ten minutes (`oats automations refresh`). `oats trigger|schedule
+  add … --workspace <member>` writes the file. See
+  [schedules.md](../schedules.md#workspace-triggers-and-schedules) and
+  [desktop-cli-api.md](../desktop-cli-api.md) for the list rows.
+- **Desktop facts** (feature `desktop-facts`): additive fields the Desktop's
+  Workspace view shows instead of deriving them, on `oats inspect --soul`,
+  `oats souls`, `oats capabilities`, `oats workspace status` and `oats status`
+  (`--json`). Among them: each capability's `composedFrom` and the defaults a
+  soul turned off, a soul's spawn defaults and whether it is `spawnable` here,
+  member clones, the lock, newer package versions, file locations, and an
+  instance's `startedAt`, `modelFrom` and `identityAddress`. See
   [desktop-cli-api.md](../desktop-cli-api.md#desktop-facts-feature-desktop-facts-oats-0290).
-  - `oats inspect --soul --json`: each capability's `composedFrom` (`workspace`,
-    `team:<label>` or `soul`), and `capabilitiesOff[]`, the defaults the soul
-    turned off (`<id>: off` or `<slot>: none`).
-  - `oats souls --json` rows: the default `harness`/`model` a spawn starts with,
-    and `spawnable` and `problem`, the refusal a spawn would meet (it spawns
-    nothing). Also `file`.
-  - `oats capabilities --json` rows: `layer` on package rows too, `description`,
-    `skills`/`commands`/`hooks` by name, `file`, and a member capability's `tree`
-    (its Git tree id).
-  - `oats workspace status --json`:
-    - the workspace and team `defaults` as rows;
-    - this computer's member `clones` and the rule that found each;
-    - `disabledSouls`;
-    - `lock` (`path`, `lockfileVersion`);
-    - `packages[].latest` when the shipped catalog has a newer version;
-    - file locations (`workspace.file`, `members[].url`,
-      `members[].membershipFile`).
-  - `oats status --json` instance rows: `startedAt` (the last start or restart),
-    `modelFrom` (also recorded in `instance.json`) and `identityAddress`. A member
-    module's drift `current` gains `version`.
-  - URLs are GitHub pages at the row's commit, `null` for any other host.
-  - `oats help` lists `spawn --provider`.
-- **`oats schedule test <id>`**: where a schedule runs, whether its soul resolves
-  (a spawn preview) and when it is next due. It spawns nothing, like
-  `oats trigger test`.
-- **`launchConfig`** on a trigger's `spawn` and on a spawn schedule: the soul starts
-  on that launch configuration of the running host (`oats-local.yaml`
-  `launch-configs`). A package trigger template can expose it as a parameter.
-- `oats trigger status --json` rows add `nextDue`, `concurrency` and `liveCount`;
-  `oats trigger test --json` `wouldFire` items add `repo`.
-- **`OATS_SETTINGS_ORIGINS`** beside `OATS_SETTINGS`, for every hook and
-  capability command (and readiness probes): where each leaf of the payload came
-  from, a JSON pointer → `{ kind, at }` (`manifest-default`, `workspace`, `soul`,
-  `host`, `spawn`). A provider can tell a soul-set value from a host-set one
-  without reading `soul.yaml`. `instance.json` records it with the settings
-  (`capabilities[].settingsOrigins`, `capabilityRuntime[].settingsOrigins`).
+- **`oats schedule test <id>`**: where a schedule runs, whether its soul
+  resolves, and when it is next due. It spawns nothing.
+- **`launchConfig`** on a trigger's `spawn` and on a spawn schedule: the
+  running host's launch configuration to start the soul with.
+- `oats trigger status --json` rows add `nextDue`, `concurrency` and
+  `liveCount`; `oats trigger test --json` `wouldFire` items add `repo`.
+- **`OATS_SETTINGS_ORIGINS`** beside `OATS_SETTINGS`, for every hook,
+  capability command and readiness probe: where each leaf of the payload came
+  from (`manifest-default`, `workspace`, `soul`, `host`, `spawn`), also
+  recorded in `instance.json`.
 
 ## Changed
 
-- **oats.framework 1.3.0 pinned.** The official catalog pins `oats.framework` to
-  `oats-framework/v1.3.0` (this repository's workspace pins it too). 0.28.1 was never
-  released, so this pin covers three framework releases:
-  - **1.2.0:** the setup-admin skills. oats.setup 2.1.0 adds `oats-setup-model`,
-    `oats-workspace-config`, `oats-teams`, `oats-automations` and a setup inject,
-    and oats.core 2.1.0 is current for an instance's view. The `oats-setup-admin`
-    soul uses them.
-  - **1.2.1:** OKF knowledge operations in onboarding (oats.setup 2.1.1,
-    `oats-onboarding`).
-  - **1.3.0:** `knowledge-theory-expert` is a package soul
-    (`oats spawn oats.framework/knowledge-theory-expert`), with
-    oats.knowledge-theory 1.1.0.
-
-  A workspace picks it up by pinning `oats.framework: v1.3.0` and running
-  `oats sync`.
-- **A local trigger's id is `local/<id>`** in `oats trigger` rows, in its dedup keys
-  and state, and in a triggered instance's `instance.json.trigger.id` and event
-  file. It was the bare id in 0.28.0. Every `oats trigger` verb still accepts the
+- **oats.framework 1.3.0 pinned** (covering 1.2.0, 1.2.1 and 1.3.0): the
+  setup-admin skills in oats.setup 2.1.0 and oats.core 2.1.0, OKF knowledge
+  operations in onboarding (oats.setup 2.1.1), and `knowledge-theory-expert`
+  as a package soul with oats.knowledge-theory 1.1.0. Pin
+  `oats.framework: v1.3.0` and run `oats sync`.
+- **A local trigger's id is `local/<id>`** in `oats trigger` rows, its state
+  and a triggered instance's `instance.json`. Every verb still accepts the
   bare id.
 
 ## Removed
 
-- **BREAKING: capability-defined agents.** A capability manifest's `agents:` is
-  refused at resolution, with
-  `E_CAPABILITY_AGENTS_REMOVED { capability, agents, from }`. The remedy names the
-  replacement: a **package soul** (`souls/<name>/` in the package, spawned as
-  `oats spawn <package>/<name>`) or a **member soul**. `oats spawn <name>` no
-  longer falls back to an agent declared by a materialized or locked module; an
-  unknown name is `E_SOUL_UNKNOWN`. The manifest schema drops `agents`.
-  - A home an earlier kernel spawned for one (its agent directory holds only
-    `instances/`) is still listed by `oats status`, may be a `--parent`, and
-    retires. Nothing creates one any more.
-  - This repository's users moved:
-    - oats.okf 4.0.0's harvester is a package soul;
-    - the post-commit **`reviewer`** is an oats.dev **1.1.0** package soul
-      (`oats.dev/reviewer`, beside oats.review 1.3.0; the pin moves to
-      `v1.1.0`), and oats.review's inject spawns it unchanged, now named
-      `oats-dev-reviewer-<short-sha>`;
-    - **`knowledge-theory-expert`** is an oats.framework **1.3.0** package soul
-      (`oats spawn oats.framework/knowledge-theory-expert`), with
-      oats.knowledge-theory 1.1.0.
-  - A v2 soul.yaml declares no harness or model, so the reviewer's harness and
-    model now come from the **spawner's launch configuration** (its former pin was
-    pi, gpt-5.6-sol).
+- **BREAKING: capability-defined agents.** A manifest's `agents:` is refused
+  at resolution (`E_CAPABILITY_AGENTS_REMOVED`), naming the replacement: a
+  **package soul** (`oats spawn <package>/<name>`) or a member soul. `oats spawn
+  <name>` no longer falls back to a module's agent (`E_SOUL_UNKNOWN`). Homes
+  spawned earlier for one stay listed, may be a `--parent`, and retire.
+  - OKF's harvester is an oats.okf 4.0.0 package soul; the post-commit
+    `reviewer` is `oats.dev/reviewer` (oats.dev 1.1.0, beside oats.review
+    1.3.0), spawned as `oats-dev-reviewer-<short-sha>`; and
+    `knowledge-theory-expert` is an oats.framework 1.3.0 package soul.
+  - The reviewer's harness and model now come from the spawner's launch
+    configuration (it was pinned to pi, gpt-5.6-sol).
 
 ## Fixed
 
-- A package soul's derived instance name is checked and de-duplicated as the name
-  the home gets (`acme-pkg-keeper-<purpose>`, not `acme-pkg--keeper-…`). A
-  purpose inside the limit is no longer refused, and a second spawn with the same
-  purpose is `…-2` instead of a collision. An over-long purpose is
-  `E_INSTANCE_NAME_INVALID` naming how many characters the purpose may have
-  (`details.maxPurpose`).
-
-- Concurrent spawns of the same instance: a spawn that loses the race now refuses
-  with `E_PLACEMENT_TAKEN` (it created nothing). It used to fail with an uncoded
-  "instance already exists" error, surfaced as `E_SPAWN_FAILED`.
+- A package soul's derived instance name is checked and de-duplicated as the
+  name the home gets; an over-long purpose is `E_INSTANCE_NAME_INVALID` with
+  `details.maxPurpose`.
+- A spawn that loses a race for the same instance is `E_PLACEMENT_TAKEN`
+  (it was `E_SPAWN_FAILED`).
 - Disabled-here messages name the per-kind key (`triggers.disabled`,
   `schedules.disabled`).
 
 ## Desktop
 
-- **Schedules and Triggers tabs** on the automations contract. Rows are grouped by
-  where they run: on this computer, needing attention here, or elsewhere. Workspace
-  and local items are listed together, with an origin chip, a filter and a search.
-  - Each row has an on-here switch, the soul and where it comes from, the cron in
-    words or the trigger's event, and where it runs and as whom. It also shows the
-    last and next run, and a menu (Open, Test, Run now, on/off here, Open file).
-  - A row opens a detail page: the prompt verbatim, the schedule or event, recent
-    runs, the kernel's placement verdict, where it comes from, and the test result.
-  - The old Schedules read path is gone.
-- **Why each capability is there.** The soul page and an instance's soul tab tag
-  each capability `workspace`, `team · <label>` or `soul`, and list the defaults the
-  soul turned off (including a slot it emptied), from the kernel's Desktop facts.
-- **A moved module names its versions**: "moved 2.1.5 → 2.2.0" in the instance
-  panel's module drift.
+- **Schedules and Triggers tabs** on the automations contract: rows grouped by
+  where they run, workspace and local items together, a detail page per item
+  with its prompt, runs, placement verdict and test result. The old Schedules
+  read path is gone.
+- The soul page and an instance's soul tab tag why each capability is there
+  (`workspace`, `team · <label>` or `soul`) and list the defaults turned off.
+- Module drift names versions ("moved 2.1.5 → 2.2.0").
 - The Desktop accepts OATS CLIs `>=0.25.8 <0.30.0`.
 
-## Internal
-
-- The release workflow runs the test suite in six parallel shards, like PR CI, and
-  publication waits for every shard.
-
 ## Upgrading from 0.28
 
-> **0.29.0 and oats.okf 4.0.0 move in lockstep.** On kernel 0.29.0, oats.okf ≤3.x
-> is refused because it declares a capability agent, and oats.okf 4.0.0 requires
-> kernel 0.29.0. A deployment on okf 3.x therefore **stays on kernel 0.28 until it
-> moves its pins**. It then upgrades in one sitting, in this order:
+> **0.29.0 and oats.okf 4.0.0 move in lockstep.** Kernel 0.29.0 refuses
+> oats.okf ≤3.x (it declares a capability agent), and oats.okf 4.0.0 requires
+> kernel 0.29.0. A deployment on okf 3.x stays on kernel 0.28 until it moves
+> its pins, then upgrades in one sitting:
 
 1. **Upgrade the kernel**: the npm package, the pi adapter and the Desktop, all
    0.29.0.
-2. **Move the pins** to the official catalog's: `oats.okf: v4.0.0`,
-   `oats.dev: v1.1.0`, `oats.framework: v1.3.0`.
+2. **Move the pins** to `oats.okf: v4.0.0`, `oats.dev: v1.1.0`,
+   `oats.framework: v1.3.0`.
 3. **Run `oats sync`.**
 
-Between step 1 and step 3, a package pinned below its 0.29 release still declares
-`agents:`. A spawn, preview or `inspect --soul` of any soul that composes it
-refuses with `E_CAPABILITY_AGENTS_REMOVED`:
-- **oats.okf ≤3.x** (`memory-harvest`): this is **every soul with oats.okf in its
-  knowledge slot**;
-- **oats.dev 1.0.x** (`reviewer`);
-- **oats.framework ≤1.2.x** (`knowledge-theory-expert`).
-
-Harvest is off by default in okf 4.0.0. Switch it on
-(`oats okf setup --harvest on`) where you want it.
-
-Homes spawned earlier keep loading their recorded modules. Homes spawned for a
-capability agent stay listed and retirable.
+Between steps 1 and 3, any soul that composes oats.okf ≤3.x (every soul with
+oats.okf in its knowledge slot), oats.dev 1.0.x or oats.framework ≤1.2.x is
+refused with `E_CAPABILITY_AGENTS_REMOVED`. Harvest is off by default in okf
+4.0.0; switch it on with `oats okf setup --harvest on`. Homes spawned earlier
+keep loading their recorded modules.
 
 ## oats.okf 4.0.0 (catalog pin and bundled mirror)
 
-The official catalog now pins `oats.okf` to `v4.0.0` (tag object `239f2885`,
-commit `1f0ba12f`). The copy bundled in this package is its byte mirror.
-
-**BREAKING:**
-- The package requires `oats >=0.29.0`; an older kernel refuses it
-  (`E_CAPABILITY_INCOMPATIBLE`).
-- The `okf` and `memory-harvest` skills are gone from `oats.okf`.
-
-- **Three capabilities.** The package now exports:
-  - `oats.okf`: the knowledge slot;
-  - `oats.okf-harvest`: the harvester's completion and status commands;
-  - `oats.okf-maintenance`: the maintainer's review context.
-
-  The catalog maps `oats.okf-harvest` and `oats.okf-maintenance` to the
-  `oats.okf` package.
-- **Working souls get two skills and the inject.** A soul with `oats.okf` in
-  its knowledge slot gets `okf-consultation` and `okf-instance-knowledge`, and
-  the okf inject.
-- **The harvester is a package soul.** `oats okf run-source` (and `oats okf
-  harvest`) spawns `oats.okf/knowledge-harvester`. It is named
-  `okf-harvester-<run>` and homes under
-  `agents/oats-okf--knowledge-harvester/`. It is no longer the `memory-harvest`
-  capability agent. After a successful completion it stays alive in the `okf`
-  team until its PR is merged or closed. `oats.okf/knowledge-maintainer` is the
-  package's second soul.
-- **The harvest-review trigger.** The package ships the trigger template
-  `harvest-review` (`triggers/harvest-review.json`). It watches the labelled
-  harvest PRs.
-- **`harvest: on|off`** (default **off**). Harvest is a host switch in
-  `oats-local.yaml` `settings.oats.okf.harvest` (`oats okf setup --harvest
-  on|off`). Off means no source registration, capture or custody. A soul can
-  only opt out (`knowledge: { harvest: off }`).
-- **`oats okf read` is removed** (`E_REMOVED`). Use `oats okf cat --base
-  <alias> <path>`, which takes the same path and gives the same text and
-  receipt.
-
-The bundled mirror now covers the three capability directories
-(`capabilities/oats-okf`, `capabilities/oats-okf-harvest`,
-`capabilities/oats-okf-maintenance`). The package's souls and trigger are
-checked byte for byte in `scripts/okf-source-inventory.json` (schemaVersion 2).
-The npm package does not ship them, because the kernel reads a package's souls
-and triggers from Git at its locked commit.
+The official catalog pins `oats.okf` to `v4.0.0`; the bundled copy is its
+byte mirror.
+
+- **BREAKING:** requires `oats >=0.29.0` (`E_CAPABILITY_INCOMPATIBLE` on an
+  older kernel), and the `okf` and `memory-harvest` skills are gone.
+- **Three capabilities:** `oats.okf` (the knowledge slot), `oats.okf-harvest`
+  and `oats.okf-maintenance`. A soul with `oats.okf` in its knowledge slot gets
+  the `okf-consultation` and `okf-instance-knowledge` skills and the inject.
+- **The harvester is a package soul**, `oats.okf/knowledge-harvester`,
+  spawned by `oats okf run-source` / `harvest` as `okf-harvester-<run>`. It
+  stays alive in the `okf` team until its PR is merged or closed.
+  `oats.okf/knowledge-maintainer` is the second soul, and the trigger template
+  `harvest-review` watches labelled harvest PRs.
+- **`harvest: on|off`** (default off) is a host switch
+  (`oats okf setup --harvest on|off`); a soul can only opt out
+  (`knowledge: { harvest: off }`).
+- **`oats okf read` is removed** (`E_REMOVED`); use `oats okf cat --base
+  <alias> <path>`.

package/docs/release-notes/v0.29.1.md

@@ -59,7 +59,7 @@ view shows nothing new.
   kernel's workspace status and reads the branch's PR with `gh`, cached for a
   minute. The row shows `#N`, with draft, merged or closed in words. Remote
   instances, and hosts without a signed-in `gh`, show no badge.
-- **W6 Git & GitHub** (#239, #240, #241, #242, #243). The instance's Git panel
+- **Git & GitHub** (#239, #240, #241, #242, #243). The instance's Git panel
   follows the design:
   - **Branch** shows the work mode, the distance from the default branch and
     whether the tree is clean, with the rest behind Details.