@awebai/oats 0.69.8 → 0.69.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -35,12 +35,15 @@ The [official catalog](docs/official-catalog.md) is the reviewed list of officia
35
35
  curl -fsSL https://raw.githubusercontent.com/awebai/oats/main/skills/oats-getting-started/SKILL.md
36
36
  ```
37
37
 
38
- If you are a person, give your coding agent (Claude Code, Codex, pi or any other) this page and say "set up OATS for me". It then:
38
+ If you are a person, give your coding agent (Claude Code, Codex, pi or any other) this page and say "set up OATS for this project". It then:
39
39
 
40
- - **Asks first, in one round:** your project, its repositories, the knowledge tools you use, and a username for agent messaging.
41
- - **Installs OATS and OATS Desktop,** then creates your workspace in one commit: the workspace, a messaging team, a setup expert and a first developer. Or it joins this machine to an existing workspace.
42
- - **Gives your agents identities and messaging:** one command signs up a hosted [aweb](https://aweb.ai) team for the new workspace, with no API key and no pull requests to merge.
43
- - **Hands over to the setup expert,** an OATS agent that sets up the rest with you. You type only passwords, logins and tokens.
40
+ - **Asks first, in one round:** your project, its repositories and where the workspace should live, the knowledge tools you use, and how your agents message each other ([aweb](https://aweb.ai) by default).
41
+ - **Installs OATS, OATS Desktop and the messaging CLI.**
42
+ - **Creates your workspace's team:** you sign in to your aweb account in your browser, and one command creates the team, owned by your account, that every agent you spawn joins.
43
+ - **Writes your workspace** in one commit, in your repository or a new private one: the workspace and its team, nothing else. Or it joins this machine to an existing workspace.
44
+ - **Spawns the setup expert and opens the Desktop on it.** The setup expert is an OATS agent that turns OATS's defaults into your own coordination, knowledge and tasks capabilities, with you. You type only passwords, logins and tokens.
45
+
46
+ You end with a working workspace, the Desktop open on it, and its setup expert running.
44
47
 
45
48
  Download the skill, don't web-fetch it: a tool that summarises pages would lose its exact commands.
46
49
 
package/bin/oats.mjs CHANGED
@@ -84,7 +84,7 @@ const { receiveAttachment, uploadAttachment, readStreamBounded, MAX_ATTACHMENT_B
84
84
  const { observeInstanceGit, diffInstanceFile } = await kernelImport("instance-git", () => import("../lib/instance-git.mjs"));
85
85
  const { planStop, applyStop, planRetire, retireDefaultsLine, stopClosingLine, descendantsOf, resolveInstance: resolveInstanceForCli, setInstanceColor, setInstanceBackground, setInstanceSameWork, STOP_WARNINGS } = await kernelImport("instance-lifecycle", () => import("../lib/instance-lifecycle.mjs"));
86
86
  const { extraWorktreeLines, formatBytes, warningLines, workRecoveryLines } = await kernelImport("retire-output", () => import("../lib/retire-output.mjs"));
87
- const { livenessWord, lostLine, statusWord } = await kernelImport("status-words", () => import("../lib/status-words.mjs"));
87
+ const { livenessWord, lostLine, statusWord, waitingLine } = await kernelImport("status-words", () => import("../lib/status-words.mjs"));
88
88
  const { retainedRecoveryLines, retainedWorktreeLines, retainedWorktrees } = await kernelImport("retained-after-retire", () => import("../lib/retained-after-retire.mjs"));
89
89
  const await_import_lifecycle = () => ({ resolveInstance: resolveInstanceForCli });
90
90
  const { homeTarget, soulTarget, isWorkspaceContext, inspectDocument, withComposition, withSkills, readinessDocument, policyOf, policySoul, manifestMissingRequires, INSPECT_OPERATIONS_API } = await kernelImport("instance-inspect", () => import("../lib/instance-inspect.mjs"));
@@ -2601,7 +2601,7 @@ function printStatus({ root, agents: data, ws, problems }, verbose) {
2601
2601
  { const lost = lostLine(i); if (lost) console.log(` ${lost}`); }
2602
2602
  // Feature waiting-on-you: non-null only on a running row; the reader has
2603
2603
  // already validated the message (one line, no control characters).
2604
- if (i.running === true && i.waitingOnYou) console.log(` ! needs input (${i.waitingOnYou.reason ?? "unknown"})${i.waitingOnYou.message ? `: ${i.waitingOnYou.message}` : ""}`);
2604
+ { const waiting = waitingLine(i); if (waiting) console.log(` ${waiting}`); }
2605
2605
  const key = i.home ?? `${a.name}/${i.instance}`;
2606
2606
  if (i.identity) console.log(` identity: ${servedIdentityLine(i.identity)}`);
2607
2607
  // The kernel the home's plain `oats` runs (its last launch's), when it is not this one.
@@ -4571,8 +4571,13 @@ oats instance attention [--message <text>] [--clear] --json
4571
4571
  - **Where it shows.** `waitingOnYou` on the events read, on `oats status
4572
4572
  --json` instance rows (running rows only) and on `oats session inspect
4573
4573
  --json` (beside `state`, whose enum is unchanged; `null` unless the harness
4574
- is running). Plain `oats status` prints `! needs input (<reason>):
4575
- <message>` under a running instance's row while it holds a claim.
4574
+ is running). Plain `oats status` prints `! needs input (<reason>) since
4575
+ <start>, <elapsed>: <message>` under a running instance's row while it holds
4576
+ a claim (the message and its colon are omitted when absent). The start is
4577
+ local to the CLI machine: `HH:MM` today, `Mon D HH:MM` on another day in
4578
+ the same year, or `YYYY-MM-DD HH:MM` in another year. Elapsed time is floored
4579
+ to `under a minute`, `N min`, `N h` or `N d`. A future start omits elapsed
4580
+ time; an unparseable start retains the line without any time.
4576
4581
  - **Cost.** To compute the field, `oats status` reads the home log of each
4577
4582
  running row (the workspace log only when the home log is absent), with
4578
4583
  the same bounded read as the events read: at most the last 4 MiB, so a
@@ -2,8 +2,9 @@
2
2
 
3
3
  **The quick way:** the README's [Start here](../README.md#start-here): your
4
4
  coding agent downloads the `oats-getting-started` skill verbatim and follows
5
- it. It installs OATS, creates your workspace with its own setup expert soul (or joins
6
- an existing workspace), and hands over to that expert. This page is the manual
5
+ it. It installs OATS, creates your workspace and its team (or joins an
6
+ existing workspace), and spawns the workspace's setup expert, `oats.framework`'s
7
+ `oats-setup-expert`, which does the rest with you. This page is the manual
7
8
  path, for writing a workspace by hand.
8
9
 
9
10
  The model is in [workspaces.md](workspaces.md), packages in
@@ -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.7.0
44
- oats.aweb: v1.32.1
44
+ oats.aweb: v1.33.1
45
45
  oats.linear: v1.0.1
46
46
  oats.jira: v1.0.1
47
47
  defaults:
@@ -9,10 +9,10 @@ or workspace membership alone does not make a package official.
9
9
 
10
10
  | package | release | capabilities | package souls |
11
11
  |---|---|---|---|
12
- | `oats.framework` | `oats-framework/v1.18.0` (this repository) | `oats.core`, `oats.setup`, `oats.onboarding`, `oats.support`, `oats.knowledge-theory` | `knowledge-theory-expert`, `oats-setup-expert` |
12
+ | `oats.framework` | `oats-framework/v1.19.0` (this repository) | `oats.core`, `oats.setup`, `oats.onboarding`, `oats.support`, `oats.knowledge-theory` | `knowledge-theory-expert`, `oats-setup-expert` |
13
13
  | `oats.okf` | `v5.7.0` | `oats.okf` (knowledge), `oats.okf-harvest`, `oats.okf-maintenance` | `knowledge-harvester`, `knowledge-maintainer` |
14
- | `oats.aweb` | `v1.32.1` | `oats.aweb` (messaging), `oats.aweb-tasks` (tasks) | |
15
- | `oats.engineering` | `v1.17.2` | `oats.engineering-expert`, `oats.developer`, `oats.code-review`, `oats.maintainer` | `code-reviewer` |
14
+ | `oats.aweb` | `v1.33.1` | `oats.aweb` (messaging), `oats.aweb-tasks` (tasks) | |
15
+ | `oats.engineering` | `v1.18.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.1.0` | `oats.cloning` | `cloner` |
18
18
  | `oats.jira` | `v1.0.1` | `oats.jira` (tasks) | |
package/docs/packages.md CHANGED
@@ -51,7 +51,7 @@ packages:
51
51
  - **Bare version** (`v5.7.0`, `5.7.0`, `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.7.0` or `oats-framework/v1.18.0`) and the payload path. An id
54
+ convention (`v5.7.0` or `oats-framework/v1.19.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
@@ -74,9 +74,9 @@ members:
74
74
  - git:github.com/acme/agents
75
75
  - git:github.com/acme/platform
76
76
  packages:
77
- oats.framework: v1.18.0
77
+ oats.framework: v1.19.0
78
78
  oats.okf: v5.7.0
79
- oats.aweb: v1.32.1
79
+ oats.aweb: v1.33.1
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.32.1 # a catalog version
137
+ oats package add oats.aweb v1.33.1 # 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
  ```
@@ -353,11 +353,11 @@ A soul that names one of the package's capabilities with
353
353
  "policy": "docs/official-catalog.md",
354
354
  "packages": {
355
355
  "oats.okf": { "url": "https://github.com/awebai/oats-okf.git", "ref": "v5.7.0", "path": "oats-package" },
356
- "oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.18.0", "path": "oats-package" }
356
+ "oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.19.0", "path": "oats-package" }
357
357
  }
358
358
  }
359
359
  ```
360
360
 
361
- `ref` carries the tag convention: a workspace's `oats.framework: v1.18.0`
362
- resolves to tag `oats-framework/v1.18.0`. Resolving through the catalog never
361
+ `ref` carries the tag convention: a workspace's `oats.framework: v1.19.0`
362
+ resolves to tag `oats-framework/v1.19.0`. Resolving through the catalog never
363
363
  advances a lock by itself: `oats sync` does, and says so.
@@ -0,0 +1,92 @@
1
+ # OATS 0.69.9
2
+
3
+ 0.69.9 moves the official catalog to three package releases: `oats.framework`
4
+ 1.19.0 (the setup expert attaches a person to a messaging account created for
5
+ the workspace), `oats.aweb` 1.33.1 (a workspace set up without a browser
6
+ sign-in, and setup no longer writes aw's rules into `AGENTS.md` or
7
+ `CLAUDE.md`) and `oats.engineering` 1.18.0 (a waiting agent sets a checkpoint,
8
+ so a stalled child no longer stalls it). Plain `oats status` shows how long a
9
+ needs-input claim has waited, and the Desktop says when an older Claude home
10
+ can't report its dialogs.
11
+
12
+ ## Upgrade
13
+
14
+ - **Either order of the Desktop and the CLI works.**
15
+ [Upgrading](../upgrading.md) installs the Desktop first, and a host that
16
+ installed the CLI first is fine too: the 0.69.9 Desktop accepts OATS CLIs
17
+ `>=0.26.0 <0.70.0`, and so does the 0.69.8 Desktop.
18
+ - **Package moves:** the official catalog pins oats.framework 1.19.0,
19
+ oats.aweb 1.33.1 and oats.engineering 1.18.0, with no change to their OATS
20
+ floors (oats.aweb keeps aw >=1.36.33). A deployment takes each by raising its
21
+ own pin (`/oats-package-pins`), then `oats sync`. Running instances keep the
22
+ modules they were spawned with: new spawns get the new ones, and a stopped
23
+ home moves with `oats instance upgrade`.
24
+ - **A stop doesn't hold while a checkpoint is pending.** With oats.engineering
25
+ 1.18.0, an instance stopped while it waits comes back when its checkpoint
26
+ fires, because a wake job starts a stopped home. To keep it stopped, run
27
+ `oats schedule disable <id>`, or retire it. A checkpoint fires only on a host
28
+ whose schedule timer is installed (`oats schedule host install`).
29
+ - **Joined teams on a Claude home are read at task boundaries.** With
30
+ oats.aweb 1.33.1, a Claude home takes no live wakes for its joined teams,
31
+ `--yolo` or not: an idle session reads that mail only once something else
32
+ wakes it. Its default team, and pi and Codex homes, are unchanged. If you
33
+ paused a home with `aw wake pause`, start it under this version before you
34
+ resume it. A Claude channel home then needs no resume, and a pi or Codex
35
+ home stays paused until you resume it.
36
+ - **A deployment set up by an earlier `oats aweb setup` may still carry aw's
37
+ rules** in `AGENTS.md` or `CLAUDE.md`. Nothing in OATS reads them; the
38
+ oats.aweb CHANGELOG (1.33.0) says how to remove them.
39
+
40
+ ## Changed
41
+
42
+ - **`oats.aweb` 1.33.1.** `oats aweb setup --username` creates a workspace's
43
+ account and team without a browser sign-in, and `/oats-aweb`'s new section
44
+ "attach yourself to the account" has the setup expert run `aw claim-human`
45
+ with the address the person gives; the account is theirs once they click the
46
+ link aw mails them. **On aweb Cloud today that link fails** for an account
47
+ that `--username` created ("Verification failed"): aweb's fix ships in its
48
+ next Cloud release. Until then, sign in to your own account instead, as
49
+ getting started in this release does. Setup's `aw init` no longer writes
50
+ aw's rules into the deployment. A shorter always-loaded inject, the approved route as the
51
+ guidance for unattended Claude homes, joined teams read at task boundaries on
52
+ Claude homes, and an opt-in attention flag for unread mail with a persisting
53
+ broker error (it needs aw's `mail inbox --count-only`) are in it too.
54
+ 1.33.1 makes `oats aweb invite` work on such a workspace and adds
55
+ `awebUrl`, the service to hand on, to its JSON answer; an aw pre-release
56
+ above the floor passes the provider's version checks
57
+ ([CHANGELOG](https://github.com/awebai/oats-aweb/blob/v1.33.1/CHANGELOG.md);
58
+ [awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
59
+
60
+ - **`oats.engineering` 1.18.0: a stalled child no longer stalls its waiter.**
61
+ Before a developer, expert or maintainer ends a turn to wait on a child, it
62
+ sets a checkpoint: a wake job on its own home, due when the result is
63
+ overdue. When it fires, the waiter inspects the child, then unblocks it or
64
+ asks it one precise question; a second overdue checkpoint with no movement
65
+ replaces the child. A waiter sets one only where `wakeHold` reads `on-claims`
66
+ or `not-exposed`, and otherwise hands the wait up. The package's own CI now
67
+ checks layer neutrality, and a reviewer reports a failure that stops its
68
+ round ([CHANGELOG](https://github.com/awebai/oats-engineering/blob/v1.18.0/CHANGELOG.md)).
69
+
70
+ - Plain `oats status` now shows when a running instance's needs-input claim
71
+ started, in the CLI machine's local time, and how long it has waited
72
+ (`under a minute`, minutes, hours or days). A start in the future shows
73
+ only its time; an unparseable start keeps the previous line without time.
74
+ JSON output is unchanged.
75
+
76
+ - **`oats.core` 2.12.1, in `oats.framework` 1.19.0:** `/oats-operate` gives the needs-input line that plain `oats status` prints from OATS 0.69.9, with when the claim started and how long it has waited.
77
+
78
+ - **`oats.framework` 1.19.0: the setup expert attaches the person to a messaging account created for the workspace.** `oats.onboarding` 1.1.0's `/oats-tailor-workspace` gains a normal step 3, before the deployment-agent step: when getting started created the workspace's account without the person's sign-in, the setup expert attaches the person through the messaging capability's own step (with aweb, `/oats-aweb`'s "attach yourself to the account", from the `oats.aweb` release that ships it), and skips it when the person signed in to their own account. When the answer waits on the person's email, the account is theirs only once they click its link, and a refusal leaves it unattached; the briefing reports which. Until it is theirs, the skill and `oats.setup` 2.10.1's `/oats-setup-expert` say the team is on an account created for the workspace, never that it is the person's ([awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
79
+
80
+ - **Getting started: a new workspace ends with the Desktop open on it and its setup expert running.** `oats-getting-started` now installs OATS, OATS Desktop and the messaging CLI first (`aw`, with no soul), then has the person sign in to their own aweb account in their browser (`aw auth login`) and creates the workspace's team with one call that installs its root in the deployment (`aw team ensure --workspace-key <host repo key> --label <workspace> --expect-account <account>`): the team is owned by their aweb account. It asks where the workspace lives (inside a monorepo, a dedicated private host, or a first new repository), writes the skeleton with the team id from that answer (one framework pin, no soul of its own, no `tasks:` default), spawns `oats.framework`'s `oats-setup-expert` with `oats onboard`'s `next.spawn` and opens the Desktop on the workspace with the setup expert selected (`--instance`; an older Desktop ignores it). It needs `oats.framework` 1.18.0 and stops on an older catalog. It also stops when Node is under 22, naming the minimum and the version found, and recommends Git 2.45 or later (older Git works, with whole-tree fetches); on Linux, x64 or arm64, it installs Node 22 from NodeSource and, on Ubuntu, Git from the git-core PPA. SSH, signing and the DCO sign-off leave the main path (`/oats-git-setup`, optional); GitHub stays where the flow needs it: the Desktop's download, the host repository and its push. Its messaging gate is the soul's messaging capability and its readiness, with aweb as the default ([awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
81
+
82
+ - **Getting started stops when this machine's messaging root is not a member of the workspace's team.** In step 9, when `oats aweb setup --check-only` answers `"member": false` for a new workspace whose team step 5 created, the skill spawns nothing and names the fix; a machine found-list's first check, before its signup, still goes on to it. With no root (`"root": null`), step 5's team creation did not finish in the deployment's `.aw`, and its line for an interrupted run continues it. With a root, the workspace file's team id is not step 5's `canonical_team_id`, so it is corrected, committed and synced. After a found-list signup or an invited join, it stops and reports what the check shows, without rerunning them ([awebai/oats#1665](https://github.com/awebai/oats/issues/1665)).
83
+
84
+ ## Fixed
85
+
86
+ - **Desktop explains when an older Claude home's questions and permission requests aren't reported
87
+ as needs input.** Its roster hover card and the instance panel's Session card say when its recorded
88
+ oats.core comes from oats.framework before 1.6.0 (oats.core 2.4.0), and the panel suggests upgrading
89
+ or respawning it to report those dialogs. The explanation clears when the home's recorded version
90
+ supports reporting. It works for local and remote rows; missing or unknown version evidence shows
91
+ nothing. The live "Needs input" marker is unchanged, and an agent's own attention claim can appear
92
+ alongside the dialog reporting explanation.
package/docs/upgrading.md CHANGED
@@ -6,11 +6,11 @@ host that comes from it.
6
6
 
7
7
  ## Upgrading to the latest version
8
8
 
9
- The latest version is **OATS 0.69.8** ([release notes](release-notes/v0.69.8.md)).
10
- The 0.69.8 Desktop accepts OATS CLIs `>=0.26.0 <0.70.0`.
9
+ The latest version is **OATS 0.69.9** ([release notes](release-notes/v0.69.9.md)).
10
+ The 0.69.9 Desktop accepts OATS CLIs `>=0.26.0 <0.70.0`.
11
11
 
12
12
  **First, read the `## Upgrade` section of every release after yours, up to
13
- 0.69.8,** in the [release notes](release-notes/): it says what to do before
13
+ 0.69.9,** in the [release notes](release-notes/): it says what to do before
14
14
  the CLI changes, and what else must change with it (the Desktop, another
15
15
  tool, a package pin). [Coming from an older version](#coming-from-an-older-version)
16
16
  names the releases that ask for more than the steps below. `oats version`
@@ -19,8 +19,8 @@ prints the version you have.
19
19
  Then, on each host:
20
20
 
21
21
  ```sh
22
- # 0. where the Desktop is installed: Desktop 0.69.8 first
23
- npm install -g @awebai/oats@0.69.8 # 1. the CLI
22
+ # 0. where the Desktop is installed: Desktop 0.69.9 first
23
+ npm install -g @awebai/oats@0.69.9 # 1. the CLI
24
24
  oats update # 2. in each deployment: the plan, then it asks before it runs
25
25
  oats doctor # 3. in the same deployment
26
26
  ```
@@ -202,6 +202,11 @@ of the Desktop and the CLI, and an optional package pin. A change a script
202
202
  must follow is in its release's Upgrade section whether or not it is listed
203
203
  here.
204
204
 
205
+ - **[0.69.9](release-notes/v0.69.9.md#upgrade):** the catalog pins
206
+ oats.framework 1.19.0, oats.aweb 1.33.1 and oats.engineering 1.18.0. With
207
+ oats.engineering 1.18.0, a stop doesn't hold while a checkpoint is pending:
208
+ `oats schedule disable <id>` keeps it stopped. Claude homes read their
209
+ joined teams at task boundaries, so an idle one doesn't wake for that mail.
205
210
  - **[0.69.8](release-notes/v0.69.8.md#upgrade):** the catalog pins
206
211
  oats.framework 1.18.0.
207
212
  - **[0.69.7](release-notes/v0.69.7.md#upgrade):** the catalog pins
@@ -54,7 +54,7 @@ members: # repo refs, NO @revision (E_WORKSPAC
54
54
  - git:github.com/acme/tools # a member that ALSO publishes a package (see below)
55
55
 
56
56
  packages: # the ONLY versioned things
57
- oats.framework: v1.18.0 # bare version → resolves through the official catalog
57
+ oats.framework: v1.19.0 # bare version → resolves through the official catalog
58
58
  oats.okf: v5.7.0
59
59
  acme.tools: git:github.com/acme/tools@v0.4.0 # outside the catalog → git:<repo>@<tag|OID>; still a package
60
60
 
@@ -18,6 +18,38 @@ export const livenessWord = (i) => i.running === true ? "RUNNING" : i.running ==
18
18
  /** A row's word: a retire under way wins over its liveness. */
19
19
  export const statusWord = (i) => i.retirePending ? "RETIRING" : livenessWord(i);
20
20
 
21
+ const MONTHS = ["Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec"];
22
+
23
+ /** Plain status's claim line, or null unless running. The clock defaults to the CLI machine's
24
+ * timezone; explicit `now` and `timeZone` keep calendar-boundary tests independent of the host.
25
+ * Elapsed words match the client's waitedText without a dependency on packages/client. */
26
+ export function waitingLine(i, { now = Date.now(), timeZone } = {}) {
27
+ if (i.running !== true || !i.waitingOnYou) return null;
28
+ const claim = i.waitingOnYou, since = Date.parse(claim.since);
29
+ let timing = "";
30
+ if (Number.isFinite(since)) {
31
+ const clock = new Intl.DateTimeFormat("en-US", {
32
+ timeZone, year: "numeric", month: "2-digit", day: "numeric",
33
+ hour: "2-digit", minute: "2-digit", hourCycle: "h23",
34
+ });
35
+ const parts = (at) => Object.fromEntries(clock.formatToParts(at).map(p => [p.type, p.value]));
36
+ const at = parts(since), today = parts(now);
37
+ const time = `${at.hour}:${at.minute}`;
38
+ let start = time;
39
+ if (at.year !== today.year) {
40
+ start = `${at.year.padStart(4, "0")}-${at.month}-${at.day.padStart(2, "0")} ${time}`;
41
+ } else if (at.month !== today.month || at.day !== today.day) start = `${MONTHS[Number(at.month) - 1]} ${at.day} ${time}`;
42
+ timing = ` since ${start}`;
43
+ const ms = now - since;
44
+ if (ms >= 0) {
45
+ const min = Math.floor(ms / 60000), h = Math.floor(min / 60);
46
+ const elapsed = min < 1 ? "under a minute" : min < 60 ? `${min} min` : h < 24 ? `${h} h` : `${Math.floor(h / 24)} d`;
47
+ timing += `, ${elapsed}`;
48
+ }
49
+ }
50
+ return `! needs input (${claim.reason ?? "unknown"})${timing}${claim.message ? `: ${claim.message}` : ""}`;
51
+ }
52
+
21
53
  /** The one line under a LOST row that says how to bring it back, or null for any other row. Local:
22
54
  * the resume by hand, or the next sweep. `host` (a `--server` or roster row): both refuse `--server`
23
55
  * (E_BAD_ARGS), so the line says to run them on that host. */
@@ -8,7 +8,7 @@
8
8
  },
9
9
  "oats.aweb": {
10
10
  "url": "https://github.com/awebai/oats-aweb.git",
11
- "ref": "v1.32.1",
11
+ "ref": "v1.33.1",
12
12
  "path": "oats-package"
13
13
  },
14
14
  "oats.jira": {
@@ -28,7 +28,7 @@
28
28
  },
29
29
  "oats.engineering": {
30
30
  "url": "https://github.com/awebai/oats-engineering.git",
31
- "ref": "v1.17.2",
31
+ "ref": "v1.18.0",
32
32
  "path": "oats-package"
33
33
  },
34
34
  "oats.cloning": {
@@ -48,7 +48,7 @@
48
48
  },
49
49
  "oats.framework": {
50
50
  "url": "https://github.com/awebai/oats.git",
51
- "ref": "oats-framework/v1.18.0",
51
+ "ref": "oats-framework/v1.19.0",
52
52
  "path": "oats-package"
53
53
  }
54
54
  },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@awebai/oats",
3
- "version": "0.69.8",
3
+ "version": "0.69.9",
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",
@@ -0,0 +1,25 @@
1
+ // docs/release-notes/v0.40.0.md: oats.framework 1.6.0 carries oats.core 2.4.0,
2
+ // the first Claude needs-input hooks. Compare the home's recorded version, never the lock.
3
+ const NEEDS_INPUT_FRAMEWORK_MIN = Object.freeze([1, 6, 0]);
4
+
5
+ /** The recorded framework version when Claude dialogs cannot be reported as needs input, else null.
6
+ * Both local and remote rows carry drift rows, or a recorded map when the workspace
7
+ * wasn't read. Missing evidence says nothing about reporting coverage. */
8
+ export function needsInputReportingGap(row) {
9
+ if (row?.harness !== 'claude') return null;
10
+ const modules = row.modules;
11
+ const core = Array.isArray(modules) ? modules.find(m => m?.name === 'oats.core')
12
+ : modules && typeof modules === 'object' && Object.hasOwn(modules, 'oats.core') ? modules['oats.core'] : null;
13
+ const from = core?.from;
14
+ if (from?.kind !== 'package' || from.package !== 'oats.framework' || typeof from.version !== 'string') return null;
15
+ // Semver: core numbers and numeric prerelease identifiers have no leading zeros;
16
+ // build identifiers do.
17
+ const match = /^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-([0-9A-Za-z-]+(?:\.[0-9A-Za-z-]+)*))?(?:\+[0-9A-Za-z-]+(?:\.[0-9A-Za-z-]+)*)?$/.exec(from.version);
18
+ if (!match || match[4]?.split('.').some(id => /^\d+$/.test(id) && id.length > 1 && id[0] === '0')) return null;
19
+ for (let i = 0; i < NEEDS_INPUT_FRAMEWORK_MIN.length; i++) {
20
+ const number = Number(match[i + 1]), minimum = NEEDS_INPUT_FRAMEWORK_MIN[i];
21
+ if (number !== minimum) return number < minimum ? from.version : null;
22
+ }
23
+ // A prerelease of the first supporting release still sorts below it.
24
+ return match[4] ? from.version : null;
25
+ }