@awebai/oats 0.69.21 → 0.69.23

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.
Files changed (73) hide show
  1. package/bin/oats.mjs +131 -23
  2. package/docs/capabilities.md +12 -2
  3. package/docs/capability-manifest.schema.json +1 -1
  4. package/docs/container.md +290 -5
  5. package/docs/design/2026-11-18-kernel-test-ownership.md +82 -0
  6. package/docs/design/2026-11-19-aweb-suite-retirement.md +123 -0
  7. package/docs/design/2026-11-19-sandboxes.md +878 -0
  8. package/docs/design/README.md +3 -0
  9. package/docs/desktop-cli-api.md +416 -72
  10. package/docs/desktop.md +377 -148
  11. package/docs/implementation.md +15 -2
  12. package/docs/integrations.md +3 -3
  13. package/docs/knowledge-capability-authoring.md +10 -7
  14. package/docs/knowledge-reference/acceptance.md +21 -19
  15. package/docs/knowledge-reference/adoption.md +18 -4
  16. package/docs/knowledge-reference/model.md +11 -9
  17. package/docs/knowledge-reference/package-craft.md +2 -2
  18. package/docs/knowledge-reference/proposal.md +117 -0
  19. package/docs/knowledge-reference/provider-mapping.md +10 -10
  20. package/docs/knowledge-reference/reader-capture.md +26 -22
  21. package/docs/knowledge-theory.md +1 -1
  22. package/docs/knowledge.md +5 -5
  23. package/docs/official-catalog.md +47 -4
  24. package/docs/packages.md +13 -13
  25. package/docs/release-lane.md +8 -6
  26. package/docs/release-notes/v0.69.22.md +221 -0
  27. package/docs/release-notes/v0.69.23.md +231 -0
  28. package/docs/servers.md +10 -6
  29. package/docs/souls-and-instances.md +51 -22
  30. package/docs/tui.md +48 -7
  31. package/docs/upgrading.md +17 -5
  32. package/docs/workspaces.md +2 -2
  33. package/lib/argv.mjs +6 -2
  34. package/lib/capability-contract.mjs +2 -2
  35. package/lib/command-flags.mjs +39 -2
  36. package/lib/core.mjs +25 -14
  37. package/lib/instance-board.mjs +337 -0
  38. package/lib/instance-events.mjs +48 -10
  39. package/lib/instance-lifecycle.mjs +19 -15
  40. package/lib/instance-listing.mjs +18 -10
  41. package/lib/instance-related-work.mjs +143 -0
  42. package/lib/kernel-features.mjs +4 -1
  43. package/lib/servers.mjs +123 -13
  44. package/package-catalog.json +3 -3
  45. package/package.json +1 -1
  46. package/packages/client/above-tested.mjs +3 -2
  47. package/packages/client/capability-list.mjs +69 -0
  48. package/packages/client/capability-origin.mjs +54 -0
  49. package/packages/client/cli-adapter.mjs +9 -1
  50. package/packages/client/deployment-data.mjs +7 -2
  51. package/packages/client/deployment-panel.mjs +4 -1
  52. package/packages/client/home-board.mjs +50 -0
  53. package/packages/client/instance-pin.mjs +28 -0
  54. package/packages/client/instance-record-outcome.mjs +31 -0
  55. package/packages/client/instance-tree.mjs +96 -24
  56. package/packages/client/keymap.mjs +16 -3
  57. package/packages/client/mail-contract.mjs +130 -0
  58. package/packages/client/panel-views.mjs +7 -7
  59. package/packages/client/related-work.mjs +84 -0
  60. package/packages/client/remote-roster.mjs +11 -3
  61. package/packages/client/roster-sections.mjs +10 -7
  62. package/packages/client/soul-role.mjs +44 -0
  63. package/packages/client/waiting-on-you.mjs +10 -0
  64. package/packages/client/workspace-cli.mjs +13 -2
  65. package/packages/tui/lib/actions.mjs +11 -4
  66. package/packages/tui/lib/client.mjs +3 -1
  67. package/packages/tui/lib/main.mjs +16 -2
  68. package/packages/tui/lib/model.mjs +48 -5
  69. package/packages/tui/lib/store.mjs +28 -2
  70. package/skills/oats-getting-started/SKILL.md +97 -24
  71. package/docs/knowledge-reference/harvester.md +0 -109
  72. package/lib/instance-same-work.mjs +0 -67
  73. package/packages/client/same-work.mjs +0 -49
@@ -0,0 +1,231 @@
1
+ # OATS 0.69.23
2
+
3
+ An agent can keep facts in its person's view and ask them questions with options, on its board
4
+ (`oats instance board`), and oats.core teaches agents to use it. The Desktop reads an agent's own mail, received and
5
+ sent, in a read-only sheet that never marks anything read, through the messaging layer's new `messaging:mail`
6
+ operation (oats.aweb 1.46.0). The sidebar draws lines between related work again, and the kernel's same-work flag becomes the related-work flag, which also binds a sibling (the old spellings stay as aliases). The team image's supervisor runs
7
+ one generic optional child, and the bb image moves to its own repository. The catalog pins oats.framework 1.27.0,
8
+ oats.aweb 1.46.0 and oats.okf 6.3.0.
9
+
10
+ ## Upgrade
11
+
12
+ - **Either order of the Desktop and the CLI works** from a Desktop newer than
13
+ 0.69.17 ([Either order works](../upgrading.md#either-order-works)).
14
+ - **Package pins:** oats.framework 1.27.0 (from 1.26.0), oats.aweb 1.46.0
15
+ (from 1.45.0) and oats.okf 6.3.0 (from 6.2.0). `oats sync` takes them.
16
+ Respawn instances, or move a stopped one with `oats instance upgrade`, to
17
+ take the new modules: the board teaching (oats.core 2.15.0) and the mail
18
+ read (oats.aweb 1.46.0) reach an agent only through its module copies.
19
+ Until then the Desktop's mail sheet shows `E_OPERATION_UNKNOWN` for that
20
+ agent.
21
+ - **The mail read needs aw 1.36.53 or later**; below it, it answers
22
+ `E_AW_TOO_OLD` (oats.aweb's aw floor is unchanged otherwise).
23
+ - **If you tried the experimental bb image of 0.69.22** (`container/agent-bb`
24
+ with `container/agent/compose.agent.bb.yaml`): rebuild your team image
25
+ from this release's `container/agent`, since the 0.69.22 supervisor does
26
+ not know `AGENT_CHILD`; build the bb image from
27
+ [oats-project/oats-bb](https://github.com/oats-project/oats-bb) on that
28
+ team image; replace `compose.agent.bb.yaml` in your Compose commands by
29
+ that repository's fragment, which sets `AGENT_CHILD: "bb"`; and set no
30
+ `AGENT_BB`. A container that still sets `AGENT_BB` does not start.
31
+ - **The same-work flag is now the related-work flag; the old spellings
32
+ still work.** `oats spawn … --same-work` and `oats instance same-work …`
33
+ are deprecated aliases of `oats spawn … --related-work` and `oats instance
34
+ related-work <instance> on|off`, with the same binding. Each use prints one
35
+ line on stderr (`--same-work is renamed: use --related-work`, `oats
36
+ instance same-work is renamed: use oats instance related-work`); `--json`
37
+ output is unchanged. Instances flagged before the upgrade keep their flag.
38
+ Move skills and scripts to `--related-work` once every host they run
39
+ against is on this release; the aliases stay until their removal is
40
+ decided, with its own release-notes entry.
41
+
42
+ ## Added
43
+
44
+ - **An agent's mail in the Desktop.** Alt+M (⌥⌘M on macOS), the palette's **Agent: mail** or **Mail** in Details opens the agent's own mail, received and sent, newest first, in a read-only sheet from the right. Each message shows who it is from or to, its subject and its body as plain text attributed to its sender, and whether it is encrypted, not read by the agent yet, high priority or from an unverified sender. **r** reads it again, **Older mail** reads further back, and Esc closes it ([An agent's mail](../desktop.md#an-agents-mail)).
45
+
46
+ Reading it never acknowledges or marks anything read: the Desktop runs only the messaging layer's `messaging:mail` operation, and only when you open the sheet or ask it to read again. Nothing else on the screen shows an agent's mail. It needs an agent whose messaging layer has the operation; an older one says to upgrade it (`oats instance upgrade`) or start a new agent of its soul.
47
+
48
+ - **The agent's board** (feature `instance-board`, `boardApi: 1`). An agent
49
+ keeps facts in its person's view and asks them questions, from its own
50
+ session:
51
+ - `oats instance board set <key> --label <text> --value <text> [--unit
52
+ <text>] [--link <https-url>]` and `oats instance board unset <key>`. At
53
+ most 12 facts. The kernel keeps each fact's last 20 values. Facts last as
54
+ long as the home.
55
+ - `oats instance board ask <question> --option <text> --option <text>
56
+ [--option <text>]… [--id <id>] [--context-file <f>]` and `oats instance
57
+ board ask --clear <id>`. Each question has 2 to 4 options. At most 9 are
58
+ open, with ids `q1`, `q2`… (never reused) unless `--id` names one. A
59
+ question belongs to the session it was asked in.
60
+ - While a question is open, the kernel holds a needs-input claim of
61
+ producer `oats.board`, reason `attention`, with the oldest question as its
62
+ message. The waiting dot and the waiting row show it as they show any
63
+ claim. It holds no scheduled wake.
64
+ - `board` on `oats status --json` and `oats server roster --json` instance
65
+ rows: the facts and the open questions, at most 8 KiB per row
66
+ (`E_BOARD_FULL` refuses a write past it), or `null` with no board.
67
+ `oats inspect --home <h> --board` adds each fact's history and each
68
+ question's context.
69
+ - The board is the home's `.oats-board.json`. It is kernel-owned: a
70
+ capability can't declare it, and a retire counts it as no work.
71
+ - The kernel routes no answer. A client types the person's answer in the
72
+ agent's terminal as `<id>: <text>`.
73
+
74
+ See [The agent's board](../desktop-cli-api.md#the-agents-board-oats-instance-board).
75
+
76
+ ## Changed
77
+
78
+ - **Related work, with a parent or a sibling** (feature
79
+ `instance-related-work`; `instance-same-work` is still advertised beside
80
+ it). The flag binds an instance's recorded parent, as before, and now also
81
+ its recorded sibling when it has no parent. A top-level instance's sibling
82
+ can carry it, so clients can draw a line between two siblings. A sibling
83
+ binding names the sibling the home records: a sibling of a top-level R
84
+ binds R, and a sibling of R's sibling S binds S. `--related-work`, and
85
+ `oats instance related-work <instance> on`, on an instance that records
86
+ neither a parent nor a sibling are refused with `E_BAD_ARGS`, naming why,
87
+ and nothing is spawned or written. The flag reads off after a relink that
88
+ changes the relation (a parent or a sibling retired), until `on` binds it
89
+ again.
90
+ - `oats status --json` rows carry `relatedWork: true`, and `sameWork: true`
91
+ beside it when the flag is bound to the parent (never for a sibling). The
92
+ verb answers `{"instance", "relatedWork", "sameWork"}`. The home file is
93
+ `.oats-related-work.json`, `{"relatedWorkApi": 1, "parent" | "sibling":
94
+ "<instance>", "at": "<ISO time>"}`. An existing `.oats-same-work.json`
95
+ still reads as a parent binding while the new file is absent; the first
96
+ write of the new file removes it, and `off` removes both. Both
97
+ `.oats-related-work` and `.oats-same-work` are kernel-owned home names: a
98
+ capability cannot declare either.
99
+ - **`--server`.** The roster and `oats status --server --json` relay
100
+ `relatedWork: true`, and `sameWork: true` beside it for a parent binding.
101
+ A host on an older OATS, which advertises only `instance-same-work`, is
102
+ sent the old spellings for an instance bound to its parent, and its rows'
103
+ `sameWork: true` reach this machine with `relatedWork: true` beside it. A
104
+ sibling binding is refused there with `E_REMOTE_INCOMPATIBLE`, naming the
105
+ host and the feature it lacks; it is never dropped. See
106
+ [Related work](../desktop-cli-api.md#related-work-oats-instance-related-work).
107
+ - **The team image's supervisor runs one generic optional child, and knows
108
+ no product.** A derived image declares the child in
109
+ `/etc/agent-child.json` (its command, literal and file-read environment,
110
+ readiness URL, loopback ports, version check and stop budget, in a closed
111
+ grammar), and the deployment switches it on from outside the image with
112
+ one fixed Compose entry, `AGENT_CHILD: "<name>"`. Without the switch the
113
+ supervisor reads no file and runs as on the base image. With it, the
114
+ supervisor refuses the start, before any child, on a missing or malformed
115
+ declaration, a declaration that is not root's own regular file, a name
116
+ that differs from the switch, or a command that resolves under a writable
117
+ mount. The child's order, start timeout, restart backoff and process
118
+ group are fixed in the base image; its stop budget is capped at eight
119
+ seconds, so the ordered stop fits the 50-second grace whatever an image
120
+ declares. A file-read variable must hold its value on one line: a file
121
+ with whitespace inside its value refuses the start, and the value reaches
122
+ only the child. Acceptance with `AGENT_CHILD=<name>` exported reads the
123
+ declaration from the running container and checks the file, the declared
124
+ listeners, that nothing but sshd listens beyond loopback, and the declared
125
+ version. Every agent in the container can reach the child's loopback
126
+ ports. See [An optional child](../container.md#an-optional-child).
127
+
128
+ - **OATS pins oats.aweb 1.46.0** (from 1.45.0). It adds the view operation `messaging:mail`: an instance's own mail, read without acknowledging anything, which the Desktop's mail sheet reads (`mailApi: 1`, [Mail](../desktop-cli-api.md#mail-mailapi-1)). Floors are unchanged: OATS >=0.68.0, aw >=1.36.33, tested aw 1.36.58. The mail read alone needs aw >=1.36.53 and answers `E_AW_TOO_OLD` below it. Running instances keep the module they were spawned with: respawn them, or move a stopped one with `oats instance upgrade`, to take 1.46.0. Until then, their mail sheet shows `E_OPERATION_UNKNOWN`.
129
+
130
+ - **Desktop: the sidebar draws its lines again, for related work only.** Where an instance's host
131
+ reports related work, the sidebar draws the lines it drew before its redesign, closed or open,
132
+ and the command palette draws the same lines by the same rule
133
+ ([the sidebar's instance tree](../desktop.md#the-sidebars-instance-tree)).
134
+ - **A solid line** joins a parent to a child whose work is related to its parent's. Any other
135
+ child keeps its indent with no line.
136
+ - **A dotted line** joins the dots of two top-level instances of one group when the one linked
137
+ as a sibling of the other reports related work. A top-level instance whose work isn't related
138
+ breaks the dotted line, and the order of the rows doesn't change.
139
+ - **No flag, no line, on every host.** On an older OATS (with `instance-same-work` only), a
140
+ child's line follows `--same-work` and siblings get none. An OATS with neither feature reports
141
+ no related work, so its instances get no line (before, the command palette drew every line
142
+ for it).
143
+ - Both lines hold 3:1 contrast on every row fill, in every theme. A screen reader hears
144
+ "related work" after "under <parent>", and after "sibling of <name>" at both ends of a joined
145
+ pair, in place of the words it heard for a child's flag before.
146
+
147
+ - **oats.framework 1.27.0** (`oats.core` 2.15.0, `oats.knowledge-theory` 1.1.2,
148
+ `oats.setup` 2.16.1). `oats.core`'s inject and `/oats-operate` teach the
149
+ agent's board where the kernel lists `instance-board`, with `attention` as
150
+ the fallback (#2002). The `knowledge-capability-authoring` skill, its copied references
151
+ and the `knowledge-theory-expert` soul teach judgment and proposal at the
152
+ working instance's own checkpoints, with a reviewer accepting every
153
+ proposal. An independent harvester is an option a capability may choose
154
+ (#2009). `oats.setup`'s onboarding and package-pins skills name oats.okf
155
+ v6.3.0 in their examples. Guidance text only: no floor moves, and nothing
156
+ changes for a deployment beyond `oats sync` taking the new tag.
157
+
158
+ - **`oats.core` teaches the agent's board.** Its inject and `/oats-operate`
159
+ say that, where `oats version --json` lists `instance-board`, an agent
160
+ asks a decision between 2 and 4 options on its board (`oats instance board
161
+ ask`, with the summary, context, next step and links in `--context-file`,
162
+ and an option for each choice saying what it does). The answer arrives typed as `<id>: <text>`, and the
163
+ agent closes the question with `oats instance board ask --clear <id>` once
164
+ it has read it. The agent keeps only what its person must keep in view as
165
+ board facts (`oats instance board set`). On an OATS without the board (no
166
+ `instance-board` feature), it uses `oats instance attention`;
167
+ after `E_EVENTS_FAILED` it runs the same board command again.
168
+ See [The agent's board](../desktop-cli-api.md#the-agents-board-oats-instance-board).
169
+
170
+ - **The official catalog pins oats.okf 6.3.0** (from 6.2.0), and OATS's own
171
+ workspace takes it. Knowledge proposals are lighter (oats-project/oats-okf#164):
172
+ `oats okf propose` refuses only what protects against real harm (secrets and
173
+ personal data leaving the host, a base that would be invalid, forged
174
+ provenance, unsafe files, the soul's consent, credentials, one attempt per
175
+ proposal). What the knowledge maintainer judges at review anyway (a claim
176
+ outside the proposer's nodes, a missing subject, a broken link, an unfilled
177
+ `proposal.md`) becomes a `W_*` warning, listed under `## Check warnings` in
178
+ the PR body, which the maintainer resolves before merging. `--slug` and
179
+ `--digest` are optional: `--plan`, then `--apply` (it prints the outgoing
180
+ diff and stops), then `--apply` again publishes exactly what it printed.
181
+ Every 6.2 invocation still works with the same result. **What a deployment
182
+ must change:** nothing; the floor stays OATS >=0.69.2. Running instances
183
+ keep the module they were spawned with: respawn them, or move a stopped one
184
+ with `oats instance upgrade`, to take 6.3.0. The generated mirror under
185
+ `mirrors/oats-okf*` is finalized from the v6.3.0 tag
186
+ ([oats.okf's CHANGELOG](https://github.com/oats-project/oats-okf/blob/v6.3.0/CHANGELOG.md)).
187
+
188
+ ## Fixed
189
+
190
+ - **Getting started pushes straight to a free plan's private repository.**
191
+ On a private repository whose plan has no rulesets, GitHub answers the
192
+ `oats-getting-started` skill's rules read with a 403 "Upgrade to GitHub
193
+ Pro". Step 7 read that failure as a guarded branch and opened a pull
194
+ request the person then had to merge. It now counts that 403 as no rules,
195
+ as `oats-workspace-config`'s check already does. The skill still opens a
196
+ pull request when others can push, when the branch is protected, when any
197
+ other read fails, or when the push is refused.
198
+ - **Getting started's default workspace name is the repository's.** When a
199
+ project has both a repository and a folder of different names, step 1 now
200
+ proposes the repository's name, and the folder's only when there's no
201
+ repository.
202
+
203
+ ## Removed
204
+
205
+ - **`AGENT_BB`, `container/agent-bb`, `container/agent/compose.agent.bb.yaml`
206
+ and the bb relay have left this repository.** They shipped in 0.69.22 as
207
+ experimental, with no compatibility promise in that release's docs and
208
+ notes, and are removed without an alias. The bb image, its Compose
209
+ fragment, the relay and their operator docs now live in
210
+ [oats-project/oats-bb](https://github.com/oats-project/oats-bb), where the
211
+ image declares bb as its optional child and its fragment sets
212
+ `AGENT_CHILD`. A container that still sets `AGENT_BB`, to any value, is
213
+ refused at start with a line that names `AGENT_CHILD`, and acceptance
214
+ refuses it too.
215
+
216
+ ## Documentation
217
+
218
+ - **The knowledge-capability authors' guide teaches proposals, not a
219
+ harvester.** The reference model's judgment step is now the working
220
+ instance's own, at its knowledge checkpoints, with a reviewer accepting every
221
+ proposal: [judgment and proposal](../knowledge-reference/proposal.md)
222
+ replaces the harvester page, and the model, reader/capture, provider-mapping,
223
+ acceptance and package-craft pages follow it. An independent harvester stays
224
+ an [option](../knowledge-reference/adoption.md#an-option-an-independent-harvester)
225
+ a capability may choose, with the obligations it then carries. The
226
+ `oats.knowledge-theory` skill `knowledge-capability-authoring`, its copied
227
+ references and the `knowledge-theory-expert` soul change with it; they ship
228
+ with the next `oats.framework` release.
229
+
230
+ - **A view operation may carry one structured field.** Beside its `documents`, a view's result may hold one field named after its operation and versioned by its own `<name>Api`. The kernel validates `documents` only and relays the result unchanged, locally and through `--server`, so a client can rely on the field reaching it as the provider wrote it ([desktop-cli-api.md](../desktop-cli-api.md#oats-operation-run)).
231
+ - **`messaging:mail`, `mailApi: 1`: an agent's own mail, read without acknowledging it.** The messaging layer's answer is described once for every messaging provider: received and sent mail, newest first across the agent's identities, with bounded bodies and answers, paging, partial long conversations, per-identity errors and how older sides answer ([desktop-cli-api.md](../desktop-cli-api.md#mail-mailapi-1)). oats.aweb is its first provider. No kernel change: an older kernel relays it the same way.
package/docs/servers.md CHANGED
@@ -462,7 +462,7 @@ schedule's spec still travel as arguments.
462
462
 
463
463
  | Command | Where it runs | The server must advertise |
464
464
  |---|---|---|
465
- | `spawn` | registered workspace | the requested harness, backend and yolo option; `launch-config` for `--launch-config`; `schedule` for a wake schedule; `spawn-name` for `--name`; `spawn-task-stdin` for a `--task` or `--task-file` kept off the command line (without it: the task as an argument, and a warning; [a routed spawn's task](#a-routed-spawns-task)); `spawn-preview-2` for `--preview`; `spawn-preview-2`, `spawn-apply-2` and `spawn-idempotency-2` for a spawn bound to its preview and a key (without them: one call and a warning); `spawn-suggest-name` for `--suggest-name` on a preview, `spawn-apply-suggest-name` on an apply; `instance-background` for `--background` or `--no-background`; `instance-same-work` for `--same-work` |
465
+ | `spawn` | registered workspace | the requested harness, backend and yolo option; `launch-config` for `--launch-config`; `schedule` for a wake schedule; `spawn-name` for `--name`; `spawn-task-stdin` for a `--task` or `--task-file` kept off the command line (without it: the task as an argument, and a warning; [a routed spawn's task](#a-routed-spawns-task)); `spawn-preview-2` for `--preview`; `spawn-preview-2`, `spawn-apply-2` and `spawn-idempotency-2` for a spawn bound to its preview and a key (without them: one call and a warning); `spawn-suggest-name` for `--suggest-name` on a preview, `spawn-apply-suggest-name` on an apply; `instance-background` for `--background` or `--no-background`; `instance-related-work` for `--related-work`, or `instance-same-work` alone (an older OATS), which is sent `--same-work` for a parent binding and refuses a sibling one with `E_REMOTE_INCOMPATIBLE`, the binding read from the spawn's arguments and the host's roster |
466
466
  | `status` | registered workspace | |
467
467
  | `retire` | the instance's home | `retire-home` to retire by exact home |
468
468
  | `session inspect`, `session attach` | the instance's home | `session`; `session-attach-detach-key` for `attach --detach-key`; `session-attach-no-status-line` for `attach --no-status-line`, which a host without it ignores |
@@ -479,7 +479,7 @@ schedule's spec still travel as arguments.
479
479
  | `instance color` | the instance's home | `instance-color` |
480
480
  | `instance background` | the instance's home | `instance-background` |
481
481
  | `instance pin` | the instance's home | `instance-pin` |
482
- | `instance same-work` | the instance's home | `instance-same-work` |
482
+ | `instance related-work` | the instance's home | `instance-related-work`; a host with only `instance-same-work` (an older OATS) is asked `instance same-work` for an instance bound to its parent, and `on` for one bound to its sibling is `E_REMOTE_INCOMPATIBLE` there |
483
483
 
484
484
  `instance suggest-name` and `instance upgrade` are never routed: `--server` is
485
485
  `E_BAD_ARGS`. `instance suggest-name` names a spawn on the machine that asks,
@@ -646,10 +646,14 @@ carries `waitingOnYou` (needs input) when the host's kernel reports it, and
646
646
  only then: an older host's row has no such key. `retire` (0.59.0, a retire
647
647
  of the home running, unknown, failed or interrupted) is relayed the same
648
648
  way, through the kernel's own read of it, and a value that read refuses is
649
- dropped ([`retire`](desktop-cli-api.md#row-retire)). `sameWork` (feature
650
- `instance-same-work`, the instance does the same work as its parent) is
651
- relayed only when the host's row has `sameWork: true`, and is absent
652
- otherwise ([`sameWork`](desktop-cli-api.md#row-same-work)). `pinned` (feature
649
+ dropped ([`retire`](desktop-cli-api.md#row-retire)). `relatedWork` (feature
650
+ `instance-related-work`, the instance does related work with its parent, or
651
+ with its sibling) is relayed only when the host's row has `relatedWork:
652
+ true`, and is absent otherwise. From a host whose features list
653
+ `instance-same-work` and not `instance-related-work` (an older OATS), its
654
+ row's `sameWork: true` is relayed as `relatedWork: true`. `sameWork: true`
655
+ is relayed beside `relatedWork: true` for a parent binding, and never alone
656
+ ([`relatedWork`](desktop-cli-api.md#row-related-work)). `pinned` (feature
653
657
  `instance-pin`, the instance is pinned at the top of its machine's list) is
654
658
  relayed only when the host's row has exactly `pinned: true`, and is absent
655
659
  otherwise ([`pinned`](desktop-cli-api.md#row-pinned)). A removed or edited registration keeps
@@ -459,29 +459,46 @@ extra trees: see [`attached`](#attached--another-instances-tree)),
459
459
  because an attached agent serves that owner; relation flags other than a
460
460
  redundant child-of-owner are rejected.
461
461
 
462
- `--same-work` (feature `instance-same-work`) records that the new instance
463
- does the same work as its parent; clients draw the parent→child line for an
464
- instance that carries it. It is bound to the parent the new home records,
465
- whichever relation gave it: a child, a sibling of an anchor that has a
466
- parent, a `parent` relation whose anchor had a parent (the new instance
467
- inherits it), or an attached spawn (the owner). A spawn that would record no
468
- parent (unrelated, a sibling of a root, a `parent` relation over a root
469
- anchor) is refused with `E_BAD_ARGS` before anything is created, a preview
470
- included. The flag is the home's own file, `.oats-same-work.json`, naming the
471
- parent it was set against, and it is on only while that is still the home's
472
- recorded `parentInstance`: after a reparent (a retire's lineage splice, or a
473
- `parent` spawn re-pointing its anchor) it reads off. It survives a restart, a
474
- stop and a start, a resume and `oats instance upgrade`; only `off` or
475
- retirement clears it.
476
-
477
- `oats instance same-work <instance> on|off` sets or clears the flag on an
462
+ `--related-work` (feature `instance-related-work`) records that the new
463
+ instance does related work with its parent, or, when it has no parent, with
464
+ its sibling; clients draw the line between the two for an instance that
465
+ carries it. The kernel never sets it on its own. It is bound to the parent
466
+ the new home records, whichever relation gave it: a child, a sibling of an
467
+ anchor that has a parent, a `parent` relation whose anchor had a parent (the
468
+ new instance inherits it), or an attached spawn (the owner). With no parent
469
+ it is bound to the sibling the new home records: a sibling of an anchor with
470
+ no parent binds that anchor, and a `parent` relation over an anchor with a
471
+ sibling link and no parent binds the sibling it inherits. The sibling is the
472
+ one the home records, the anchor it was spawned beside: a sibling of a
473
+ top-level R binds R, and a sibling of R's sibling S binds S, not R. A spawn
474
+ that would record neither (unrelated, a `parent` relation over a top-level
475
+ anchor with no sibling link) is refused with `E_BAD_ARGS` before anything is
476
+ created, a preview included. The flag is the home's own file,
477
+ `.oats-related-work.json`, naming the parent or the sibling it was set
478
+ against. A parent binding is on only while that is still the home's
479
+ recorded `parentInstance`, and a sibling binding only while the home records
480
+ no parent and that sibling is still its `siblingInstance`: after a relink (a
481
+ retire's lineage splice, or a `parent` spawn re-pointing its anchor) it
482
+ reads off. It survives a restart, a stop and a start, a resume and `oats
483
+ instance upgrade`; only `off` or retirement clears it.
484
+
485
+ `oats instance related-work <instance> on|off` sets or clears the flag on an
478
486
  existing instance, addressed as `oats instance color` addresses it and routed
479
- with `--server`. `on` needs a recorded parent and binds the flag to the
480
- current one, so it also rebinds after a reparent; `off` always succeeds. An
481
- instance with the flag on carries `sameWork: true` on its `oats status
482
- --json` row; otherwise the key is absent. The answer, the errors and the
483
- remote relay are in
484
- [desktop-cli-api.md](desktop-cli-api.md#same-work-as-the-parent-oats-instance-same-work).
487
+ with `--server`. `on` needs a recorded parent or sibling and binds the flag
488
+ to the current one, so it also rebinds after a relink; `off` always
489
+ succeeds. An instance with the flag on carries `relatedWork: true` on its
490
+ `oats status --json` row, and `sameWork: true` beside it when the flag is
491
+ bound to its parent; otherwise the keys are absent.
492
+
493
+ The flag was the same-work flag (`--same-work`, `oats instance same-work`,
494
+ `.oats-same-work.json`, a parent binding only). The old spellings are
495
+ deprecated aliases of the new ones: they work the same, by the same binding
496
+ rule, and each use prints one line on stderr naming the new spelling, never
497
+ in `--json` output. Move skills and scripts to `--related-work` once their
498
+ hosts run an OATS that has it. An old `.oats-same-work.json` still reads as
499
+ a parent binding until the new record is written, which removes it; `off`
500
+ removes both. The answer, the errors and the remote relay are in
501
+ [desktop-cli-api.md](desktop-cli-api.md#related-work-oats-instance-related-work).
485
502
 
486
503
  `oats instance pin <instance> on|off` (feature `instance-pin`) pins an
487
504
  instance at the top of its machine's list, or removes the pin, addressed as
@@ -494,6 +511,18 @@ retire removes it with the home. No spawn flag or `soul.yaml` key sets it.
494
511
  The answer and the errors are in
495
512
  [desktop-cli-api.md](desktop-cli-api.md#pinned-instances-oats-instance-pin).
496
513
 
514
+ `oats instance board` (feature `instance-board`) is the agent's board, written
515
+ by the agent from its own session, like `oats instance attention`. `board set
516
+ <key> --label <text> --value <text>` keeps a fact in its person's view (`board
517
+ unset <key>` removes it), and `board ask <question> --option <text> --option
518
+ <text>` asks them a question with 2 to 4 options, which it closes with `board
519
+ ask --clear <id>` once it has read the answer. The answer arrives typed in its
520
+ terminal as `<id>: <text>`. Facts last as long as the home; a question belongs
521
+ to the session it was asked in. Clients read the board from the `board` on the
522
+ instance's `oats status --json` row. Its bounds, the claim it holds while a
523
+ question is open and the errors are in
524
+ [desktop-cli-api.md](desktop-cli-api.md#the-agents-board-oats-instance-board).
525
+
497
526
  `spawnOrigin` records the caller independently of these links. For new spawns
498
527
  from OATS 0.64.0, it is `instance` when the caller's `OATS_INSTANCE` and/or
499
528
  `OATS_INSTANCE_HOME` resolve consistently to an extant home in this deployment;
package/docs/tui.md CHANGED
@@ -180,9 +180,11 @@ while a terminal is open); under 80 columns it has the whole width.
180
180
  group's top instance, so starting or stopping an instance moves nothing. An instance
181
181
  that others were spawned from has them indented under it, and keeps its
182
182
  place when it gains or loses one. Under one parent, the instances that do
183
- its work (the kernel's `sameWork`, from an OATS with `instance-same-work`)
183
+ its work (the kernel's `relatedWork`, from an OATS with `instance-related-work`)
184
184
  come first, then the others, each part newest first, as the Desktop lists
185
- them. An empty row stands between each run
185
+ them. Pinned instances come before all of these, at every level, and an
186
+ instance with a pinned one below it counts as pinned
187
+ ([Pinning](#pinning)). An empty row stands between each run
186
188
  of instances related to no other and the group before or after it. The
187
189
  indent alone says which instance is under which: no mark is drawn for
188
190
  it. A row whose instances are folded away (`h`) says how many after its
@@ -744,9 +746,14 @@ The panel can be split in two **groups**, side by side or one above the
744
746
  other. Each group is a panel of [tabs](#tabs) of its own: a tab bar, a shown
745
747
  tab and the marks of its hidden ones.
746
748
 
747
- - **Splitting.** The leader then `|` splits the panel side by side, and the
748
- leader then `-` one above the other; in the Instances view `|` and `-`
749
- do the same without the leader. The tabs open stay in the first group
749
+ - **The list out of the way.** The leader then `b` gives the shown terminal the
750
+ whole screen with the focus, and again gives the list back with the focus (the
751
+ Desktop's `b` hides its sidebar; the list is the TUI's). With no terminal shown
752
+ it does nothing.
753
+ - **Splitting.** The leader then `|` (or `h`) splits the panel side by side, and the
754
+ leader then `-` (or `v`) one above the other; in the Instances view `|` and `-`
755
+ do the same without the leader. (`h` and `v` are Herdr's letters, shared with the
756
+ Desktop since its UI rework.) The tabs open stay in the first group
750
757
  (left, or top). The second group starts empty and is the focused group.
751
758
  - A split needs a tab open, and none starting.
752
759
  - **There are at most two groups.** With two, the split keys do nothing,
@@ -1301,6 +1308,38 @@ The exit status never depends on it.
1301
1308
  there can leave `.oats-stop-pending.json` in the agent's home, and then
1302
1309
  the agent can be started but not stopped while that file exists.
1303
1310
 
1311
+ ## Pinning
1312
+
1313
+ `p` pins the selected instance to the top of its machine's list, or unpins a
1314
+ pinned one. It runs `oats instance pin <name> on|off` at once, with no
1315
+ confirmation: a pin changes only the order, and `p` again undoes it. The line
1316
+ under the sidebar's title says `Pinning <name>…`, then the result, and the
1317
+ list is read again, so the row moves.
1318
+
1319
+ - **The order** is the Desktop's, from the same code. Pinned instances come
1320
+ first at every level: the groups of a machine's list, the instances of a
1321
+ group, and the children of one parent. An instance counts as pinned when
1322
+ it or any instance below it is, so pinning a child lifts its whole group,
1323
+ and the path down to it rises among its siblings. Among pinned instances,
1324
+ and among the others, the order is spawn time, newest first. Under one
1325
+ parent, the instances that do its work still come first. A pinned
1326
+ background instance leads the Background section. A filter never
1327
+ reorders the list. The palette lists the instances you opened most
1328
+ recently first, as before, and the others in this order.
1329
+ - **Shared.** The pin is kept in the instance's home, so everyone who views
1330
+ that machine sees it, in the TUI, the Desktop and another machine's view.
1331
+ There is no pin of your own.
1332
+ - **When `p` does nothing**, the line says why: this OATS doesn't list the
1333
+ `instance-pin` feature (then `oats instance pin <name> on|off` needs a
1334
+ newer OATS too), the instance is held by a spawn or a retire, or its pin
1335
+ is still changing. For an instance on another machine whose OATS doesn't
1336
+ list the feature, the kernel refuses before it sends anything, and the
1337
+ line gives its words.
1338
+ - **The key.** `p` is a default key from this version on. A `tui.json` that
1339
+ gives `p` to another action is refused at the start, with a line that
1340
+ names the key and both actions: move that action to another key, or give
1341
+ `pin` another key (or none) in `tui.json`.
1342
+
1304
1343
  ## Resuming lost sessions
1305
1344
 
1306
1345
  After a shutdown, a reboot or a crash, the instances that were running have
@@ -1472,6 +1511,7 @@ that kind.
1472
1511
  | close the empty group | – | – | – | – | – | `x` |
1473
1512
  | stop, restart, start, retire | `X`, `R`, `S`, `D` | – | – | – | – | `X`, `R`, `S`, `D` |
1474
1513
  | spawn another of the soul | `N` | – | – | – | – | `N` |
1514
+ | pin or unpin (`oats tui` only; the Desktop's is in the row's menu) | `p` | – | – | – | – | – |
1475
1515
  | the Instances, Souls, Capabilities views | `1`, `2`, `3` | – | – | – | – | `1`, `2`, `3` |
1476
1516
  | the help | `?` | – | – | – | – | `?` |
1477
1517
  | the list | `Esc` | – | – | – | – | `Esc` |
@@ -1855,8 +1895,9 @@ open, `Alt+Shift+Up` and `Alt+Shift+Down` move between its groups instead
1855
1895
  ([The palette](#the-palette)).
1856
1896
 
1857
1897
  `CHORDS` also holds the Desktop's `edit-instance` (`Alt+R`, its name and
1858
- colour dialog). The TUI has no such action, so it binds no key for it and
1859
- `Alt+R` stays the agent's.
1898
+ colour dialog) and `mail` (`Alt+M`, its read-only mail sheet). The TUI has no
1899
+ such actions, so it binds no keys for them and `Alt+R` and `Alt+M` stay the
1900
+ agent's.
1860
1901
 
1861
1902
  There are three families, one choice per user for both clients
1862
1903
  ([Switch family](#switch-family)):
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.69.21** ([release notes](release-notes/v0.69.21.md)).
10
- The 0.69.21 Desktop accepts OATS CLIs `>=0.26.0`, tested through 0.69: the
9
+ The latest version is **OATS 0.69.23** ([release notes](release-notes/v0.69.23.md)).
10
+ The 0.69.23 Desktop accepts OATS CLIs `>=0.26.0`, tested through 0.69: 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.69.21,** in the [release notes](release-notes/): it says what to do before
14
+ 0.69.23,** 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.69.21, in either order
24
- npm install -g @awebai/oats@0.69.21 # 1. the CLI
23
+ # 0. where the Desktop is installed: Desktop 0.69.23, in either order
24
+ npm install -g @awebai/oats@0.69.23 # 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,18 @@ 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.69.23](release-notes/v0.69.23.md#upgrade):** the catalog pins
221
+ oats.framework 1.27.0, oats.aweb 1.46.0 and oats.okf 6.3.0. Respawn
222
+ instances, or move stopped ones with `oats instance upgrade`, to take the
223
+ board teaching and the mail read. `--same-work` and `oats instance
224
+ same-work` are deprecated aliases of `--related-work` and `oats instance
225
+ related-work`. A team image that ran the experimental
226
+ bb image is rebuilt, with the bb image from oats-project/oats-bb.
227
+ - **[0.69.22](release-notes/v0.69.22.md#upgrade):** the catalog pins
228
+ oats.aweb 1.45.0; `setup --install-aw` installs the tested aw by default.
229
+ The Desktop's leader is Ctrl+Space (Ctrl+X a click away; a leader you set is
230
+ kept). A `tui.json` that binds `p` to another action moves it. Respawn
231
+ instances to take the new module.
220
232
  - **[0.69.21](release-notes/v0.69.21.md#upgrade):** the catalog pins
221
233
  oats.aweb 1.43.0. A deployment on a non-public aw registry runs
222
234
  `oats aweb setup --registry <origin>`, reruns `oats aweb resident create`,
@@ -54,8 +54,8 @@ 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.26.0 # bare version → resolves through the official catalog
58
- oats.okf: v6.2.0
57
+ oats.framework: v1.27.0 # bare version → resolves through the official catalog
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
 
61
61
  teams: # SHARED teams: the same provider team for everyone
package/lib/argv.mjs CHANGED
@@ -4,7 +4,7 @@
4
4
  * Dependency-free. */
5
5
 
6
6
  /** The kernel's switches: a value never rides one (`--yolo=false` must not turn yolo on). */
7
- const KERNEL_SWITCHES = new Set(["allow-child-spawns", "apply", "background", "check", "clear", "composed-skills", "delete-branch", "discard-worktree", "dry-run", "ephemeral", "force", "help", "host", "if-absent", "install-oats", "instructions", "json", "keep-dir", "keep-env", "no-background", "no-child-spawns", "no-default", "no-launch", "no-recursive", "no-yolo", "plan", "policy", "preview", "print", "replace", "run-source", "same-work", "self", "skills", "suggest-name", "verbose", "yes", "yolo"]);
7
+ const KERNEL_SWITCHES = new Set(["allow-child-spawns", "apply", "background", "board", "check", "clear", "composed-skills", "delete-branch", "discard-worktree", "dry-run", "ephemeral", "force", "help", "host", "if-absent", "install-oats", "instructions", "json", "keep-dir", "keep-env", "no-background", "no-child-spawns", "no-default", "no-launch", "no-recursive", "no-yolo", "plan", "policy", "preview", "print", "related-work", "replace", "run-source", "same-work", "self", "skills", "suggest-name", "verbose", "yes", "yolo"]);
8
8
  /** `--flag=value` is `--flag value`: every kernel reader (flag(), valueFlag(), the onboard and
9
9
  * routed-command loops) then applies the spaced form's validation to it. `problem` is an empty
10
10
  * `--flag=`, a switch given a value, or a value that is itself an option (`--model=--yolo`):
@@ -16,8 +16,12 @@ const INLINE_TEXT_FLAGS = new Set(["message"]);
16
16
  /** Free-text flags whose inline value is always kept whole, the empty one included:
17
17
  * `--description=` clears a trigger's or schedule's description. */
18
18
  const INLINE_WHOLE_FLAGS = new Set(["description"]);
19
+ /** A word that is a switch everywhere but one form, where it takes a value: `oats instance board ask
20
+ * --clear <id>` (feature instance-board). There, `--clear=<id>` is `--clear <id>`. */
21
+ const VALUE_IN_FORM = [{ words: ["instance", "board", "ask"], name: "clear" }];
19
22
  export function expandInlineValues(argv) {
20
23
  const out = [];
24
+ const valued = new Set(VALUE_IN_FORM.filter((f) => f.words.every((w, i) => argv[i] === w)).map((f) => f.name));
21
25
  const inline = new Map();
22
26
  let problem;
23
27
  for (const a of argv) {
@@ -25,7 +29,7 @@ export function expandInlineValues(argv) {
25
29
  if (!a.startsWith("--") || eq <= 2) { out.push(a); continue; }
26
30
  const name = a.slice(2, eq), value = a.slice(eq + 1);
27
31
  if (INLINE_WHOLE_FLAGS.has(name) || (INLINE_TEXT_FLAGS.has(name) && value.startsWith("--"))) { inline.set(name, value); out.push(`--${name}`); continue; }
28
- problem ??= KERNEL_SWITCHES.has(name) ? `--${name} takes no value (got ${a})` : value === "" ? `--${name}= needs a value` : value.startsWith("--") ? `--${name}= takes a value, not an option (got ${a})` : undefined;
32
+ problem ??= KERNEL_SWITCHES.has(name) && !valued.has(name) ? `--${name} takes no value (got ${a})` : value === "" ? `--${name}= needs a value` : value.startsWith("--") ? `--${name}= takes a value, not an option (got ${a})` : undefined;
29
33
  out.push(`--${name}`, value);
30
34
  }
31
35
  return { argv: out, problem, inline };
@@ -181,13 +181,13 @@ const DISPOSABLE_HOME_PREFIX_RE = /^\.[A-Za-z0-9_][A-Za-z0-9._-]*-\*$/;
181
181
  * declaration may not cover them: these exact names, and every exact name
182
182
  * starting with one of these prefixes (the events log; the stop, restart and
183
183
  * start receipts and locks; the rollback marker; AGENTS.md backups; the
184
- * attachments directory; the instance colour, `.oats-color.json`; the background record, `.oats-background.json`; the pin, `.oats-pinned.json`; the same-work flag, `.oats-same-work.json`). This is the one list: a new kernel-written top-level
184
+ * attachments directory; the instance colour, `.oats-color.json`; the background record, `.oats-background.json`; the pin, `.oats-pinned.json`; the related-work flag, `.oats-related-work.json`, and `.oats-same-work.json`, the file of the same-work flag it replaced, which the kernel still reads while the new one is absent; the agent's board, `.oats-board.json`, and its lock). This is the one list: a new kernel-written top-level
185
185
  * home entry MUST be added here and to the `not` patterns of
186
186
  * `retirement.disposable.home` in docs/capability-manifest.schema.json. A
187
187
  * prefix declaration can reach none of them except through `.oats-`, which is
188
188
  * refused whole; `.oats-<provider>` as an exact name stays declarable. */
189
189
  const KERNEL_HOME_NAMES = new Set([".oats", ".agents", ".claude"]);
190
- const KERNEL_HOME_NAME_PREFIXES = [".oats-events", ".oats-stop", ".oats-restart", ".oats-rollback", ".oats-agents-md", ".oats-start", ".oats-attachments", ".oats-color", ".oats-background", ".oats-pinned", ".oats-same-work"];
190
+ const KERNEL_HOME_NAME_PREFIXES = [".oats-events", ".oats-stop", ".oats-restart", ".oats-rollback", ".oats-agents-md", ".oats-start", ".oats-attachments", ".oats-color", ".oats-background", ".oats-pinned", ".oats-same-work", ".oats-related-work", ".oats-board"];
191
191
 
192
192
  /** Why `root` is not a declarable home entry: "shape" (not one hidden top-level
193
193
  * name or prefix), "kernel-owned", or undefined when it is sound. */