@awebai/oats 0.26.0 → 0.27.1

package/docs/servers.md

@@ -25,8 +25,8 @@ oats server list
 - `--path` names directories to prepend to the remote PATH for every routed
   command (`~/.local/bin:/opt/pi/bin`). A non-interactive ssh command runs in
   the login shell's minimal PATH, and the remote kernel's spawn preflight looks
-  for the runtime binary (`claude`, `pi`, `codex`) there; without this, a
-  runtime installed under the user's home is "not found" even though it runs
+  for the harness binary (`claude`, `pi`, `codex`) there; without this, a
+  harness installed under the user's home is "not found" even though it runs
   fine in an interactive shell on that host.
 - Registrations live in `~/.oats/servers.json` on this machine, never in a
   repository scope.
@@ -44,13 +44,13 @@ worktree, identity, launch, retirement. The local side only routes: a local
 `--task-file` travels as text, every argument is quoted for the remote login
 shell, and the remote's version and envelope are checked before either
 mutation (spawn and retire). A spawn is also held to what the remote
-advertises: a runtime it does not list (including the soul's own default as
+advertises: a harness it does not list (including the soul's own default as
 the remote roster reports it), a session backend it lacks, or a launch option
 such as `--yolo` it does not know is refused with `E_REMOTE_INCOMPATIBLE`
 saying what was established. A remote that advertises nothing (any kernel
 before 0.22.2) is assumed to run pi and claude on tmux with no options, and
 the refusal says so rather than claiming the remote lacks the feature; a soul
-the remote roster does not list with a runtime is validated by the remote
+the remote roster does not list with a harness is validated by the remote
 kernel itself at spawn. `--dir` and `--server` do not combine; the remote
 workspace comes from the registration.
 

package/docs/souls-and-instances.md

@@ -68,9 +68,9 @@ compatibility:                            # optional floors on PACKAGE versions
 | `compatibility` | `<cap>: <semver range>` checked against the locked package version (`E_COMPATIBILITY`). |
 
 Schema: [`soul.schema.json`](soul.schema.json). Not in v2: `kind`, `type`,
-`repo`, `runtime`, `model`, `backend`, `yolo`, `launch-config`, `children`,
+`repo`, `harness`, `model`, `backend`, `yolo`, `launch-config`, `children`,
 `requires`, `source:`, `stores.inherit`. Runtime, model, backend, yolo and the
-launch configuration are spawn-time host choices (`--runtime`, `--model`,
+launch configuration are spawn-time host choices (`--harness`, `--model`,
 `--backend`, `--yolo`, `--launch-config`, or a launch configuration in
 `oats-local.yaml`), not soul identity: a soul is model-agnostic as an artifact.
 A child-spawn policy is a spawn flag too (`--no-child-spawns`).
@@ -303,13 +303,13 @@ evidence but never waits for a model or GitHub: independent processing and
 source-targeted inspection continue after the home disappears.
 
 `oats retire <instance> --self` lets an instance retire itself when the human
-or briefing says it is done. A live runtime cannot give a stable final
+or briefing says it is done. A live harness cannot give a stable final
 inspection of its own work, so the calling process inspects, runs, and removes
 nothing: it records the intent beside its home as
 `.oats-retire-pending-<instance>.json` and starts a detached completion, then returns so the instance can report final
 status before its tmux window dies a few seconds later. The completion then
 retires the instance exactly as an external `oats retire` would: quiesce the
-runtime, preserve uncommitted work, run retire hooks, repair lineage, remove
+harness, preserve uncommitted work, run retire hooks, repair lineage, remove
 the worktree and the home. Success leaves nothing behind: the home and the
 marker are gone. A failure writes `.oats-retired-<instance>.json` beside the
 retained home (plus the usual quarantine marker when hooks reported incomplete
@@ -399,7 +399,7 @@ directory; without it, the deployment directory (where `oats-local.yaml` is) is
 used. No implicit fallback changes the other modes.
 
 `--work-dir` and `--branch` are rejected. Canonical instructions, skill
-composition, provider trust and runtime preflight still apply. No worktree setup
+composition, provider trust and harness preflight still apply. No worktree setup
 runs. Retirement preserves nonempty work in verified recovery storage beside the
 home (`workRecovery.path/work`) before deleting it, including files created by
 hooks; directory work has no disposable-root exemptions. The work-root cannot be
@@ -469,7 +469,7 @@ they are stated separately:
   compatibility aliases for the separately published pi extension.
 - **Lifecycle hooks**: `OATS_INSTANCE_HOME` and `OATS_HOME`, alongside the rest of
   the hook contract. `OATS_HOME` predates `OATS_INSTANCE_HOME` and is kept because
-  shipped capability hooks read it; it is **not** exported to runtime sessions.
+  shipped capability hooks read it; it is **not** exported to harness sessions.
 
 Neither is `OATS_HOME_DIR`, which is the package store root — do not conflate
 them.

package/injects/instance-boundary.md

@@ -1,7 +1,7 @@
 ## Your two directories
 
 **`<instance-home>` is where this session starts** — the specific gitignored OATS
-instance directory you woke up in, given to your runtime and to every lifecycle
+instance directory you woke up in, given to your harness and to every lifecycle
 hook as `$OATS_INSTANCE_HOME`. It is not your user home (`~`), not the repository
 root, and not the work tree. Anything that says "your home" means this directory.