@awebai/oats 0.29.4 → 0.30.1

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

@@ -1,102 +1,54 @@
 # OATS v0.22.1
 
-A bounded reliability release, made from the first day of operating OATS on
-its own repository from the published 0.22.0 artifacts. Every item below was
-either reproduced during that run or found by the independent review that
-preceded it, plus the golden fixtures that guard the kernel's outputs and a
-release-workflow correction (a release with nothing to bump finishes rather
-than fails). The Desktop compatibility band (`>=0.22.0 <0.23.0`) already
-covers this kernel; no Desktop rebuild is needed.
+A reliability release. The Desktop compatibility band (`>=0.22.0 <0.23.0`)
+already covers this kernel; no Desktop rebuild is needed.
 
 ## Fixes
 
-- **`oats create` in a fresh scope no longer crashes.** After `oats init`,
-  the first `oats create` died with a raw stack trace because it demanded the
-  `agents/` directory that only `create` itself populates. It now bootstraps
-  the roster root at the enclosing repository, reports that once (and as
-  `agentsRoot` in `--json`), and the 0.22.0 workaround `mkdir agents` is no
-  longer needed.
-- **Spawn preflights executables and compensates every post-hook failure.**
-  A missing runtime binary or tmux was detected only after the home, worktree,
-  branch, and required capability hooks (an aweb identity) had been created,
-  and those throws bypassed compensation, leaving a branch, a worktree, and
-  remote state with no `instance.json` and no quarantine. The runtime binary,
-  tmux (when launching), and the task input are now checked before any
-  mutation, and one compensation path owns every failure after the spawn
-  hooks: retire hooks run once, Git topology is removed and verified, a
-  window that may have been created is stopped and verified before
-  credentials are touched, and unresolvable cleanup retains the home with
-  its receipt for a retryable `oats retire`. Six fault-injection tests cover
-  the paths.
-- **The turn record's stream lock is ownership-safe and bounded.** A late
-  contender could judge a live holder's lock stale by age and enter the same
-  critical section, and the old holder then unlinked whatever lock was in
-  place. The lock now carries an owner token; staleness is proven from the
-  holder's liveness, with age only as the fallback for a foreign-host or
-  tokenless lock; release removes only a lock the releaser owns; and every
-  failed acquire iteration passes one deadline check, so an unreadable lock
-  or a lock that cannot be removed fails with the underlying code and path
-  instead of spinning forever. Known limit, documented: a pid reused after a
-  reboot makes an abandoned lock read as held until an operator removes it.
-- **README claims match the implementation.** Native captured turns are
+- **`oats create` in a fresh scope no longer crashes.** It bootstraps the
+  roster root at the enclosing repository and reports it (`agentsRoot` in
+  `--json`); the `mkdir agents` workaround is no longer needed.
+- **Spawn preflights executables and compensates every failure.** The runtime
+  binary, tmux (when launching), and the task input are checked before any
+  mutation. After the spawn hooks, one compensation path runs retire hooks,
+  removes and verifies Git topology, stops any created window, and retains the
+  home with its receipt for a retryable `oats retire` when cleanup cannot
+  finish.
+- **The turn record's stream lock is ownership-safe and bounded.** The lock
+  carries an owner token, staleness is judged from the holder's liveness, only
+  the owner releases it, and acquisition has a deadline. Known limit: a pid
+  reused after a reboot makes an abandoned lock read as held until an operator
+  removes it.
+- **README claims match the implementation.** Captured turns are
   content-addressed, not signed; projected aweb mail and chat keep their
-  original signatures; capture covers Claude Code, Pi, and Codex transcripts
-  plus aw client logs on machines where `oats setup` ran, subject to the
-  ignore list. The contracts document and the turn-record specification say
-  the same.
-- **Bundled capabilities match their published tags.** The copies of the
-  official packages bundled under `capabilities/` claimed the published
-  version numbers but differed from the published payloads; the bundled
-  `oats.okf` still imported kernel internals and shipped an older harvester
-  layout. All six are now byte-identical to the tagged payloads (`oats.okf`
-  1.4.1, `oats.aweb` 1.8.0, `oats.jira` 1.0.0, `oats.linear` 1.0.0,
-  `oats.authoring` 1.0.0, `oats.review` 1.2.0 from `oats.dev` 1.0.0). Two
-  new tests guard it: no file under `capabilities/` may name kernel internals
-  or shell out to `oats root`, and every bundled manifest must carry the
-  version the catalog pins. The clean-room smoke asserts the same pin before
-  wrapping the bundled package, so it now proves the released package and
-  kernel combination. The bundled `oats.linear` README and test moved with
-  their package.
+  original signatures.
+- **Bundled capabilities match their published tags.** The bundled official
+  packages are byte-identical to the tagged payloads (`oats.okf` 1.4.1,
+  `oats.aweb` 1.8.0, `oats.jira` 1.0.0, `oats.linear` 1.0.0, `oats.authoring`
+  1.0.0, `oats.review` 1.2.0 from `oats.dev` 1.0.0), and tests enforce the pin.
+- A release with nothing to bump now finishes instead of failing.
 
 ## Documentation
 
-- **Run your first OATS team** (`docs/first-team.md`) is the tested path from
-  install to a real task, harvest, retirement, and a successor, with the
-  caveats the run met: the harvester runs in Pi even for Claude Code workers,
-  a Claude Code spawn needs two interactive confirmations today, and a
-  messaging layer entry that excludes a soul must state `global: true`.
-- **First-team example** (`docs/first-team-demo.md`) records what actually
-  happened on 2026-09-05: two workers, two promotions, one successor that
-  read its predecessor's promoted lesson.
-- **Migration from OAS** is rewritten from shipped state: the packages are
-  published, the seven catalog aliases exist, and the OAS npm deprecation
-  remains with its maintainer.
-- `docs/layers.md` is now the OATS contracts and `docs/integrations.md` the
-  binding guide; `docs/2026-09-03-architecture-proposal.md` records the
-  component model and the migration plan agreed with the framework's author.
-
-## Known operating limits and issues, not fixed here
-
-- The qualified `oats.okf` 1.4.1 configuration runs its harvester in Pi, so
-  a Pi-runnable model is required even for Claude Code workers.
-- A Claude Code worker's first launch can stop on Claude's folder-trust
-  prompt and on the aweb channel plugin's development-channels
-  confirmation; attach to the tmux session and answer them. A created
-  window is not evidence that the agent has started.
-- Retiring an instance reports its aweb identity deleted while the server
-  keeps the alias (aweb-aaum.6). Local cleanup is complete; the name cannot
-  be reused until an administrator removes the alias. Use a fresh
-  `--purpose` for successors.
-- The OKF harvester's default model assumes the `github-copilot` provider;
-  set `harvest-model` under the knowledge layer settings to a model your Pi
-  can run. A package change is proposed.
-- `oats spawn` resolves the roster root from the working directory, so from
-  a workspace root pass `--dir <repo>` even though `oats status --team`
-  lists the souls.
-- `oats status` lists the retirement-baselines directory as a phantom
-  instance, retire leaves that baseline file behind, and `oats retire --json`
-  prints a bare object rather than the schema-v1 envelope. Tracked; each
-  changes a golden fixture deliberately.
+- [Run your first OATS team](../first-team.md): the tested path from install
+  to a task, harvest, retirement, and a successor.
+- [Migration from OAS](https://github.com/awebai/oats/blob/v0.22.1/docs/migration-from-oas.md)
+  is rewritten for the published packages and catalog aliases.
+
+## Known limits in this release
+
+- The `oats.okf` 1.4.1 harvester runs in Pi, so a Pi-runnable model is needed
+  even for Claude Code workers; its default model assumes the `github-copilot`
+  provider, so set `harvest-model` to a model your Pi can run.
+- A Claude Code worker's first launch can stop on the folder-trust prompt and
+  on the aweb channel plugin's confirmation; attach to the tmux session and
+  answer them.
+- Retiring an instance leaves its aweb alias reserved on the server; use a
+  fresh `--purpose` for successors.
+- From a workspace root, `oats spawn` needs `--dir <repo>`.
+- `oats status` lists the retirement-baselines directory as an instance,
+  retire leaves that baseline file behind, and `oats retire --json` prints a
+  bare object rather than the schema-v1 envelope.
 
 ## Install
 

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

@@ -22,4 +22,4 @@ saved route on this machine still has its actions disabled with the same
 explanation.
 
 Nothing else changes: no kernel, session start, start dialog or record
-schema change. Tag v0.22.9 and everything it shipped stand.
+schema change.

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

@@ -1,49 +1,3 @@
 # OATS v0.22.11
 
-Schedules: cron-driven agent work that runs on the execution host, from
-the CLI and from Desktop, including while the GUI is closed.
-
-## Schedules (kernel)
-
-`oats schedule` keeps a per-workspace `oats-schedules.json` of jobs of three
-kinds: **spawn** launches a soul as a fresh disposable instance with a task,
-**command** runs an `oats` command in a directory (a harvest, for example),
-and **wake** starts a stopped instance if needed and sends it a message
-through its terminal. Cron expressions are five-field with an IANA time
-zone, evaluated by croner; missed minutes are skipped, never caught up.
-
-One host timer (`oats schedule host install`: a launchd agent or a systemd
-user timer) ticks every registered workspace once a minute under a shared
-limit on concurrent scheduled launches. A remote workspace's schedules live
-and run on that server; `--server` routes every subcommand there.
-`oats spawn --wake-file <json>` binds a wake schedule to the new home.
-
-Outcomes are what the kernel observed, not a claim that a task succeeded:
-launched, active, ended, stopped, launch-failed, delivered, started,
-skipped, and unknown. A launch whose effects the kernel cannot confirm (a
-timed-out or envelope-less command, an incomplete rollback) keeps its slot
-as unknown until `oats schedule reconcile <id>` adopts a named receipt or
-the operator clears it with `--clear`. A wake's launch slot follows the
-runtime through the session start receipt, so a persistent home whose
-process exited frees the slot. Locks are never reclaimed automatically;
-an unreadable or dead owner names the directory to remove.
-`oats version --json` advertises feature `schedule` and `scheduleApi: 1`.
-See docs/schedules.md.
-
-## Schedules (Desktop)
-
-A **Schedules** view per workspace: create, edit, pause, run now, check run
-state and delete jobs through a single JSON spec; the Soul roster's
-**Schedule…** preselects the soul; the spawn dialog offers a recurring wake
-for the new agent, forwarded inline to a remote server. Mutations require
-an explicit workspace. The reconcile result and its recovery instructions
-stay visible across polling. **Enable host scheduler** installs the timer
-and registers the workspace. See docs/desktop.md.
-
-## Tests
-
-The kernel adds `test/schedule.test.mjs` (fixture homes, injected
-spawn/start/input, dummy commands, fixture-only host unit paths) and
-`test/schedule-session.test.mjs`, which drives a real private tmux socket
-to prove literal delivery, same-minute deduplication and slot release when
-a runtime stops. Nothing in the suites touches a live timer.
+Tagged, not published; its changes shipped in v0.22.12.

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

@@ -1,8 +1,7 @@
 # OATS v0.22.12
 
-The same reviewed content as the unpublished v0.22.11 tag, whose hosted
-run failed in test fixtures before anything was published; those fixtures
-are fixed here.
+Ships the content of the unpublished v0.22.11 tag, with its failing test
+fixtures fixed.
 
 Schedules: cron-driven agent work that runs on the execution host, from
 the CLI and from Desktop, including while the GUI is closed.
@@ -32,7 +31,7 @@ runtime through the session start receipt, so a persistent home whose
 process exited frees the slot. Locks are never reclaimed automatically;
 an unreadable or dead owner names the directory to remove.
 `oats version --json` advertises feature `schedule` and `scheduleApi: 1`.
-See docs/schedules.md.
+See [Schedules](../schedules.md).
 
 ## Schedules (Desktop)
 
@@ -42,12 +41,4 @@ state and delete jobs through a single JSON spec; the Soul roster's
 for the new agent, forwarded inline to a remote server. Mutations require
 an explicit workspace. The reconcile result and its recovery instructions
 stay visible across polling. **Enable host scheduler** installs the timer
-and registers the workspace. See docs/desktop.md.
-
-## Tests
-
-The kernel adds `test/schedule.test.mjs` (fixture homes, injected
-spawn/start/input, dummy commands, fixture-only host unit paths) and
-`test/schedule-session.test.mjs`, which drives a real private tmux socket
-to prove literal delivery, same-minute deduplication and slot release when
-a runtime stops. Nothing in the suites touches a live timer.
+and registers the workspace. See [the Desktop guide](../desktop.md).

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

@@ -1,44 +1,3 @@
 # OATS v0.22.13
 
-Terminal essentials for the Desktop and one kernel operation behind them:
-attachments reach the agent as a path, never as typed input.
-
-## Attachments (kernel)
-
-`oats session upload --file <local> --home <abs>` copies a file into the
-instance home's private `.oats-attachments/` directory (0700, file 0600,
-`name-2` when the name is taken) and answers `{path, bytes, sha256}`. With
-`--server <id> --instance <name>` (or `--home`), the same saved route as
-`session attach` is resolved, the remote must advertise the new
-`session-upload` feature, and the bytes travel on ssh stdin into
-`oats session receive --home <abs> --name <file>` on the execution host,
-which reads stdin event-driven, enforces the 64 MiB kernel bound before
-writing anything, allocates the destination exclusively so simultaneous
-uploads never overwrite each other, refuses a symlinked or redirected
-attachments directory, and reports the path only after the bytes are
-synced. The local side refuses the answer unless size and sha256 equal the
-local file's. Each side buffers the whole file up to the bound; a remote
-file is never a local path over SSH. Upload never sends terminal input.
-`oats version --json` lists `session-upload` in `remote` and `features`.
-The CLI's temporary tmux viewer session hides its status line; the agents'
-session and the operator's tmux settings are untouched.
-
-## Desktop
-
-Drop files or paste clipboard images onto an agent terminal: the paths are
-inserted into the draft with bracketed paste and no Enter, local files in
-place, clipboard images saved privately under the app's data directory, and
-remote terminals uploaded through the installed CLI first (both CLIs must
-advertise `session-upload`; a failed transfer leaves the draft unchanged and
-never inserts a local path). Up to 16 files and 25 MB per drop. The viewer's
-tmux status bar is hidden. Ctrl+Tab stays tab navigation inside terminals
-on macOS while other Ctrl chords stay with the program. An already-open
-terminal fills an empty split without a second attach; separators resize by
-pointer or keyboard. Guide: docs/desktop.md, "Attach files and screenshots".
-
-## Design
-
-docs/design/2026-09-07-architecture-reassessment.md records the direction:
-keep the package and capability-layer machinery, fix the places where the
-CLI and GUI bypass it, one session contract with both tmux and Herdr
-adapters until Herdr is qualified, and the Desktop correction sequence.
+Tagged, not published; its changes shipped in v0.22.14.

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

@@ -1,8 +1,7 @@
 # OATS v0.22.14
 
-The same reviewed content as the unpublished v0.22.13 tag, whose hosted
-run failed in one Desktop test pin before anything was published; the
-test now checks the behaviour instead of the source text.
+Ships the content of the unpublished v0.22.13 tag, with its failing Desktop
+test fixed.
 
 Terminal essentials for the Desktop and one kernel operation behind them:
 attachments reach the agent as a path, never as typed input.
@@ -38,11 +37,4 @@ never inserts a local path). Up to 16 files and 25 MB per drop. The viewer's
 tmux status bar is hidden. Ctrl+Tab stays tab navigation inside terminals
 on macOS while other Ctrl chords stay with the program. An already-open
 terminal fills an empty split without a second attach; separators resize by
-pointer or keyboard. Guide: docs/desktop.md, "Attach files and screenshots".
-
-## Design
-
-docs/design/2026-09-07-architecture-reassessment.md records the direction:
-keep the package and capability-layer machinery, fix the places where the
-CLI and GUI bypass it, one session contract with both tmux and Herdr
-adapters until Herdr is qualified, and the Desktop correction sequence.
+pointer or keyboard. See [Attach files and screenshots](../desktop.md#attach-files-and-screenshots).

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

@@ -1,48 +1,3 @@
 # OATS v0.22.15
 
-Souls and capabilities become something you inspect and manage, through
-one kernel contract, and knowledge providers declare what they can do.
-
-## Provider operations and inspection (kernel)
-
-`oats inspect --json` answers everything a GUI needs in one envelope for a
-scope, a selected soul or a running home: souls with runtime defaults,
-editability and instructions; installed capabilities with health from the
-package engine, separately from their effective activation, provenance and
-settings; effective layer bindings; and the operations each provider
-declares, with availability and the reason when unavailable. For a home the
-answer is its captured bindings (with current manifests and trust), the live
-config beside it, and the drift between them. Same-named souls in member
-repositories are addressed by name plus agents root; a home selects its own
-soul under its own root.
-
-`oats operation run <layer>:<name>` resolves the provider that fills a layer
-for a home or a soul, checks declaration, trust and host requirements, runs
-the provider's own command in the right place with the right identity, and
-relays its receipt; a view answers labeled documents. Unconfirmed outcomes
-carry what was observed and a scheduled operation keeps its slot until
-reconciled. Manifests declare `operations`. Schedules gain kind
-`operation`. `oats use --json` answers receipts and `--inherit` returns a
-level to inheritance; `oats soul set` edits an editable soul's defaults and
-instructions in place. All four route to a registered server through the
-saved route; the probe advertises `operations` and `operationsApi: 1`. The
-retire receipt no longer implies a harvest. See
-docs/design/operations-contract.md.
-
-## oats.okf 1.6.0
-
-The official knowledge provider declares `inspect` (a view of STATE.md,
-log.md and pending notes) and `harvest` (the existing action); the catalog
-pins v1.6.0. Existing scopes keep their locked 1.5.2 until their owners
-update them; the GUI then shows no operations for those providers, which is
-the truthful state.
-
-## Desktop
-
-Souls & capabilities replaces the launch-centric roster: select a soul to
-inspect it, Launch and Schedule are explicit, defaults and instructions are
-editable where the kernel says so, installed capabilities are shown apart
-from activation with enable, disable and inherit at an exact scope, an
-instance's menu opens Knowledge & capabilities, provider views render as
-text, and schedules run declared provider operations. See
-docs/design/2026-09-07-desktop-souls-capabilities.md.
+Tagged, not published; its changes shipped in v0.22.16.

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

@@ -1,9 +1,7 @@
 # OATS v0.22.16
 
-The same reviewed content as the unpublished v0.22.15 tag, whose hosted
-run failed in frozen test data (retirement goldens still carrying the
-removed `harvested` field, and a Desktop harvest fixture predating the
-operations gate) before anything was published; only tests changed.
+Ships the content of the unpublished v0.22.15 tag, with its failing test
+data fixed.
 
 Souls and capabilities become something you inspect and manage, through
 one kernel contract, and knowledge providers declare what they can do.
@@ -31,8 +29,8 @@ reconciled. Manifests declare `operations`. Schedules gain kind
 level to inheritance; `oats soul set` edits an editable soul's defaults and
 instructions in place. All four route to a registered server through the
 saved route; the probe advertises `operations` and `operationsApi: 1`. The
-retire receipt no longer implies a harvest. See
-docs/design/operations-contract.md.
+retire receipt no longer implies a harvest. See the
+[operations contract](https://github.com/awebai/oats/blob/7838d3ca70772f63854b198601fbc45437c2e999/docs/design/operations-contract.md).
 
 ## oats.okf 1.6.0
 
@@ -49,5 +47,5 @@ inspect it, Launch and Schedule are explicit, defaults and instructions are
 editable where the kernel says so, installed capabilities are shown apart
 from activation with enable, disable and inherit at an exact scope, an
 instance's menu opens Knowledge & capabilities, provider views render as
-text, and schedules run declared provider operations. See
-docs/design/2026-09-07-desktop-souls-capabilities.md.
+text, and schedules run declared provider operations. See the
+[design note](https://github.com/awebai/oats/blob/7838d3ca70772f63854b198601fbc45437c2e999/docs/design/2026-09-07-desktop-souls-capabilities.md).

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

@@ -1,101 +1,3 @@
 # OATS v0.22.18
 
-Choose how an agent runs without replacing its home. Desktop offers
-**Start…** for stopped instances and **Restart with…** for running
-instances, with harness, model, permissions and named launch
-configurations. The kernel records what each home was started with and
-starts it again the same way.
-
-## Named launch configurations
-
-Define a reusable configuration in a scope's `oats-config.yaml`, or use
-**Manage launch configurations** in Desktop. A configuration chooses `pi`,
-`claude` or `codex`, an optional executable or wrapper, literal arguments,
-environment values or references, a default model and the shared `yolo`
-setting.
-
-```yaml
-launch-configs:
-  codex-personal:
-    runtime: codex
-    args: ["--profile", "personal"]
-    yolo: true
-```
-
-Arguments are passed literally; native configuration files and account
-settings stay under the harness's control. For environment credentials use
-a reference such as `API_KEY: {fromEnv: PERSONAL_KEY}`: the execution host
-resolves it each time the agent starts. The recorded recipe, receipts,
-previews, roster answers and spawn answers do not expose the value (the
-launch itself and its transport necessarily use it). A configuration cannot name the kernel's own launch
-environment or override environment a capability owns.
-
-An existing instance keeps its recorded launch configuration even if the
-scope's definition changes or disappears. Select a named configuration
-explicitly to apply its current definition. Changing only the model or
-permissions keeps the rest of the recorded invocation; choosing a harness
-without a configuration starts that harness's defaults, with no model
-carried across harnesses.
-
-`oats launch-config list | set | remove | preview` author and inspect
-configurations; `oats spawn --launch-config` starts a new instance under
-one; a soul may name a default (`launch-config:` in soul.yaml,
-`oats soul set --launch-config`).
-
-## Restart in place
-
-`oats session start` with a selection validates the requested launch
-(recipe, executable, references, capability preparation, runtime packages)
-and starts a stopped instance; it never stops a running harness. Only
-`oats session restart` does: it runs the same checks first, then sends
-SIGTERM to the harness under the pane's launcher and waits a bounded time
-for it to end; it does not escalate to a forced kill and refuses to launch
-a second harness if it cannot confirm the first has stopped, reporting what
-was signalled and observed. The instance keeps its home, identity, work and
-notes; OATS does not transfer a native conversation between harnesses.
-Save work before restarting.
-
-Capabilities take part through what was captured for the home: a capability
-may declare a `launch` hook to prepare another harness (under the settings
-captured at spawn, with the scope's current manifest and trust); a
-capability that contributed harness-specific arguments and cannot prepare
-the new one refuses the switch. Homes that predate launch recipes are
-converted narrowly from their recorded command when a selection asks for
-it; unrecognized arguments are refused by name.
-
-One limitation, stated rather than hidden: a runtime-package requirement is
-verified with the package manager's controlled list command under the
-launch's environment and executable, which cannot carry a configuration's
-arguments. When such a requirement applies and the configuration passes
-arguments, the launch is not reported verified (`E_LAUNCH_PROBE_UNSUPPORTED`):
-put native configuration a required package must see in a wrapper
-executable or the environment.
-
-```sh
-oats launch-config list --dir /path/to/team
-oats launch-config preview --home /path/to/instance --runtime codex --json
-oats session restart --home /path/to/instance --launch-config codex-personal
-```
-
-Local tmux and Herdr sessions use the same lifecycle operations. Registered
-servers support configuration management and start/restart choices through
-their installed OATS CLI (probe tokens `launch-config`, `session-restart`);
-existing remote homes keep their saved route, and an older kernel is
-refused after the compatibility probe, before any mutation or stop.
-
-## Desktop fixes
-
-Tabs from other workspaces stay hidden. Instance action menus are positioned
-correctly when opened and remain stable through roster refreshes. Failed
-launch preflight checks are shown in the invocation preview, and an accepted
-launch is not presented as a running agent until the terminal is observed.
-
-## Also in this release
-
-- Capture lock (source only; the installed capture service is unchanged):
-  nonce-checked ownership, cleanup of a failed initialization that respects
-  a replacement, release outcomes reported as observed, and the privacy
-  loader's exit no longer leaves a lock behind.
-- A design proposal for managing agents from an iPhone over Tailscale
-  (docs/design/2026-09-07-mobile-agent-management-proposal.md); no
-  implementation ships.
+Tagged, not published; its changes shipped in v0.22.19.

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

@@ -1,12 +1,7 @@
 # OATS v0.22.19
 
-Version 0.22.18 was tagged but never published: its hosted gate failed on
-four tests that pass on macOS and fail on Linux (two launch tests calling
-the kernel directly resolved the real harness binary on the test process
-PATH, one launch test spawned zsh, which the runner does not install, and
-one capture-lock test where Linux reused the inode of an unlinked
-directory). The tag stays fixed and unpublished. This release carries the
-same content with the corrections below.
+Ships the content of the unpublished v0.22.18 tag, with fixes for tests that
+failed on Linux.
 
 Choose how an agent runs without replacing its home. Desktop offers
 **Start…** for stopped instances and **Restart with…** for running
@@ -71,7 +66,7 @@ the new one refuses the switch. Homes that predate launch recipes are
 converted narrowly from their recorded command when a selection asks for
 it; unrecognized arguments are refused by name.
 
-One limitation, stated rather than hidden: a runtime-package requirement is
+Known limit: a runtime-package requirement is
 verified with the package manager's controlled list command under the
 launch's environment and executable, which cannot carry a configuration's
 arguments. When such a requirement applies and the configuration passes
@@ -107,9 +102,3 @@ launch is not presented as a running agent until the terminal is observed.
   is held open until its owner record is written or its cleanup finishes,
   preventing its inode from being reused during cleanup; a replacement
   directory is left alone.
-- Test fixtures: the launch tests resolve their fake harness binaries on the
-  test process PATH and exercise only the shells the host installs; no
-  kernel change.
-- A design proposal for managing agents from an iPhone over Tailscale
-  (docs/design/2026-09-07-mobile-agent-management-proposal.md); no
-  implementation ships.

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

@@ -30,14 +30,9 @@ Register an existing SSH host with `oats server add`, then use `--server`
 on spawn, status, retire and session inspect/attach. Saved routes keep
 retirement and attachment available if a registration changes. SSH retains
 responsibility for keys and host verification. Desktop includes a server
-selector and the remote terminal adapter; remote roster projection remains
-a follow-up, so use the CLI to attach to a remote instance in this release.
-
-Live checks covered native Codex launch and subsequent terminal input on
-both local backends. A real remote Claude session accepted input through
-the Desktop terminal helper, survived viewer closure, and ended its viewer
-on retirement. Herdr roster checks include public IDs beyond the ninth
-workspace. These checks do not establish reboot recovery.
+selector and the remote terminal adapter; it does not show remote rosters in
+this release, so use the CLI to attach to a remote instance. Recovery after a
+host reboot is not supported.
 
 ## Learning and retirement
 
@@ -56,14 +51,10 @@ as instances. Retiring an instance whose work tree is large no longer fails with
 now runs with a buffer far above Node's 1 MiB default (found on a real
 ~9,500-file tree).
 
-## Package versions and remaining work
+## Package versions and known limits
 
 The catalog pins `oats.okf` v1.5.0 and `oats.aweb` v1.9.0. The latter updates
 native Codex's messaging instructions; its Pi and Claude channel delivery
 is unchanged. Native Codex has no automatic aweb delivery in this release.
-
-The aweb host wake broker, session-delivery capability glue, retained-identity
-handover and supported standing-seat reboot recovery are still being
-completed. Hosted temporary aliases also remain non-reusable until aweb's
-certificate-retirement fix ships; use fresh purpose names. A configured
-team or successful spawn does not mean its standing agents have migrated.
+Hosted temporary aliases are not reusable after retirement; use fresh purpose
+names.

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

@@ -73,7 +73,6 @@ reusable yet.
   `features` list carries `retire-home`.
 - `oats retire --json` keeps stdout to the envelope (the cross-repo note goes
   to stderr).
-- Goldens carry `environmentNamespaces` in the resolved capability projection.
 - Viewers for remote instances resolve by home: `session inspect|attach
   --server <id> --home <remote home>` uses the saved route that owns the home
   and refuses a name paired with a different one.

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

@@ -1,7 +1,7 @@
 # OATS v0.22.4
 
 Two fixes found by running the wake broker and the record-fed harvester as
-real host services, the oats.aweb 1.10.1 floor, and the managed lead soul.
+host services, and the oats.aweb 1.10.1 floor.
 
 ## Session commands under a service locale
 
@@ -25,16 +25,3 @@ Session-mode delivery now requires an installed Claude Code channel plugin
 to be `aweb-channel` 1.7.9 or later (as it already required `@awebai/pi`
 0.3.10): an older plugin starts its own channel server beside the wake
 broker and can fetch a message before the broker delivers it.
-
-## Managed operating-lead soul
-
-`agents/lead/soul` is tracked: the operating lead's role instructions and
-two knowledge notes (runtime and messaging ownership; where rollout state
-lives), ready for a retained-identity binding at its cutover.
-
-## Also
-
-- `docs/operating-team-migration.md` records the published 0.22.3 rollout and
-  the live wake-broker acceptance on Claude, Codex and Pi.
-- oats.okf 1.5.1 (harvest-runtime, promotion exclusions, replan detector) is
-  not in this release; it ships when its independent review completes.

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

@@ -1,8 +1,7 @@
 # OATS v0.22.5
 
-A small release: the knowledge package 1.5.1 pin, a way to move a pinned
-package lock from the CLI, and the operating records from the first team
-rollouts.
+A small release: the knowledge package 1.5.1 pin and a way to move a pinned
+package lock from the CLI.
 
 ## Bundled: oats.okf 1.5.1
 
@@ -25,12 +24,3 @@ invalidated, then `oats trust`). A plain `oats update <package>` keeps an
 explicit selector, as before, and `--to` without a package is refused rather
 than falling through to the kernel self-update (`oats update` with no
 package).
-
-## Also
-
-- The managed oats coordinator soul (`agents/oats-coordinator/soul`) is
-  tracked, with playbooks for the release lane, payload publication and
-  review routing.
-- `docs/operating-team-migration.md` records the installed 0.22.4 rollout,
-  the completed record-fed and note-fed harvest cycles, and the standing
-  seats prepared for cutover.

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

@@ -48,6 +48,3 @@ leaving a bound alias behind, retirement reads the alias from the home's
 ## Also
 
 - `oats use` from no binding writes a targeted binding with `global: false`.
-- `docs/operating-team-migration.md` records the live rollout, the memory
-  incident and its mitigation, the serial launch constraint and the TSM
-  deployment hold.