@awebai/oats 0.64.0 → 0.66.0

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 (51) hide show
  1. package/README.md +11 -5
  2. package/bin/oats.mjs +109 -11
  3. package/docs/desktop-cli-api.md +88 -5
  4. package/docs/desktop.md +14 -5
  5. package/docs/implementation.md +26 -3
  6. package/docs/integrations.md +1 -1
  7. package/docs/official-catalog.md +2 -2
  8. package/docs/packages.md +7 -7
  9. package/docs/release-notes/v0.65.0.md +187 -0
  10. package/docs/release-notes/v0.66.0.md +183 -0
  11. package/docs/servers.md +2 -2
  12. package/docs/tui.md +548 -249
  13. package/docs/upgrading.md +1 -1
  14. package/docs/workspaces.md +132 -1
  15. package/lib/core.mjs +14 -4
  16. package/lib/deployments.mjs +341 -0
  17. package/lib/resolved-deployment.mjs +37 -0
  18. package/lib/workspace.mjs +2 -0
  19. package/package-catalog.json +2 -2
  20. package/package.json +1 -1
  21. package/packages/client/cli-locator.mjs +2 -2
  22. package/packages/client/deployment-label.mjs +2 -2
  23. package/packages/client/deployment-list-cli.mjs +98 -0
  24. package/packages/client/deployment-list.mjs +91 -0
  25. package/packages/client/keymap.mjs +133 -0
  26. package/packages/client/machine-contract.mjs +1 -5
  27. package/packages/client/own-codes.mjs +2 -0
  28. package/packages/client/panel-views.mjs +1 -1
  29. package/packages/client/workspace-admission.mjs +2 -1
  30. package/packages/record/bin/setup.mjs +10 -2
  31. package/packages/record/docs/capture-service.md +45 -6
  32. package/packages/record/lib/capture-service-install.mjs +6 -95
  33. package/packages/record/lib/capture-setup-write.mjs +233 -0
  34. package/packages/tui/README.md +10 -9
  35. package/packages/tui/lib/actions.mjs +89 -64
  36. package/packages/tui/lib/client.mjs +4 -1
  37. package/packages/tui/lib/config.mjs +184 -36
  38. package/packages/tui/lib/main.mjs +161 -40
  39. package/packages/tui/lib/model.mjs +73 -41
  40. package/packages/tui/lib/read.mjs +15 -45
  41. package/packages/tui/lib/store.mjs +174 -40
  42. package/packages/tui/lib/term/keys.mjs +135 -33
  43. package/packages/tui/lib/term/kitty.mjs +198 -0
  44. package/packages/tui/lib/term/through.mjs +160 -24
  45. package/packages/tui/lib/term/tty.mjs +43 -12
  46. package/packages/tui/lib/views/act.mjs +17 -13
  47. package/packages/tui/lib/views/frame.mjs +418 -421
  48. package/packages/tui/lib/views/help.mjs +90 -29
  49. package/packages/tui/lib/views/instances.mjs +38 -9
  50. package/packages/tui/lib/views/switcher.mjs +65 -21
  51. package/skills/oats-getting-started/SKILL.md +102 -32
@@ -0,0 +1,187 @@
1
+ # OATS 0.65.0
2
+
3
+ Unreleased
4
+
5
+ ## Upgrade
6
+
7
+ - **Install the Desktop first and the CLI second,** as
8
+ [Upgrading](../upgrading.md) says: a 0.64 Desktop refuses a 0.65.0 CLI. The
9
+ 0.65.0 Desktop accepts OATS CLIs `>=0.26.0 <0.66.0`. With an older CLI its
10
+ switcher shows the saved workspaces only and says "Update oats".
11
+
12
+ - **No package moves.** The official catalog keeps oats.framework 1.13.3; no
13
+ `oats sync` is needed for this release.
14
+
15
+ - **This computer's deployments list fills itself.** Nothing to run: the
16
+ first kernel command in a deployment lists it, `oats onboard` lists what it
17
+ creates, the first command that touches the list imports `~/Agents` once,
18
+ and the 0.65.0 Desktop's first launch imports its own saved and recent
19
+ workspaces. The Desktop and `oats tui` both read it, and no longer look
20
+ inside `~/Agents`. `oats deployments` shows the list, and
21
+ `oats deployments remove` takes off a row you don't want.
22
+
23
+ - **Coming from 0.61 or earlier:** do 0.62.0's Upgrade steps too (the capture
24
+ service's `oats setup`, once per user on each host, from that user's shell).
25
+
26
+ ## Added
27
+
28
+ - **One list of this computer's deployments, `~/.oats/config/deployments.json`,
29
+ and `oats deployments`** to read and change it
30
+ ([#1390](https://github.com/awebai/oats/issues/1390);
31
+ [This computer's deployments](../workspaces.md#this-computers-deployments)).
32
+ The clients read it to offer the deployments that are not open. It holds
33
+ this computer's deployments only; other machines stay in the server
34
+ registry.
35
+ - **`oats deployments [list] [--json]`** shows each deployment's path, its
36
+ state (`ok`, `missing`, `not-a-deployment` or `unreadable`, from
37
+ existence checks only) and how it was listed. `add [<dir>]` lists the
38
+ deployment at or above `<dir>`; `remove <path>` takes a row off the list
39
+ and touches nothing on disk; `import --from desktop <path>...` is the
40
+ Desktop's one-time import of its own lists. The JSON is in the
41
+ [Desktop CLI API](../desktop-cli-api.md#this-computers-deployments-oats-deployments),
42
+ under the feature `deployments-list`.
43
+ - **The list fills itself.** `oats onboard` lists what it creates (`listed`
44
+ in its result; a failed add never fails the onboard). Any kernel command
45
+ that resolves a deployment that is not listed yet (`status`, `spawn`,
46
+ `sync`, `doctor` and the others that read a deployment) lists it,
47
+ silently. A deployment inside a linked Git worktree or submodule is
48
+ listed by the first command that resolves its instance root (`status`,
49
+ `spawn`, `session` and the like), not by `sync`, `doctor` and the other
50
+ configuration commands. Once it is listed, a command reads the list and
51
+ nothing more: no lock, no write, no process (at most about
52
+ 0.5 ms a command); another spelling of it, a link for example, adds
53
+ one realpath. A busy lock never delays a command, and a command routed
54
+ with `--server` lists nothing.
55
+ - **A removed deployment stays removed.** Nothing automatic lists a path
56
+ `oats deployments remove` took out; `oats deployments add` or
57
+ `oats onboard` brings it back.
58
+ - **`~/Agents` is imported once.** The first command that touches the list
59
+ lists the deployments directly inside `~/Agents` (at most 200 entries, no
60
+ link followed) and records that it did. Nothing reads `~/Agents` again.
61
+ - **Five new codes:** `E_DEPLOYMENTS_INVALID`, `E_DEPLOYMENTS_VERSION`,
62
+ `E_DEPLOYMENTS_BUSY`, `E_DEPLOYMENTS_WRITE` and `E_DEPLOYMENTS_IMPORT`
63
+ (`~/Agents` cannot be read for the first-use import), each saying what
64
+ to do.
65
+
66
+ - Desktop: the TUI's leader. Alt+O on Linux and Windows, ⌃\ on macOS, then
67
+ one key from the TUI's own table: `k` or Space the command palette, `1` `2`
68
+ `3` Instances, Souls and Capabilities, ↑/↓ the terminal of the roster row
69
+ before or after, ←/→ the tabs, `z` focus mode, `w` close the tab, `|` `-`
70
+ the splits, Tab and `x` the split's groups, `X` `R` `S` `D` Stop, Restart,
71
+ Start and Retire, `n` `N` spawn, `/` the filter, `o` the workspace
72
+ switcher, `?` the shortcuts and Esc the instance roster. It works from a
73
+ terminal too: there the leader pressed twice sends the program what the
74
+ chord sends (Alt+O is ESC o, ⌃\ is 0x1c). While it waits, a panel at the
75
+ bottom of the main area lists the keys that apply now. `m` (move a tab to
76
+ the other group) has nothing to act on in the Desktop and is left out. A
77
+ test holds the Desktop's table to the TUI's, so the two cannot drift apart
78
+ ([Desktop keyboard](../../packages/desktop/docs/desktop-keyboard.md#the-leader)).
79
+ - Desktop: the TUI's plain keys in the sidebar. With focus in the sidebar,
80
+ `1` `2` `3`, `w`, `/`, `r`, `z`, `c`, `[` `]`, `|` `-`, `X` `D` `S` `R`,
81
+ `n` `N` and `?` do what they do in the TUI, each rebindable in the
82
+ shortcuts editor; on a roster row `k` `j` `g` `G` `h` `l` and
83
+ PageUp/PageDown move through the tree
84
+ ([Sidebar keys](../../packages/desktop/docs/desktop-keyboard.md#sidebar-keys)).
85
+ - Desktop: help leads with the leader. The shortcuts editor opens on a
86
+ Leader group, the leader's chord and then one row per key after it, which
87
+ its search finds (`alt+o k`), then the sidebar keys. The sidebar footer
88
+ starts with the leader's chord and "commands", a button that starts it.
89
+
90
+ ## Changed
91
+
92
+ - **The Desktop's switcher lists this computer's deployments from the
93
+ kernel's list,** `oats deployments`
94
+ ([#1390](https://github.com/awebai/oats/issues/1390)), and no longer looks
95
+ inside `~/Agents`.
96
+ - **Under "On this computer"** a window with no workspace shows the
97
+ deployments on that list that are not open, beside the saved ones.
98
+ - **A row that can't be opened says why:** missing (the folder is gone, or
99
+ its volume isn't mounted), not a deployment any more, or can't be checked.
100
+ - **Remove** beside a row takes it off the list, and off the Desktop's saved
101
+ workspaces when it is one. Nothing on disk changes. From the keyboard:
102
+ Right Arrow, then Enter.
103
+ - **Every deployment the Desktop opens is listed:** an add, an onboarding,
104
+ and the deployment it was launched on. A failure is a notification, and
105
+ the deployment stays open.
106
+ - **Once, at the first launch,** the Desktop moves its own list of recently
107
+ added workspaces and its saved workspaces onto the list, then renames
108
+ `workspace-recents.json` to `workspace-recents.imported.json`. It reads
109
+ recents for nothing else.
110
+ - **With an older oats,** which has no such list, the switcher shows the
111
+ saved workspaces and says "This oats can't list this computer's
112
+ deployments. Update oats." See [OATS Desktop](../desktop.md#opening-a-workspace).
113
+
114
+ - **`oats tui`'s switcher lists this computer's deployments from the
115
+ kernel's list,** `oats deployments`
116
+ ([#1390](https://github.com/awebai/oats/issues/1390)), and no longer looks
117
+ inside `~/Agents`.
118
+ - **Started outside every deployment** with no `--dir`, it reads the list
119
+ and starts with the switcher when the list holds a row. With none, it
120
+ exits with `E_NO_DEPLOYMENT`, and the line says how to open one
121
+ (`oats tui --dir <path>`) or create one (`oats onboard`). A list that
122
+ can't be read exits with the kernel's own code and message.
123
+ - **Opening a deployment lists it:** the deployment a run starts in, from
124
+ where you are or with `--dir`, is added to the list once. A failure is
125
+ said once, under the sidebar's title, and opens nothing less.
126
+ - **Under "On this machine, not opened"** stand the list's deployments the
127
+ run hasn't opened. A row that can't be opened says why: `Not found.`,
128
+ `Not an OATS deployment any more.` or `Can't be read.`
129
+ - **`Delete` on such a row asks, then removes it from the list,** with
130
+ `Enter`; nothing on disk changes. `tui.json` can give `remove` another
131
+ key. `r` reads the list again.
132
+ - The `More folders than are listed here.` row is gone. See
133
+ [OATS TUI](../tui.md#the-switcher).
134
+
135
+ - **The `oats-getting-started` skill suggests no deployment directory.** It
136
+ asks for `D` and no longer suggests `~/Agents/<workspace>`: from this
137
+ release `oats onboard` lists `D` in this computer's list of deployments, so
138
+ the Desktop and the TUI find it wherever it is
139
+ ([#1390](https://github.com/awebai/oats/issues/1390)). On Linux, the person
140
+ picks `D` in the Desktop's switcher, where it is listed; when it isn't
141
+ (an older Desktop, or a list that could not be written), they add it with
142
+ **Add local workspace… → Browse**.
143
+
144
+ - **OATS Desktop accepts an `oats` CLI 0.65.x.** Its band is now
145
+ `>=0.26.0 <0.66.0`. 0.65 adds no new gate on the band: the Desktop reads
146
+ `oats deployments` only behind its feature `deployments-list`, and does not
147
+ read `listed` on `oats onboard --json`.
148
+
149
+ - Desktop: the command palette (⌘K / Ctrl+Shift+K) now opens on its first
150
+ row, the top of the list, which its last-focus order makes the most recently
151
+ focused path. With a query it opens on the first match. It no longer opens on
152
+ the agent you were on before, which was often a row in the middle of the
153
+ list (#1391).
154
+
155
+ - Desktop: none of the existing default shortcuts changes. A shortcut you set
156
+ yourself that now shares its chord with the leader or a sidebar key is kept
157
+ as it is, and the shortcuts editor shows the clash until you rebind or reset
158
+ one side.
159
+
160
+ - **`oats tui` is one sidebar and the main area, with no header and no
161
+ footer.** An agent's open terminal now spans every row, and zoomed (`z`)
162
+ it has the whole screen. The sidebar starts with the workspace's name and
163
+ what the view holds of other machines. A deployment's state and reason,
164
+ the note of a one-deployment view and the line after an open stand under
165
+ it. The three views follow as an accordion, each with its key: the open
166
+ one's heading with its list under it, and with no instances
167
+ `No agents yet: n spawns one`. A short cheat sheet comes last: the
168
+ leader, the palette, what `Enter` does now, spawn, help and quit; the
169
+ leader's hint, the palette and the help name the other keys. On a narrow
170
+ sidebar a row's name keeps its cells ahead of its word. The filter field
171
+ and a kept filter stand on the open view's heading. The counts and the
172
+ time of the read have left the screen. The help shows that time at its top, with how many rows were
173
+ withheld. From 80 columns the switcher, the palette, the spawn prompt, the
174
+ help and the confirmations cover the main area, and the sidebar stays
175
+ beside them. Under 80 columns they cover the whole screen, with their keys
176
+ on their first row, as the detail does
177
+ ([docs/tui.md](../tui.md#what-it-shows)).
178
+
179
+ - **The leader is `Alt+O` on Linux and Windows.** `Ctrl+\` was a stretch on
180
+ most keyboards and needs AltGr on many layouts. macOS keeps `Ctrl+\` for
181
+ now. `open.detachKey` in `tui.json` still names another key, `C-\`
182
+ among them. `Alt+O` counts as the leader only when it arrives as one
183
+ keypress: an `Esc` then `o` typed as two keys reaches the agent unchanged.
184
+ The leader pressed twice now types it into the terminal that has the
185
+ focus, and the leader then `Esc` gives the list the focus. The cheat
186
+ sheet and the help name keys as people read them: `Alt+O`, `Ctrl+K`,
187
+ `Enter` ([docs/tui.md](../tui.md#the-leader)).
@@ -0,0 +1,183 @@
1
+ # OATS 0.66.0
2
+
3
+ Unreleased
4
+
5
+ ## Upgrade
6
+
7
+ - **Install the Desktop first and the CLI second,** as
8
+ [Upgrading](../upgrading.md) says: a 0.65 Desktop refuses a 0.66.0 CLI. The
9
+ 0.66.0 Desktop accepts OATS CLIs `>=0.26.0 <0.67.0`.
10
+
11
+ - **Two package moves:** the official catalog pins oats.framework 1.13.4 and
12
+ oats.aweb 1.30.0 (Provider updates, below). A deployment that pins them
13
+ takes them with `oats sync`, and only new spawns use them. Neither floor
14
+ changes.
15
+
16
+ - **`oats tui` moves its key file** to `~/.oats/config/tui.json` the first
17
+ time it starts (Changed, below). If you keep the file in a dotfiles
18
+ manager, point it at the new path first.
19
+
20
+ - **Coming from 0.61 or earlier:** do 0.62.0's Upgrade steps too (the capture
21
+ service's `oats setup`, once per user on each host, from that user's shell).
22
+
23
+ - **`oats server connect` needs `--dir`, inside a deployment too**
24
+ ([#1390](https://github.com/awebai/oats/issues/1390);
25
+ [Connect a machine](../servers.md#connect-a-machine)). The folder on the
26
+ host no longer defaults to `~/Agents/<this deployment's directory name>`:
27
+ only you know where the deployment goes there. A script that ran `connect`
28
+ without it now gets `E_BAD_ARGS` "--dir <path on the host> is required:
29
+ the folder on `<host>` for this deployment (absolute, or ~/… resolved
30
+ there)" before anything runs; add `--dir`. `--workspace-ref` still
31
+ defaults from the deployment, and existing registrations are unchanged.
32
+
33
+ ## Added
34
+
35
+ - **`oats tui` takes the OATS Desktop's Ctrl+Shift chords, where your
36
+ terminal lets them through** ([Chords](../tui.md#chords)): `Ctrl+Shift+K`
37
+ the palette, `Ctrl+Shift+P` a spawn, `Ctrl+Tab` and `Ctrl+Shift+Tab` the
38
+ next and previous tab, `Ctrl+Shift+W` close the terminal, `Ctrl+Shift+F`
39
+ the filter, `Ctrl+Shift+E` and `Ctrl+Shift+O` the splits. Each does what
40
+ the leader then a key does, from every focus, an agent's terminal too,
41
+ and never reaches the agent. They are extras: the leader stays the key
42
+ that always works, and the cheat sheet does not name them.
43
+ - **Only where the terminal says it can.** At start the TUI asks for the
44
+ kitty keyboard protocol (flags 1 and 4) and asks the terminal which flags
45
+ it has. Only when the terminal answers does it take the chords and list
46
+ them in the help, with the keys your terminal may take first (foot's
47
+ Ctrl+Shift+C, V, R, N, O, U, Z, X and Q). Without an answer everything
48
+ is as before. foot, Ghostty, kitty, Alacritty and WezTerm answer; VTE
49
+ terminals and Terminal.app do not. On macOS only `Ctrl+Tab` and
50
+ `Ctrl+Shift+Tab` are chords: the Desktop's hold ⌘, which a terminal
51
+ never passes on.
52
+ - **`Alt+O` and `Esc` then `o` are told apart exactly** under the
53
+ protocol, with no timing.
54
+ - **An agent gets the same bytes as before:** every key typed into its
55
+ terminal is turned back into the bytes it sends without the protocol,
56
+ and no tmux setting is changed. With a terminal that confirms flag 1
57
+ but not flag 4, Shift with Alt or Ctrl on a key that is not a letter
58
+ is typed as the US layout makes it.
59
+ - **The protocol is popped on every way out** and at a suspend, beside the
60
+ terminal modes the TUI already restores.
61
+
62
+ ## Changed
63
+
64
+ - **OATS Desktop's Add a machine dialog no longer suggests a folder**
65
+ ([#1390](https://github.com/awebai/oats/issues/1390)). **Folder on that
66
+ machine** starts empty and you have to fill it in. Its hint reads "A path on
67
+ that machine, starting with / or ~/". If you click **Add machine** with the
68
+ folder empty, the dialog says so beside the field and runs nothing. It used
69
+ to fill in `~/Agents/<deployment folder name>`. The Name default
70
+ (`<host>-<deployment folder name>`) is unchanged.
71
+
72
+ - **`oats deployments add` walks up to a regular `oats-local.yaml` only**
73
+ ([#1397](https://github.com/awebai/oats/issues/1397);
74
+ [This computer's deployments](../workspaces.md#this-computers-deployments)).
75
+ A directory or a link of that name is passed over, as a client passes it
76
+ over when it admits a deployment, instead of being listed and then shown
77
+ as `not-a-deployment`.
78
+ - **A deployment under a temporary directory is no longer listed
79
+ automatically** ([#1397](https://github.com/awebai/oats/issues/1397)). A
80
+ kernel command run in one (`os.tmpdir()`, `/tmp`, `/private/tmp` or
81
+ `/var/folders`, compared after realpath) leaves the list alone, so test
82
+ fixtures no longer fill it with rows that turn `missing`. Such a
83
+ deployment stays reachable: `oats deployments add`, `oats onboard` and a
84
+ client opening it still list it.
85
+
86
+ - **`oats tui` reads its key file from `~/.oats/config/tui.json`**
87
+ ([#1390](https://github.com/awebai/oats/issues/1390)), beside the kernel's
88
+ own files: `$OATS_HOME_DIR/config/tui.json` when `OATS_HOME_DIR` is set.
89
+ `XDG_CONFIG_HOME` is no longer read for it.
90
+ - **An existing file is moved for you** the first time the TUI starts: it
91
+ copies `~/.config/oats/tui.json` (or `$XDG_CONFIG_HOME/oats/tui.json`)
92
+ to the new path and renames the old file `tui.json.migrated`, beside
93
+ it. Nothing else changes.
94
+ - **If both files are there, the TUI refuses to start** with
95
+ `E_TUI_CONFIG`, naming both: copy what you need into
96
+ `~/.oats/config/tui.json`, then remove the old file.
97
+ - **If you keep `tui.json` in a dotfiles manager,** point it at
98
+ `~/.oats/config/tui.json`. A manager that puts the old file back makes
99
+ both files present, and the TUI refuses until you remove it.
100
+ - When the move can't be made (the old file is a link to nothing,
101
+ `tui.json.migrated` is already there, the file system has no hard links,
102
+ or a step fails), the TUI says why and stops: move the file yourself.
103
+ See [OATS TUI](../tui.md#the-move-from-configoats).
104
+
105
+ - **OATS Desktop accepts an `oats` CLI 0.66.x.** Its band is now
106
+ `>=0.26.0 <0.67.0`. 0.66 adds no new gate on the band: the Desktop's Add a
107
+ machine already passes the `--dir` that `oats server connect` now requires.
108
+
109
+ - **A new workspace gets messaging, a team and a first developer in its first
110
+ commit, with no pull requests and no API key.** The `oats-getting-started`
111
+ skill asks for an aweb username in its one round of questions, writes the
112
+ workspace with `oats.aweb`, a team `default:<username>.aweb.ai`,
113
+ `defaultTeam` and a developer soul beside the setup expert, then signs up
114
+ the account with `oats aweb setup --username` before the spawn. Later
115
+ changes follow oats.setup's push rule (the next entry). The skill also runs `gh auth setup-git` when gh is
116
+ already logged in, so the first push and `oats onboard` no longer fail with
117
+ "could not read Username". The README's Start here tells a coding agent
118
+ exactly what to download and follow.
119
+
120
+ - **The setup soul that the `oats-getting-started` skill writes leaves when
121
+ to push to `oats.setup`.** Its `AGENTS.md` states no push rule of its own.
122
+ From `oats.setup` 2.8.3 (oats.framework 1.13.4), the setup expert checks
123
+ before each push (`/oats-workspace-config`, "Change a shared file"): it
124
+ pushes straight to the default branch only where nobody else can push and
125
+ nothing guards that branch, and to a member repository only on the
126
+ person's yes; otherwise it opens a pull request. An older `oats.setup`
127
+ always opens one ([#1314](https://github.com/awebai/oats/issues/1314)).
128
+
129
+ ## Fixed
130
+
131
+ - Capture setup now shares one checked publisher for hooks, service definitions
132
+ and pending activation markers: it syncs file contents before rename, then
133
+ the containing directory, and syncs newly created parent entries in order.
134
+ Required sync failures exit nonzero; failures after publication name the
135
+ affected target and stage without claiming rollback or established durability.
136
+
137
+ ## Provider updates
138
+
139
+ - **oats.framework 1.13.4: oats.setup 2.8.3.** Text only: its floor
140
+ (`compatibility.oats`) does not change.
141
+ - **Straight pushes to a repository only the person can push to.** The
142
+ briefing's rule for shared files was "only by pull request".
143
+ `/oats-workspace-config`'s "Change a shared file" now has two routes. A
144
+ commit goes straight to a repository's default branch, the workspace's
145
+ host or a member repository alike, only when checks right before the
146
+ push show that the person alone can push to it and nothing guards the
147
+ branch:
148
+ - they are its admin and its only collaborator with push access; for an
149
+ organization's repository, an active member and its only owner;
150
+ - no deploy key can write;
151
+ - no branch protection or ruleset guards the default branch (a plan
152
+ without rulesets counts as unguarded).
153
+
154
+ For the host, the setup expert then pushes and tells them what changed.
155
+ For a member repository, it first shows them the commit and says that
156
+ the push runs that repository's push-triggered CI and deploys, and it
157
+ pushes only on their yes. Otherwise the change is a pull request, and a
158
+ refused push never takes another route. The briefing,
159
+ `/oats-setup-expert`, `/oats-package-pins`, `/oats-teams`,
160
+ `/oats-automations` and `/oats-setup-model` follow it
161
+ ([#1314](https://github.com/awebai/oats/issues/1314)).
162
+ - **`/oats-setup-model` on a capture setup that failed after
163
+ publication.** When the setup summary says that publication may have
164
+ occurred but durability was not established, inspect the named target
165
+ and stage before rerunning, and keep that evidence. A sync or close
166
+ failure after the rename does not mean that the old file was restored
167
+ ([#1340](https://github.com/awebai/oats/issues/1340)).
168
+
169
+ - **oats.aweb 1.30.0: Codex readiness from the kernel's launch record.** The
170
+ catalog and this workspace pin `oats.aweb: v1.30.0`
171
+ ([#1345](https://github.com/awebai/oats/issues/1345)).
172
+ - Readiness takes a home's runtime from the kernel's recorded
173
+ `instance.json` `launch.harness` (or top-level `harness`), not from
174
+ provider metadata. A home recorded as Codex needs the host wake broker:
175
+ a missing Codex target or primary stream reports `wake-stream-missing`.
176
+ Malformed or inconsistent kernel fields report
177
+ `receive-record-unavailable`.
178
+ - A malformed `status.updated_at` from `aw wake status` reports
179
+ `wake-status-timestamp-unknown`, naming the aw client and daemon
180
+ versions, instead of `wake-status-stale`.
181
+ - The floors are unchanged (OATS >=0.52.0, aw >=1.36.33). A deployment
182
+ gets it by pinning `oats.aweb: v1.30.0` and running `oats sync`; only
183
+ new spawns use it.
package/docs/servers.md CHANGED
@@ -71,7 +71,7 @@ which is where a [macOS keychain](#git-on-a-macos-host) problem shows up.
71
71
  ## Connect a machine
72
72
 
73
73
  ```bash
74
- oats server connect altair-aweb --ssh altair --path /opt/homebrew/bin --install-oats
74
+ oats server connect altair-aweb --ssh altair --dir '~/acme' --path /opt/homebrew/bin --install-oats
75
75
  ```
76
76
 
77
77
  Run from a deployment, `server connect` puts that deployment's workspace on
@@ -81,8 +81,8 @@ missing, so after a human step you run the same command again.
81
81
 
82
82
  | Option | Default |
83
83
  |---|---|
84
+ | `--dir <path>` | none, inside a deployment too: the folder on the host for this deployment, absolute or `~/…` (resolved by the host). Without it: `E_BAD_ARGS` "--dir <path on the host> is required: the folder on `<host>` for this deployment (absolute, or ~/… resolved there)". A registration made before it was required is unchanged |
84
85
  | `--workspace-ref <ref>` | this deployment's `oats-local.yaml` `workspace:` |
85
- | `--dir <path>` | `~/Agents/<this deployment's directory name>`; absolute or `~/…`, resolved by the host |
86
86
  | `--oats <path>`, `--path <dirs>`, `--label <text>` | as for `server add`; `--path` is where the host finds `npm`, `oats` and the harnesses |
87
87
  | `--install-oats` | off: a missing or older OATS is a human step |
88
88
  | `--replace` | off: an id registered for another host or directory is refused |