@awebai/oats 0.69.9 → 0.69.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -39,7 +39,7 @@ If you are a person, give your coding agent (Claude Code, Codex, pi or any other
39
39
 
40
40
  - **Asks first, in one round:** your project, its repositories and where the workspace should live, the knowledge tools you use, and how your agents message each other ([aweb](https://aweb.ai) by default).
41
41
  - **Installs OATS, OATS Desktop and the messaging CLI.**
42
- - **Creates your workspace's team:** you sign in to your aweb account in your browser, and one command creates the team, owned by your account, that every agent you spawn joins.
42
+ - **Creates your workspace's team,** with no sign-in: the workspace's team, on an aweb account created for it, that every agent you spawn joins. You attach yourself to the account later in the setup, with the setup expert, or sign in to your own aweb account instead if you want the team on it from the start.
43
43
  - **Writes your workspace** in one commit, in your repository or a new private one: the workspace and its team, nothing else. Or it joins this machine to an existing workspace.
44
44
  - **Spawns the setup expert and opens the Desktop on it.** The setup expert is an OATS agent that turns OATS's defaults into your own coordination, knowledge and tasks capabilities, with you. You type only passwords, logins and tokens.
45
45
 
package/bin/oats.mjs CHANGED
@@ -3893,7 +3893,7 @@ async function capabilityCommand() {
3893
3893
  if (!hit) return NOT_DISPATCHED;
3894
3894
  // Without --soul the dispatch chose the soul (feature operator-default-soul): say which, on stderr,
3895
3895
  // so a provider's stdout (its --json envelope included) is untouched.
3896
- if (hit.defaultSoul) process.stderr.write(`oats ${cmd}: no --soul given; running as soul ${hit.defaultSoul}, the first soul of this deployment that provides "${cmd}" (pass --soul <name> to choose)\n`);
3896
+ if (hit.defaultSoul) process.stderr.write(`oats ${cmd}: using the settings and teams of soul ${hit.defaultSoul}, the first soul by name in this deployment that provides "${cmd}"; pass --soul <name> to use another\n`);
3897
3897
  // The same team/workspace facts a spawn hook receives (lead decision c3-7).
3898
3898
  const teamCtx = teamEnv(resolvedFromPrepared(hit.prepared, hit.deployment));
3899
3899
  // No home, so no recorded soul: OATS_SOUL is the soul's source at the resolved commit, read
@@ -74,9 +74,12 @@ A self-contained package has an `oats.json`:
74
74
  resolves as a spawn of a soul would: the soul named by `--soul <name>`, or,
75
75
  without `--soul`, the first soul of the deployment by name, not disabled
76
76
  there, whose resolution provides the namespace (souls whose resolution is
77
- refused are skipped). The chosen soul is named on stderr (`oats <namespace>:
78
- no --soul given; running as soul <member>/<soul>, …`), so the command's
79
- stdout, its `--json` envelope included, is the provider's alone. When no
77
+ refused are skipped). The chosen soul is named on stderr, so the command's
78
+ stdout, its `--json` envelope included, is the provider's alone:
79
+ `oats <namespace>: using the settings and teams of soul <member>/<soul>, …`.
80
+ The command runs with that soul's resolution (its provider settings, its
81
+ teams, its source and its name, in the variables below) and starts no
82
+ instance of it. When no
80
83
  soul provides the namespace, the command is refused with `E_BAD_ARGS` (`no
81
84
  soul of this deployment provides the <namespace> namespace; pass --soul
82
85
  <name>`, with any skipped souls and their codes in `details.skipped`).
@@ -416,8 +419,8 @@ the workspace's slot default. Teams compose nothing, so a soul's composition
416
419
  is the same for every person and machine. A resolved capability whose manifest says `layer: X` fills slot X; two for one slot are
417
420
  `E_SLOT_CONFLICT`. Provider settings start from the manifest's own declared
418
421
  defaults (`settings.<key>.default`, the lowest layer), then take the workspace's
419
- `messaging` payload for the messaging slot, the soul's
420
- slot payload, `oats-local.yaml` `settings.<cap>`, and `oats spawn --provider`,
422
+ `messaging` payload for the messaging slot or its `tasks` payload for the tasks
423
+ slot, the soul's slot payload, `oats-local.yaml` `settings.<cap>`, and `oats spawn --provider`,
421
424
  deep-merged in that order. There are no agent types, no `global`, no
422
425
  per-deployment activation or exclusion maps.
423
426
 
@@ -802,6 +805,25 @@ resolver accepts it only from the deployment's own `oats-local.yaml`
802
805
  Declare it for any key whose value points at something a committed file must
803
806
  never be able to choose.
804
807
 
808
+ The mirror is `committedOnly: true`: a key that must be the same for every
809
+ deployment of the workspace, such as which shared list a tasks provider uses.
810
+ The resolver accepts it only from committed, reviewed files, and refuses it in
811
+ the deployment's `oats-local.yaml` `settings.<capability>` and in a
812
+ `--provider` flag (`E_WORKSPACE_SCHEMA`, reason `committed-only-key`). It is a
813
+ refusal, not a warning, and the key's presence is enough, even with the
814
+ committed value. Where it may be set follows the capability's layer: for a
815
+ messaging or tasks capability, `oats-workspace.yaml` under `messaging:` or
816
+ `tasks:`, or a soul's slot payload; for a knowledge capability, a soul's
817
+ `knowledge:` payload; for a capability with no layer, only its manifest
818
+ default. The refusal names the key, where it was set (`details.layer` `host` or
819
+ `spawn`, `details.at`), where it may be set (`details.allowed`) and the fix. A
820
+ key marked both `hostOnly` and `committedOnly` could be set by nothing but its
821
+ default, so the resolver refuses the manifest (`E_PACKAGE_MANIFEST` for a
822
+ package capability, `E_CAPABILITY_MISSING` for a member one, `details.why`
823
+ `settings-flag-conflict`). The kernel does not validate manifests against the
824
+ schema, so a kernel without the feature `settings-committed-only` ignores the
825
+ flag and merges the key from any layer.
826
+
805
827
  A hook may return only names in its manifest's exact `environment` declaration.
806
828
  For package capabilities that declaration is part of the integrity-locked tree
807
829
  the workspace declared; for member capabilities it is part of what membership
@@ -335,8 +335,16 @@
335
335
  "hostOnly": {
336
336
  "type": "boolean",
337
337
  "description": "When true, this key is a host fact (a custody path, a state directory): the resolver accepts it only from the deployment's oats-local.yaml settings.<capability> and refuses it in the workspace file, a soul's slot payload and --provider flags (E_WORKSPACE_SCHEMA reason host-only-key). Decision 27."
338
+ },
339
+ "committedOnly": {
340
+ "type": "boolean",
341
+ "description": "When true, this key must be the same for every deployment (the mirror of hostOnly): the resolver accepts it only from committed, reviewed files (the manifest default, oats-workspace.yaml's messaging: or tasks: payload for a capability of that slot, a soul's slot payload) and refuses it in oats-local.yaml settings.<capability> and --provider flags (E_WORKSPACE_SCHEMA reason committed-only-key). Never true together with hostOnly. Kernels without the settings-committed-only feature ignore it."
338
342
  }
339
343
  },
344
+ "not": {
345
+ "required": ["hostOnly", "committedOnly"],
346
+ "properties": { "hostOnly": { "const": true }, "committedOnly": { "const": true } }
347
+ },
340
348
  "additionalProperties": false
341
349
  }
342
350
  },
@@ -57,7 +57,7 @@ refused (`E_WORKSPACE_SCHEMA`).
57
57
 
58
58
  | key | meaning |
59
59
  |---|---|
60
- | `workspace` | Repo ref of the workspace host (`git:host/org/repo`, `https://…`, `git@host:…`, `file:///…`, `/abs/bare.git`). Read with your own Git credentials; it need not be cloned. |
60
+ | `workspace` | Repo ref of the workspace host (`git:host/org/repo`, `https://…`, `git@host:…`, `ssh://<user>@<host>[:<port>]/…` with no password, `file:///…`, `/abs/bare.git`). Read with your own Git credentials; it need not be cloned. |
61
61
  | `standalone` | A repo ref to realize on its own: its souls and `from: here` capabilities plus `oats.core`, with no workspace lookup. For a repository whose workspace this machine cannot read ([workspaces.md](workspaces.md#the-standalone-case)). |
62
62
  | `clones` | `<repo key>: <absolute path>` for a member clone that is not at `<deployment>/<member name>/`. Only a soul whose work target needs a clone (`work: worktree \| checkout`) uses it. Lookup order: `spawn --repo`, then this map, then `<deployment>/<member name>` (a member named `agents` → `<deployment>/agents-repo`). None → `E_CLONE_MISSING`; a directory whose `origin` is another repository → `E_CLONE_MISMATCH`. |
63
63
  | `launchPromptAnswers` | Ignored, with a warning to remove it; a home entry `awebDevelopmentChannel: false` is refused. See [the development-channel confirmation](#the-development-channel-confirmation). |
@@ -130,7 +130,7 @@ see the [official catalog](official-catalog.md) for current pins.
130
130
  | `servers-per-workspace` | `workspaceKey` on registrations and `oats server list --json` rows; `oats server list --workspace-ref <ref>` and its `unknownWorkspace`; `workspaceKey` on `oats server check --json`, OATS 0.39.0 ([Servers per workspace](#servers-per-workspace)) | |
131
131
  | `server-connect` | `oats server connect`; `oats onboard --check`; `workspaceReadable` on `oats server check --json`, OATS 0.39.0 ([`oats server connect`](#oats-server-connect)) | |
132
132
  | `capability-route` | `oats <namespace> <command> … --server <id>` runs the capability command on the server, OATS 0.39.0 ([Capability commands on a server](#capability-commands-on-a-server)) | |
133
- | `operator-default-soul` | a capability command from a deployment without `--soul` runs as the first soul that provides its namespace (named on stderr); none is `E_BAD_ARGS`, OATS 0.39.0 ([capabilities.md](capabilities.md)) | |
133
+ | `operator-default-soul` | a capability command from a deployment without `--soul` resolves as the first soul that provides its namespace, using its settings and teams (named on stderr); none is `E_BAD_ARGS`, OATS 0.39.0 ([capabilities.md](capabilities.md)) | |
134
134
  | `waiting-on-you` | the `waiting` event kind and the session boundary rule; `oats instance waiting` and `oats instance attention`; `waitingOnYou` (with `message`) on `oats status --json` instance rows, on `oats session inspect --json` and in the events read, OATS 0.40.0 ([Waiting on you](#waiting-on-you)) | `eventsApi: 2` |
135
135
  | `automation-descriptions` | a `description` on every trigger and schedule row, local or workspace, by one rule; `oats schedule update <id> --description=<text>` (the description only) and `oats trigger update <id> --description=<text>`; `--description=<text>` on `schedule add` and `trigger add`, OATS 0.43.0 ([Shared row fields](#automations-shared-rows)) | |
136
136
  | `souls-capabilities` | `capabilities` on `oats souls --json` rows: the capabilities each soul composes, keyed like `oats capabilities` rows, with `from`, OATS 0.45.0 ([`oats capabilities` and `oats souls`](#oats-capabilities---dir---json--capabilitiesapi-1--oats-souls---dir---json--soulsapi-1)) | |
@@ -169,6 +169,8 @@ see the [official catalog](official-catalog.md) for current pins.
169
169
  | `wake-hold` | a scheduled wake sends no key while the home has a live `permission`, `question` or unknown-reason claim, or a claims read that can't be trusted: the run is `skipped`, `reason: "waiting-on-you"`, `pending: true`, with `held` ([A held wake](schedules.md#a-held-wake)); the `wake-held` event ([the event kinds](#events)); `wakeHold` on every successful `session inspect --json` ([Inspect, input and attach](execution-targets.md#inspect-input-and-attach)), from the hook answer `dialogClaims` ([Commands and hooks](capabilities.md#commands-and-hooks)). Gate on the feature, then on `wakeHold`: the feature says this kernel holds, `wakeHold` whether this home's dialogs become claims, and `unknown` is not covered | |
170
170
  | `lifecycle-claim-start` | every `oats session start` and `oats session restart`, and a scheduled start, holds the home's lifecycle claim for the whole start (#1602), as `details.action: "start"`: a retire, a stop apply or an upgrade apply that arrives while it runs is refused `E_LIFECYCLE_BUSY` with `details.action: "start"`; the start or restart is refused `E_INSTANCE_RETIRING` beside a retire and `E_LIFECYCLE_BUSY` (with `details.holder` and `details.action`) beside a stop or an upgrade, before any effect; two starts still answer `E_SESSION_START_BUSY` ([Commands that meet on one home](#lifecycle-pairs)). A restart holds one claim across its stop and its launch. A kernel without it takes no claim for these, and reads a `start` holder as a retire | |
171
171
  | `spawn-attribution` | the kernel validates who spawned an instance: `spawnedBy` (`{instance, home}` or `null`) in `instance.json`, on the `spawned` event and on `oats status --json` rows and remote rows, and `OATS_SPAWNER_HOME` for spawn hooks ([Spawned by](#spawned-by)); `attributedHuman` on `oats status --json` rows and on remote rows ([Attributed human](#attributed-human)). Absent: no `spawnedBy` and no `attributedHuman`, and a capability must not read a missing `OATS_SPAWNER_HOME` as a person's spawn | |
172
+ | `workspace-tasks-payload` | oats-workspace.yaml may carry a top-level `tasks:` payload, merged for the capability that fills the tasks slot exactly as `messaging:` is for the messaging one; its leaves' `settingsOrigins` are `{kind: "workspace", at: "oats-workspace.yaml#/tasks"}` ([Provider payloads have three homes](workspaces.md#provider-payloads-have-three-homes)). A kernel without it refuses a workspace file that carries `tasks:` (unknown property) | |
173
+ | `settings-committed-only` | a manifest `settings.<key>.committedOnly: true` is enforced: that key in oats-local.yaml `settings.<cap>` or a `--provider <cap>` flag is refused `E_WORKSPACE_SCHEMA` reason `committed-only-key`, with `details.layer`, `details.at` and `details.allowed` ([Commands and hooks](capabilities.md#commands-and-hooks)). A kernel without it ignores the flag and merges the key | |
172
174
 
173
175
  Payload-only integers, never in the probe: `onboardApi: 2`, `syncApi: 1`,
174
176
  `workspaceStatusApi: 1`, `capabilitiesApi: 1`, the `oats souls` document's
@@ -41,7 +41,7 @@ arrives from.
41
41
  # oats-workspace.yaml: one default per slot, for every soul
42
42
  packages:
43
43
  oats.okf: v5.7.0
44
- oats.aweb: v1.33.1
44
+ oats.aweb: v1.35.0
45
45
  oats.linear: v1.0.1
46
46
  oats.jira: v1.0.1
47
47
  defaults:
@@ -102,7 +102,12 @@ operations in full.
102
102
  provider in `capabilities:` (`oats.jira`, `oats.linear`) then holds two and
103
103
  fails with `E_SLOT_CONFLICT`: to keep its own, it adds
104
104
  `oats.aweb-tasks: off` to its `capabilities:`. A soul opts out of tasks
105
- entirely with `tasks: none`.
105
+ entirely with `tasks: none`. **A new workspace** made by the `oats-getting-started`
106
+ skill with aweb (not on a machine found-list) has it by default: the
107
+ skill writes this default (the team's first aweb task opts it in), unless
108
+ the person's projects
109
+ already use a tracker (GitHub issues in use, Jira, Linear and the like),
110
+ when it writes `tasks: none` and the setup expert connects the tracker.
106
111
  - **`oats.aweb`** mints a messaging identity for each instance at spawn and
107
112
  removes it at retire, contributes the aweb messaging skills, and wires the
108
113
  channel so sessions are woken by mail. Under `delivery: channel`, Claude Code
@@ -151,6 +156,12 @@ Building an integration is implementing a contract. The framework's
151
156
  `oats-local.yaml` `settings.<cap>` and refuses it elsewhere
152
157
  (`E_WORKSPACE_SCHEMA`, reason `host-only-key`). The provider cannot enforce
153
158
  this itself: it receives one merged payload without provenance.
159
+ - A setting every deployment must share (which shared task list to use) is
160
+ declared `committedOnly: true`, the mirror: the resolver refuses it from
161
+ `oats-local.yaml` `settings.<cap>` and `--provider` (`E_WORKSPACE_SCHEMA`,
162
+ reason `committed-only-key`), so it comes only from the workspace's
163
+ `messaging:` or `tasks:`, a soul's slot payload or the manifest default.
164
+ Kernels without the feature `settings-committed-only` ignore the flag.
154
165
  - A slot provider that declares `binding` answers `oats readiness` through
155
166
  its `binding.check` command
156
167
  ([capabilities.md](capabilities.md#readiness-check-bindingcheck)).
@@ -11,13 +11,13 @@
11
11
  "workspace": {
12
12
  "type": "string",
13
13
  "minLength": 1,
14
- "pattern": "^(?:git@[^@\\s]+|[^@\\s]+)$",
14
+ "pattern": "^(?:git@[^@\\s]+|ssh:/{2}[A-Za-z0-9._~][A-Za-z0-9._~-]*@[^@\\s]+|[^@\\s]+)$",
15
15
  "description": "Repo ref of the workspace host; observed over the remote, need not be cloned."
16
16
  },
17
17
  "standalone": {
18
18
  "type": "string",
19
19
  "minLength": 1,
20
- "pattern": "^(?:git@[^@\\s]+|[^@\\s]+)$",
20
+ "pattern": "^(?:git@[^@\\s]+|ssh:/{2}[A-Za-z0-9._~][A-Za-z0-9._~-]*@[^@\\s]+|[^@\\s]+)$",
21
21
  "description": "Repo ref to realize in the STANDALONE view: its own souls and from: here capabilities plus oats.core, no workspace lookup. Use when the repo's workspace cannot be read; `workspace:` still names the repo you point the kernel at."
22
22
  },
23
23
  "clones": {
@@ -11,7 +11,7 @@
11
11
  "workspace": {
12
12
  "type": "string",
13
13
  "minLength": 1,
14
- "pattern": "^(?:git@[^@\\s]+|[^@\\s]+)$",
14
+ "pattern": "^(?:git@[^@\\s]+|ssh:/{2}[A-Za-z0-9._~][A-Za-z0-9._~-]*@[^@\\s]+|[^@\\s]+)$",
15
15
  "description": "Repo ref of the workspace host, without revision."
16
16
  }
17
17
  }
@@ -52,6 +52,10 @@
52
52
  "type": "object",
53
53
  "description": "Opaque provider payload consumed by the messaging core capability. A team's provider id is teams.<label>.team."
54
54
  },
55
+ "tasks": {
56
+ "type": "object",
57
+ "description": "Opaque provider payload consumed by the capability that fills the tasks slot, merged at the same layer as messaging: (above the manifest's defaults, below a soul's tasks: payload). Kernels before the workspace-tasks-payload feature refuse this key."
58
+ },
55
59
  "external": {
56
60
  "type": "array",
57
61
  "items": { "$ref": "#/$defs/external" },
@@ -72,12 +76,12 @@
72
76
  "memberRef": {
73
77
  "type": "string",
74
78
  "minLength": 1,
75
- "pattern": "^(?:git@[^@\\s]+|[^@\\s]+)$",
76
- "description": "A repo ref (git:<host>/<path>, https://…, git@host:path.git, file:///…) with NO @revision."
79
+ "pattern": "^(?:git@[^@\\s]+|ssh:/{2}[A-Za-z0-9._~][A-Za-z0-9._~-]*@[^@\\s]+|[^@\\s]+)$",
80
+ "description": "A repo ref (git:<host>/<path>, https://…, git@host:path.git, ssh://<user>@<host>[:<port>]/<path> with no password, file:///…) with NO @revision."
77
81
  },
78
82
  "pinnedRef": {
79
83
  "type": "string",
80
- "pattern": "^(?:git@[^@\\s]+|[^@\\s]+)@[0-9a-f]{40}$",
84
+ "pattern": "^(?:git@[^@\\s]+|ssh:/{2}[A-Za-z0-9._~][A-Za-z0-9._~-]*@[^@\\s]+|[^@\\s]+)@[0-9a-f]{40}$",
81
85
  "description": "<repo ref>@<full 40-hex commit OID>."
82
86
  },
83
87
  "repoKey": {
@@ -9,9 +9,9 @@ or workspace membership alone does not make a package official.
9
9
 
10
10
  | package | release | capabilities | package souls |
11
11
  |---|---|---|---|
12
- | `oats.framework` | `oats-framework/v1.19.0` (this repository) | `oats.core`, `oats.setup`, `oats.onboarding`, `oats.support`, `oats.knowledge-theory` | `knowledge-theory-expert`, `oats-setup-expert` |
12
+ | `oats.framework` | `oats-framework/v1.21.0` (this repository) | `oats.core`, `oats.setup`, `oats.onboarding`, `oats.support`, `oats.knowledge-theory` | `knowledge-theory-expert`, `oats-setup-expert` |
13
13
  | `oats.okf` | `v5.7.0` | `oats.okf` (knowledge), `oats.okf-harvest`, `oats.okf-maintenance` | `knowledge-harvester`, `knowledge-maintainer` |
14
- | `oats.aweb` | `v1.33.1` | `oats.aweb` (messaging), `oats.aweb-tasks` (tasks) | |
14
+ | `oats.aweb` | `v1.35.0` | `oats.aweb` (messaging), `oats.aweb-tasks` (tasks) | |
15
15
  | `oats.engineering` | `v1.18.0` | `oats.engineering-expert`, `oats.developer`, `oats.code-review`, `oats.maintainer` | `code-reviewer` |
16
16
  | `oats.authoring` | `v1.0.3` | `oats.authoring` | |
17
17
  | `oats.cloning` | `v1.1.0` | `oats.cloning` | `cloner` |
package/docs/packages.md CHANGED
@@ -51,7 +51,7 @@ packages:
51
51
  - **Bare version** (`v5.7.0`, `5.7.0`, `1.0.0-rc.1`): the id is looked up in
52
52
  the official catalog — `package-catalog.json` in the `oats` repo, or the file
53
53
  named by `OATS_PACKAGE_CATALOG` — which supplies the repo url, the tag
54
- convention (`v5.7.0` or `oats-framework/v1.19.0`) and the payload path. An id
54
+ convention (`v5.7.0` or `oats-framework/v1.21.0`) and the payload path. An id
55
55
  the catalog does not know is `E_PACKAGE_MISSING` ("use `git:<repo>@<ref>` for
56
56
  a package outside the catalog"). The catalog is the reviewed official list
57
57
  ([official-catalog.md](official-catalog.md)) and the only way a
@@ -74,9 +74,9 @@ members:
74
74
  - git:github.com/acme/agents
75
75
  - git:github.com/acme/platform
76
76
  packages:
77
- oats.framework: v1.19.0
77
+ oats.framework: v1.21.0
78
78
  oats.okf: v5.7.0
79
- oats.aweb: v1.33.1
79
+ oats.aweb: v1.35.0
80
80
  teams:
81
81
  platform: { team: "platform:acme.aweb.ai", description: Platform engineering }
82
82
  defaults:
@@ -134,7 +134,7 @@ Declaring a package in the workspace's `packages:` is the trust decision
134
134
  ## `oats package add | remove`
135
135
 
136
136
  ```bash
137
- oats package add oats.aweb v1.33.1 # a catalog version
137
+ oats package add oats.aweb v1.35.0 # a catalog version
138
138
  oats package add acme.tools git:github.com/acme/tools@v0.4.0
139
139
  oats package remove acme.tools
140
140
  ```
@@ -353,11 +353,11 @@ A soul that names one of the package's capabilities with
353
353
  "policy": "docs/official-catalog.md",
354
354
  "packages": {
355
355
  "oats.okf": { "url": "https://github.com/awebai/oats-okf.git", "ref": "v5.7.0", "path": "oats-package" },
356
- "oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.19.0", "path": "oats-package" }
356
+ "oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.21.0", "path": "oats-package" }
357
357
  }
358
358
  }
359
359
  ```
360
360
 
361
- `ref` carries the tag convention: a workspace's `oats.framework: v1.19.0`
362
- resolves to tag `oats-framework/v1.19.0`. Resolving through the catalog never
361
+ `ref` carries the tag convention: a workspace's `oats.framework: v1.21.0`
362
+ resolves to tag `oats-framework/v1.21.0`. Resolving through the catalog never
363
363
  advances a lock by itself: `oats sync` does, and says so.
@@ -0,0 +1,66 @@
1
+ # OATS 0.69.10
2
+
3
+ 0.69.10 moves the official catalog to `oats.framework` 1.20.0 (the setup
4
+ expert talks to a newcomer in everyday words, and puts a local-only project on
5
+ GitHub on the person's yes) and `oats.aweb` 1.34.0 (messaging only: aweb tasks
6
+ are taught only where `oats.aweb-tasks` is composed; tested with aw 1.36.53).
7
+ Getting started now sets up a new workspace with no aweb sign-in, and gives its
8
+ agents aweb's task list unless they already use a tracker. A repository
9
+ reference may now be an `ssh://` address with a user. A local schedule accepts
10
+ any soul the workspace offers.
11
+
12
+ ## Upgrade
13
+
14
+ - **Either order of the Desktop and the CLI works.**
15
+ [Upgrading](../upgrading.md) installs the Desktop first, and a host that
16
+ installed the CLI first is fine too: the 0.69.10 Desktop accepts OATS CLIs
17
+ `>=0.26.0 <0.70.0`, and so do the 0.69.9 and 0.69.8 Desktops.
18
+ - **Package moves:** the official catalog pins oats.framework 1.20.0 and
19
+ oats.aweb 1.34.0, with no change to their OATS floors (oats.aweb keeps aw
20
+ >=1.36.33, and is tested with 1.36.53). A deployment takes each by raising
21
+ its own pin (`/oats-package-pins`), then `oats sync`. Running instances keep
22
+ the modules they were spawned with: new spawns get the new ones, and a
23
+ stopped home moves with `oats instance upgrade`.
24
+ - **With oats.aweb 1.34.0, aweb tasks come only from `oats.aweb-tasks`.**
25
+ oats.aweb no longer mentions task coordination in anything it puts into a
26
+ home. A deployment that uses aweb tasks composes `oats.aweb-tasks` (for
27
+ example `defaults: { tasks: { oats.aweb-tasks: { from: package } } }`);
28
+ without it, its agents get no task guidance after the upgrade. The rule that
29
+ `aw lock` and `aw roles` stay outside OATS moves with it.
30
+ - **An `ssh://user@host/...` repository reference is refused by older
31
+ kernels.** Before any member uses the form in a shared `oats-workspace.yaml`,
32
+ upgrade every deployment of that workspace to 0.69.10: an older kernel
33
+ refuses the file.
34
+
35
+ ## Changed
36
+
37
+ - **`oats.framework` 1.20.0 ships the setup expert's newcomer changes.** `oats.setup` 2.11.0's `/oats-setup-expert` talks to a newcomer in everyday words, and puts a project that lives only on the person's computer on GitHub when they say yes, after checking for secrets and for files GitHub refuses (#1710, #1711, #1712). `oats.onboarding` 1.1.1's `/oats-tailor-workspace` uses the same plain words, and keeps the tasks default a new workspace was given rather than adding a second tasks provider (#1710, #1716). No command they name needs a newer OATS than each capability already admits ([awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
38
+ - **`oats.aweb` 1.34.0: messaging only; aweb tasks by opt-in.** Nothing oats.aweb puts into a home names the task layer, `aw task`, `aw work`, `aw lock`, `aw roles` or task claims: not the inject, not the `Comms:` line, not its skills. `oats.aweb-tasks` teaches them, and its inject and skill open with the workspace's opt-in. The inject gives the whole messaging loop for mail and chat ([awebai/oats-aweb#186](https://github.com/awebai/oats-aweb/pull/186)).
39
+ - **`oats.aweb` 1.33.3: tested with aw 1.36.53.** `AW_TESTED` moves to 1.36.53, npm's `latest` now that aweb Cloud serves invite preview; the floor stays 1.36.33. A resident create whose API key is refused can be rerun under aw 1.36.53. The unread-count readiness warning follows whether health publishes now, inside readiness's time budget, and the alias-conflict refusal names its remedy without a ticket or kernel version ([awebai/oats-aweb#179](https://github.com/awebai/oats-aweb/pull/179), [#182](https://github.com/awebai/oats-aweb/pull/182), [#184](https://github.com/awebai/oats-aweb/pull/184)).
40
+ - **The setup expert talks to a newcomer in everyday words.** `oats.framework`'s `/oats-setup-expert` and `/oats-tailor-workspace` assume the person may not know what a repository, Git or a terminal is. They ask about the person's project, their code on GitHub and the group their agents talk in, each question with a recommended default, and avoid OATS's and Git's own words. A command, a change or a link is shown only where the person must act on it, introduced in a plain sentence; the setup briefing's rules on what the person types and on showing a change before a push come first. A newcomer test run found the setup expert's first question saying "agents can only work in a repository the workspace lists as a member" ([awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
41
+ - **The setup expert puts a project that lives only on the person's computer on GitHub, on their yes.** OATS reads a workspace's members over Git, so `/oats-setup-expert` step 3 now first handles a folder whose code is on no GitHub repository. A folder inside a repository that is already on GitHub is not copied: the person is asked whether that repository is the project to add. Before asking, it finds what would be pushed without changing the folder:
42
+ - for a new repository, the files Git would take, without dependency and build folders or files too large for GitHub;
43
+ - for a repository with commits, its current branch and its history, with its whole history searched for secrets.
44
+
45
+ Files named like a secret or holding a private key are certain: left out of a new repository, and a reason not to push one whose history holds them. Other files whose content may hold a password or key are shown to the person by name, and they choose. The scans print file names only, never a secret's value. It shows the person the files, what it leaves out, and whether the project's own automations would start. It then proposes a private repository under their GitHub login, named after the folder. A new repository is created with the secrets left out and the staged files checked against what was shown. Where a secret is in a repository's history, nothing is pushed: the person chooses a fresh copy or keeping it local. On a no it creates nothing and says the agents can't work on that project until its code is on GitHub. A newcomer test run found the setup expert improvising this step ([awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
46
+ - **The local-only project step cleans up and checks a repository's history for files GitHub refuses.** `/oats-setup-expert` step 3's previews now remove their temporary scratch repository. For a repository with commits, it lists by name any file over 100 MiB in its branch's history, since GitHub refuses that push, and then pushes nothing and offers a fresh copy of the current files or keeping the project local ([awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
47
+ - **Getting started speaks to a newcomer and asks less.** These changes come from newcomer test runs of `oats-getting-started` on fresh machines.
48
+ - **Wording:** the skill talks in everyday words (projects, code, folders, "the setup assistant") and keeps file paths, commands, error codes and raw output to itself.
49
+ - **Step 1** first runs step 2's read-only checks, then asks three things: what the agents should help with, which projects, and whether this is a fresh start or joining someone's setup. It proposes everything else as defaults: the name (from the project's), where the shared setup lives and under which GitHub owner (from the project's repositories or the login), the messaging account, the folder where the agents live (default `<home>/Agents/<workspace>`) and the Desktop. It doesn't ask for the harness. When an answer changes a default, the skill derives them again and shows the final values.
50
+ - **One confirmation covers every change to the person's computer** that the checks found needed: the installs, the PATH line, the Claude channel plugin, folder trust, the Desktop and any missing system package. The list names each change by what and where, Git's own settings included. A new private GitHub repository for a new workspace goes on the same list, and so does the name on the first commit when Git has none, so neither is asked again later. The skill never runs `sudo` for anything outside that list. When the agent's own permission check refuses a step, the skill never runs it another way: it asks the person once, by name, retries once, and otherwise says what is missing. The person never types a command with `!`, and types one in a terminal only for a password or login when no window can be opened for them.
51
+ - **The Desktop downloads in the background** right after the GitHub login, with its checksum and attestation, while the CLI installs. It is installed only once all three have passed.
52
+ - **Linux:** the Desktop's system libraries are checked before the install. A missing ALSA is a system package to confirm; a missing FUSE 2 installs nothing, and the Desktop starts with `--appimage-extract-and-run`.
53
+ - **Minimums:** a new workspace needs `oats.framework` 1.19.0 or later, whose setup expert attaches the person to the workspace's messaging account (1.18.0 before), and its `oats.aweb` pin is never below 1.33.1, the release whose invite works after a no-sign-in setup.
54
+ - **An existing workspace** names its setup expert and the machine's messaging root after the machine's short hostname, with a suffix hashed from the machine's id (never the id itself) for hostnames many machines share. From `oats.aweb` 1.33.1 the invite answer's `awebUrl` is the service URL the join needs; without it the join takes the service from the invite, and stops if it can't.
55
+ - **The hand-off** tells the person to switch to the Desktop and click the setup assistant, since it has already started and will ask them its first question there. Attaching the person to the workspace's messaging account happens later in the setup, with the setup expert ([awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
56
+ - **Getting started creates a new workspace's aweb account and team with no sign-in.** By default, `oats-getting-started` no longer asks the person to sign in to aweb in their browser. Step 1 names the account `N` (default `<workspace>-oats`) and its root `A` (`<workspace>-root`). The skeleton's team is `default:N.aweb.ai`. Step 9 creates the account and team with `oats aweb setup --soul S --username N --name A --label L`, plan first, and goes on only when the answer's `result.team` equals that line and `result.membershipVerified` is true. When `N` is taken, the person picks another, the team line is changed, committed and synced, and the signup runs again. The person is told the team is on an aweb account created for the workspace, which they attach themselves to later in the setup, with the setup expert (`/oats-tailor-workspace`). Signing in with `aw auth login` and `aw team ensure`, for a team owned by their own aweb account from the start, is now the optional step 5 ([awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
57
+ - **Getting started: a new workspace's agents track work in aweb's task list by default, unless the person already uses a tracker.** With aweb, `oats-getting-started` now writes `tasks: { oats.aweb-tasks: { from: package } }` into a new workspace's `defaults`. It writes `tasks: none` when the person's projects already use a tracker, and the setup expert then connects that tracker with them. The skill finds a tracker rather than asking about one: a GitHub repository with an issue updated in the last 180 days and not opened by a bot (issues switched on but unused don't count), a tracker the person names, or ticket keys such as `ABC-123` in recent branch names or commit subjects. It asks one prefilled question only when unsure: ticket keys the person didn't name, a project kept somewhere other than GitHub, or an issues check that failed. The setup expert's tailor skill keeps that default rather than adding a second tasks provider. The hand-off names the choice and how to change it, and with a tracker asks the person to leave aweb's task list empty, because one task there opts the whole team in ([awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
58
+ - **Getting started: pi's aweb extension comes without its skills.** After `pi install npm:@awebai/pi`, `oats-getting-started` sets the extension's entry in pi's `settings.json` to `"skills": []`, so OATS's install puts no machine-wide aweb skills on the computer; each agent gets its skills from its own capabilities ([awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
59
+ - **An `ssh://` reference with a user is accepted wherever a repository reference is.** `oats-local.yaml` (`workspace`, `standalone`), `oats-membership.yaml` (`workspace`) and `oats-workspace.yaml` (`members`, `stores` and an external soul's pinned `source`) now accept `ssh://<user>@<host>[:<port>]/<path>`, with a user of letters, digits and `. _ ~ -` that doesn't start with `-`, the way the kernel already read it and the way `git@host:path` always was. Before, `oats onboard --workspace ssh://user@host/path` was refused with `E_WORKSPACE_SCHEMA`, while the refusal showed the reference without its user, so it looked valid. A password (`ssh://user:password@…`, percent-encoded or not), an empty user and a second `@` in the host or path stay refused, so in a pinned source the last `@` is always the pin. A package's `git:` reference keeps its own grammar. Existing files need no change ([awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
60
+ - **An operator command run without `--soul` says what the chosen soul is for.** `oats <namespace>` from a deployment directory, with no `--soul`, now prints `oats <namespace>: using the settings and teams of soul <member>/<soul>, the first soul by name in this deployment that provides "<namespace>"; pass --soul <name> to use another` on stderr, in place of `no --soul given; running as soul …`. Which soul is chosen is unchanged ([operator commands](../capabilities.md)). The old line read as if an unrelated soul were acting: a newcomer test run on a fresh workspace saw `oats aweb` say it was "running as" the knowledge-theory expert ([awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
61
+
62
+ ## Fixed
63
+
64
+ - **A local spawn schedule accepts any soul the workspace offers.** `oats schedule add` and `update` refused a local spawn job whose `agent` is a member or package soul this deployment had never spawned (`agent: no soul named "<soul>" under <root>/agents`, `E_SCHEDULE_INVALID`), although `oats spawn` resolves it, and a run always resolves its soul as `oats spawn` does. Such a job is now checked by `oats spawn <agent> --preview` with the job's own `launchConfig`, `harness`, `model`, `backend` and `repo`: a job whose preview fails is still refused with `E_SCHEDULE_INVALID`, field `agent`, now carrying spawn's own message and its code in `details.code`; a soul already spawned here is accepted without the preview, as before. `oats schedule test` reports such a soul as resolving (and now passes the job's `repo` to its preview), and the job runs at its due minutes and through `run-now` ([Kinds](../schedules.md#kinds)).
65
+ - **`oats schedule reconcile` keeps a spawn attempt it cannot attribute.** When a spawn job's result was never recorded and its `agent` is a qualified or package soul, whose runs spawn names after the soul's stem, reconcile no longer takes the missing `<agent>-<purpose>-<minute>` home as proof that nothing launched: it answers `unknown` and keeps the attempt and its slot until you check by hand and run `reconcile <id> --clear`. Before, it recorded `launch-failed` and freed the slot while the run's instance could still be running. A local or workspace job whose `agent` is a member soul under `agents/` is reconciled as before ([What a run reports](../schedules.md#what-a-run-reports)).
66
+ - **Getting started: the steward's global address names the oats.aweb release that carries its route.** On a machine found-list, the skill gated the steward's global address on oats.aweb 1.34.0, which ships without the resident root route; it now names 1.35.0. On 1.34.0 the plan already fell back to a local team identity, so only the stated version changes.
@@ -0,0 +1,107 @@
1
+ # OATS 0.69.11
2
+
3
+ 0.69.11 lets a workspace give the tasks provider one shared setting in
4
+ `oats-workspace.yaml` (`tasks:`), and lets a capability mark a setting
5
+ `committedOnly`, so no deployment can override it locally. It moves the official
6
+ catalog to `oats.framework` 1.21.0 (`/oats-host-delivery` installs the pi
7
+ extension without its bundled skills, and `/oats-upgrade` covers a first Desktop
8
+ install) and `oats.aweb` 1.35.0 (`oats.aweb-tasks` gains a shared `team`
9
+ setting and a readiness check, and pi homes get a warning while the extension
10
+ still loads its skills). Getting started takes fixes from a second round of
11
+ newcomer runs on fresh machines.
12
+
13
+ ## Upgrade
14
+
15
+ - **Either order of the Desktop and the CLI works.**
16
+ [Upgrading](../upgrading.md) installs the Desktop first, and a host that
17
+ installed the CLI first is fine too: the 0.69.11 Desktop accepts OATS CLIs
18
+ `>=0.26.0 <0.70.0`, as the 0.69.10 and 0.69.9 Desktops do.
19
+ - **Package moves:** the official catalog pins oats.framework 1.21.0 and
20
+ oats.aweb 1.35.0, with no change to their OATS floors (oats.aweb keeps aw
21
+ >=1.36.33, and is tested with 1.36.53). A deployment takes each by raising
22
+ its own pin (`/oats-package-pins`), then `oats sync`. Running instances keep
23
+ the modules they were spawned with: new spawns get the new ones, and a
24
+ stopped home moves with `oats instance upgrade`.
25
+ - **A pi home may warn `pi-extension-skills-loaded`** (oats.aweb 1.35.0) when
26
+ its pi folder's `settings.json` lists `npm:@awebai/pi` without
27
+ `"skills": []`. The warning names the file and the one entry to change; the
28
+ extension still loads, and `pi install` and `pi update` keep the filter.
29
+ - **Where `oats.aweb-tasks` is composed, readiness gains one provider item.**
30
+ With no `team` setting it passes and reads nothing.
31
+ - **Since oats.aweb 1.33.2 (pinned from 0.69.10 on), spawn and readiness warn
32
+ `aw-newer-than-tested`** when the aw on PATH is newer than the aw the
33
+ provider is tested with and the home's team root names a service other than
34
+ the aweb Cloud: a server on an older aweb may refuse it. The fix it names
35
+ first is upgrading that server's aweb. Cloud homes never warn, and it is
36
+ never a refusal. (0.69.10's notes left this out.)
37
+ - **A workspace sets `tasks:` only once every deployment that reads it runs a
38
+ kernel listing `workspace-tasks-payload`** (`oats version --json`
39
+ features). An older kernel refuses the whole file, so every resolve and spawn
40
+ on that deployment stops. A file without `tasks:` resolves exactly as before.
41
+ - **A capability's `committedOnly` setting is enforced only by kernels with
42
+ `settings-committed-only`.** An older kernel ignores the flag and still merges
43
+ the key from oats-local.yaml and `--provider`. A provider that relies on it
44
+ sets its kernel range to this release or later.
45
+
46
+ ## Added
47
+
48
+ - **A workspace `tasks:` payload** (feature `workspace-tasks-payload`). The
49
+ workspace file may carry a top-level `tasks:`, an opaque payload for whichever
50
+ capability fills the tasks slot, merged at the same layer as `messaging:`:
51
+ the manifest's defaults, then the workspace's `messaging:` or `tasks:`, the
52
+ soul's slot payload, oats-local.yaml `settings.<cap>`, then `--provider`. Its
53
+ leaves' origin is `{kind: "workspace", at: "oats-workspace.yaml#/tasks"}`. A
54
+ `hostOnly` key or `byTeam` in it is refused, as in `messaging:`. There is no
55
+ workspace `knowledge:` payload
56
+ ([Provider payloads have three homes](../workspaces.md#provider-payloads-have-three-homes),
57
+ [awebai/oats#1719](https://github.com/awebai/oats/issues/1719)).
58
+ - **`committedOnly` settings** (feature `settings-committed-only`), the mirror
59
+ of `hostOnly`. A manifest's `settings.<key>.committedOnly: true` makes the
60
+ resolver refuse that key in oats-local.yaml `settings.<cap>` and in
61
+ `--provider <cap>` with `E_WORKSPACE_SCHEMA`, reason `committed-only-key`. The
62
+ key's presence is refused, even with the committed value. The refusal names
63
+ the key, where it was set, where it may be set (`details.allowed`) and the
64
+ fix. For a messaging or tasks capability, that is oats-workspace.yaml under
65
+ `messaging:` or `tasks:`, or a soul's slot payload. A key marked both
66
+ `hostOnly` and `committedOnly` is a manifest fault, `details.why`
67
+ `settings-flag-conflict`
68
+ ([Commands and hooks](../capabilities.md#commands-and-hooks)).
69
+ - **An unknown top-level key in oats-workspace.yaml says the workspace may be
70
+ newer than the kernel.** Beside "unknown property", the problem adds "if this
71
+ is not a typo, the workspace uses a feature newer than this kernel (OATS
72
+ <version>): upgrade OATS", with reason `unknown-root-key`. Nested unknown keys
73
+ are unchanged.
74
+
75
+ ## Changed
76
+
77
+ - **`oats.framework` 1.21.0 ships two setup steps.** `oats.setup` 2.12.0's `/oats-host-delivery` gains the pi step of channel delivery: install `@awebai/pi`, then set its entry in the pi folder's `settings.json` to `{"source": "npm:@awebai/pi", "skills": []}`, so pi loads the extension without the skills it bundles (#1722). Its `/oats-upgrade` now covers a first Desktop install: on a host without the Desktop it asks whether the person wants it, and installs that release's Desktop (#1724). No command they name needs a newer OATS than `oats.setup` already admits ([awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
78
+ - **`oats.aweb` 1.35.0: one tasks team for every deployment; pi without its
79
+ bundled skills.** `oats.aweb-tasks` gains `team: <label>`, the aweb team
80
+ whose task list every deployment shares. It is set only in the workspace's
81
+ or a soul's `tasks:` payload, and marked `committedOnly`. Its new readiness
82
+ check refuses a home that has not joined the team, naming
83
+ `oats aweb join --labels <label>` or `tasks: none`. Both pi `install` texts
84
+ install `@awebai/pi` with `"skills": []`, and readiness warns
85
+ `pi-extension-skills-loaded` where it still loads them. A joined team that has
86
+ become the default is kept, with a warning, until the home is respawned
87
+ ([awebai/oats-aweb#188](https://github.com/awebai/oats-aweb/pull/188)-[#191](https://github.com/awebai/oats-aweb/pull/191)).
88
+ - **Getting started: the steward's global address waits for a release that
89
+ carries its route.** The skill named oats.aweb 1.35.0 as the first release
90
+ with the resident root route, but 1.35.0 ships without it
91
+ ([awebai/oats-aweb#147](https://github.com/awebai/oats-aweb/pull/147) is not
92
+ merged). It now names no version and always takes the fallback, a local team
93
+ identity, until a release carries the route. That was already the outcome on
94
+ 1.35.0, because the plan fell back; only the stated version changes.
95
+ - **Getting started: fixes from a second round of newcomer runs on fresh machines.** In `oats-getting-started`:
96
+ - **The whole file:** its description and its first line tell the agent to download it whole with `curl -fsSL` and follow it as written; a summary of it, from a web fetch that summarises, is not the procedure.
97
+ - **One change per command:** each change step 1's yes named runs as its own command, never batched with others, so a permission check that reads the conversation sees it by name. A refused command is never split into pieces or re-run in parts, `sudo` included: the agent asks the person once, naming the change, and retries once on their yes.
98
+ - **The time budget:** the setup takes a few minutes and seconds of the person's time. The agent waits about a minute for the Desktop's background download once the CLI is installed; when it hasn't verified by then, it goes on without the Desktop and records that in the hand-over; the person can install it later with the setup expert, through `/oats-upgrade`. `/oats-upgrade` (oats.setup) now covers that first install: on a host without the Desktop it asks whether the person wants it, and its Desktop step installs that release's Desktop.
99
+ - **A terminal window on Linux** that `systemd-run --user` can't open (no user session bus) is started directly and detached (`setsid -f xdg-terminal-exec` or `setsid -f x-terminal-emulator`, with the display variables the agent already has, never guessed) before the person is given a command to type.
100
+ - **GitHub:** the skill always checks the login, even right after it installed `gh`, before starting a device login.
101
+ - **A monorepo host:** step 1's one yes names the two setup files pushed straight to its default branch (which runs its automatic checks or deploys), and step 7 pushes them without asking again. A repository others can push to, a protected default branch or a refused push takes a pull request instead, and the hand-over records the skeleton as pushed or merged.
102
+ - **The hand-off** names no versions, package sources or internal flags or codes, and the setup expert, when named as the Desktop lists it, only by its display form; anything the person may want later goes in the hand-over file.
103
+ - **pi's skills filter** matches `npm:@awebai/pi` alone or with a version, never another `@awebai/pi-…` package. The skill now says that Claude's aweb channel plugin still carries one skill of its own until aweb ships it without one, a known gap ([awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
104
+
105
+ ## Documentation
106
+
107
+ - **`/oats-host-delivery` installs the pi extension without its skills.** `oats.framework`'s host-delivery skill gains the pi step of channel delivery: the setup expert runs `pi install npm:@awebai/pi`, then makes the extension's entry in the pi folder's `settings.json` `{"source": "npm:@awebai/pi", "skills": []}`, so pi loads the extension and none of the skills `@awebai/pi` bundles. A home gets its skills through its OATS capabilities only. The filter is interim, until aweb publishes the extension without skills; oats.aweb's readiness warns `pi-extension-skills-loaded` while it is missing.
package/docs/schedules.md CHANGED
@@ -75,16 +75,25 @@ refuses the key on a trigger.
75
75
  - **spawn** `{…, agent, agentsRoot?, repo?, backend?, purpose?, task,
76
76
  launchConfig?, harness?, model?, yolo?, wake?}` — every due minute launches
77
77
  one disposable instance of `agent` with the options `oats spawn` takes.
78
- `agentsRoot`, when given, must be the deployment's `agents/` root; `repo`
78
+ `agent` is resolved as `oats spawn <agent>` resolves it (a member or
79
+ package soul the workspace offers, see `oats souls`), whether or not this
80
+ deployment has spawned it before. `add` and `update` refuse a job whose
81
+ `oats spawn <agent> --preview`, with the job's `launchConfig`, `harness`,
82
+ `model`, `backend` and `repo`, fails (`E_SCHEDULE_INVALID`, field `agent`,
83
+ with spawn's own message and its code in `details.code`), or whose preview
84
+ answer cannot be confirmed; a soul this deployment has already spawned is
85
+ accepted without the preview. `agentsRoot`, when given, must be the deployment's `agents/` root; `repo`
79
86
  is the work repository, as `--repo`. `backend` is `tmux`; `backend: herdr`
80
87
  is refused (`E_HERDR_REMOVED`, naming the file and key: Herdr was removed in
81
88
  0.31.0), and a stored job that names it is reported invalid and never runs.
82
89
  `model` is a model id (a letter or
83
90
  digit, then letters, digits and `. _ : / @ + - [ ]`, at most 128
84
91
  characters) or `@native-default`; `agent` and `repo` never start with `-`,
85
- so no value can be read as an option of the child `oats spawn`. Each run is
86
- named `<agent>-<purpose or id>-<YYYYMMDDHHMM>`, at most 64 characters (a
87
- longer one is refused when saved, `E_SCHEDULE_INVALID`). The task gets a
92
+ so no value can be read as an option of the child `oats spawn`. Spawn names
93
+ each run after the soul's stem, `<stem>-<purpose or id>-<YYYYMMDDHHMM>`: the
94
+ stem is the soul's name, `<package>-<soul>` for a package soul. Instance
95
+ names are at most 64 characters; a job whose `<agent>-<purpose or
96
+ id>-<YYYYMMDDHHMM>` is longer is refused when saved (`E_SCHEDULE_INVALID`). The task gets a
88
97
  trailing block naming the job and the minute and ending with `oats retire
89
98
  --self`. `wake` (`{cron, tz, message}`) attaches a wake schedule to each
90
99
  launched instance.
@@ -771,7 +780,12 @@ exited, or its tmux server is gone), so its due minutes are skipped with
771
780
  `previous instance stopped: retire it (oats retire <instance>) or start it
772
781
  again (oats session start --home <home>)`, and
773
782
  `oats schedule run-now` refuses with the same words (`E_SCHEDULE_RUNNING`).
774
- While the instance runs, they are skipped as `still running`. After a reboot, a wake job
783
+ While a spawn, command or operation job's run is live, `oats schedule run-now`
784
+ refuses with `schedule <id> is still running` (`E_SCHEDULE_RUNNING`) and its
785
+ due minutes are skipped as `still running`: a job runs once at a time, never
786
+ overlapping its own run, and a skipped minute is not queued. A wake job is not
787
+ held this way: delivering to a running home takes no slot (see **Slots**
788
+ below). After a reboot, a wake job
775
789
  starts its instance's session at its next due minute, and a spawn job shows
776
790
  `stopped` with the command to retire or start its instance.
777
791
 
@@ -780,7 +794,12 @@ or answered no envelope, or an attempt was never recorded. A job with a
780
794
  persisted attempt is skipped until `oats schedule reconcile <id>` (an
781
795
  unknown `lastRun` alone does not block it; see below), which adopts only an attributable
782
796
  receipt (a spawn job's instance, named for its minute, or the instance a
783
- command's answer named). When nothing is attributable, check the roster and
797
+ command's answer named). A spawn job's instance is found by the name
798
+ `<agent>-<purpose or id>-<YYYYMMDDHHMM>`, and no home of that name proves the
799
+ attempt launched nothing only when `agent` is the bare name of a member soul
800
+ under `agents/`. For a qualified or package soul, whose runs spawn names after
801
+ its stem, reconcile answers `unknown` and keeps the attempt and its slot. When
802
+ nothing is attributable, check the roster and
784
803
  the host by hand, then `reconcile <id> --clear` records `launch-failed` and
785
804
  frees the slot. The unresolved attempt shows in `show` as `attempt:
786
805
  {scheduledFor, startedAt, error?, exited?, exitStatus?, exitSignal?}`;
@@ -187,7 +187,8 @@ For current settings and the respawn/cleanup sequence, see [knowledge.md](knowle
187
187
  digest. `oats status` compares these with the workspace's current state and
188
188
  shows `moved` / `missing` per module (drift is shown, not prevented).
189
189
  - `providers.<cap>`: the merged provider payload the capability was bound with
190
- (soul ⊕ machine settings ⊕ `--provider`), so a later inspection can tell
190
+ (manifest defaults ⊕ the workspace's `messaging:` or `tasks:` ⊕ soul ⊕
191
+ machine settings ⊕ `--provider`), so a later inspection can tell
191
192
  which instance holds a retained seat or a one-off state root. `spawn
192
193
  --preview` shows the same map before anything exists, as `settings.<cap>`,
193
194
  beside `providers` (the `--provider` flags as given).
package/docs/upgrading.md CHANGED
@@ -6,11 +6,11 @@ host that comes from it.
6
6
 
7
7
  ## Upgrading to the latest version
8
8
 
9
- The latest version is **OATS 0.69.9** ([release notes](release-notes/v0.69.9.md)).
10
- The 0.69.9 Desktop accepts OATS CLIs `>=0.26.0 <0.70.0`.
9
+ The latest version is **OATS 0.69.11** ([release notes](release-notes/v0.69.11.md)).
10
+ The 0.69.11 Desktop accepts OATS CLIs `>=0.26.0 <0.70.0`.
11
11
 
12
12
  **First, read the `## Upgrade` section of every release after yours, up to
13
- 0.69.9,** in the [release notes](release-notes/): it says what to do before
13
+ 0.69.11,** in the [release notes](release-notes/): it says what to do before
14
14
  the CLI changes, and what else must change with it (the Desktop, another
15
15
  tool, a package pin). [Coming from an older version](#coming-from-an-older-version)
16
16
  names the releases that ask for more than the steps below. `oats version`
@@ -19,8 +19,8 @@ prints the version you have.
19
19
  Then, on each host:
20
20
 
21
21
  ```sh
22
- # 0. where the Desktop is installed: Desktop 0.69.9 first
23
- npm install -g @awebai/oats@0.69.9 # 1. the CLI
22
+ # 0. where the Desktop is installed: Desktop 0.69.11 first
23
+ npm install -g @awebai/oats@0.69.11 # 1. the CLI
24
24
  oats update # 2. in each deployment: the plan, then it asks before it runs
25
25
  oats doctor # 3. in the same deployment
26
26
  ```
@@ -202,6 +202,16 @@ of the Desktop and the CLI, and an optional package pin. A change a script
202
202
  must follow is in its release's Upgrade section whether or not it is listed
203
203
  here.
204
204
 
205
+ - **[0.69.11](release-notes/v0.69.11.md#upgrade):** the catalog pins
206
+ oats.framework 1.21.0 and oats.aweb 1.35.0. Upgrade every deployment of a
207
+ workspace before its shared `oats-workspace.yaml` sets `tasks:` (an older
208
+ kernel refuses the file). A pi home may warn `pi-extension-skills-loaded`
209
+ until its pi extension entry carries `"skills": []`.
210
+ - **[0.69.10](release-notes/v0.69.10.md#upgrade):** the catalog pins
211
+ oats.framework 1.20.0 and oats.aweb 1.34.0. With oats.aweb 1.34.0, a
212
+ deployment that uses aweb tasks composes `oats.aweb-tasks`. Upgrade every
213
+ deployment of a workspace before its shared `oats-workspace.yaml` uses an
214
+ `ssh://user@host/...` reference.
205
215
  - **[0.69.9](release-notes/v0.69.9.md#upgrade):** the catalog pins
206
216
  oats.framework 1.19.0, oats.aweb 1.33.1 and oats.engineering 1.18.0. With
207
217
  oats.engineering 1.18.0, a stop doesn't hold while a checkpoint is pending: