@awebai/oats 0.69.18 → 0.69.20

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 (52) hide show
  1. package/bin/oats.mjs +2 -2
  2. package/docs/capabilities.md +27 -14
  3. package/docs/container.md +416 -43
  4. package/docs/design/2026-09-27-team-model-v2.md +2 -2
  5. package/docs/design/2026-09-28-automations-trust.md +1 -1
  6. package/docs/desktop-cli-api.md +52 -31
  7. package/docs/desktop.md +29 -6
  8. package/docs/execution-targets.md +32 -17
  9. package/docs/implementation.md +4 -3
  10. package/docs/integrations.md +2 -2
  11. package/docs/knowledge.md +5 -5
  12. package/docs/official-catalog.md +5 -5
  13. package/docs/packages.md +13 -13
  14. package/docs/release-lane.md +6 -4
  15. package/docs/release-notes/v0.69.19.md +172 -0
  16. package/docs/release-notes/v0.69.20.md +325 -0
  17. package/docs/servers.md +6 -4
  18. package/docs/souls-and-instances.md +37 -13
  19. package/docs/tui.md +8 -8
  20. package/docs/upgrading.md +17 -5
  21. package/docs/workspaces.md +13 -7
  22. package/injects/work-directory.md +27 -2
  23. package/injects/work-workspace.md +32 -6
  24. package/lib/core.mjs +33 -197
  25. package/lib/hook-outcome.mjs +6 -0
  26. package/lib/host-run.mjs +24 -19
  27. package/lib/instance-lifecycle.mjs +3 -1
  28. package/lib/instance-listing.mjs +3 -2
  29. package/lib/launch-prompt-fixtures/README.md +6 -0
  30. package/lib/retire-admission.mjs +215 -0
  31. package/lib/servers.mjs +3 -0
  32. package/lib/session-resume-contract.mjs +1 -1
  33. package/lib/session-resume.mjs +130 -47
  34. package/lib/session-seen.mjs +3 -3
  35. package/package-catalog.json +3 -3
  36. package/package.json +3 -1
  37. package/packages/client/attributed-human.mjs +13 -0
  38. package/packages/client/deployment-data.mjs +4 -0
  39. package/packages/client/deployment-panel.mjs +2 -0
  40. package/packages/client/instance-lifecycle.mjs +6 -4
  41. package/packages/client/instance-presentation.mjs +2 -2
  42. package/packages/client/instance-tree.mjs +18 -7
  43. package/packages/client/lifecycle-confirmation.mjs +4 -2
  44. package/packages/client/lifecycle-contract.mjs +11 -6
  45. package/packages/client/remote-roster.mjs +4 -0
  46. package/packages/record/README.md +15 -2
  47. package/packages/record/docs/capture-service.md +14 -0
  48. package/packages/record/lib/canonical.mjs +2 -70
  49. package/packages/record/lib/capture-aw-unit.mjs +14 -3
  50. package/packages/record/lib/capture-aw.mjs +11 -5
  51. package/packages/record/lib/capture-health.mjs +16 -5
  52. package/skills/oats-getting-started/SKILL.md +3 -3
@@ -0,0 +1,172 @@
1
+ # OATS 0.69.19
2
+
3
+ The official catalog pins oats.aweb 1.42.1, which makes retained seats safer
4
+ and shortens the always-loaded messaging instructions, and oats.framework
5
+ 1.25.2. Instances in `workspace` and `directory` mode can make extra trees of
6
+ their own for repository work. `oats host run` runs the resume sweep each
7
+ minute, and the sweep retries a refused start and counts a home's starts per
8
+ hour. The Desktop's sidebar lists instances newest first. oats.okf stays
9
+ 6.0.3.
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.aweb 1.42.1 (from 1.41.0) and oats.framework 1.25.2
17
+ (from 1.25.0). oats.okf stays 6.0.3. `oats sync` takes them; the two oats.aweb
18
+ steps below apply only where they match.
19
+ - **A retained seat reads its aweb service only from its own record.** If
20
+ you set `OATS_AWEB_URL` for a retained seat, record the server in the seat
21
+ with `aw workspace connect --service <server>`, run in the seat's parent
22
+ directory, then unset the variable. A seat whose `workspace.yaml` already
23
+ names its server is unchanged.
24
+ - **A non-boolean `identity.e2ee` or `identity.takeOver` is refused** at spawn
25
+ and start. `true`, `false` and the strings `"true"`/`"false"` are accepted,
26
+ and an empty value reads as unset. Set any other value to `true` or `false`.
27
+ - **Scripts that read `oats session resume --json`:** the row reason
28
+ `refused-this-boot` is gone. A refused start waiting for its next attempt
29
+ is `start-refused-retrying`, and `keeps-getting-lost` now means 3 starts in
30
+ the last hour (details under Changed). The Desktop doesn't depend on these
31
+ reasons.
32
+ - **Respawn instances** to take the shorter aweb text and the extra-trees
33
+ briefing of the `workspace` and `directory` modes: a running instance keeps
34
+ the text it was composed with.
35
+
36
+ ## Added
37
+
38
+ - **Team image acceptance in CI.** Pull requests now build the team agent image
39
+ from their exact head commit and run the existing container acceptance script
40
+ on an amd64 runner with a private Compose fixture and no inference credentials.
41
+ Release image publication is prepared after the OATS release, by digest with an
42
+ exact release retention tag. The run and release notes record the immutable
43
+ reference. Publication remains disabled pending the registry decision and
44
+ requires a stable OATS release tag of at least 0.69.18 plus a committed final
45
+ aw image pin of at least 1.36.59.
46
+
47
+ - Manual verification of an image built with its selected commit's own packed
48
+ kernel, with exact installed-file paths, sizes, modes and hashes checked
49
+ against HEAD. A separate proof compares the default installed payload with
50
+ and without the read-only build-context mount. Packed mode remains manual
51
+ until the compatible image baseline lands; publication stays disabled.
52
+ With the committed baseline, the packed job refuses; positive real
53
+ packed-image acceptance is **NOT RUN** until that compatible baseline lands.
54
+
55
+ ## Changed
56
+
57
+ - **The catalog pins oats.aweb 1.42.1** (from 1.41.0). 1.42.0 is never
58
+ pinned: a comment in it named the kernel's private module, which the mirror
59
+ check refuses. 1.42.1 requires OATS >=0.68.0, the aw floor stays 1.36.33,
60
+ and the tested aw is 1.36.58. Most of
61
+ the release is about retained seats: an atomic seat lock, a lock held on
62
+ another host refuses with its release, a killed or failed spawn never
63
+ deletes the standing identity's workspace, and a seat with no membership of
64
+ its team is refused before any effect. The captured-execution variables are
65
+ now ignored, with one warning each. The always-loaded messaging
66
+ instructions are shorter, and new spawns get the new text.
67
+
68
+ - **The Desktop's Add machine dialog gives an invented host as its example.**
69
+ The host field's placeholder now reads "ssh host alias, e.g. devbox"; it
70
+ named one deployment's own machine. Nothing else in the dialog changes.
71
+
72
+ - **The `directory` work mode teaches extra trees.** Its briefing granted
73
+ none, while the instance-boundary block says repository work happens "there,
74
+ or in the extra trees your mode block grants", and `oats worktree add`
75
+ already worked from a directory home. `./work` stays an owned directory
76
+ that never becomes a repository; repository work that needs a branch goes in
77
+ an extra tree of the instance's own, with the same "Extra trees" section as
78
+ the `workspace` briefing:
79
+ `oats worktree add --purpose <p> --branch <b> --base <remote-branch> --repo <repo>`.
80
+ `--repo` is always named: the home's recorded repository is configuration
81
+ context, the deployment directory by default, so `add` without it is
82
+ refused there (`E_CLONE_MISSING`). A directory instance's `TASK.md` says the
83
+ same ("Work in ./work; do repository work only in your extra trees.")
84
+ ([work modes](../souls-and-instances.md#directory--independent-execution)).
85
+ Existing homes keep the briefing they were composed with; a new spawn picks
86
+ this one up.
87
+
88
+ - **`oats.framework` 1.25.2: `oats.core` 2.13.2** (through 1.25.1).
89
+ `oats.core`'s `/oats-operate` says that `workspace`- and `directory`-mode
90
+ instances can make extra trees too: work that needs a branch goes in an
91
+ extra tree of the instance's own, made with `oats worktree add --repo
92
+ <repo>`. Member clones stay read-only, and a directory instance's `./work`
93
+ never becomes a repository.
94
+
95
+ No capability needs a newer OATS: `oats worktree add --repo` has worked
96
+ from those homes since OATS 0.49.0.
97
+
98
+ - **`oats host run` runs the resume sweep each minute, not only at its
99
+ start.** An agent whose session is lost while the host runs (its harness
100
+ crashed or was killed) is started again by the sweep of the next minute,
101
+ within the sweep's own bounds: at most 3 starts of a home in an hour, a
102
+ refused start retried with backoff, and a home given up after 3 such hours
103
+ in a row. Before, a container that stayed up never started a lost agent
104
+ again; only a restart of the container did.
105
+
106
+ A home the sweep started counts as seen running for that start. A home
107
+ that is lost again within the minute, before any read saw it running, is
108
+ therefore started again and counted, not left as `not-seen-recently`.
109
+
110
+ The sweep replaces the listing `oats host run` ran each minute, and records
111
+ what that listing recorded. A sweep that still runs at the next minute is
112
+ not run beside itself. Progress says a sweep only when its outcomes differ
113
+ from those of the sweep before. The answer's `sweep` is the first sweep's.
114
+ Stopping is unchanged: a sweep that runs gets the same 10 seconds, and the
115
+ admission fence stops its further starts.
116
+
117
+ - **`oats session resume` tries a refused start again, and counts a home's
118
+ starts per hour.** A start the sweep ran and that was refused (a launch
119
+ variable not set, no wake broker running yet) launched nothing and says how
120
+ the host was at that moment. It no longer answers the loss for good: the
121
+ sweep tries that home again no sooner than 1 minute later, doubling to 15
122
+ minutes at most, until the loss is 24 hours old. A home that keeps getting
123
+ lost is still started at most 3 times, now in an hour instead of in a boot,
124
+ and a sweep starts it again when the oldest of those starts is an hour old.
125
+ A home that uses up its starts 3 hours in a row is given up until a person
126
+ starts it.
127
+ Both the count and the delays are kept for one boot. On upgrade, a home's
128
+ count of starts for the current boot begins at zero once: the earlier
129
+ kernel's note holds no start times.
130
+
131
+ **Contract change for clients of `oats session resume --json`**
132
+ ([the machine sweep](../desktop-cli-api.md#the-machine-sweep-oats-session-resume)):
133
+ - the row reason `refused-this-boot` is no longer emitted. A refusal that
134
+ is waiting for its next attempt is `start-refused-retrying`, with the
135
+ refusal's `code` and `message`;
136
+ - `start-refused`, `start-refused-retrying` and `keeps-getting-lost` rows
137
+ carry `nextAttemptAt`, an ISO time (not on a host without a boot id,
138
+ where nothing is noted);
139
+ - `keeps-getting-lost` keeps its name and now means 3 starts in the last
140
+ hour, not in this boot. It is final only without `nextAttemptAt`: after
141
+ 3 such hours in a row;
142
+ - a refused start and `keeps-getting-lost` no longer make later sweeps
143
+ answer the home `not-seen-recently`.
144
+
145
+ - **The Desktop's sidebar lists instances newest first.** The instance tree
146
+ is in spawn order, newest on top, instead of by name, at every level: a
147
+ group of related instances by its first instance, the children under a
148
+ parent the same way. Spawning a child doesn't move its group, and starting
149
+ or stopping an instance still moves nothing. The TUI's list and the command
150
+ palette's never-focused rows follow the same order.
151
+
152
+ - Release image preparation installs the exact kernel version just published,
153
+ preserves unrelated committed lock entries and retains the generated inputs.
154
+ Acceptance verifies the installed version before registry login. Publication
155
+ remains disabled; its prepared path adds only the exact release retention tag,
156
+ refuses tag conflicts and records an immutable digest receipt with explicit
157
+ build/startup coverage and unrun agent and containment checks.
158
+
159
+ - **The `workspace` work mode teaches extra trees.** Its briefing no longer
160
+ lists worktrees among the Git operations it forbids, which contradicted the
161
+ instance-boundary block ("repository work happens there, or in the extra
162
+ trees your mode block grants"). Member clones stay read-only through
163
+ `./work`; work that needs a member's branch goes in an extra tree of the
164
+ instance's own, made with
165
+ `oats worktree add --purpose <p> --branch <b> --base <remote-branch> --repo <member>`,
166
+ which moves none of the clone's refs. `--repo` is always named in this mode:
167
+ the home's recorded repository is the deployment directory, so `add` without
168
+ it is refused (`E_CLONE_MISSING`). A workspace instance's `TASK.md` says the
169
+ same. What work an instance takes on stays its role's and its task's call
170
+ ([work modes](../souls-and-instances.md#workspace--cross-repo-coordinator)).
171
+ Existing homes keep the briefing they were composed with; a new spawn picks
172
+ this one up.
@@ -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.
package/docs/servers.md CHANGED
@@ -246,7 +246,7 @@ symlinks. Neither the caller's command nor stdin chooses a destination path.
246
246
  ## Connect a machine
247
247
 
248
248
  ```bash
249
- oats server connect altair-aweb --ssh altair --dir '~/acme' --install-oats
249
+ oats server connect devbox-aweb --ssh devbox --dir '~/acme' --install-oats
250
250
  ```
251
251
 
252
252
  Run from a deployment, `server connect` puts that deployment's workspace on
@@ -569,15 +569,17 @@ registration.
569
569
  **Capability commands.** Any capability command routes with `--server`:
570
570
 
571
571
  ```bash
572
- oats aweb setup --join aweb --invite-stdin --soul dev --server altair-aweb < invite.txt
572
+ oats aweb setup --join aweb --invite-stdin --soul dev --server devbox-aweb < invite.txt
573
573
  ```
574
574
 
575
575
  The host runs the same argv, minus `--server <id>` (or `--server=<id>`;
576
576
  after a `--` the argv is the provider's and is never read), as `oats <namespace>
577
577
  <command> …` from the registered workspace directory: the kernel's
578
578
  capability dispatch finds the deployment from its working directory, so no
579
- `--dir` is added to the provider's argv. `--soul` and every other flag go
580
- through untouched. Stdin is forwarded as is and never read or logged here;
579
+ `--dir` is added to the provider's argv. `--soul` and other flags go
580
+ through untouched, except `--invite <token>` and `--invite=<token>`: routed
581
+ commands refuse both with `E_BAD_ARGS` before ssh runs. Use `--invite-stdin`
582
+ 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
583
  when stdin is a terminal nothing is forwarded and the host's stdin is
582
584
  closed. The host's stdout, stderr and exit status are relayed; with
583
585
  `--json` its envelope is relayed verbatim, and when nothing comes back this
@@ -1841,8 +1841,9 @@ after the capability injects (`injects/instance-boundary.md`):
1841
1841
  target another one deliberately).
1842
1842
  - `<instance-home>/work` — the repository or workspace view — is where
1843
1843
  repository reading, editing, building, testing, git and commits happen, to the
1844
- extent the mode below permits. In `worktree` and `checkout` mode, the
1845
- instance's [extra trees](#extra-trees) in the home serve the same purpose.
1844
+ extent the mode below permits. In `worktree`, `checkout`, `workspace` and
1845
+ `directory` mode, the instance's [extra trees](#extra-trees) in the home
1846
+ serve the same purpose.
1846
1847
  - The home has no soul link: the composed `AGENTS.md` already carries the
1847
1848
  soul's instructions, and `instance.json` `soulDir` records the (read-only,
1848
1849
  per-commit) soul directory every hook and dispatched command receives as
@@ -2014,6 +2015,14 @@ without Git. `repo` (or `--repo`) supplies context only and may be an ordinary
2014
2015
  directory; without it, the deployment directory (where `oats-local.yaml` is) is
2015
2016
  used. No implicit fallback changes the other modes.
2016
2017
 
2018
+ Repository work that needs a branch — a change the instance's role and task
2019
+ call for, or a repository at the remote's current state — goes in an
2020
+ [extra tree](#extra-trees) of the instance's own, never in `work/` (which
2021
+ never becomes a repository) and never in the `repo` directory. An extra tree
2022
+ always names its repository (`--repo`): the recorded `repo` is context only,
2023
+ the deployment directory by default, so `oats worktree add` without `--repo`
2024
+ is refused when it is not a clone (`E_CLONE_MISSING`).
2025
+
2017
2026
  `--work-dir` and `--branch` are rejected. Canonical instructions, skill
2018
2027
  composition, provider trust and harness preflight still apply. Retirement preserves nonempty work in verified recovery storage beside the
2019
2028
  home (`workRecovery.path/work`) before deleting it, including files created by
@@ -2048,21 +2057,34 @@ where it works are decoupled.
2048
2057
 
2049
2058
  Rules:
2050
2059
 
2051
- - Read freely across member repos; **never edit or commit inside them** —
2052
- route changes to the owning repo's agents or the human.
2053
- - No git state operations in any member repo.
2060
+ - Read freely across member repos through `work/`; **never edit or commit
2061
+ inside the member clones** — others use them.
2062
+ - No Git state operations in any member clone (no branch switches, resets,
2063
+ pulls, stashes, or `git worktree` run by hand).
2064
+ - Work that needs a branch of a member — a change the instance's role and
2065
+ task call for, or a member at the remote's current state — goes in an
2066
+ [extra tree](#extra-trees) of the instance's own, which `oats worktree add`
2067
+ makes without moving any of the clone's refs. Otherwise route the change to
2068
+ the owning repo's agents or the human. The mode says where work happens;
2069
+ what work the instance takes on is its role's and its task's call.
2054
2070
  - Knowledge promotion follows the knowledge capability's own protocol, never
2055
2071
  direct edits through the workspace view.
2056
2072
 
2057
- The instance records no branch: the workspace is not a Git tree.
2073
+ The instance records no branch: the workspace is not a Git tree. For the same
2074
+ reason an extra tree always names its repository (`--repo`): the instance's
2075
+ recorded repository is the deployment directory.
2058
2076
 
2059
2077
  ### Extra trees
2060
2078
 
2061
- An instance in `worktree` or `checkout` mode can create extra trees: linked
2062
- Git worktrees in its home, beside `work/`. It does so when the work needs
2063
- another branch, or another repository of the deployment (one task that
2064
- touches several repositories). The `worktree` and `checkout` briefings teach
2065
- it; the `workspace`, `directory` and `attached` briefings do not.
2079
+ An instance in `worktree`, `checkout`, `workspace` or `directory` mode can
2080
+ create extra trees: linked Git worktrees in its home, beside `work/`. It does
2081
+ so when the work needs another branch, or another repository of the deployment
2082
+ (one task that touches several repositories); in `workspace` mode, whenever
2083
+ work needs a branch of a member, since `work/` is read-only; in `directory`
2084
+ mode, whenever work needs a branch at all, since `work/` is not a Git tree.
2085
+ The `worktree`, `checkout`, `workspace` and `directory` briefings teach it
2086
+ (the `workspace` and `directory` ones with `--repo` always, in one shared
2087
+ section); the `attached` briefing does not.
2066
2088
 
2067
2089
  ```text
2068
2090
  oats worktree add --purpose <p> --branch <b> --base <remote-branch>
@@ -2326,5 +2348,7 @@ member repository's `souls/<name>` (`soul.yaml` + `AGENTS.md`) and run
2326
2348
 
2327
2349
  Homes left by mechanisms earlier releases removed are reported once by
2328
2350
  `oats status` and `oats doctor`: `legacy-local-agents` (a `local-agents/`
2329
- directory) and `legacy-captured-home`. Retire such instances and re-spawn the
2330
- soul from the deployment.
2351
+ directory) and `legacy-captured-home`. Follow the reported cleanup remedy,
2352
+ then re-spawn the soul from the deployment. For captured homes, inspect and
2353
+ clean up external state first; without positive proof that no spawn hook
2354
+ ran, retirement needs `oats retire <instance> --force`.