@awebai/oats 0.55.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.
@@ -41,7 +41,7 @@ arrives from.
41
41
  # oats-workspace.yaml: one default per slot, for every soul
42
42
  packages:
43
43
  oats.okf: v5.0.5
44
- oats.aweb: v1.27.2
44
+ oats.aweb: v1.27.3
45
45
  oats.linear: v1.0.1
46
46
  oats.jira: v1.0.1
47
47
  defaults:
@@ -11,7 +11,7 @@ or workspace membership alone does not make a package official.
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
13
  | `oats.okf` | `v5.0.5` | `oats.okf` (knowledge), `oats.okf-harvest`, `oats.okf-maintenance` | `knowledge-harvester`, `knowledge-maintainer` |
14
- | `oats.aweb` | `v1.27.2` | `oats.aweb` (messaging) | |
14
+ | `oats.aweb` | `v1.27.3` | `oats.aweb` (messaging) | |
15
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` |
package/docs/packages.md CHANGED
@@ -76,7 +76,7 @@ members:
76
76
  packages:
77
77
  oats.framework: v1.10.0
78
78
  oats.okf: v5.0.5
79
- oats.aweb: v1.27.2
79
+ oats.aweb: v1.27.3
80
80
  teams:
81
81
  platform: { team: "platform:acme.aweb.ai", description: Platform engineering }
82
82
  defaults:
@@ -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.2 # 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
  ```
@@ -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.
@@ -8,7 +8,7 @@
8
8
  },
9
9
  "oats.aweb": {
10
10
  "url": "https://github.com/awebai/oats-aweb.git",
11
- "ref": "v1.27.2",
11
+ "ref": "v1.27.3",
12
12
  "path": "oats-package"
13
13
  },
14
14
  "oats.jira": {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@awebai/oats",
3
- "version": "0.55.0",
3
+ "version": "0.55.1",
4
4
  "description": "OATS (Open Agent Team Specification) — durable souls, disposable instances, targetable capability packages, and the runtime-neutral oats CLI/kernel.",
5
5
  "keywords": [
6
6
  "agents",
@@ -79,6 +79,10 @@ turn-record recall --reindex # full rebuild of the derived in
79
79
 
80
80
  Store root: `--root`, else `$TURN_RECORD_ROOT`, else `~/.turn-record`.
81
81
 
82
+ `recall --show` refuses a turn hidden by its author's tombstone, including a
83
+ session event whose tombstone lives in another stream. It emits no turn payload
84
+ and exits with status 1, as it does for a missing turn.
85
+
82
86
  **The `node` that `setup` writes down.** The hooks and the watcher's unit name
83
87
  a `node` by its path, and only `setup` run again rewrites them. Which path
84
88
  depends on how it is run:
@@ -61,8 +61,9 @@ try {
61
61
  console.error(`no turn ${args.show}`);
62
62
  process.exitCode = 1; return;
63
63
  }
64
- // Tombstoned turns are hidden from tool output, id lookup included.
65
- if (store.hiddenIds(byId).has(args.show)) {
64
+ // Session targets are absent from the bulk union: evaluate the claims
65
+ // against the resolved turn so id lookup respects their tombstones too.
66
+ if (store.claimHides(store.tombstoneClaims(byId), turn)) {
66
67
  console.error(`turn ${args.show} is tombstoned`);
67
68
  process.exitCode = 1; return;
68
69
  }