@awebai/oats 0.29.1 → 0.29.3

package/docs/release-notes/v0.29.2.md

@@ -0,0 +1,51 @@
+# OATS 0.29.2
+
+## oats.aweb 1.15.0 (catalog pin and bundled mirror)
+
+The catalog and this repo's workspace pin `oats.aweb` to `v1.15.0`, and the
+bundled `capabilities/oats-aweb` is the tag's tree.
+
+- **Live receive on joined teams.** An instance's joined teams now receive
+  live through the host wake broker. Session homes register the primary
+  identity plus every joined identity. Claude and Pi channel homes use aw's
+  mixed mode, and Codex keeps polling. Readiness reports each joined team's
+  actual mode (`joined-team-receive` or `joined-team-poll-only`, with the
+  reason). This needs aw >= 1.36.12.
+- **The identity-home scrub (critical fix).** Provider commands and nested
+  spawns and retires no longer inherit the caller's `AWEB_IDENTITY_HOME`.
+  Inside an instance, that variable made aw refuse cwd-rooted commands, which
+  broke roster and join. On retire, it could delete the caller's workspace.
+- **Home operations work under the kernel.** `oats operation run
+  messaging:teams|join|leave` gets exactly one JSON-v1 envelope, whose `ok`
+  agrees with the exit status. The Desktop's teams, join and leave buttons now
+  work. A partial multi-label join or leave records every label it completed.
+  A failed spawn hands its joined teams to compensation. `oats aweb join`
+  refuses resident-grant homes (`E_TEAM_GLOBAL_MODE`).
+- **An agent playbook.** The new `oats-aweb` skill carries the playbook, and
+  the inject is shorter and points to it. `oats aweb roster --label <label>`
+  is new.
+- **Deferred to 1.16: per-workspace personal-team enrollment.** It needs a
+  per-deployment login and a recorded owner. 1.15 makes no `aw auth` or
+  `aw team ensure` call, and the primary team resolves as in 1.14.2. A
+  host-set `settings.oats.aweb.roots.personal` is ignored with the readiness
+  warning `personal-root-deferred`.
+
+## Desktop
+
+- **Line counts on the Changes rows** (#245, #246). The server passes kernel
+  #238's per-file counts through, and each W6 Changes row ends with "+84 −3",
+  or "binary". An unknown count (untracked, submodule) and older kernels show
+  nothing, never "+0".
+- **The Git & GitHub tab counts unresolved review threads** (#247). The tab and
+  the collapsed rail button say "Git & GitHub, 2 unresolved review threads".
+- **Send N threads to <instance>** (#248, #249). When the instance's PR has
+  unresolved review threads, the Pull request card offers to send them to the
+  instance.
+  - The server composes the text, and the preview shows exactly what will be
+    pasted.
+  - The text is one line, framed as untrusted input from GitHub reviewers,
+    with control, bidi and zero-width characters stripped.
+  - It is pasted into the instance's terminal without Enter.
+  - A digest of the previewed bytes guards the send: if the threads changed,
+    nothing is pasted and the preview refreshes.
+- The Desktop still accepts OATS CLIs `>=0.25.8 <0.30.0`.

package/docs/release-notes/v0.29.3.md

@@ -0,0 +1,53 @@
+# OATS 0.29.3
+
+## Changed
+
+- **There is no "personal team"; a workspace has its default team.** The
+  vocabulary follows the teams contract's amendment of 2026-09-26: a workspace
+  has its **default team** (the team for the workspace key in its owner's
+  namespace), and agents may join other teams. The model is unchanged:
+  - an instance is in the workspace's default team only, by default;
+  - joining an eligible team is an explicit act;
+  - `OATS_TEAMS` is `[]` for a soul with no label.
+
+  The kernel's docs, comments and the `unmapped-team-label` warning use the
+  new words. The warning now reads "… fall back to the workspace's default team
+  for it". The oats.framework skills (oats.core 2.1.1, oats.setup 2.1.2,
+  oats.framework 1.3.1) teach the same model. The kernel carries no wire name
+  with "personal", and there are no compatibility aliases.
+- **The messaging provider uses the same words** (oats.aweb 1.16.0, below).
+
+## oats.aweb 1.16.0 (catalog pin and bundled mirror)
+
+- **The catalog and this repo's workspace pin `oats.aweb` to `v1.16.0`, and
+  the bundled `capabilities/oats-aweb` is the tag's tree.** It renames the
+  provider's wire names to the default-team vocabulary:
+  - the teams operation's `personal` field becomes `defaultTeam`
+    (`{ team, source }`, where `source` is `setting` or `root`);
+  - `E_TEAM_PERSONAL` becomes `E_TEAM_DEFAULT`;
+  - the broker receive label `personal` becomes `default`;
+  - `settings.oats.aweb.roots.personal` is removed: `roots` keys are team ids
+    only, and the `personal-root-deferred` warning is gone.
+
+  There are no aliases: a reader of the old names must move to the new ones,
+  as the Desktop does in this release. A home spawned under 1.15 still resolves
+  its default team from its recorded team. Per-workspace default-team
+  enrollment is still deferred.
+
+## oats.framework 1.3.1 (catalog pin)
+
+- **The catalog and this repo's workspace pin `oats.framework` to
+  `oats-framework/v1.3.1`.** Its only change is the default-team vocabulary
+  above, in `oats.core` 2.1.1 and `oats.setup` 2.1.2. A deployment on
+  `oats.framework: v1.3.0` keeps working, and moving the pin to `v1.3.1` picks
+  up the new skill text.
+
+## Desktop
+
+- **"Default team" everywhere** (#252). The teams panel reads oats.aweb 1.16's
+  `defaultTeam` and says where the team comes from: the workspace or host
+  setting, or the messaging root's active team. The spawn dialog, the soul
+  inspector and the teams panel say "Default team" in place of "Personal".
+  A 1.15 `personal` document no longer decodes, so this Desktop needs the
+  oats.aweb 1.16.0 pin.
+- The Desktop still accepts OATS CLIs `>=0.25.8 <0.30.0`.

package/docs/workspaces.md

@@ -59,7 +59,7 @@ members:                                   # repo refs, NO @revision (E_WORKSPAC
   - git:github.com/acme/tools              # a member that ALSO publishes a package (see below)
 
 packages:                                  # the ONLY versioned things
-  oats.framework: v1.3.0                   # bare version → resolves through the official catalog
+  oats.framework: v1.3.1                   # bare version → resolves through the official catalog
   oats.okf: v4.0.0
   acme.tools: git:github.com/acme/tools@v0.4.0   # outside the catalog → git:<repo>@<tag|OID>; still a package
 
@@ -399,7 +399,7 @@ keys, with `byTeam` stripped) ⊕ soul slot payload ⊕ `local.settings[cap]`
 **No `byTeam[<label>]` is merged into it, the primary's included** (teams
 amendment K): each label's `base ⊕ byTeam[label]` reaches the provider only as
 that label's entry in `OATS_TEAMS` (the preview's `teams`). So `settings.team`
-(and `OATS_TEAM_ID`) is the personal team if the host, the soul or the spawn
+(and `OATS_TEAM_ID`) is the workspace's default team if the host, the soul or the spawn
 set one; empty means the provider's own default. The provider's own `binding` contract
 (`normalize → bind → check`) runs over the merged payload exactly as before.
 Two teams, two messaging identities, one workspace:
@@ -420,7 +420,7 @@ one. A label under `byTeam` that is not declared in `teams:` is
 act.** `spawn --preview` shows the merged `settings.<cap>` and the `teams`, so
 the delivery is verifiable, and `instance.json` records both. With oats.aweb
 1.13.1 (which reads `team` from its settings and ignores `OATS_TEAMS`) the
-primary identity therefore mints into the personal team: the `.aw` root's
+primary identity therefore mints into the workspace's default team: the `.aw` root's
 active team, or the one the host set. What the payload does not change is
 **where the `.aw` root is found**: the hook still searches
 bounded candidates, first hit wins — the instance home, the Git repository

package/lib/core.mjs

@@ -1485,17 +1485,17 @@ export function instanceSoulDir(home, meta = undefined) {
 /** The team facts a lifecycle hook receives (workspace model only, lead decision
  * c3-7): the team SCOPE is the deployment directory, the team ID is the messaging
  * slot's merged payload `team` (workspace base ⊕ soul ⊕ host ⊕ spawn; no byTeam entry
- * is merged since teams amendment K): the personal team if one is set; empty = the
+ * is merged since teams amendment K): the workspace's default team if one is set; empty = the
  * provider's default (for oats.aweb, the root's active team). The provider also gets
  * the soul's primary team LABEL and the workspace's name and canonical key, so it can
- * derive a per-person, per-workspace personal team; each label's mapped payload is in
+ * derive the workspace's default team; each label's mapped payload is in
  * OATS_TEAMS.
  * OATS_TEAM_NAME (the 0.25 `team:` block's name) is always empty, so an ambient
  * value never reaches a hook. Human decision 2026-09-24 (messaging default).
  *
  * Teams contract 2026-09-25 (decision 4): `resolved.teams` is the ELIGIBLE teams,
  * `[{ label, team, mapped, payload }]` in soul order. OATS_TEAM_LABELS is their
- * labels comma-joined and OATS_TEAMS their JSON (`[]` = no label: personal only).
+ * labels comma-joined and OATS_TEAMS their JSON (`[]` = no label: the workspace's default team only).
  * Both are empty when the teams are not known (a home spawned before 0.26.0 whose
  * workspace cannot be read now) — empty means "unknown", never "none".
  * OATS_TEAMS_SOURCE says where the list came from: `live` (the workspace read now,

package/lib/resolve.mjs

@@ -346,7 +346,7 @@ export function teamLabelsOf(soulEntry) {
  * `{ label, team, mapped, payload }`. `payload` is workspace.messaging's base ⊕ byTeam[label] when the
  * workspace maps the label, else the base alone with `mapped: false`; `team` is the payload's team id
  * when mapped (null otherwise). Kernel-owned and delivered BESIDE a provider's settings, never inside
- * them; joining any of them is the messaging provider's explicit act. No label → [] ("personal only").
+ * them; joining any of them is the messaging provider's explicit act. No label → [] (the workspace's default team only).
  * Pure: resolveSoul validates every carried label's entry (reserved byTeam, hostOnly keys) first.
  */
 export function teamsOf(workspace, labels) {
@@ -731,7 +731,7 @@ export async function resolveSoul(discovery, soulEntry, { local = null, lock = n
       // Decision 23 as amended by K (teams contract, co-lead ruling): the provider's settings are
       // base ⊕ soul ⊕ host ⊕ spawn. No byTeam[<label>] is merged, the primary's included: each
       // label's base ⊕ byTeam[label] is delivered only in its `teams` entry (teamsOf → OATS_TEAMS),
-      // so settings.team is the personal team a host, soul or spawn set. `byTeam` never reaches the
+      // so settings.team is the default team a host, soul or spawn set. `byTeam` never reaches the
       // provider, and the primary team's own payload may still not nest one.
       const { byTeam, ...base } = workspace.messaging;
       committed(base, "/messaging", { kind: "workspace", at: "oats-workspace.yaml#/messaging" });

package/lib/workspace.mjs

@@ -753,8 +753,8 @@ export function workspaceWarnings(workspace, members, externalRows, packageSouls
 
 /** Teams contract decision 5: a soul label the workspace declares in `teams:` but does not map in
  *  `messaging.byTeam` is a WARNING, not a problem — the label stays eligible-but-unmapped and the
- *  messaging provider falls back to the personal team for it. (An undeclared label is E_TEAM_UNKNOWN.)
- *  ONE warning per unmapped label, naming its souls (a personal-only workspace would otherwise print
+ *  messaging provider falls back to the workspace's default team for it. (An undeclared label is E_TEAM_UNKNOWN.)
+ *  ONE warning per unmapped label, naming its souls (a workspace on its default team alone would otherwise print
  *  a line per soul): { code, label, souls, paths, message }, sorted by label. */
 const byCodepointOrder = (a, b) => (a < b ? -1 : a > b ? 1 : 0);
 function unmappedLabelWarnings(workspace, members, externalRows, teams) {
@@ -774,7 +774,7 @@ function unmappedLabelWarnings(workspace, members, externalRows, teams) {
     const order = names.map((n, i) => i).sort((x, y) => byCodepointOrder(names[x], names[y]) || byCodepointOrder(paths[x], paths[y]));
     const sorted = order.map((i) => names[i]);
     return { code: "unmapped-team-label", label, souls: sorted, paths: order.map((i) => paths[i]),
-      message: `team ${show(label)} has no messaging.byTeam entry; its souls (${sorted.join(", ")}) fall back to the personal team for it` };
+      message: `team ${show(label)} has no messaging.byTeam entry; its souls (${sorted.join(", ")}) fall back to the workspace's default team for it` };
   });
 }
 

package/package-catalog.json

@@ -8,7 +8,7 @@
     },
     "oats.aweb": {
       "url": "https://github.com/awebai/oats-aweb.git",
-      "ref": "v1.14.2",
+      "ref": "v1.16.0",
       "path": "oats-package"
     },
     "oats.jira": {
@@ -33,7 +33,7 @@
     },
     "oats.framework": {
       "url": "https://github.com/awebai/oats.git",
-      "ref": "oats-framework/v1.3.0",
+      "ref": "oats-framework/v1.3.1",
       "path": "oats-package"
     }
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awebai/oats",
-  "version": "0.29.1",
+  "version": "0.29.3",
   "description": "OATS (Open Agent Team Specification) — durable souls, disposable instances, targetable capability packages, and the runtime-neutral oats CLI/kernel.",
   "keywords": [
     "agents",