@awebai/oats 0.70.1 → 0.70.2

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.
@@ -1340,6 +1340,64 @@ or at a session boundary.
1340
1340
  - **Codex:** not reported. A provider error fires neither its `Stop` hook nor
1341
1341
  `notify` (Codex 0.160.0), so nothing can observe the turn from outside it.
1342
1342
 
1343
+ **A pi dialog** (from `@awebai/oats-pi` 0.70.2). pi has no question dialog of
1344
+ its own: each blocking one is an extension's (`ctx.ui.select`, `confirm`,
1345
+ `input`, `editor` or `custom`; a question tool's, say). The bridge holds a claim
1346
+ of producer `oats.pi`, reason `question`, from pi's `ui_prompt_start` to its
1347
+ `ui_prompt_end` (pi 0.84.4 and later), in pi's terminal UI and in RPC mode alike,
1348
+ so the same holds for every pi home: a pi in a tmux pane and one a session
1349
+ provider runs. The
1350
+ message is the dialog's title, made one line and cut to fit as the Claude
1351
+ emitter's is; a dialog with no title sets the claim with no text. pi reports
1352
+ nested and overlapping dialogs as one span, with the first one's title. The
1353
+ claim clears when the dialog closes, however it closes, and when the session
1354
+ ends with it open: the bridge waits for that write before pi exits. A producer
1355
+ holds one claim, so an open dialog is shown over a failed turn's `attention`,
1356
+ which shows again once the dialog closes if no run has started since. Outside an
1357
+ OATS instance the bridge reports nothing. What it does not see: a screen of pi's
1358
+ own (its project trust prompt, a picker a person opened), which fires neither
1359
+ event; a question a host asks outside pi (a session provider's own question
1360
+ tool); and anything on a pi before 0.84.4.
1361
+
1362
+ **Whose claim it is.** More than one bridge can run in a home (a nested pi and
1363
+ a subagent's session carry the home's `OATS_INSTANCE_HOME` too), and a pi can
1364
+ die with its dialog open. So the bridge that sets the claim, a dialog's or a
1365
+ failed turn's, records a mark while the claim stands: `<home>/.pi/oats-pi-claim.json`,
1366
+ `{pid, start, token, reason}`, the holder's process (its pid and its start
1367
+ time, so a reused pid is not taken for it), the bridge that wrote it, and the
1368
+ claim's reason. A bridge tells its own claim by that mark, never by the claim's
1369
+ reason, and clears only its own. A holder that is alive keeps its claim: a
1370
+ second pi's first run does not clear it, and another pi's `attention` never
1371
+ replaces its `question`; only a `question` replaces another live pi's
1372
+ `attention`. A pi whose claim a live holder blocks looks again every second, so
1373
+ a second pi's open dialog is claimed once the first pi's has closed. A claim
1374
+ nobody alive holds is cleared by the home's next pi: a
1375
+ `question` whose holder is gone (a pi killed with its dialog open) when that pi
1376
+ starts, and a failed turn's, or a claim with no mark (a bridge from before the
1377
+ mark left it), at its first run; a pi that starts and ends with no run clears
1378
+ no failed turn. A pi that lives on clears a second pi's `question` whose holder
1379
+ is gone when its run ends, or at its next one. A session that ends on a failed turn leaves
1380
+ the claim and removes its mark. A clear the kernel does not take keeps the mark
1381
+ and is tried again at the bridge's next step, and a question's by itself too, a
1382
+ second later and then at growing waits up to a minute. Three limits: bridges are not fenced against each
1383
+ other, so one pi's clear that lands just after another pi's set leaves that
1384
+ pi's dialog with no claim until it closes; a failed turn that another pi's
1385
+ question replaced is not shown again when that dialog closes; and a dialog that
1386
+ opens before a pi's first run takes a failed turn an earlier session left with
1387
+ it. The mark is in the agent's own home and decides
1388
+ only claims the agent could set or clear itself, so it needs no protection from
1389
+ the agent, in a sandboxed home either. Every write is producer `oats.pi`'s: no
1390
+ other producer's claim is touched.
1391
+
1392
+ **A pi claim that outlives its dialog.** With no pi left running or starting in
1393
+ the home, a dead pi's `question` stays, and it holds every scheduled wake: the hold reads
1394
+ claims, not whether the session runs. For a home on a session provider that
1395
+ lasts until the claim is cleared, because a wake never starts such a home; a
1396
+ tmux home's next start voids it, as a session boundary voids every claim. A
1397
+ hold that runs long is a reason to look: run `oats instance waiting clear
1398
+ --producer oats.pi --home <home>` from anywhere. A mark left behind is removed
1399
+ by the home's next pi.
1400
+
1343
1401
  **Whether a home is covered** (oats.core 2.11.0). Spawn and launch hooks answer
1344
1402
  [`dialogClaims: "reported"`](#commands-and-hooks), so the home reads `wakeHold:
1345
1403
  "on-claims"`, only when they wrote these settings and the Claude Code this launch
@@ -1349,8 +1407,9 @@ reads `unknown`: an older Claude Code, no executable handed, a failed or
1349
1407
  unreadable `--version`, a settings file oats.core left alone, or a launch that
1350
1408
  runs another program than the hooks were handed. An earlier
1351
1409
  `reported` doesn't survive that, and a preview answers nothing. Every other
1352
- harness answers nothing too. A pi home reads `unknown`: an extension can open its
1353
- own dialog, and the kernel can't see which load. `reported` doesn't mean every
1410
+ harness answers nothing too. A pi home reads `unknown`: the bridge's claims hold
1411
+ a wake while one of its dialogs is open (above), but the kernel can't see
1412
+ whether that bridge is loaded, on which pi, or which screens fire no event. `reported` doesn't mean every
1354
1413
  dialog: [What a hold leaves open](schedules.md#what-a-hold-leaves-open) names what
1355
1414
  it can't see, the Claude dialogs that fire no hook among them.
1356
1415
 
@@ -5175,9 +5175,10 @@ oats instance attention [--message=<text>] [--clear] --json
5175
5175
  on a turn an API error ended, or `question` for an error class that can
5176
5176
  open a menu, cleared when the session moves on). See
5177
5177
  [capabilities.md](capabilities.md), "oats.core: needs input".
5178
- - `oats.pi`: the `@awebai/oats-pi` bridge (`attention` on a turn a provider
5179
- error ended, once pi has stopped retrying, cleared by the next run). See
5180
- the same section, "A failed turn".
5178
+ - `oats.pi`: the `@awebai/oats-pi` bridge (`question` while a dialog an
5179
+ extension opened is open, its title as the message; `attention` on a turn
5180
+ a provider error ended, once pi has stopped retrying, cleared by the next
5181
+ run). See the same section, "A pi dialog" and "A failed turn".
5181
5182
  - `agent`: the instance itself, through `oats instance attention`, and
5182
5183
  only through it: `oats instance waiting --producer agent` is
5183
5184
  `E_BAD_ARGS`. **Agent claims are cleared only by the agent (`--clear`)
package/docs/desktop.md CHANGED
@@ -911,7 +911,12 @@ on a Soul roster card preselects that soul. Choose the task or message, repeat
911
911
  pattern and time zone; new agent jobs also offer harness, model, permissions
912
912
  and session backend. The list shows the next run, last observed outcome and
913
913
  whether the host scheduler is enabled. Pause, edit, run now and delete operate
914
- on that workspace's saved jobs. Launching an agent is reported separately from
914
+ on that workspace's saved jobs. The session backend is tmux or a session
915
+ provider the chosen soul offers (bb, where the soul has it). bb launches only
916
+ in full mode, so choosing it sets permissions to YOLO; a schedule saved without
917
+ it is marked **Refused at each run** or **Needs YOLO** in the list. A wake to
918
+ an agent on a session provider is sent as its session's input and never
919
+ starts a stopped one: it is delivered once the agent runs again. Launching an agent is reported separately from
915
920
  the end of its run; neither means its task succeeded. While a schedule's last
916
921
  run is **launch failed** or **invalid**, the sidebar's **Automations** shows a
917
922
  red dot, and a screen reader hears "Automations, a run failed"; it clears once
@@ -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: v6.3.0
44
- oats.aweb: v1.47.0
44
+ oats.aweb: v1.48.0
45
45
  oats.linear: v1.0.1
46
46
  oats.jira: v1.0.1
47
47
  defaults:
@@ -97,7 +97,7 @@ operations in full.
97
97
  - **`oats.aweb-tasks`** (in the `oats.aweb` package from 1.31.0) fills the
98
98
  tasks slot with aweb tasks, acting as the instance's own `oats.aweb`
99
99
  identity in its default team. **An existing workspace opts in** by pinning
100
- `oats.aweb: v1.47.0` (the feature needs 1.31.0 or later), adding
100
+ `oats.aweb: v1.48.0` (the feature needs 1.31.0 or later), adding
101
101
  `tasks: { oats.aweb-tasks: { from: package } }` to `defaults`, and running
102
102
  `oats sync`. Only new spawns get it. A soul that names its own tasks
103
103
  provider in `capabilities:` (`oats.jira`, `oats.linear`) then holds two and
@@ -29,7 +29,7 @@ an author soul:
29
29
  ```yaml
30
30
  # oats-workspace.yaml
31
31
  packages:
32
- oats.framework: v1.28.0 # provides oats.core, oats.setup, oats.knowledge-theory
32
+ oats.framework: v1.29.0 # provides oats.core, oats.setup, oats.knowledge-theory
33
33
 
34
34
  # souls/<author-soul>/soul.yaml
35
35
  capabilities:
@@ -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.28.0` (this repository) | `oats.core`, `oats.setup`, `oats.onboarding`, `oats.support`, `oats.knowledge-theory`, `oats.coordination-setup` | `knowledge-theory-expert`, `oats-setup-expert` |
12
+ | `oats.framework` | `oats-framework/v1.29.0` (this repository) | `oats.core`, `oats.setup`, `oats.onboarding`, `oats.support`, `oats.knowledge-theory`, `oats.coordination-setup` | `knowledge-theory-expert`, `oats-setup-expert` |
13
13
  | `oats.okf` | `v6.3.0` | `oats.okf` (knowledge), `oats.okf-harvest`, `oats.okf-maintenance` | `knowledge-harvester`, `knowledge-maintainer` |
14
- | `oats.aweb` | `v1.47.0` | `oats.aweb` (messaging), `oats.aweb-tasks` (tasks) | |
14
+ | `oats.aweb` | `v1.48.0` | `oats.aweb` (messaging), `oats.aweb-tasks` (tasks) | |
15
15
  | `oats.engineering` | `v1.18.0` (frozen: see Coordination templates) | `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
@@ -55,7 +55,7 @@ packages:
55
55
  - **Bare version** (`v5.8.0`, `5.8.0`, `1.0.0-rc.1`): the id is looked up in
56
56
  the official catalog — `package-catalog.json` in the `oats` repo, or the file
57
57
  named by `OATS_PACKAGE_CATALOG` — which supplies the repo url, the tag
58
- convention (`v5.8.0` or `oats-framework/v1.28.0`) and the payload path. An id
58
+ convention (`v5.8.0` or `oats-framework/v1.29.0`) and the payload path. An id
59
59
  the catalog does not know is `E_PACKAGE_MISSING` ("use `git:<repo>@<ref>` for
60
60
  a package outside the catalog"). The catalog is the reviewed official list
61
61
  ([official-catalog.md](official-catalog.md)) and the only way a
@@ -78,9 +78,9 @@ members:
78
78
  - git:github.com/acme/agents
79
79
  - git:github.com/acme/platform
80
80
  packages:
81
- oats.framework: v1.28.0
81
+ oats.framework: v1.29.0
82
82
  oats.okf: v6.3.0
83
- oats.aweb: v1.47.0
83
+ oats.aweb: v1.48.0
84
84
  teams:
85
85
  platform: { team: "platform:acme.aweb.ai", description: Platform engineering }
86
86
  defaults:
@@ -155,7 +155,7 @@ Declaring a package in the workspace's `packages:` is the trust decision
155
155
  ## `oats package add | remove`
156
156
 
157
157
  ```bash
158
- oats package add oats.aweb v1.47.0 # a catalog version
158
+ oats package add oats.aweb v1.48.0 # a catalog version
159
159
  oats package add acme.tools git:github.com/acme/tools@v0.4.0
160
160
  oats package remove acme.tools
161
161
  ```
@@ -432,11 +432,11 @@ A soul that names one of the package's capabilities with
432
432
  "policy": "docs/official-catalog.md",
433
433
  "packages": {
434
434
  "oats.okf": { "url": "https://github.com/awebai/oats-okf.git", "ref": "v6.3.0", "path": "oats-package" },
435
- "oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.28.0", "path": "oats-package" }
435
+ "oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.29.0", "path": "oats-package" }
436
436
  }
437
437
  }
438
438
  ```
439
439
 
440
- `ref` carries the tag convention: a workspace's `oats.framework: v1.28.0`
441
- resolves to tag `oats-framework/v1.28.0`. Resolving through the catalog never
440
+ `ref` carries the tag convention: a workspace's `oats.framework: v1.29.0`
441
+ resolves to tag `oats-framework/v1.29.0`. Resolving through the catalog never
442
442
  advances a lock by itself: `oats sync` does, and says so.
@@ -0,0 +1,93 @@
1
+ # OATS 0.70.2
2
+
3
+ Unreleased
4
+
5
+ A pi agent waiting on a dialog now reads as needing input, and a scheduled
6
+ wake holds until it is answered. The Desktop's Schedules form edits a schedule
7
+ on a session provider. The catalog pins oats.aweb 1.48.0 and oats.framework
8
+ 1.29.0.
9
+
10
+ ## Upgrade
11
+
12
+ - **The Desktop and the CLI** can be upgraded in either order.
13
+ - **The pi bridge** (`@awebai/oats-pi` 0.70.2) reaches each pi folder with
14
+ `oats update`; until then a pi agent's dialog sets no claim.
15
+ - **OATS pins oats.aweb 1.48.0, which needs OATS 0.70.0 or later.** Upgrade
16
+ the CLI to 0.70.0 or later before `oats sync` takes the pin: an older kernel
17
+ refuses the package. Running instances keep the module they were spawned
18
+ with: respawn them, or move a stopped one with `oats instance upgrade`, to
19
+ take 1.48.0.
20
+
21
+ ## Added
22
+
23
+ - **A pi agent's question raises needs-input, in every pi home.** Nothing set a
24
+ claim when a pi instance waited on a dialog, so it read as running while it
25
+ waited for a person, and a scheduled wake's Enter answered the dialog. The pi
26
+ bridge (`@awebai/oats-pi`) now holds a waiting claim of producer `oats.pi`,
27
+ reason `question`, for as long as a dialog an extension opened is open (a
28
+ question tool's `select`, `confirm`, `input`, `editor` or custom screen),
29
+ with the dialog's title as its message. `oats status`, `oats session inspect`
30
+ and the Desktop show the instance as needing input, with the question, and a
31
+ scheduled wake holds until the dialog is answered
32
+ ([A held wake](../schedules.md#a-held-wake)). The claim clears when the
33
+ dialog closes and when the session ends with it open. It reaches every pi
34
+ home, a pi in a tmux pane and one a session provider runs in RPC mode alike,
35
+ on pi 0.84.4 and later, and needs the bridge updated in each pi folder
36
+ ([upgrading](../upgrading.md)). No key or event is new: the claim is the one
37
+ a failed turn already uses, and an open dialog is shown over a failed turn
38
+ ([A pi dialog](../capabilities.md#oatscore-needs-input)).
39
+ - **The bridge clears only its own claim.** It records a mark while its claim
40
+ stands, `<home>/.pi/oats-pi-claim.json`, naming the pi process that set it,
41
+ and tells its claim by that mark, never by the claim's reason. A second pi
42
+ in the home (a nested one, a subagent's session) no longer clears a live
43
+ pi's claim at its first run, and never replaces its question. No other
44
+ producer's claim is touched.
45
+ - **A pi that died with its dialog open.** Its question is cleared when the
46
+ home's next pi starts. With no pi to start it stays and holds the home's
47
+ scheduled wakes, on a session provider until it is cleared: `oats instance
48
+ waiting clear --producer oats.pi --home <home>`.
49
+ - **What it does not cover.** A pi home's `wakeHold` still reads `unknown`:
50
+ the kernel can't see whether the bridge is loaded, and a screen of pi's own
51
+ (its project trust prompt, a picker a person opened) has no claim.
52
+
53
+ - **Desktop: the Schedules form edits a schedule that launches on a session
54
+ provider.** A new-agent schedule's **Session backend** now offers tmux and
55
+ each session provider the chosen soul's capabilities supply (bb, where the
56
+ soul has it), and **Edit** opens a schedule stored on one instead of sending
57
+ you to the CLI; a save keeps the backend
58
+ ([Scheduling agents and wake messages](../desktop.md#scheduling-agents-and-wake-messages)).
59
+ - bb launches only in full mode: choosing it sets permissions to YOLO and
60
+ the form says why. A schedule saved without it (with the CLI, say) is
61
+ marked **Refused at each run** (`yolo: false`) or **Needs YOLO** (no
62
+ `yolo`: refused unless its launch configuration sets it) in the list and
63
+ on its page.
64
+ - A wake to an agent on a session provider is edited as any wake. The form
65
+ says it is sent as the session's input and never starts a stopped agent
66
+ there.
67
+ - An Edit that is still reading the soul's session backends is dropped by
68
+ anything else that happens to the list meanwhile (a switch, a run, a
69
+ Delete, a refresh, another workspace), so a late answer never brings back
70
+ a form holding the old definition.
71
+
72
+ ## Changed
73
+
74
+ - **OATS pins oats.aweb 1.48.0** (from 1.47.0). The package's requirements
75
+ follow the session backend: the channel packages (`aweb-channel`,
76
+ `@awebai/pi`) are required of `tmux` launches only, and a session provider's
77
+ launch requires an installed `aweb-channel` to be 1.7.9 or later, and an
78
+ installed `@awebai/pi` 0.3.10 or later, so no older package opens its own mail stream beside
79
+ the wake broker's. A retire removes a provider home's broker registration
80
+ when either record names a session provider. Homes on tmux behave as before.
81
+
82
+ - **oats.framework 1.29.0** (`oats.core` 2.16.1, `oats.knowledge-theory`
83
+ 1.1.4).
84
+ - `oats.core`'s `/oats-operate` says a pi home's extension dialogs raise
85
+ needs-input, and that the claim holds a scheduled wake while one is open,
86
+ from `@awebai/oats-pi` 0.70.2 (#2071). A pi home's `wakeHold` still reads
87
+ `unknown`: a screen of pi's own has no claim.
88
+ - `oats.knowledge-theory`'s capability-authoring reference shows the
89
+ `oats.framework` v1.28.0 pin in its example (it showed v1.27.0).
90
+ - The catalog pins oats.framework 1.29.0.
91
+ - Guidance text only. Nothing changes for a deployment beyond `oats sync`
92
+ taking the new tag; existing homes take the new skills through
93
+ `oats instance upgrade` or a new spawn.
package/docs/schedules.md CHANGED
@@ -1131,8 +1131,11 @@ A hold reads claims, so it can only be as good as they are. `on-claims` says no
1131
1131
  more than that:
1132
1132
 
1133
1133
  - **Harnesses with no claims stay exposed.** No claim is ever written there, so
1134
- every wake types. pi homes read `unknown`: an extension can open its own
1135
- dialog, and the kernel can't see which load.
1134
+ every wake types. pi homes read `unknown`. A dialog an extension opens there
1135
+ holds a wake, through the pi bridge's `question` claim
1136
+ ([A pi dialog](capabilities.md#oatscore-needs-input), `@awebai/oats-pi` after
1137
+ 0.70.1 on pi 0.84.4 or later), but the kernel can't see whether that bridge is
1138
+ loaded, and a screen of pi's own fires no event.
1136
1139
  - **A dialog that opens before the Enter is still answered.** That covers one that
1137
1140
  opens between the read and the Enter, and the lag between a dialog opening and
1138
1141
  its claim being written. A claim lands after its dialog: a `permission` claim
package/docs/upgrading.md CHANGED
@@ -6,12 +6,12 @@ host that comes from it.
6
6
 
7
7
  ## Upgrading to the latest version
8
8
 
9
- The latest version is **OATS 0.70.1** ([release notes](release-notes/v0.70.1.md)).
10
- The 0.70.1 Desktop accepts OATS CLIs `>=0.26.0`, tested through 0.70: the
9
+ The latest version is **OATS 0.70.2** ([release notes](release-notes/v0.70.2.md)).
10
+ The 0.70.2 Desktop accepts OATS CLIs `>=0.26.0`, tested through 0.70: the
11
11
  Desktop and the CLI can be upgraded [in either order](#either-order-works).
12
12
 
13
13
  **First, read the `## Upgrade` section of every release after yours, up to
14
- 0.70.1,** in the [release notes](release-notes/): it says what to do before
14
+ 0.70.2,** in the [release notes](release-notes/): it says what to do before
15
15
  the CLI changes, and what else must change with it (the Desktop, another
16
16
  tool, a package pin). [Coming from an older version](#coming-from-an-older-version)
17
17
  names the releases that ask for more than the steps below. `oats version`
@@ -20,8 +20,8 @@ prints the version you have.
20
20
  Then, on each host:
21
21
 
22
22
  ```sh
23
- # 0. where the Desktop is installed: Desktop 0.70.1, in either order
24
- npm install -g @awebai/oats@0.70.1 # 1. the CLI
23
+ # 0. where the Desktop is installed: Desktop 0.70.2, in either order
24
+ npm install -g @awebai/oats@0.70.2 # 1. the CLI
25
25
  oats update # 2. in each deployment: the plan, then it asks before it runs
26
26
  oats doctor # 3. in the same deployment
27
27
  ```
@@ -217,6 +217,10 @@ of the Desktop and the CLI, and an optional package pin. A change a script
217
217
  must follow is in its release's Upgrade section whether or not it is listed
218
218
  here.
219
219
 
220
+ - **[0.70.2](release-notes/v0.70.2.md#upgrade):** the catalog pins
221
+ oats.aweb 1.48.0, which needs OATS 0.70.0 or later, and oats.framework
222
+ 1.29.0: upgrade the CLI before `oats sync`, and respawn or move instances
223
+ with `oats instance upgrade` to take them.
220
224
  - **[0.70.1](release-notes/v0.70.1.md#upgrade):** a scheduled or triggered
221
225
  spawn on a provider that launches only in full mode (bb's) needs `yolo:
222
226
  true`, or a launch configuration that sets it; a job without it is now
@@ -54,7 +54,7 @@ members: # repo refs, NO @revision (E_WORKSPAC
54
54
  - git:github.com/acme/tools # a member that ALSO publishes a package (see below)
55
55
 
56
56
  packages: # the ONLY versioned things
57
- oats.framework: v1.28.0 # bare version → resolves through the official catalog
57
+ oats.framework: v1.29.0 # bare version → resolves through the official catalog
58
58
  oats.okf: v6.3.0
59
59
  acme.tools: git:github.com/acme/tools@v0.4.0 # outside the catalog → git:<repo>@<tag|OID>; still a package
60
60
 
@@ -8,7 +8,7 @@
8
8
  },
9
9
  "oats.aweb": {
10
10
  "url": "https://github.com/awebai/oats-aweb.git",
11
- "ref": "v1.47.0",
11
+ "ref": "v1.48.0",
12
12
  "path": "oats-package"
13
13
  },
14
14
  "oats.jira": {
@@ -48,7 +48,7 @@
48
48
  },
49
49
  "oats.framework": {
50
50
  "url": "https://github.com/awebai/oats.git",
51
- "ref": "oats-framework/v1.28.0",
51
+ "ref": "oats-framework/v1.29.0",
52
52
  "path": "oats-package"
53
53
  }
54
54
  },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@awebai/oats",
3
- "version": "0.70.1",
3
+ "version": "0.70.2",
4
4
  "description": "OATS (Open Agent Team Specification) — durable souls, disposable instances, targetable capability packages, and the runtime-neutral oats CLI/kernel.",
5
5
  "keywords": [
6
6
  "agents",
@@ -29,3 +29,32 @@ export function sessionBackendNames(cli, inspection = null) {
29
29
  const own = Array.isArray(cli?.sessionBackends) ? listedBackends(cli.sessionBackends) : ['tmux'];
30
30
  return [...new Set([...own, ...sessionProviderNames(inspection)])];
31
31
  }
32
+
33
+ /** The session providers that launch only in full mode (`yolo: true`): the provider refuses any other launch
34
+ * at its readiness check (`E_BACKEND_SANDBOXED_MODE`), so a spawn, a schedule's run or a trigger's fire on one
35
+ * without it creates nothing. bb, today (the bb contract, A8: bb homes run in full mode only).
36
+ *
37
+ * THE ONE PLACE a client names them. The kernel does not list this: only the provider knows its mode, and it
38
+ * says so when asked about a planned launch (`oats spawn --preview`, since 0.70.1). A form does not ask that
39
+ * way: the Desktop's preview boundary admits `backend: "tmux"` alone (spawn-preview-contract.mjs
40
+ * `previewChoices`) and a preview may take the provider's whole 20 s, and a soul's readiness asks the check
41
+ * with no launch, so it reads ready. When a provider lifts the refusal, or another one adds it, change this
42
+ * list (or replace it with what the kernel then reports) and nothing else. */
43
+ export const FULL_MODE_ONLY_PROVIDERS = Object.freeze(['bb']);
44
+
45
+ /** Whether `backend` names a provider that launches only in full mode. */
46
+ export const fullModeOnly = (backend) => typeof backend === 'string' && FULL_MODE_ONLY_PROVIDERS.includes(backend);
47
+
48
+ /** What a spawn definition's permission choice means on its backend (`{ backend, yolo }`, as a schedule or a
49
+ * trigger's spawn stores them), for a backend that launches only in full mode:
50
+ *
51
+ * 'refused' `yolo: false`: every launch is refused
52
+ * 'default' no `yolo`: the launch takes its launch configuration's choice (docs/execution-targets.md
53
+ * "Permissions"), so it is refused unless that sets full mode
54
+ * null `yolo: true`, or a backend that takes any mode: nothing to say
55
+ *
56
+ * Pure: no I/O, never throws. */
57
+ export function fullModeProblem(spawn) {
58
+ if (!record(spawn) || !fullModeOnly(spawn.backend) || spawn.yolo === true) return null;
59
+ return spawn.yolo === false ? 'refused' : 'default';
60
+ }
@@ -562,7 +562,7 @@ installed CLI's catalog:
562
562
  node -e 'const c=require(process.argv[1]);console.log(c.packages["oats.framework"].ref,c.packages["oats.aweb"].ref)' "$(oats root)/package-catalog.json"
563
563
  ```
564
564
 
565
- It prints the two refs, for example `oats-framework/v1.28.0 v1.47.0`. If the
565
+ It prints the two refs, for example `oats-framework/v1.29.0 v1.48.0`. If the
566
566
  framework's version (after the `/`) is below `1.19.0`, or with aweb
567
567
  `oats.aweb`'s is below `v1.33.1`, this OATS release is older than this
568
568
  skill: stop, and tell the person to wait for the next OATS
@@ -856,8 +856,8 @@ name: acme
856
856
  members:
857
857
  - git:github.com/acme/acme-oats # the host; the setup expert adds the others
858
858
  packages:
859
- oats.framework: v1.28.0 # the installed CLI's catalog versions (below)
860
- oats.aweb: v1.47.0 # messaging: agent identities, mail and chat
859
+ oats.framework: v1.29.0 # the installed CLI's catalog versions (below)
860
+ oats.aweb: v1.48.0 # messaging: agent identities, mail and chat
861
861
  oats.machine: v0.1.1 # on a machine found-list only: the machine's steward
862
862
  defaults:
863
863
  capabilities: