@awebai/oats 0.54.0 → 0.55.1

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 (35) hide show
  1. package/bin/oats.mjs +5 -5
  2. package/docs/desktop-cli-api.md +15 -4
  3. package/docs/integrations.md +2 -2
  4. package/docs/knowledge.md +14 -2
  5. package/docs/official-catalog.md +4 -4
  6. package/docs/packages.md +10 -10
  7. package/docs/release-notes/v0.55.0.md +158 -0
  8. package/docs/release-notes/v0.55.1.md +45 -0
  9. package/docs/servers.md +13 -3
  10. package/docs/workspaces.md +1 -1
  11. package/lib/servers.mjs +82 -34
  12. package/package-catalog.json +3 -3
  13. package/package.json +1 -1
  14. package/packages/client/cli-locator.mjs +2 -2
  15. package/packages/client/workspace-views.mjs +4 -3
  16. package/packages/record/README.md +58 -13
  17. package/packages/record/bin/capture.mjs +107 -53
  18. package/packages/record/bin/recall.mjs +3 -2
  19. package/packages/record/docs/capture-service.md +193 -0
  20. package/packages/record/docs/capture-status.schema.json +100 -0
  21. package/packages/record/lib/capture-aw.mjs +96 -94
  22. package/packages/record/lib/capture-cc.mjs +109 -187
  23. package/packages/record/lib/capture-db-reader.mjs +39 -0
  24. package/packages/record/lib/capture-issues.mjs +64 -0
  25. package/packages/record/lib/capture-scratch.mjs +111 -0
  26. package/packages/record/lib/capture-state.mjs +105 -0
  27. package/packages/record/lib/derived-state.mjs +60 -0
  28. package/packages/record/lib/formats.mjs +31 -31
  29. package/packages/record/lib/index-db.mjs +74 -34
  30. package/packages/record/lib/receipt-summary.mjs +62 -0
  31. package/packages/record/lib/session-snapshot.mjs +56 -1
  32. package/packages/record/lib/sqlite-rows.mjs +14 -0
  33. package/packages/record/lib/store.mjs +122 -43
  34. package/packages/record/lib/transcript-prefix.mjs +40 -0
  35. package/skills/oats-getting-started/SKILL.md +1 -1
package/bin/oats.mjs CHANGED
@@ -4061,7 +4061,7 @@ async function experimentalCmd() {
4061
4061
  /** `oats server add|list|remove|check`. A registration is where and how:
4062
4062
  * an OpenSSH host alias, the remote workspace, the remote oats path. Keys
4063
4063
  * and passwords never enter it; ssh owns those. */
4064
- function serverCmd() {
4064
+ async function serverCmd() {
4065
4065
  const bail = (code, msg, details) => (JSON_MODE ? jsonFail(code, msg, details) : die(msg));
4066
4066
  const sub = args[1];
4067
4067
  const usage = "usage: oats server add <id> --ssh <host-alias> --workspace </abs/path> [--oats <path>] [--path <dir:dir>] [--label <text>] [--replace] | connect <id> --ssh <host-alias> [--workspace-ref <ref>] [--dir </abs/path or ~/path on the host>] [--oats <path>] [--path <dir:dir>] [--label <text>] [--install-oats] [--replace] | list [--workspace-ref <ref>] | remove <id> | check <id> | roster [--server <id>] | forget <id> --instance <name> [--json]";
@@ -4083,12 +4083,12 @@ function serverCmd() {
4083
4083
  }
4084
4084
  if (sub === "roster") {
4085
4085
  // The remote roster for the Desktop and operators: grouped by saved route
4086
- // target, one bounded status pull per target, saved routes as the action
4086
+ // target, one bounded status pull per target, all at once, saved routes as the action
4087
4087
  // authority. --server narrows to one registry id.
4088
4088
  const only = flag("server") === true ? bail("E_BAD_ARGS", "--server needs a registered server id") : flag("server");
4089
4089
  const ms = (name) => { const v = flag(name); if (v === undefined) return undefined; const n = Number(v); if (!Number.isInteger(n) || n < 1000) bail("E_BAD_ARGS", `--${name} takes whole milliseconds, at least 1000`); return n; };
4090
4090
  let out;
4091
- try { out = rosterGroups({ server: only, io: { budgetMs: ms("budget"), perTargetTimeoutMs: ms("per-target") } }); } catch (e) { bail(e.code || "E_SERVERS_UNREADABLE", e.message); }
4091
+ try { out = await rosterGroups({ server: only, io: { budgetMs: ms("budget"), perTargetTimeoutMs: ms("per-target") } }); } catch (e) { bail(e.code || "E_SERVERS_UNREADABLE", e.message); }
4092
4092
  if (JSON_MODE) { jsonOk(out); return; }
4093
4093
  if (!out.groups.length) { console.log("no remote groups: no registrations and no saved routes"); return; }
4094
4094
  for (const g of out.groups) {
@@ -4097,7 +4097,7 @@ function serverCmd() {
4097
4097
  for (const i of g.instances) console.log(` • ${i.instance} ${i.missingRemotely ? "GONE on the host (saved route is stale: oats server forget)" : i.running === true ? "RUNNING" : i.running === false ? "idle" : "unknown"}${i.retirePending ? " RETIRING" : ""}${i.rollbackIncomplete ? " QUARANTINED" : ""}${i.savedRoute ? "" : " (observed only, no saved route)"}${i.runtimeError ? ` ${i.runtimeError}` : ""}`);
4098
4098
  for (const f of g.retireFailures || []) console.log(` ! deferred retirement of ${f.instance} (${f.agent}) FAILED there${f.error?.message ? `: ${f.error.message}` : ""}${f.retry ? ` — retry on the host: ${f.retry}` : ""}`);
4099
4099
  }
4100
- console.log(` bounds: ${out.bounds.perTargetTimeoutMs} ms per target within ${out.bounds.budgetMs} ms, ${out.bounds.elapsedMs} ms used${out.bounds.skipped ? `, ${out.bounds.skipped} target(s) not reached` : ""}`);
4100
+ console.log(` bounds: ${out.bounds.perTargetTimeoutMs} ms per target within ${out.bounds.budgetMs} ms, ${out.bounds.elapsedMs} ms used`);
4101
4101
  return;
4102
4102
  }
4103
4103
  let servers;
@@ -4556,7 +4556,7 @@ else {
4556
4556
  const wantsHelp = args.slice(1).some((a) => a === "--help" || a === "-h");
4557
4557
  if (cmd && KERNEL_COMMANDS.has(cmd) && wantsHelp) { if (JSON_MODE) { jsonOk({ command: cmd, usage: usageLinesFor(cmd) }); process.exit(0); } usageFor(cmd); process.exit(0); }
4558
4558
  if (flag("server") !== undefined && ROUTED_COMMANDS.has(cmd)) await serverRouteCmd();
4559
- else if (cmd === "server") serverCmd();
4559
+ else if (cmd === "server") await serverCmd();
4560
4560
  else if (cmd === "inspect") await inspectCmd();
4561
4561
  else if (cmd === "operation") await operationCmd();
4562
4562
  else if (cmd === "launch-config") await launchConfigCmd();
@@ -2827,9 +2827,14 @@ route target:
2827
2827
  ```
2828
2828
 
2829
2829
  - **`probe`**: `{ok: true, features}` when the host's `status --json` was
2830
- pulled, else `{ok: false, error: {code, message}}` (ssh failed, the host
2831
- answered `ok: false`, or `E_ROSTER_BUDGET`: the roster's budget ran out
2832
- before this target), with no `features` key.
2830
+ pulled, else `{ok: false, error: {code, message}}` (ssh failed or timed
2831
+ out, `E_SSH`; or the host answered `ok: false`), with no `features` key.
2832
+ Every group is probed at once, each within its own deadline, so a group's
2833
+ `probe` depends only on its own host: one that does not answer in time is
2834
+ `E_SSH` with `ssh to <host> timed out: no answer within <n> s`, and every
2835
+ other group is unaffected. Before 0.55.0 the probes ran one after another
2836
+ against the total budget, and a group the budget did not reach was
2837
+ `E_ROSTER_BUDGET`; that code is no longer answered.
2833
2838
  - **`probe.features`** (feature `server-probe-features`, OATS 0.49.0): the
2834
2839
  host's kernel features, relayed from the top-level `features` of its
2835
2840
  [`status --json`](#the-roster-oats-status---json), never probed: the roster
@@ -2845,7 +2850,7 @@ route target:
2845
2850
  - **`workspace`** (feature `workspace-identity`, OATS 0.36.0): the host's
2846
2851
  own `status --json` [`workspace` object](#workspace-identity-feature-workspace-identity-oats-0360),
2847
2852
  relayed verbatim, or `null` when the host reports none (a deployment
2848
- without `oats-local.yaml`, or a failed or skipped probe). A host before
2853
+ without `oats-local.yaml`, or a failed probe). A host before
2849
2854
  0.36.0 answers the reachability-only object (`{reachable, code?, reason?,
2850
2855
  message?}`) with no identity fields, so the identity is there only when
2851
2856
  the object has a `key` field (which a 0.36.0 host always sends, `null` for
@@ -2884,6 +2889,12 @@ route target:
2884
2889
  - `running` is `null` when unknown; `backend` is `tmux` for a row with a tmux
2885
2890
  target, else `null`; `tmux`, `sessionTarget` (the recorded target of a home
2886
2891
  a Herdr-era kernel opened) and `runtimeError` are as the host reports them.
2892
+ - **`bounds`**: `{budgetMs, perTargetTimeoutMs, elapsedMs}`. Each group's
2893
+ probe may take the smaller of `perTargetTimeoutMs` (`--per-target`,
2894
+ default 20 s) and `budgetMs` (`--budget`, default 45 s, the deadline of the
2895
+ whole answer); `elapsedMs` is what the answer took, about the slowest
2896
+ group's probe. Before 0.55.0 `bounds` also carried `skipped`, the number of
2897
+ groups the budget did not reach; it is gone with `E_ROSTER_BUDGET`.
2887
2898
 
2888
2899
  <a id="servers-per-workspace"></a>
2889
2900
  ### Servers per workspace (feature `servers-per-workspace`)
@@ -40,8 +40,8 @@ arrives from.
40
40
  ```yaml
41
41
  # oats-workspace.yaml: one default per slot, for every soul
42
42
  packages:
43
- oats.okf: v5.0.3
44
- oats.aweb: v1.27.1
43
+ oats.okf: v5.0.5
44
+ oats.aweb: v1.27.3
45
45
  oats.linear: v1.0.1
46
46
  oats.jira: v1.0.1
47
47
  defaults:
package/docs/knowledge.md CHANGED
@@ -6,7 +6,7 @@ kernel owns slot selection, composition and command dispatch; the capability
6
6
  owns its knowledge format, instructions and promotion procedure. The model is
7
7
  in [Knowledge, instances and evolving expertise](knowledge-theory.md).
8
8
 
9
- This is the operator guide for **oats.okf 5.0.3**. Provider implementation and
9
+ This is the operator guide for **oats.okf 5.0.5**. Provider implementation and
10
10
  recovery details belong to the [oats-okf README](https://github.com/awebai/oats-okf).
11
11
 
12
12
  | Surface | What it holds |
@@ -23,7 +23,7 @@ recovery details belong to the [oats-okf README](https://github.com/awebai/oats-
23
23
  ```yaml
24
24
  # oats-workspace.yaml (excerpt)
25
25
  packages:
26
- oats.okf: v5.0.3
26
+ oats.okf: v5.0.5
27
27
  defaults:
28
28
  knowledge: { oats.okf: { from: package } }
29
29
  stores:
@@ -161,6 +161,18 @@ changes the soul declaration. `knowledge: none` removes the layer entirely.
161
161
  automatic transcript capture, source registry, worker cursor or retire
162
162
  harvest. An unrelated harvester can outlive its source; this is a
163
163
  lifecycle property, not proof that missing source authority can be ignored.
164
+
165
+ One proposal per checkpoint, each concept a claim of its own in it, and
166
+ claims only for the nodes the source soul owns; a lesson for a node it only
167
+ reads goes in one line in the instance's hand-back, for that node's owner.
168
+ One harvester at a time, per instance (oats.okf 5.0.5): the source notes the
169
+ harvester's instance name and spawns no other while `oats status` still
170
+ lists it, since a harvester retires once it has handed over. What it learns
171
+ meanwhile goes into its next proposal; an instance that hands back with one
172
+ still listed names it and the claims still waiting. A harvester retained
173
+ after a publication failure stays listed, so it holds back its source's
174
+ later proposals: once that failure is dealt with, the operator retires it
175
+ (`oats retire <harvester>`).
164
176
  3. **Judge and submit.** The harvester checks recorded source configuration,
165
177
  accepted knowledge and open/recent harvest PRs. It reads named backing
166
178
  notes, edits only owned nodes in its own Git checkout, validates the
@@ -10,9 +10,9 @@ or workspace membership alone does not make a package official.
10
10
  | package | release | capabilities | package souls |
11
11
  |---|---|---|---|
12
12
  | `oats.framework` | `oats-framework/v1.10.0` (this repository) | `oats.core`, `oats.setup`, `oats.support`, `oats.knowledge-theory` | `knowledge-theory-expert` |
13
- | `oats.okf` | `v5.0.3` | `oats.okf` (knowledge), `oats.okf-harvest`, `oats.okf-maintenance` | `knowledge-harvester`, `knowledge-maintainer` |
14
- | `oats.aweb` | `v1.27.1` | `oats.aweb` (messaging) | |
15
- | `oats.engineering` | `v1.9.1` | `oats.engineering-expert`, `oats.developer`, `oats.code-review`, `oats.maintainer` | `code-reviewer` |
13
+ | `oats.okf` | `v5.0.5` | `oats.okf` (knowledge), `oats.okf-harvest`, `oats.okf-maintenance` | `knowledge-harvester`, `knowledge-maintainer` |
14
+ | `oats.aweb` | `v1.27.3` | `oats.aweb` (messaging) | |
15
+ | `oats.engineering` | `v1.10.0` | `oats.engineering-expert`, `oats.developer`, `oats.code-review`, `oats.maintainer` | `code-reviewer` |
16
16
  | `oats.authoring` | `v1.0.3` | `oats.authoring` | |
17
17
  | `oats.cloning` | `v1.0.1` | `oats.cloning` | `cloner` |
18
18
  | `oats.jira` | `v1.0.1` | `oats.jira` (tasks) | |
@@ -29,7 +29,7 @@ no lock and adds nothing to an existing workspace.
29
29
  ## Find and use packages
30
30
 
31
31
  - A workspace pins an official package by **bare version** in its
32
- `packages:` map (`oats.okf: v5.0.3`); `oats sync` resolves it through the
32
+ `packages:` map (`oats.okf: v5.0.5`); `oats sync` resolves it through the
33
33
  catalog to an exact commit, fetches it, verifies its integrity and locks it.
34
34
  A package outside the catalog is written `git:<repo>@<ref>`. Pinning does
35
35
  not join a team or adopt the publisher's workspace. See
package/docs/packages.md CHANGED
@@ -44,14 +44,14 @@ whole organisation:
44
44
 
45
45
  ```yaml
46
46
  packages:
47
- oats.okf: v5.0.3 # bare version → the official catalog
47
+ oats.okf: v5.0.5 # bare version → the official catalog
48
48
  acme.tools: git:github.com/acme/tools@v0.4.0 # direct ref: git:<repo>@<tag or full OID>
49
49
  ```
50
50
 
51
- - **Bare version** (`v5.0.3`, `5.0.3`, `1.0.0-rc.1`): the id is looked up in
51
+ - **Bare version** (`v5.0.5`, `5.0.5`, `1.0.0-rc.1`): the id is looked up in
52
52
  the official catalog — `package-catalog.json` in the `oats` repo, or the file
53
53
  named by `OATS_PACKAGE_CATALOG` — which supplies the repo url, the tag
54
- convention (`v5.0.3` or `oats-framework/v1.10.0`) and the payload path. An id
54
+ convention (`v5.0.5` or `oats-framework/v1.10.0`) and the payload path. An id
55
55
  the catalog does not know is `E_PACKAGE_MISSING` ("use `git:<repo>@<ref>` for
56
56
  a package outside the catalog"). The catalog is the reviewed official list
57
57
  ([official-catalog.md](official-catalog.md)) and the only way a
@@ -75,8 +75,8 @@ members:
75
75
  - git:github.com/acme/platform
76
76
  packages:
77
77
  oats.framework: v1.10.0
78
- oats.okf: v5.0.3
79
- oats.aweb: v1.27.1
78
+ oats.okf: v5.0.5
79
+ oats.aweb: v1.27.3
80
80
  teams:
81
81
  platform: { team: "platform:acme.aweb.ai", description: Platform engineering }
82
82
  defaults:
@@ -105,7 +105,7 @@ decision recorded in the lock.
105
105
  $ oats sync
106
106
  workspace acme (github.com/acme/agents @ 3f2a9c1e)
107
107
  members agents ✓↔ (@ 3f2a9c1e) platform ✓↔ (@ 77c0a1b2) billing ✗ (no-backlink)
108
- packages acme.tools 0.4.0 ✓ (@ 47f4b816) oats.okf 5.0.3 ✓ (@ e687a94a)
108
+ packages acme.tools 0.4.0 ✓ (@ 47f4b816) oats.okf 5.0.5 ✓ (@ 73b85020)
109
109
  changed acme.tools — → 0.4.0 (@ 47f4b816)
110
110
  souls 9 discovered (6 members, 1 external, 2 package, 0 disabled here) · 0 private capabilities
111
111
  teams platform (shared) · this deployment's: oats teams
@@ -134,7 +134,7 @@ Declaring a package in the workspace's `packages:` is the trust decision
134
134
  ## `oats package add | remove`
135
135
 
136
136
  ```bash
137
- oats package add oats.aweb v1.27.1 # a catalog version
137
+ oats package add oats.aweb v1.27.3 # a catalog version
138
138
  oats package add acme.tools git:github.com/acme/tools@v0.4.0
139
139
  oats package remove acme.tools
140
140
  ```
@@ -160,8 +160,8 @@ same workspace commit hold identical locks.
160
160
  "source": "catalog:oats.okf",
161
161
  "url": "https://github.com/awebai/oats-okf.git",
162
162
  "path": "oats-package",
163
- "version": "5.0.3",
164
- "commit": "e687a94a40494521a671979dd168e3d62b11bcde",
163
+ "version": "5.0.5",
164
+ "commit": "73b85020e52b8584cb15f153a39712f900e69918",
165
165
  "integrity": "sha256-…",
166
166
  "capabilities": ["oats.okf", "oats.okf-harvest", "oats.okf-maintenance"]
167
167
  },
@@ -352,7 +352,7 @@ A soul that names one of the package's capabilities with
352
352
  {
353
353
  "policy": "docs/official-catalog.md",
354
354
  "packages": {
355
- "oats.okf": { "url": "https://github.com/awebai/oats-okf.git", "ref": "v5.0.3", "path": "oats-package" },
355
+ "oats.okf": { "url": "https://github.com/awebai/oats-okf.git", "ref": "v5.0.5", "path": "oats-package" },
356
356
  "oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.10.0", "path": "oats-package" }
357
357
  }
358
358
  }
@@ -0,0 +1,158 @@
1
+ # OATS 0.55.0
2
+
3
+ 2026-10-14
4
+
5
+ ## Upgrade
6
+
7
+ - **Install the Desktop first and the CLI second,** as
8
+ [Upgrading](../upgrading.md) says: a 0.54.0 Desktop refuses a 0.55.0 CLI.
9
+
10
+ - **The first capture after the upgrade takes longer.** It reconciles the
11
+ existing journals, resets the search index and rebuilds it from them, in
12
+ one synchronous pass that can take minutes on a large record; later passes
13
+ read only what is new. See Fixed
14
+ ([#1108](https://github.com/awebai/oats/issues/1108)).
15
+
16
+ - **A script that reads `oats server roster --json`** no longer sees
17
+ `E_ROSTER_BUDGET` or `bounds.skipped`: every server is probed, and one
18
+ that does not answer reports its own `E_SSH` timeout. See Removed
19
+ ([#1117](https://github.com/awebai/oats/issues/1117)).
20
+
21
+ - **The official catalog's versions in this release** are oats.framework
22
+ 1.10.0, oats.okf 5.0.5, oats.aweb 1.27.2 and oats.engineering 1.10.0: see
23
+ Provider updates. Pin what your workspace uses, then run `oats sync`.
24
+ Running instances keep what they were spawned with; new spawns get the new
25
+ versions, so a standing maintainer gets oats.engineering 1.10.0's lane
26
+ rules only by being re-spawned. The same holds for oats.okf 5.0.5: an
27
+ instance spawned before the pin keeps its old frozen-remote guard (and
28
+ still fails with `E_OWNER` on a host that rewrites Git URLs) and its old
29
+ proposal brief until it is re-spawned.
30
+
31
+ ## Changed
32
+
33
+ - **The Desktop accepts OATS CLIs `>=0.25.8 <0.56.0`.** The compatibility band
34
+ admits 0.55. Upgrade the CLI and the Desktop together: a 0.54.0 Desktop
35
+ refuses a 0.55.0 CLI. No new gate on the band. `oats tui` runs the kernel it
36
+ ships with and is held to the same band.
37
+
38
+ ## Fixed
39
+
40
+ - Capture streams transcript content, stores per-input cursors and journal IDs on
41
+ disk, and indexes only new journal bytes in bounded transactions ([#1108](https://github.com/awebai/oats/issues/1108)).
42
+ Background input logs share an append-only assumption: an edit to an old
43
+ aweb-log line is no longer picked up merely because the log grows. Use
44
+ `capture --reset-cursors [--source aw|cc|pi|codex]` to request reprocessing.
45
+ Detected native-transcript prefix changes are set aside before appending, to
46
+ preserve v0.53.0 downgrade/re-upgrade compatibility. Restore the prefix and
47
+ use `capture --retry-set-aside`, or exclude the source through the existing
48
+ ignore list (which also excludes its later turns). `capture --health` reports
49
+ these inputs. This changes capture algorithms; it introduces no service
50
+ schedule, record-size policy, or bounded-runner guarantee. Content buffers and
51
+ caches are bounded apart from the largest record; sorted path/root metadata
52
+ and explicit receipt inventories can still grow with input counts. The first
53
+ capture after upgrade reconciles existing journals and rebuilds the index,
54
+ with substantial per-input/per-stream synchronous commit cost still unresolved.
55
+ Refused aweb entries are counted and consumed; reset source cursors to retry
56
+ them. Snapshot and receipt scratch stays on the record-root volume, with
57
+ conservative cleanup of proven abandoned allocations under the capture lock.
58
+
59
+ - Capture health reads current set-aside issues, including direct library calls,
60
+ while command snapshots retain their historical run fields. Reading an existing
61
+ capture database requires read-only SQLite support (Node 22.12+/23.2+; prefer
62
+ 22.13+ on 22.x without an experimental flag). Unsupported runtimes, schemas,
63
+ WAL databases and unavailable readers fail closed; normal capture's runtime
64
+ floor is unchanged.
65
+
66
+ - **A server that can't be reached no longer hides the others.** The remote
67
+ roster (`oats server roster`, the Desktop's view of other machines) probes
68
+ every registered server at once, each within its own deadline. A server
69
+ that is switched off now costs only its own entry, which shows that it
70
+ timed out (`E_SSH`, `ssh to <host> timed out: no answer within <n> s`), and
71
+ the servers registered after it are read as usual. Before, the probes ran
72
+ one after another against one 45 s budget. Four registrations on one
73
+ offline host could use the budget up, and the servers after them were
74
+ never asked ([#1117](https://github.com/awebai/oats/issues/1117)).
75
+ - **Retry on a remote window reads the servers again.** In the Desktop, the
76
+ roster's **Retry** on a window with a deployment on another machine now
77
+ reads the servers at once, or waits for the read already running, before it
78
+ shows the roster. Before, it showed the last read's result until the next
79
+ background read, 10 s later
80
+ ([#1117](https://github.com/awebai/oats/issues/1117)).
81
+
82
+ ## Removed
83
+
84
+ - **`E_ROSTER_BUDGET` and `bounds.skipped`** in `oats server roster --json`.
85
+ Every group is probed, so no group is reported as not reached any more, and
86
+ `bounds` is `{budgetMs, perTargetTimeoutMs, elapsedMs}`. `--budget` stays,
87
+ as the deadline of the whole answer, which caps each probe's `--per-target`
88
+ allowance
89
+ ([the roster](../desktop-cli-api.md#the-remote-roster-oats-server-roster---json)).
90
+
91
+ ## Provider updates
92
+
93
+ - **oats.okf 5.0.5** (from 5.0.3; 5.0.4 is included).
94
+ - **A host's Git URL rewriting no longer breaks Git bases**
95
+ ([oats-okf#76](https://github.com/awebai/oats-okf/issues/76), 5.0.4). A
96
+ host whose global or system Git config routes a bound repository through
97
+ `url.<base>.insteadOf` or `pushInsteadOf` (a deploy key on an ssh alias,
98
+ for example) failed every okf call with `E_OWNER`. The frozen-remote
99
+ guard now resolves the binding's `repository` with the host's own
100
+ rewrites and compares that with the clone's fetch and push URLs; the
101
+ binding stays as written. A rewrite in the clone's own config, a changed
102
+ origin or a `pushurl` is still refused, and URLs compare byte for byte.
103
+ - **One harvester at a time** (5.0.5). A working instance writes one
104
+ proposal per checkpoint, with claims only for the nodes its soul owns,
105
+ and spawns one knowledge harvester at a time, none while `oats status`
106
+ still lists its last one ([the flow](../knowledge.md)). Instruction text
107
+ only; it reaches instances spawned after the pin.
108
+ - The official catalog, the reference workspace and the generated mirrors
109
+ take published `v5.0.5` at `73b85020e52b8584cb15f153a39712f900e69918`.
110
+ Compatibility remains OATS 0.29.0 or later.
111
+ - **oats.aweb 1.27.2:** the `/oats-aweb` skill's etiquette points to
112
+ `/oats-token-saving` (oats.core 2.6.0, in OATS 0.54.0) for whether to send,
113
+ to whom and how long, and keeps how to send
114
+ ([#1103](https://github.com/awebai/oats/issues/1103)). Instruction text
115
+ only; both floors are unchanged (OATS 0.52.0, aw 1.36.33). The catalog,
116
+ the reference workspace and `mirrors/oats-aweb` take published `v1.27.2`
117
+ at `f82cebe299562b38188f3373fa09a89b50d5f868`; the mirror's tree equals
118
+ the tag's.
119
+ - **oats.engineering 1.10.0: maintainers work in lanes**
120
+ ([#1103](https://github.com/awebai/oats/issues/1103),
121
+ [oats-engineering#14](https://github.com/awebai/oats-engineering/pull/14)).
122
+ The official catalog, the reference workspace and the generated mirrors
123
+ (`mirrors/oats-developer`, `mirrors/oats-code-review`,
124
+ `mirrors/oats-engineering-expert`, `mirrors/oats-maintainer`) take published
125
+ `v1.10.0` at `944470be71a96299ae4a1cfb7df0fba94a592899`; each mirror's tree
126
+ equals the tag's. Instruction text only: no skill is added or removed, and
127
+ the requirement is unchanged (OATS 0.30.0 or later). `oats.maintainer` and
128
+ `oats.engineering-expert` change; the other two capabilities only change
129
+ version. What changes:
130
+ - **Each maintainer holds a lane.** The peers' agreement becomes a written
131
+ lane map: what each lane covers, its maintainer and its second reader,
132
+ the label a PR shows its lane with, the hold label, and who owns the next
133
+ release. A maintainer's state file holds its own lane only; the forge is
134
+ the one copy of a PR's state.
135
+ - **Every PR gets one second reader, asked once,** at the head the lane's
136
+ maintainer approved. This replaces every peer reviewing every PR and
137
+ re-binding its verdict at every head.
138
+ - **Intake no longer sweeps on every wake:** a full sweep at session start,
139
+ after a compaction and at least weekly; on a wake, the event alone.
140
+ - **Peers message each other for five things** (a second read, a hold that
141
+ must stop work in flight, the release plan, a lane changing hands, a
142
+ request that belongs to the peer's lane), and send no notice before or
143
+ after a merge or a tag. A hold is a label on the forge, and the merge step
144
+ reads it.
145
+ - **The merging maintainer brings a branch up to date itself;** the verdicts
146
+ carry when the PR's own change is unchanged and CI is green. When the
147
+ default branch moved since CI ran, it runs the affected test files on a
148
+ trial merge first.
149
+ - **Experts hand over to one maintainer,** the one whose lane the work is
150
+ in, and leave the branch alone after the hand-over.
151
+ - **To adopt it:** peer maintainers rewrite their agreement as a lane map
152
+ (`/cross-review-peer`), create the lane labels and the hold label, and
153
+ drop each other's PRs from their state files. A maintainer alone has
154
+ nothing to do. Pin `oats.engineering: v1.10.0` and run `oats sync`.
155
+ Running instances keep what they were spawned with; new spawns pick
156
+ 1.10.0 up after `oats sync`. A standing maintainer gets the new rules
157
+ only by being re-spawned, not by a sync or a session restart: hand its
158
+ lane over first (`/cross-review-peer`, "A lane changes hands").
@@ -0,0 +1,45 @@
1
+ # OATS 0.55.1
2
+
3
+ 2026-10-14
4
+
5
+ A patch release: the oats.aweb 1.27.3 pin, and one fix in the record's `recall --show`.
6
+
7
+ ## Upgrade
8
+
9
+ - **Either order of Desktop and CLI works:** a 0.55.0 Desktop accepts a
10
+ 0.55.1 CLI, and the other way round.
11
+
12
+ - **Pin `oats.aweb: v1.27.3` in your workspace, then run `oats sync`.** The
13
+ catalog in this release names it. On 1.27.2, readiness reports
14
+ `unavailable` for every home that the host wake broker serves (Codex,
15
+ `delivery: session`, joined teams with `receive: native`) while delivery
16
+ works. Running instances keep the provider they were spawned with. Such an
17
+ instance reads `unavailable` until it is re-spawned; spawns after the sync
18
+ get 1.27.3. See Provider updates.
19
+
20
+ ## Fixed
21
+
22
+ - `oats recall --show` now refuses session turns hidden by their author's
23
+ tombstone, including claims in another stream. It reports the turn as
24
+ tombstoned with exit status 1 and emits no payload. Record-owner authority
25
+ resolution and index authority changes remain separate work under
26
+ [#1125](https://github.com/awebai/oats/issues/1125)
27
+ ([#1127](https://github.com/awebai/oats/pull/1127)).
28
+
29
+ ## Provider updates
30
+
31
+ - **oats.aweb 1.27.3:** fixes false `wake-status-stale` / `unavailable`
32
+ readiness on Codex, `delivery: session`, and joined-team broker routes
33
+ ([oats-aweb#116](https://github.com/awebai/oats-aweb/issues/116),
34
+ [provider fix](https://github.com/awebai/oats-aweb/pull/117)). Broker
35
+ timestamps are judged against a clock read after `aw wake status` returns,
36
+ not the readiness phase's start. No skew allowance is added: invalid and
37
+ genuinely future timestamps still fail, and inspection ordering and
38
+ observation-age warnings remain intact. The catalog, reference workspace,
39
+ docs and generated mirror now take published `v1.27.3`.
40
+ Both floors remain OATS >=0.52.0 and aw >=1.36.33; this fix needs no new aw
41
+ upgrade or service restart. Keep the existing upgrade order: meet the
42
+ kernel/aw floors (restart custody services and the wake daemon after an aw
43
+ upgrade), update the provider pin, then `oats sync`. New compositions take
44
+ the fixed provider; existing homes keep their captured module bytes.
45
+ Readiness does not prove actual message delivery.
package/docs/servers.md CHANGED
@@ -156,6 +156,12 @@ Every routed ssh call carries these options, before `--` and the host:
156
156
  | `ServerAliveInterval=15`, `ServerAliveCountMax=3` | a link that died without a reset ends the call, an attached viewer included, within about 60 s |
157
157
  | `ControlMaster=auto`, `ControlPath=~/.oats/ssh/%C`, `ControlPersist=60` | every call to one host (the probe, the command, a viewer, concurrent Desktop reads) shares one authenticated connection, kept 60 s after its last client |
158
158
 
159
+ - Concurrent first calls to a host with no master yet (the roster probes
160
+ every registration at once, so two registrations of one host do) race to
161
+ create it. ssh lets the one that loses run over a connection of its own
162
+ ("ControlSocket … already exists, disabling multiplexing"): the call still
163
+ succeeds, and later calls share the master. A dead host's registrations
164
+ each wait out the connect timeout, side by side.
159
165
  - Options given with `-o` override `~/.ssh/config`, so these replace any
160
166
  `ControlMaster`, `ControlPath` or `ControlPersist` set there for the host.
161
167
  Everything else in your ssh config (users, keys, `ProxyJump`, host
@@ -326,9 +332,13 @@ the host's own facts from its `status --json`: `identity`,
326
332
  (an older host, or a saved route the host no longer lists). A row also
327
333
  carries `waitingOnYou` (needs input) when the host's kernel reports it, and
328
334
  only then: an older host's row has no such key. A removed or edited registration keeps
329
- its group from the saved routes. State is pulled on every call within
330
- `--per-target` (default 20 s) of a total `--budget` (default 45 s); a group
331
- not reached is reported with `E_ROSTER_BUDGET`. `--server <id>` narrows it.
335
+ its group from the saved routes. State is pulled on every call, from every
336
+ group at once: each probe has its own deadline, `--per-target` (default 20 s)
337
+ capped by `--budget` (default 45 s, the deadline of the whole answer), and a
338
+ group that fails or does not answer in time reports its own `E_SSH`, so a
339
+ host that is switched off never hides the others. The groups keep their
340
+ registration order whatever order their probes finish in. `--server <id>`
341
+ narrows it.
332
342
 
333
343
  The group's `probe` also relays the host's kernel features (0.49.0,
334
344
  `probe.features`): the top-level `features` of the same `status --json`
@@ -55,7 +55,7 @@ members: # repo refs, NO @revision (E_WORKSPAC
55
55
 
56
56
  packages: # the ONLY versioned things
57
57
  oats.framework: v1.10.0 # bare version → resolves through the official catalog
58
- oats.okf: v5.0.3
58
+ oats.okf: v5.0.5
59
59
  acme.tools: git:github.com/acme/tools@v0.4.0 # outside the catalog → git:<repo>@<tag|OID>; still a package
60
60
 
61
61
  teams: # SHARED teams: the same provider team for everyone