@awebai/oats 0.69.19 → 0.69.21
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bin/oats.mjs +28 -5
- package/docs/capabilities.md +27 -14
- package/docs/capability-manifest.schema.json +1 -1
- package/docs/container.md +218 -18
- package/docs/desktop-cli-api.md +105 -11
- package/docs/desktop.md +122 -65
- package/docs/implementation.md +3 -2
- package/docs/integrations.md +2 -2
- package/docs/knowledge.md +5 -5
- package/docs/official-catalog.md +5 -5
- package/docs/packages.md +13 -13
- package/docs/release-notes/v0.69.20.md +325 -0
- package/docs/release-notes/v0.69.21.md +155 -0
- package/docs/servers.md +9 -3
- package/docs/souls-and-instances.md +15 -2
- package/docs/upgrading.md +17 -5
- package/docs/workspaces.md +13 -7
- package/lib/capability-contract.mjs +2 -2
- package/lib/command-flags.mjs +1 -0
- package/lib/core.mjs +36 -198
- package/lib/hook-outcome.mjs +6 -0
- package/lib/instance-inspect.mjs +3 -0
- package/lib/instance-lifecycle.mjs +19 -1
- package/lib/instance-listing.mjs +11 -6
- package/lib/instance-pin.mjs +59 -0
- package/lib/kernel-features.mjs +1 -1
- package/lib/launch-prompt-fixtures/README.md +6 -0
- package/lib/retire-admission.mjs +215 -0
- package/lib/servers.mjs +11 -3
- package/package-catalog.json +3 -3
- package/package.json +1 -1
- package/packages/client/attributed-human.mjs +13 -0
- package/packages/client/deployment-data.mjs +4 -0
- package/packages/client/deployment-panel.mjs +2 -0
- package/packages/client/instance-lifecycle.mjs +6 -4
- package/packages/client/lifecycle-confirmation.mjs +4 -2
- package/packages/client/lifecycle-contract.mjs +11 -6
- package/packages/client/remote-roster.mjs +4 -0
- package/packages/client/roster-row-facts.mjs +50 -0
- package/packages/record/README.md +15 -2
- package/packages/record/docs/capture-service.md +14 -0
- package/packages/record/lib/canonical.mjs +2 -70
- package/packages/record/lib/capture-aw-unit.mjs +14 -3
- package/packages/record/lib/capture-aw.mjs +11 -5
- package/packages/record/lib/capture-health.mjs +16 -5
- package/skills/oats-getting-started/SKILL.md +211 -28
package/docs/packages.md
CHANGED
|
@@ -48,14 +48,14 @@ whole organisation:
|
|
|
48
48
|
|
|
49
49
|
```yaml
|
|
50
50
|
packages:
|
|
51
|
-
oats.okf: v6.0
|
|
51
|
+
oats.okf: v6.2.0 # bare version → the official catalog
|
|
52
52
|
acme.tools: git:github.com/acme/tools@v0.4.0 # direct ref: git:<repo>@<tag or full OID>
|
|
53
53
|
```
|
|
54
54
|
|
|
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.
|
|
58
|
+
convention (`v5.8.0` or `oats-framework/v1.26.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.
|
|
82
|
-
oats.okf: v6.0
|
|
83
|
-
oats.aweb: v1.
|
|
81
|
+
oats.framework: v1.26.0
|
|
82
|
+
oats.okf: v6.2.0
|
|
83
|
+
oats.aweb: v1.43.0
|
|
84
84
|
teams:
|
|
85
85
|
platform: { team: "platform:acme.aweb.ai", description: Platform engineering }
|
|
86
86
|
defaults:
|
|
@@ -109,7 +109,7 @@ decision recorded in the lock.
|
|
|
109
109
|
$ oats sync
|
|
110
110
|
workspace acme (github.com/acme/agents @ 3f2a9c1e)
|
|
111
111
|
members agents ✓↔ (@ 3f2a9c1e) platform ✓↔ (@ 77c0a1b2) billing ✗ (no-backlink)
|
|
112
|
-
packages acme.tools 0.4.0 ✓ (@ 47f4b816) oats.okf 6.0
|
|
112
|
+
packages acme.tools 0.4.0 ✓ (@ 47f4b816) oats.okf 6.2.0 ✓ (@ 92c63060)
|
|
113
113
|
changed acme.tools — → 0.4.0 (@ 47f4b816)
|
|
114
114
|
souls 9 discovered (6 members, 1 external, 2 package, 0 disabled here) · 0 private capabilities
|
|
115
115
|
teams platform (shared) · this deployment's: oats teams
|
|
@@ -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.
|
|
158
|
+
oats package add oats.aweb v1.43.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
|
```
|
|
@@ -181,8 +181,8 @@ same workspace commit hold identical locks.
|
|
|
181
181
|
"source": "catalog:oats.okf",
|
|
182
182
|
"url": "https://github.com/awebai/oats-okf.git",
|
|
183
183
|
"path": "oats-package",
|
|
184
|
-
"version": "6.0
|
|
185
|
-
"commit": "
|
|
184
|
+
"version": "6.2.0",
|
|
185
|
+
"commit": "92c630606db81f55c3e31002cb51d0e603dc7902",
|
|
186
186
|
"integrity": "sha256-…",
|
|
187
187
|
"capabilities": ["oats.okf", "oats.okf-harvest", "oats.okf-maintenance"]
|
|
188
188
|
},
|
|
@@ -431,12 +431,12 @@ A soul that names one of the package's capabilities with
|
|
|
431
431
|
{
|
|
432
432
|
"policy": "docs/official-catalog.md",
|
|
433
433
|
"packages": {
|
|
434
|
-
"oats.okf": { "url": "https://github.com/awebai/oats-okf.git", "ref": "v6.0
|
|
435
|
-
"oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.
|
|
434
|
+
"oats.okf": { "url": "https://github.com/awebai/oats-okf.git", "ref": "v6.2.0", "path": "oats-package" },
|
|
435
|
+
"oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.26.0", "path": "oats-package" }
|
|
436
436
|
}
|
|
437
437
|
}
|
|
438
438
|
```
|
|
439
439
|
|
|
440
|
-
`ref` carries the tag convention: a workspace's `oats.framework: v1.
|
|
441
|
-
resolves to tag `oats-framework/v1.
|
|
440
|
+
`ref` carries the tag convention: a workspace's `oats.framework: v1.26.0`
|
|
441
|
+
resolves to tag `oats-framework/v1.26.0`. Resolving through the catalog never
|
|
442
442
|
advances a lock by itself: `oats sync` does, and says so.
|
|
@@ -0,0 +1,325 @@
|
|
|
1
|
+
# OATS 0.69.20
|
|
2
|
+
|
|
3
|
+
The official catalog pins oats.okf 6.2.0 and oats.framework 1.26.0. oats.aweb
|
|
4
|
+
stays 1.42.1. Retiring an old home whose recorded cleanup hooks cannot run is
|
|
5
|
+
now refused before anything stops, with `--force` as the named way out, and
|
|
6
|
+
the Desktop's Remove explains why. The team container gains an egress
|
|
7
|
+
component that routes only the services an agent needs. The Desktop shows an
|
|
8
|
+
instance's owning human. OATS's own copy of the engineering template moves to
|
|
9
|
+
template-v4.0.2.
|
|
10
|
+
|
|
11
|
+
## Upgrade
|
|
12
|
+
|
|
13
|
+
- **Either order of the Desktop and the CLI works** from a Desktop newer than
|
|
14
|
+
0.69.17 ([Either order works](../upgrading.md#either-order-works)). A
|
|
15
|
+
Desktop of 0.69.17 or older still goes first.
|
|
16
|
+
- **Package pins:** oats.okf 6.2.0 (from 6.0.3) and oats.framework 1.26.0
|
|
17
|
+
(from 1.25.2). oats.aweb stays 1.42.1. `oats sync` takes them.
|
|
18
|
+
- **Retiring an old home can now be refused.** A home spawned before
|
|
19
|
+
`capabilityRuntime`, or captured before 0.26, whose recorded retire hooks
|
|
20
|
+
cannot run is refused with `E_UNIDENTIFIED_INSTANCE_HOME`, unless its record
|
|
21
|
+
proves that no cleanup is owed. Clean up its external identities and
|
|
22
|
+
memberships with the provider's tooling, then run
|
|
23
|
+
`oats retire <instance> --force` (details under Changed).
|
|
24
|
+
- **Team-container deployments:**
|
|
25
|
+
- After pulling the updated team agent image, recreate existing agent
|
|
26
|
+
containers to apply the 50-second stop timeout. Acceptance refuses the
|
|
27
|
+
previous 45-second timeout.
|
|
28
|
+
- Deployment bundles default `team.registryRoute` to `external`. Existing
|
|
29
|
+
deployments with a registry Compose service must set
|
|
30
|
+
`team.registryRoute: local` before upgrading. External mode refuses a
|
|
31
|
+
local registry service or an owned destination, and local mode must refuse
|
|
32
|
+
a URL the local service does not serve.
|
|
33
|
+
- **Respawn instances** to take the new framework skills and this workspace's
|
|
34
|
+
template-v4.0.2 texts. A running instance keeps the texts it was composed
|
|
35
|
+
with.
|
|
36
|
+
|
|
37
|
+
## Added
|
|
38
|
+
|
|
39
|
+
- The Desktop's instance panel shows an instance's **Owning human** in its
|
|
40
|
+
Lineage section when OATS reports a human its messaging identity is
|
|
41
|
+
attributed to (`attributedHuman` on its status row, local or on a server).
|
|
42
|
+
Instances keep their own names as their labels everywhere, and an instance
|
|
43
|
+
with no human attributed looks as before
|
|
44
|
+
([An instance's owning human](../desktop.md#an-instances-owning-human)).
|
|
45
|
+
|
|
46
|
+
- The Compose egress boundary probe accepts `--json` for `{passed,receipts,error?}`
|
|
47
|
+
output and an optional derived `namePrefix` for every temporary container.
|
|
48
|
+
Receipts identify the name, image, network, confirmed creation and verified
|
|
49
|
+
absence; stderr includes receipts and unverified names in either mode.
|
|
50
|
+
|
|
51
|
+
- Agent egress policies can declare a nonempty subset of aweb, logs, registry,
|
|
52
|
+
secrets and signer. Targets and probe paths must match exactly. Namespace
|
|
53
|
+
authority TXT records are required with registry and refused without registry,
|
|
54
|
+
including messaging-only sets; the human origin is required with signer and
|
|
55
|
+
refused without signer. Omission keeps
|
|
56
|
+
the existing five-service compilation. The minimal Compose wrapper includes
|
|
57
|
+
explicit IPAM and a read-only preflight that refuses failed observations and
|
|
58
|
+
overlaps. Every subset retains the universal boundary controls; team-image CI
|
|
59
|
+
builds and probes the full set and two messaging subsets. See the
|
|
60
|
+
[container reference](../container.md#egress-component).
|
|
61
|
+
|
|
62
|
+
- The team-container deployment can build a non-root DNS/TLS egress image and
|
|
63
|
+
extend its Compose service. It routes only the named aweb, Secrets, Logs, signer
|
|
64
|
+
request and registry hosts, using pinned upstream addresses and profile-derived
|
|
65
|
+
public namespace TXT records. There is no recursive DNS or mounted service key.
|
|
66
|
+
|
|
67
|
+
- The agent Compose fragment requires `AGENT_TMP_SIZE`, in positive integer bytes
|
|
68
|
+
from the shared `agents.tmpSize` input, and applies it to the `/tmp` tmpfs. Its
|
|
69
|
+
acceptance check refuses a missing or different limit.
|
|
70
|
+
|
|
71
|
+
- Optional fragments add a public CA file with two fixed trust settings, or
|
|
72
|
+
operator-maintained bare Git mirrors at read-only `/mirrors`. Acceptance checks
|
|
73
|
+
their exact mounts and refuses writable-state aliases, multiply linked CA files
|
|
74
|
+
and arbitrary environment changes. The fixed public trust reaches the supervisor,
|
|
75
|
+
broker, direct SSH commands and login-captured tmux panes while retaining normal
|
|
76
|
+
public roots. No service credential or TLS verification bypass is added.
|
|
77
|
+
|
|
78
|
+
- Runtime acceptance proves the agent's own on-link gateway denial with live
|
|
79
|
+
controls and a plain-versus-isolated bridge regression. The ingress probe checks
|
|
80
|
+
every policy route over HTTP/1.1 and HTTP/2, with required full-policy inputs
|
|
81
|
+
and valid 200 service controls. Owned routes require separate common-path log
|
|
82
|
+
coverage before/after negatives and non-delivery for forbidden human authorities;
|
|
83
|
+
known-name refusals require completed TLS. Partial signer-only CLI calls cannot
|
|
84
|
+
emit the admission token.
|
|
85
|
+
Both checks must pass before agents launch. Readiness and rendered policy alone do not establish
|
|
86
|
+
isolation. See the [component contract](../../container/agent/egress/README.md).
|
|
87
|
+
|
|
88
|
+
- The egress component can enable two fixed external roles: Git HTTPS at
|
|
89
|
+
`github.com` and model HTTPS at `api.anthropic.com`. Operator-selected public
|
|
90
|
+
IPv4 DNS resolvers are required, with no default. Agent DNS still points only
|
|
91
|
+
at the proxy. Each external connection rejects unsafe or deployment addresses
|
|
92
|
+
and connects to a validated IP without resolving it again.
|
|
93
|
+
- External enforcement is exact SNI plus a public destination; it does not filter
|
|
94
|
+
HTTP authorities, paths, methods or repositories, or prove non-delivery at a
|
|
95
|
+
public backend. The five pinned service routes and owned-backend audit remain
|
|
96
|
+
separate. Runtime checks add verified-TLS external controls and refused-name
|
|
97
|
+
logging. Claude launch settings suppress ancillary traffic, whose actual host
|
|
98
|
+
requirements still need a real authorized start and turn.
|
|
99
|
+
|
|
100
|
+
## Changed
|
|
101
|
+
|
|
102
|
+
- **`oats.framework` 1.26.0: `oats.core` 2.14.0, `oats.setup` 2.16.0,
|
|
103
|
+
`oats.coordination-setup` 1.1.0.**
|
|
104
|
+
- `oats.core`'s `/oats-operate` says that, from OATS 0.69.20, retiring a
|
|
105
|
+
home whose recorded retire hooks cannot run is refused with
|
|
106
|
+
`E_UNIDENTIFIED_INSTANCE_HOME` before anything stops, and that
|
|
107
|
+
`oats retire <instance> --force` then removes the home, warning that the
|
|
108
|
+
skipped hooks revoked nothing (#1953).
|
|
109
|
+
- `oats.setup`'s `/oats-onboarding` pins `oats.okf` 6.2.0 for knowledge
|
|
110
|
+
operations (#1945).
|
|
111
|
+
- `oats.setup`'s `/oats-agent-permissions` example asks a person before
|
|
112
|
+
`aw` runs with `--identity-home`, `--human` or `--team`, and no longer
|
|
113
|
+
allows a bare `aw mail ack` (#1952).
|
|
114
|
+
- `oats.coordination-setup` follows engineering-coordination template v4
|
|
115
|
+
(#1943). A maintainer's green light is an option per lane, off by
|
|
116
|
+
default. The landing rules list the lanes and their owners, and a lane's
|
|
117
|
+
maintainer is found by its instance name, `<person>-<lane>-maintainer`.
|
|
118
|
+
`VERIFIED at <head>` comes from whoever specified the work.
|
|
119
|
+
|
|
120
|
+
No capability needs a newer OATS. The retire refusal is the kernel's own,
|
|
121
|
+
and the skill names the version it starts in.
|
|
122
|
+
|
|
123
|
+
- The team agent image pins the released OATS 0.69.19 dependency closure,
|
|
124
|
+
removing the unused pi extension subtree from the image lock. The other
|
|
125
|
+
committed CLI packages and their integrity pins remain unchanged.
|
|
126
|
+
|
|
127
|
+
- The agent supervisor lets the wake broker finish its five-second channel
|
|
128
|
+
delivery drain before escalation. Broker cleanup allows six seconds and
|
|
129
|
+
sshd cleanup keeps three seconds; container acceptance requires a 50-second
|
|
130
|
+
stop grace for the kernel and supervisor phases. The runtime deadline is a
|
|
131
|
+
final failure boundary for stuck OS work; wake delivery and model activity
|
|
132
|
+
require separate evidence.
|
|
133
|
+
|
|
134
|
+
- **The official catalog pins oats.okf 6.2.0** (from 6.0.3, taking 6.1.0's
|
|
135
|
+
changes with it), and OATS's own workspace takes it. A knowledge change
|
|
136
|
+
names the agent that proposed it in Git trailers on its commit, and
|
|
137
|
+
`oats okf propose --apply` checks `gh` before it pushes anything,
|
|
138
|
+
refusing `E_GH_UNAVAILABLE` with the fix (6.1.0). New in 6.2.0: an
|
|
139
|
+
optional, host-only setting `settings.oats.okf.github-token-file` (in
|
|
140
|
+
`oats-local.yaml` only) gives every remote `git` and `gh` call of oats.okf
|
|
141
|
+
the token in that file, for knowledge writes from a container; with it, a
|
|
142
|
+
publication refuses `E_HOST_CREDENTIAL` while the host could answer GitHub
|
|
143
|
+
in the token's place. `oats okf setup --check --soul <soul>` says whether a
|
|
144
|
+
deployment is provisioned for knowledge and names each fix
|
|
145
|
+
([Bringing up a deployment's knowledge store](https://github.com/oats-project/oats-okf/blob/v6.2.0/README.md#bringing-up-a-deployments-knowledge-store)).
|
|
146
|
+
Without `github-token-file` nothing changes, apart from the `gh` check
|
|
147
|
+
before a push. Three things are not yet proven in a live run: a proposal
|
|
148
|
+
opened through `github-token-file` on a real private repository; GitHub
|
|
149
|
+
refusing that write-role-only credential a direct push and a merge under
|
|
150
|
+
the example ruleset; and what GitHub reports for such a token, which
|
|
151
|
+
`setup --check` reads. A container deployment that relies on
|
|
152
|
+
`github-token-file` waits for that run. The generated mirror under
|
|
153
|
+
`mirrors/oats-okf*` is finalized from the v6.2.0 tag
|
|
154
|
+
([oats.okf's CHANGELOG](https://github.com/oats-project/oats-okf/blob/v6.2.0/CHANGELOG.md)).
|
|
155
|
+
|
|
156
|
+
- The shared ingress probe accepts an explicitly external registry with a harmless
|
|
157
|
+
verified-TLS 200 control at every pinned address over HTTP/1.1 and HTTP/2. It
|
|
158
|
+
reports positive connectivity only, without third-party refusal or backend-log
|
|
159
|
+
claims. The other four service routes and signer/human authority refusal keep
|
|
160
|
+
their full owned-backend audit. External registry addresses must not overlap
|
|
161
|
+
deployment destinations; no new route or forwarding policy is added.
|
|
162
|
+
|
|
163
|
+
- Retiring homes spawned by a kernel from before `capabilityRuntime`, and
|
|
164
|
+
captured homes from before 0.26, now refuses with
|
|
165
|
+
`E_UNIDENTIFIED_INSTANCE_HOME` if their hooks cannot run and the record
|
|
166
|
+
does not prove no cleanup is owed. Both `--plan` (including Desktop Remove)
|
|
167
|
+
and apply refuse before anything is stopped, run or removed, children included.
|
|
168
|
+
Inspect the home, clean up external identities/memberships using the provider's
|
|
169
|
+
tooling, then run `oats retire <instance> --force`. Force keeps the warnings
|
|
170
|
+
that hooks did not run and state was not revoked; it can leave external state
|
|
171
|
+
active after deleting the local credential. Captured homes need positive
|
|
172
|
+
evidence that no capability's spawn hook ran to retire without force.
|
|
173
|
+
Forced self-retirement keeps the force choice in its deferred completion.
|
|
174
|
+
|
|
175
|
+
- Retire plans for a home that cannot be entered (mode 000), or an
|
|
176
|
+
interrupted spawn's stub without recorded hook bindings, now refuse with
|
|
177
|
+
the same cleanup admission as apply. This is the before-effects plan/apply
|
|
178
|
+
rule; a refusal returns no plan claiming that work is absent. The stub's
|
|
179
|
+
refusal now names missing `capabilityRuntime` and retains the `--force`
|
|
180
|
+
remedy. Homes lacking workspace modules alone are not newly refused:
|
|
181
|
+
the cleanup rule depends on their recorded hook bindings.
|
|
182
|
+
|
|
183
|
+
- Retire hooks now run in the repository Git identifies for an instance's
|
|
184
|
+
own worktree when its record names no `repo`. Previously that home ran no
|
|
185
|
+
retire hook and warned that there was no context repository. Retirement
|
|
186
|
+
now performs the recorded cleanup in the Git-derived context without
|
|
187
|
+
rewriting the instance record.
|
|
188
|
+
|
|
189
|
+
- **OATS's own copy of the engineering template moves to template-v4.0.0,
|
|
190
|
+
taken up whole.** The template recomposed every text, so the copy is
|
|
191
|
+
template-v4.0.0's text with OATS's answers and its marked adaptations
|
|
192
|
+
written back in. This changes the texts this workspace's own souls are
|
|
193
|
+
composed from, not the kernel or any package contract.
|
|
194
|
+
- **One agent is the default,** and every expert instance holds one seat,
|
|
195
|
+
named on a `Seat:` line in its task: root lead, specialist, or helper or
|
|
196
|
+
probe. A lead sizes the tree to the work: alone, with short-lived probes
|
|
197
|
+
and helpers, or with one long-lived specialist per area for a large
|
|
198
|
+
effort or one across several areas.
|
|
199
|
+
- **Skills renamed or folded in.** `oats.engineering-expert` has five
|
|
200
|
+
skills: `/plan-and-spec`, `/orchestrate-agents` (was `/send-a-helper`),
|
|
201
|
+
`/coordinate-developers` (takes in `/verify-developer-work`),
|
|
202
|
+
`/hand-off-and-ask` (takes in `/hand-off`, `/ask-a-person`,
|
|
203
|
+
`/findings-and-blocks` and `/across-people`) and `/land-on-agreement`
|
|
204
|
+
(takes in `/find-the-maintainer`). `oats.build` has three:
|
|
205
|
+
`/build-in-the-repository` (new), `/run-the-review-loop` and
|
|
206
|
+
`/work-the-reviews`; `/test-first`, `/diagnose-before-fixing`,
|
|
207
|
+
`/design-while-writing`, `/execution-strategy`, `/prove-it-works`,
|
|
208
|
+
`/maintain-dev-docs` and `/worktrees` are gone. `oats.developer` folds
|
|
209
|
+
`/understand-the-spec` into its briefing. `oats.maintainer` has
|
|
210
|
+
`/keep-the-lane` (from `/maintainer-intake`, `/keep-it-clean` and
|
|
211
|
+
`/cross-review-peer`), `/plan-and-ship-release` (from `/plan-release`
|
|
212
|
+
and `/ship-release`), `/pr-review`, `/direction-gate` and
|
|
213
|
+
`/launch-work`; it still drops `/support-maintainer`. `oats.landing-rules`
|
|
214
|
+
gains `/landing-rules-detail` and `/wait-and-retire`, which every
|
|
215
|
+
coordinating soul now has. The souls' own texts name the new skills.
|
|
216
|
+
- **A lane maintainer's green light.** In the template it is an option a
|
|
217
|
+
lane chooses. Every OATS lane asks for it: the maintainer's read of a PR
|
|
218
|
+
from an effort is now its verdict at the exact head, `GREEN LIGHT`,
|
|
219
|
+
`RETURN` or `ESCALATE`, on direction, contracts, coherence, scope and
|
|
220
|
+
evidence. Each lane's agreements are as before: the PR's second reader,
|
|
221
|
+
the release lane's sign-off where the lane asks, and the merge where the
|
|
222
|
+
lane's arrangement puts it. A PR with no lead still gets the four gates.
|
|
223
|
+
- **Both maintainer reads look at the code and judge direction, roadmap
|
|
224
|
+
and product fit.** The lane maintainer's green light adds its own read
|
|
225
|
+
of the whole diff, from its own checkout, to the five checks: a defect
|
|
226
|
+
it finds there blocks, and it runs no review rounds of its own. The
|
|
227
|
+
release lane's sign-off keeps the four gates (direction, roadmap and
|
|
228
|
+
product fit; correctness over the whole diff; security; mergeability)
|
|
229
|
+
on every PR it signs off, at the exact head being merged, as the final
|
|
230
|
+
gate on main.
|
|
231
|
+
- **What carries to a new head.** A review carries as before, except that a
|
|
232
|
+
fix to a minor is read by the review bot where one runs, otherwise by a
|
|
233
|
+
fresh reviewer briefed with the delta, not by the round's reviewer. A `VERIFIED` note and a green light carry only
|
|
234
|
+
through an unchanged rebase or update; at any other head, whoever gave
|
|
235
|
+
one reads the delta and gives it again.
|
|
236
|
+
- **Every finished instance retires itself,** its children first
|
|
237
|
+
(`oats retire <name> --self`), and its parent checks that it is gone and
|
|
238
|
+
retires one still listed. A reviewer retires itself once its report is
|
|
239
|
+
sent: one reviewer, one report.
|
|
240
|
+
- **OATS keeps its lane map.** The template drops it; OATS's landing rules
|
|
241
|
+
still point at the pinned issue "Lane map for awebai/oats" for its lanes,
|
|
242
|
+
their owners and arrangements, and a lane's maintainer is found by its
|
|
243
|
+
`active` entry there. Maintainers keep their instance names.
|
|
244
|
+
- The model floor, the hosts rule and CI as the test run are stated once,
|
|
245
|
+
in the landing rules' house rules.
|
|
246
|
+
|
|
247
|
+
A running instance keeps the texts it was spawned with: composition is
|
|
248
|
+
frozen at spawn, so no running instance changes, and a new spawn takes
|
|
249
|
+
these. `capabilities/TEMPLATE-RELEASE` records the release and its commit.
|
|
250
|
+
The catalog's row for the engineering template moves to template-v4.0.0.
|
|
251
|
+
- **`oats.framework`'s setup expert teaches the green light as an option.**
|
|
252
|
+
`/set-landing-rules` offers a lane maintainer's green light per lane, off by
|
|
253
|
+
default: recommended for a large project (several lanes or maintainers,
|
|
254
|
+
several people), left out for a small personal project. Its carry rule
|
|
255
|
+
follows template-v4.0.0. `/adapt-to-the-organisation` and
|
|
256
|
+
`/design-the-roster` write no lane map: the landing rules list the lanes and
|
|
257
|
+
their owners, and a maintainer is found by its instance name,
|
|
258
|
+
`<person>-<lane>-maintainer`.
|
|
259
|
+
|
|
260
|
+
- **OATS's own copy of the engineering template moves to template-v4.0.2.**
|
|
261
|
+
The two patch releases fix how a lane's maintainer is found and started.
|
|
262
|
+
The copy takes them in, adapted to the lane map, where a lane's maintainer
|
|
263
|
+
is still its `active` entry. This changes the texts this workspace's own
|
|
264
|
+
souls are composed from, not the kernel or any package contract.
|
|
265
|
+
- **A refused spawn means the seat is held.** When `oats spawn` refuses a
|
|
266
|
+
maintainer's name because it is taken, a holder is running or stopped.
|
|
267
|
+
The dispatcher, the expert and the maintainer each find it and start
|
|
268
|
+
none under another name.
|
|
269
|
+
- **A new maintainer gets a name no instance has had.** The kernel accepts
|
|
270
|
+
a retired instance's name. So before starting one, the dispatcher and
|
|
271
|
+
the expert check each name of the family in turn with
|
|
272
|
+
`oats instance events <name>`, and the maintainer's launch-work says to
|
|
273
|
+
do the same. A name the roster still lists counts as used.
|
|
274
|
+
- **A maintainer named only on the roster is asked about first.** Such a
|
|
275
|
+
name may be retired or running elsewhere. The dispatcher, the expert and
|
|
276
|
+
the maintainer ask their person before starting another.
|
|
277
|
+
- **The dispatcher handles the expert's other cases too.** In another
|
|
278
|
+
person's lane, it asks their dispatcher, or that person. Where the
|
|
279
|
+
workspace has no maintainer soul, or it can't tell the lane or its
|
|
280
|
+
owner, it asks its person. In each case it starts none.
|
|
281
|
+
- **The maintainer soul's OATS review skill agrees with `pr-review`.** It
|
|
282
|
+
names the four gates for the release lane's sign-off as well as for a PR
|
|
283
|
+
with no lead, and the green light's read of the whole diff.
|
|
284
|
+
- **The official catalog** lists template-v4.0.2 as the engineering
|
|
285
|
+
template's latest release.
|
|
286
|
+
|
|
287
|
+
## Fixed
|
|
288
|
+
|
|
289
|
+
- Canary and TCP-control cleanup checks exact-name absence, including after Docker
|
|
290
|
+
timeouts, and removes a container only when its per-attempt ownership label
|
|
291
|
+
matches. Name collisions and failed observations refuse admission without
|
|
292
|
+
removing another caller's container. Diagnostics distinguish confirmed leftovers
|
|
293
|
+
from unowned or unverified names, including collisions. The host-side helpers remain outside the
|
|
294
|
+
egress image build context.
|
|
295
|
+
|
|
296
|
+
- The egress ingress routine names its signer-role requirement before sending
|
|
297
|
+
controls when given a policy without signer. Runtime boundary controls now
|
|
298
|
+
share the compiler's canonical role order, including in emitted probe
|
|
299
|
+
programs. The packaged CLI keeps its values-withheld refusal diagnostic.
|
|
300
|
+
|
|
301
|
+
- Desktop's Remove refusal now explains when OATS cannot tell what a home's
|
|
302
|
+
capabilities created or cannot run their cleanup. The headline says
|
|
303
|
+
nothing was removed and points to Details for the kernel's cause and
|
|
304
|
+
remedy. It never suggests forcing an unreadable record: that case needs
|
|
305
|
+
the file restored. Force commands appear only in Details where the
|
|
306
|
+
kernel offers them. Stop keeps its existing refusal text.
|
|
307
|
+
|
|
308
|
+
- Conversation capture stops before sealed aw client-log entries, preserves
|
|
309
|
+
the cursor, and reports them as sealed instead of failed projections.
|
|
310
|
+
Command capture sets the input aside as “sealed, not readable by this recorder”.
|
|
311
|
+
|
|
312
|
+
- Capability commands routed with `--server` refuse `--invite <token>` and
|
|
313
|
+
`--invite=<token>` before ssh starts. Use `--invite-stdin` and a pipe instead.
|
|
314
|
+
- The agent-permissions setup example asks before `aw` selects another identity,
|
|
315
|
+
human principal or team, and leaves mail acknowledgement to the classifier.
|
|
316
|
+
|
|
317
|
+
## Removed
|
|
318
|
+
|
|
319
|
+
- Removed the recorder's unused signature-verification helpers
|
|
320
|
+
`base58Decode`, `publicKeyFromDidKey`, `base64DecodeLoose`,
|
|
321
|
+
`verifyDidKeySignature` and `verifyTurnSig` from the `@awebai/turn-record/canonical` export.
|
|
322
|
+
`@awebai/turn-record` lives in this repository and is not published to npm.
|
|
323
|
+
An importer of a local copy must remove those imports or use a
|
|
324
|
+
signature-verification library. No in-repository production callers used
|
|
325
|
+
them. Source signatures are still preserved.
|
|
@@ -0,0 +1,155 @@
|
|
|
1
|
+
# OATS 0.69.21
|
|
2
|
+
|
|
3
|
+
The official catalog pins oats.aweb 1.43.0: a private aw registry is admitted
|
|
4
|
+
by one host setting, aw children no longer take exported selectors, and grant
|
|
5
|
+
seats stay in their recorded team. Instances can be pinned to the top of their
|
|
6
|
+
machine's list (`oats instance pin`). The Desktop's sidebar is reworked: two-line
|
|
7
|
+
rows, groups that start collapsed, no lineage lines, and a new foot. The
|
|
8
|
+
getting-started skill sets up a workspace on the person's own aweb server.
|
|
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)). A
|
|
14
|
+
Desktop of 0.69.17 or older still goes first.
|
|
15
|
+
- **Package pin:** oats.aweb 1.43.0 (from 1.42.1). oats.framework stays
|
|
16
|
+
1.26.0 and oats.okf 6.2.0. `oats sync` takes it.
|
|
17
|
+
|
|
18
|
+
What a deployment must change, from oats.aweb's 1.43.0 entry:
|
|
19
|
+
|
|
20
|
+
|
|
21
|
+
- **On a non-public aw registry:**
|
|
22
|
+
1. Run `oats aweb setup --registry <origin>` in the deployment.
|
|
23
|
+
2. Rerun `oats aweb resident create <name>` for each resident.
|
|
24
|
+
3. Run `oats aweb wake install` from your own shell.
|
|
25
|
+
4. Restart the homes.
|
|
26
|
+
|
|
27
|
+
Until then, setup, spawn, join, launch and readiness refuse with
|
|
28
|
+
`registry-setting-required`. A deployment on the public registry changes
|
|
29
|
+
nothing.
|
|
30
|
+
- **Exported aw selectors no longer reach aw:** `AWEB_IDENTITY_HOME`,
|
|
31
|
+
`AWEB_URL`, `AWEB_API_KEY`, `AWEB_ROLE_NAME`, `AWEB_ROLE`,
|
|
32
|
+
`AWID_REGISTRY_URL`. If you exported them for ordinary lifecycle commands,
|
|
33
|
+
record the service in the selected aw home instead, and a private registry
|
|
34
|
+
in the setting above.
|
|
35
|
+
- **Grant seats:**
|
|
36
|
+
- A grant seat with `.oats-aweb/seat.json` whose `identity.resident` or
|
|
37
|
+
default team has changed refuses start: respawn it.
|
|
38
|
+
- A home that an earlier release renewed into another team needs the
|
|
39
|
+
printed manual revoke, then `oats retire <instance> --force`.
|
|
40
|
+
- **Retained seats:** a symlinked `identity.source`, or a link or special
|
|
41
|
+
file in the copied authority, now refuses. Point it at the real directory.
|
|
42
|
+
- **Scripts:**
|
|
43
|
+
- `oats aweb setup --check-only --json` answers `member:null` with a nonzero
|
|
44
|
+
exit when the membership can't be read.
|
|
45
|
+
- `join --plan` fails with `E_SETUP_MEMBERSHIP` for an unreadable root.
|
|
46
|
+
- `setup --create`, and `setup --join` without a token, refuse while the
|
|
47
|
+
default root's membership can't be read.
|
|
48
|
+
- An unavailable username fails as `E_SETUP_USERNAME_UNAVAILABLE`, where it
|
|
49
|
+
was `E_SETUP_NATIVE`.
|
|
50
|
+
|
|
51
|
+
**Respawn instances** to take the new oats.aweb module, or move a stopped
|
|
52
|
+
home with `oats instance upgrade`. A running instance keeps the module it was
|
|
53
|
+
composed with.
|
|
54
|
+
|
|
55
|
+
## Added
|
|
56
|
+
|
|
57
|
+
- **The `oats-getting-started` skill sets up a new workspace on the
|
|
58
|
+
person's own aweb server** (#1774, #1775). Step 1's messaging line names
|
|
59
|
+
hosted aweb as the default, "unless you run your own aweb server". The
|
|
60
|
+
own-server answer collects
|
|
61
|
+
three things, none of them secret: the namespace domain the person
|
|
62
|
+
controls, the server's public URL, and whether the server uses the public
|
|
63
|
+
AWID registry. A server on a private registry is not set up yet: the
|
|
64
|
+
branch stops before writing anything, says it needs `oats.aweb` with
|
|
65
|
+
`oats aweb setup --registry` (awebai/oats-aweb#284), and offers hosted
|
|
66
|
+
aweb. It also names the prerequisites, which stay on the person's side:
|
|
67
|
+
the namespace's controller key on this computer, its `_awid` DNS record,
|
|
68
|
+
and the server reachable. Then:
|
|
69
|
+
- The skill reads the version `oats.aweb` was tested with (`tested` in
|
|
70
|
+
its `aw-compat.json`, read at the catalog's exact `oats.aweb` ref, never
|
|
71
|
+
`main`) and compares the installed `aw` with it, in `oats.aweb`'s own
|
|
72
|
+
version order. A missing or older `aw` is replaced by `tested`: the skill
|
|
73
|
+
checks the version `aw` prints, and that the program `file` reports is
|
|
74
|
+
for this machine's architecture. A newer `aw` is kept, since another
|
|
75
|
+
deployment may need it, and the hand-over says "aw X is newer than the
|
|
76
|
+
tested Y; kept". On an OATS release whose `oats.aweb` is older than
|
|
77
|
+
`v1.42.1`, the branch stops and offers hosted aweb.
|
|
78
|
+
- The workspace commits the team `<workspace>:<namespace>` as its only
|
|
79
|
+
team and its default. It writes no hosted `default:…aweb.ai` team and no
|
|
80
|
+
`localTeams`.
|
|
81
|
+
- Step 9 checks the DNS record read-only
|
|
82
|
+
(`aw id namespace check-txt`), then creates the team with
|
|
83
|
+
`oats aweb setup --create <workspace> --namespace <domain> --name <workspace>-root`,
|
|
84
|
+
registered with the person's server. It reports where the team key
|
|
85
|
+
lives (the path, never the key), and checks membership before the
|
|
86
|
+
spawn.
|
|
87
|
+
|
|
88
|
+
The skill never makes the namespace's controller key, and never asks for
|
|
89
|
+
`AWEB_API_KEY`. Hosted aweb is unchanged: it installs the latest `aw` and
|
|
90
|
+
records its version. The join of an existing workspace and the machine
|
|
91
|
+
found-list are unchanged, and don't offer the own-server branch.
|
|
92
|
+
|
|
93
|
+
- **Pin an instance at the top of its machine's list** (feature `instance-pin`).
|
|
94
|
+
`oats instance pin <instance> on|off` records or removes the pin, locally or
|
|
95
|
+
with `--server`. Its answer is `{ instancePinApi: 1, instance, home, pinned,
|
|
96
|
+
changed }`; `home` names the home it resolved, so a routed or `--home` pin
|
|
97
|
+
says which one it pinned.
|
|
98
|
+
- The pin is shared. It is kept in the instance's home, so everyone who views
|
|
99
|
+
that machine sees it: the Desktop, the TUI and another machine's routed
|
|
100
|
+
view. There is no per-viewer pin. In 0.69.21 the pin is set and read with
|
|
101
|
+
the CLI only: the Desktop and the TUI show pins, and set them, from the
|
|
102
|
+
next release.
|
|
103
|
+
- The home keeps it in `.oats-pinned.json` through restart, stop, resume and
|
|
104
|
+
`oats instance upgrade`, and a retire removes it with the home. Retire never
|
|
105
|
+
counts the file as work, and a capability cannot declare it.
|
|
106
|
+
- `pinned: true` appears on `oats status --json` rows, on `oats server roster
|
|
107
|
+
--json` rows (only when the host's row says exactly `true`) and on
|
|
108
|
+
`oats inspect --home`. The key is absent when the instance is not pinned.
|
|
109
|
+
- No spawn flag or `soul.yaml` key pins an instance: a pin is a person's
|
|
110
|
+
choice about the view. A routed pin needs a host that lists `instance-pin`.
|
|
111
|
+
|
|
112
|
+
See
|
|
113
|
+
[Pinned instances](../desktop-cli-api.md#pinned-instances-oats-instance-pin).
|
|
114
|
+
|
|
115
|
+
## Changed
|
|
116
|
+
|
|
117
|
+
- **Getting started names an unavailable aweb username.** With an oats.aweb
|
|
118
|
+
that answers `E_SETUP_USERNAME_UNAVAILABLE` (awebai/oats-aweb#286), the
|
|
119
|
+
`oats-getting-started` skill's signup step knows that nothing was created:
|
|
120
|
+
it asks the person for another `N`, or, on a machine found-list, tells
|
|
121
|
+
them why and stops. `E_SETUP_NATIVE` no longer reads as "most likely
|
|
122
|
+
taken"; on an older oats.aweb a taken `N` still fails that way.
|
|
123
|
+
|
|
124
|
+
- **The catalog pins oats.aweb 1.43.0** (awebai/oats-aweb, tag `v1.43.0`), up
|
|
125
|
+
from 1.42.1. It still requires OATS >=0.68.0; the aw floor stays 1.36.33 and
|
|
126
|
+
the tested aw 1.36.58.
|
|
127
|
+
- **Registry admission is one host setting.** A private aw registry is
|
|
128
|
+
admitted only by `settings.oats.aweb.registry`, which
|
|
129
|
+
`oats aweb setup --registry <origin>` records in `oats-local.yaml`. A saved
|
|
130
|
+
`registry_url` and an exported `AWID_REGISTRY_URL` are locators only.
|
|
131
|
+
- **aw children ignore exported selectors.** Each takes only what a call
|
|
132
|
+
passes by name. A malformed `OATS_SETTINGS` refuses instead of using
|
|
133
|
+
defaults.
|
|
134
|
+
- **A grant seat's calls stay in its recorded team,** and its
|
|
135
|
+
`.oats-aweb/seat.json` owns that team. An empty grant seat now completes
|
|
136
|
+
retire with the documented `nothing-to-delete` outcome.
|
|
137
|
+
- **Membership and custody reads fail closed.** An unreadable read is
|
|
138
|
+
unknown, never "not a member".
|
|
139
|
+
- **Setup** names an unavailable username, and points a new account at
|
|
140
|
+
`claim-human`. `--invite-stdin` reads the token without echo on a
|
|
141
|
+
terminal, and `oats aweb invite --out <file>` writes it to a new
|
|
142
|
+
owner-only file.
|
|
143
|
+
|
|
144
|
+
- **The Desktop's sidebar reads more calmly.** An agent's row is two lines: its name, then its soul and the machine it runs on ("oats-expert · falcon": this computer's own rows by its `host.name` in `oats-local.yaml`, else "This Mac"), in a 44px row with its dot centred. The repository, branch, pull request and harness badge are no longer on the row, and the row has no hover card and no tools on hover: the instance panel shows the repository, branch, harness and model, and a new **Needs input** section with the reason an agent waits, how long it has waited and its message; the row's context menu (right-click, Shift+F10 or the Menu key) opens its pull request (**Open pull request…**) and starts a stopped agent (**Start…**). Until the panel serves an agent whose terminal isn't open, the row's tooltip says its repository, branch, harness and model; with the keyboard alone those show once its terminal is open. The roster draws no lines between agents any more: a child is indented under its parent, a little space separates each group from the next, and a screen reader hears "under <parent>" (with "same work" for a child doing its parent's work) and "sibling of <name>". The order and the needs-input marks are unchanged, and the command palette keeps its lines. **Workspace overview** and **Automations** are pinned rows under the list of workspaces, and **Automations** shows a red dot, which a screen reader hears as "a run failed", while a schedule's last run failed. The foot shows **N need you** (it takes you to the first agent that needs you), **New agent** and **?** (the keyboard shortcuts). An empty roster says "No agents yet" and the key that starts one. The CLI and the docs still say "instance". See [the sidebar](../desktop.md#workspaces) and [its instance tree](../desktop.md#the-sidebars-instance-tree).
|
|
145
|
+
|
|
146
|
+
- **The Desktop's sidebar shows the top-level instances only until you open one.** An instance with children has a chevron before its name, with the number of instances under it. Click the chevron to show or hide its group; a click elsewhere on the row still opens its terminal, and Right and Left still open and close the focused row. Every instance at the top of the tree starts collapsed in each new window (except one still being set up or retired, or whose retire failed, which stays open), and an instance inside a group starts open. A collapsed instance still shows "! N below" for the hidden instances that need input. **Show in roster**, `--instance` and a spawn from the Desktop open the rows above the instance they show. The TUI's list is unchanged and still shows every instance open ([The sidebar's instance tree](../desktop.md#the-sidebars-instance-tree)).
|
|
147
|
+
|
|
148
|
+
## Fixed
|
|
149
|
+
|
|
150
|
+
- **The getting-started skill reads a failed join from what ran.** Its last messaging check (step 9, item 5) no longer says a run left the root outside the team when no root was made. After the signup or the labelled join it says no root was made or recorded, and a team create that recorded no root is rerun unchanged. Before the person's join window opens, the agent lists the per-team roots and compares the list afterwards, so a root from an earlier join is not read as this one. It compares the team's label as the provider writes the folder name: lowercase, `_` and `.` as `-`. When the window shows no `E_SETUP_` code, the agent asks for the window's last line. The agent still never sees the join's output, never reruns it, and asks for no secret ([#1746](https://github.com/oats-project/oats/issues/1746)).
|
|
151
|
+
|
|
152
|
+
## Removed
|
|
153
|
+
|
|
154
|
+
- **Show only the current workspace.** The list of workspaces always shows every workspace: the toggle, its ⌥⇧⌘O / Ctrl+Alt+Shift+O (which reaches a terminal's program again) and its palette command are gone, and a choice saved for it is ignored.
|
|
155
|
+
- **The sidebar's settings cog, its Hide sidebar button and its brand mark.** Theme, font and keyboard shortcuts are in the command palette (**Theme: choose…**, **Font: choose…**, **Shortcuts: edit keyboard shortcuts…**) and on the foot's **?**; the sidebar still hides with ⌘B / Ctrl+Shift+B, the palette's **Sidebar: toggle (hide/show)** and **Show sidebar**.
|
package/docs/servers.md
CHANGED
|
@@ -478,6 +478,7 @@ schedule's spec still travel as arguments.
|
|
|
478
478
|
| `instance stop --plan\|--apply`, `retire --plan`, `retire --plan-revision … --idempotency-key …` | the instance's home | `lifecycle-plans` (`lifecycleApi: 1`) |
|
|
479
479
|
| `instance color` | the instance's home | `instance-color` |
|
|
480
480
|
| `instance background` | the instance's home | `instance-background` |
|
|
481
|
+
| `instance pin` | the instance's home | `instance-pin` |
|
|
481
482
|
| `instance same-work` | the instance's home | `instance-same-work` |
|
|
482
483
|
|
|
483
484
|
`instance suggest-name` and `instance upgrade` are never routed: `--server` is
|
|
@@ -576,8 +577,10 @@ The host runs the same argv, minus `--server <id>` (or `--server=<id>`;
|
|
|
576
577
|
after a `--` the argv is the provider's and is never read), as `oats <namespace>
|
|
577
578
|
<command> …` from the registered workspace directory: the kernel's
|
|
578
579
|
capability dispatch finds the deployment from its working directory, so no
|
|
579
|
-
`--dir` is added to the provider's argv. `--soul` and
|
|
580
|
-
through untouched
|
|
580
|
+
`--dir` is added to the provider's argv. `--soul` and other flags go
|
|
581
|
+
through untouched, except `--invite <token>` and `--invite=<token>`: routed
|
|
582
|
+
commands refuse both with `E_BAD_ARGS` before ssh runs. Use `--invite-stdin`
|
|
583
|
+
and pipe the token on stdin to avoid exposing it in process arguments. Stdin is forwarded as is and never read or logged here;
|
|
581
584
|
when stdin is a terminal nothing is forwarded and the host's stdin is
|
|
582
585
|
closed. The host's stdout, stderr and exit status are relayed; with
|
|
583
586
|
`--json` its envelope is relayed verbatim, and when nothing comes back this
|
|
@@ -646,7 +649,10 @@ way, through the kernel's own read of it, and a value that read refuses is
|
|
|
646
649
|
dropped ([`retire`](desktop-cli-api.md#row-retire)). `sameWork` (feature
|
|
647
650
|
`instance-same-work`, the instance does the same work as its parent) is
|
|
648
651
|
relayed only when the host's row has `sameWork: true`, and is absent
|
|
649
|
-
otherwise ([`sameWork`](desktop-cli-api.md#row-same-work)).
|
|
652
|
+
otherwise ([`sameWork`](desktop-cli-api.md#row-same-work)). `pinned` (feature
|
|
653
|
+
`instance-pin`, the instance is pinned at the top of its machine's list) is
|
|
654
|
+
relayed only when the host's row has exactly `pinned: true`, and is absent
|
|
655
|
+
otherwise ([`pinned`](desktop-cli-api.md#row-pinned)). A removed or edited registration keeps
|
|
650
656
|
its group from the saved routes. State is pulled on every call, from every
|
|
651
657
|
group at once: each probe has its own deadline, `--per-target` (default 20 s)
|
|
652
658
|
capped by `--budget` (default 45 s, the deadline of the whole answer), and a
|
|
@@ -483,6 +483,17 @@ instance with the flag on carries `sameWork: true` on its `oats status
|
|
|
483
483
|
remote relay are in
|
|
484
484
|
[desktop-cli-api.md](desktop-cli-api.md#same-work-as-the-parent-oats-instance-same-work).
|
|
485
485
|
|
|
486
|
+
`oats instance pin <instance> on|off` (feature `instance-pin`) pins an
|
|
487
|
+
instance at the top of its machine's list, or removes the pin, addressed as
|
|
488
|
+
`oats instance background` addresses it and routed with `--server`. The pin
|
|
489
|
+
is the home's own file, `.oats-pinned.json`, so it is shared: every client of
|
|
490
|
+
that machine (the Desktop, the TUI, another machine's routed view) reads it
|
|
491
|
+
from the `pinned: true` on the instance's row and lists it first. It survives
|
|
492
|
+
a restart, a stop and a start, a resume and `oats instance upgrade`, and a
|
|
493
|
+
retire removes it with the home. No spawn flag or `soul.yaml` key sets it.
|
|
494
|
+
The answer and the errors are in
|
|
495
|
+
[desktop-cli-api.md](desktop-cli-api.md#pinned-instances-oats-instance-pin).
|
|
496
|
+
|
|
486
497
|
`spawnOrigin` records the caller independently of these links. For new spawns
|
|
487
498
|
from OATS 0.64.0, it is `instance` when the caller's `OATS_INSTANCE` and/or
|
|
488
499
|
`OATS_INSTANCE_HOME` resolve consistently to an extant home in this deployment;
|
|
@@ -2348,5 +2359,7 @@ member repository's `souls/<name>` (`soul.yaml` + `AGENTS.md`) and run
|
|
|
2348
2359
|
|
|
2349
2360
|
Homes left by mechanisms earlier releases removed are reported once by
|
|
2350
2361
|
`oats status` and `oats doctor`: `legacy-local-agents` (a `local-agents/`
|
|
2351
|
-
directory) and `legacy-captured-home`.
|
|
2352
|
-
soul from the deployment.
|
|
2362
|
+
directory) and `legacy-captured-home`. Follow the reported cleanup remedy,
|
|
2363
|
+
then re-spawn the soul from the deployment. For captured homes, inspect and
|
|
2364
|
+
clean up external state first; without positive proof that no spawn hook
|
|
2365
|
+
ran, retirement needs `oats retire <instance> --force`.
|