@awebai/oats 0.69.14 → 0.69.16
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 +1 -1
- package/bin/oats.mjs +79 -18
- package/docs/capabilities.md +57 -14
- package/docs/container.md +111 -17
- package/docs/desktop-cli-api.md +215 -19
- package/docs/desktop.md +3 -3
- package/docs/execution-targets.md +15 -3
- package/docs/first-team.md +4 -3
- package/docs/implementation.md +19 -9
- package/docs/integrations.md +9 -8
- package/docs/knowledge-and-learning.md +2 -2
- package/docs/knowledge-theory.md +17 -15
- package/docs/knowledge.md +202 -179
- package/docs/official-catalog.md +4 -4
- package/docs/packages.md +13 -13
- package/docs/release-notes/v0.69.15.md +444 -0
- package/docs/release-notes/v0.69.16.md +169 -0
- package/docs/schedules.md +168 -34
- package/docs/servers.md +64 -3
- package/docs/souls-and-instances.md +100 -19
- package/docs/upgrading.md +26 -6
- package/docs/workspaces.md +2 -2
- package/lib/claim.mjs +2 -3
- package/lib/command-flags.mjs +4 -2
- package/lib/core.mjs +215 -72
- package/lib/dir-lock.mjs +17 -0
- package/lib/errors.mjs +2 -1
- package/lib/host-run.mjs +218 -0
- package/lib/host-stop-child.mjs +21 -0
- package/lib/instance-git.mjs +32 -6
- package/lib/instance-lifecycle.mjs +4 -3
- package/lib/instance-listing.mjs +35 -6
- package/lib/kernel-features.mjs +4 -1
- package/lib/read-call.mjs +1 -1
- package/lib/remote.mjs +17 -14
- package/lib/schedule.mjs +237 -20
- package/lib/servers.mjs +83 -5
- package/lib/session-end.mjs +28 -8
- package/lib/session-resume.mjs +10 -18
- package/lib/session-seen.mjs +4 -64
- package/lib/status-words.mjs +11 -4
- package/lib/system-tools.mjs +1 -36
- package/lib/worktree-hooks.mjs +6 -175
- package/lib/worktree.mjs +19 -10
- package/package-catalog.json +3 -3
- package/package.json +4 -1
- package/packages/record/README.md +56 -21
- package/packages/record/docs/capture-service.md +8 -5
- package/packages/record/docs/turn-record-sot.md +9 -0
- package/packages/record/lib/capture-health.mjs +6 -4
- package/packages/record/lib/capture-lock.mjs +31 -27
- package/packages/record/lib/capture-retained-scratch.mjs +4 -3
- package/packages/record/lib/capture-scratch.mjs +2 -1
- package/packages/record/lib/derived-state.mjs +4 -2
- package/packages/record/lib/index-db.mjs +4 -2
- package/packages/record/lib/lock-holder.mjs +21 -0
- package/packages/record/lib/private-files.mjs +18 -0
- package/packages/record/lib/process-identity.mjs +310 -0
- package/packages/record/lib/store.mjs +31 -25
- package/skills/oats-getting-started/SKILL.md +9 -6
|
@@ -172,7 +172,7 @@ For current settings and the respawn/cleanup sequence, see [knowledge.md](knowle
|
|
|
172
172
|
}
|
|
173
173
|
},
|
|
174
174
|
"providers": {
|
|
175
|
-
"oats.okf": { "bindings-file": "/Users/ana/.oats/okf-bindings.json", "state-dir": "/Users/ana/.oats/okf"
|
|
175
|
+
"oats.okf": { "bindings-file": "/Users/ana/.oats/okf-bindings.json", "state-dir": "/Users/ana/.oats/okf" },
|
|
176
176
|
"acme-release-tooling": {}
|
|
177
177
|
},
|
|
178
178
|
"workspace": {
|
|
@@ -403,8 +403,7 @@ setting given without `--provider <capability>`). The full DTOs are in
|
|
|
403
403
|
Examples of spawn hooks:
|
|
404
404
|
|
|
405
405
|
- `oats.okf` validates the soul's declaration and the bindings, and creates the
|
|
406
|
-
instance knowledge files.
|
|
407
|
-
and its harvest schedule; with harvest off (the default) it registers nothing.
|
|
406
|
+
instance knowledge files. It registers no source, worker or schedule.
|
|
408
407
|
Missing knowledge configuration is an error, never permission to bootstrap an
|
|
409
408
|
empty substitute.
|
|
410
409
|
- `oats.aweb` mints a messaging identity or, with
|
|
@@ -419,9 +418,10 @@ current, appends milestones to `log.md`, and captures non-obvious insights in
|
|
|
419
418
|
|
|
420
419
|
It consults accepted knowledge remotely, at its accepted state, with
|
|
421
420
|
`oats okf index`, `cat` and `search` (the `okf-consultation` skill), and never
|
|
422
|
-
writes accepted knowledge; this is instruction, not an OS sandbox.
|
|
423
|
-
|
|
424
|
-
proposes
|
|
421
|
+
writes accepted knowledge; this is instruction, not an OS sandbox. At each
|
|
422
|
+
knowledge checkpoint, an instance with a duty to propose judges its own notes
|
|
423
|
+
and proposes durable claims as one pull request (`oats okf propose`). See
|
|
424
|
+
[knowledge](knowledge.md).
|
|
425
425
|
|
|
426
426
|
### Spawning and coordinating with other agents
|
|
427
427
|
|
|
@@ -528,10 +528,21 @@ says what a clone carries and what it does not.
|
|
|
528
528
|
### Retire
|
|
529
529
|
|
|
530
530
|
Retirement runs active capability retire hooks in reverse spawn order before the home disappears. The aweb
|
|
531
|
-
integration deletes the instance identity here.
|
|
532
|
-
|
|
533
|
-
|
|
534
|
-
|
|
531
|
+
integration deletes the instance identity here. `oats.okf` captures nothing
|
|
532
|
+
at retirement: an instance proposes before it finishes, and for one that
|
|
533
|
+
retired without proposing, the operator proposes from its retirement recovery
|
|
534
|
+
copy ([the flow](knowledge.md#the-flow)). Retirement never waits for a model
|
|
535
|
+
or GitHub.
|
|
536
|
+
|
|
537
|
+
A spawn that is killed after its spawn hooks started and before it wrote the
|
|
538
|
+
home's record (SIGKILL, a container stop, a dropped connection) leaves a home
|
|
539
|
+
`oats retire` still cleans up: the spawn records, before its first spawn hook,
|
|
540
|
+
which retire hooks a retire must run, and the retire runs them before it
|
|
541
|
+
removes the home. A home whose record does not say which retire hooks to run,
|
|
542
|
+
and that has no such marker, is refused with `E_UNIDENTIFIED_INSTANCE_HOME`
|
|
543
|
+
and kept; `--force` removes it without running a hook, once what its
|
|
544
|
+
capabilities registered is cleaned up by hand
|
|
545
|
+
([A spawn in progress](capabilities.md#manifest)).
|
|
535
546
|
|
|
536
547
|
A retire hook's warning, such as an action someone must still take, is in the
|
|
537
548
|
retire's `warnings` and stays readable after the home is gone: each one is a
|
|
@@ -743,8 +754,9 @@ way.
|
|
|
743
754
|
failed: the retire refuses with `E_WORK_INSPECTION_FAILED` at its first
|
|
744
755
|
inspection, as for any [status that fails](#retire-status-fails), with
|
|
745
756
|
`--discard-worktree` and `--force` too. A spawn into a worktree of such a
|
|
746
|
-
repository is refused the same
|
|
747
|
-
|
|
757
|
+
repository is refused with the same code before its checkout and rolled
|
|
758
|
+
back ([a checkout runs no filter driver](#checkout-filter-drivers)). Remove
|
|
759
|
+
or rename the driver in the repository's configuration, then retry.
|
|
748
760
|
- A driver that the operator's global or system configuration defines is
|
|
749
761
|
the operator's own and runs with the operator's command, in the worktree
|
|
750
762
|
and in the recovery alike. That holds when the repository's configuration
|
|
@@ -752,7 +764,10 @@ way.
|
|
|
752
764
|
`git lfs install`): the repository's values for it are replaced by the
|
|
753
765
|
operator's, so a command the repository gives that name never runs. The
|
|
754
766
|
operator's configuration is the human's; the repository's is the agent's
|
|
755
|
-
to write.
|
|
767
|
+
to write. One case runs neither: the repository defines `process` for that
|
|
768
|
+
name and the operator's configuration does not. Git has no way to unset a
|
|
769
|
+
variable on its command line, and a `process` set to nothing turns the
|
|
770
|
+
driver's `clean` and `smudge` off with it, so the file is read unfiltered.
|
|
756
771
|
- The recovery has no local configuration, so it has none of the
|
|
757
772
|
repository's drivers. Its status must still be the worktree's, and for a
|
|
758
773
|
file such a filter applies to it can differ: the worktree reads an
|
|
@@ -1303,9 +1318,12 @@ leaves what happened on disk (OATS 0.53.0):
|
|
|
1303
1318
|
- **Its pending marker, only when the home is owed a retire:** when a retire
|
|
1304
1319
|
hook was started or the removal of the home began. The usual quarantine
|
|
1305
1320
|
marker is there too when hooks reported incomplete cleanup. The instance
|
|
1306
|
-
then
|
|
1307
|
-
|
|
1308
|
-
|
|
1321
|
+
is then owed a retire: `oats session start` answers
|
|
1322
|
+
`E_INSTANCE_RETIRING`, and `oats retire <instance>` continues. `oats
|
|
1323
|
+
instance stop --apply` is not refused: the completion has ended, so
|
|
1324
|
+
nothing holds the home against a stop
|
|
1325
|
+
([a completion that was killed](#self-retire-interrupted)). In every
|
|
1326
|
+
other case the completion removes its marker.
|
|
1309
1327
|
Nothing of the home was changed, so the instance is a stopped or a
|
|
1310
1328
|
running instance like any other: a start works, and a wake schedule may
|
|
1311
1329
|
start it. A session or a child that the completion stopped on its way
|
|
@@ -1313,6 +1331,29 @@ leaves what happened on disk (OATS 0.53.0):
|
|
|
1313
1331
|
- **One event,** `retire-refused`, which says which of the two it was
|
|
1314
1332
|
([Events](desktop-cli-api.md#retire-refused-event)).
|
|
1315
1333
|
|
|
1334
|
+
<a id="self-retire-interrupted"></a>**A completion that was killed** (a
|
|
1335
|
+
`SIGKILL`, a container that stopped, a reboot) leaves no outcome, and its
|
|
1336
|
+
pending marker stays. The marker names the completion by its pid, its start
|
|
1337
|
+
and its boot, and the rule is: a pending marker holds its home only while
|
|
1338
|
+
the completion it names can still act; once that completion is gone,
|
|
1339
|
+
`oats retire <instance>` takes the retire over and completes it,
|
|
1340
|
+
`oats session start` is refused with that command in its message, and a
|
|
1341
|
+
stop is not refused: `oats instance stop --apply`, the stop a retire makes
|
|
1342
|
+
of a recorded child, and the stop `oats host run` makes of every running
|
|
1343
|
+
home when the host stops all stop a session that still runs there, and the
|
|
1344
|
+
marker stays. A
|
|
1345
|
+
completion is gone when its process has ended, when its pid runs with
|
|
1346
|
+
another start, and when the marker was written in another boot, whatever
|
|
1347
|
+
its pid reads as there. `oats status` shows the row's `retire` as
|
|
1348
|
+
`interrupted`, and `oats doctor` lists the home. A start answers
|
|
1349
|
+
`E_INSTANCE_RETIRING`, `<instance> is owed a retire (its retire was
|
|
1350
|
+
interrupted): finish it with` and the retire to run, because the home is
|
|
1351
|
+
never started again: the completion may have run retire hooks before it
|
|
1352
|
+
was killed, and a start would bring back an instance whose identity is
|
|
1353
|
+
gone. A marker that names no completion (one an OATS before 0.51.0 wrote)
|
|
1354
|
+
refuses a start and a stop as before, since whether its retire runs cannot
|
|
1355
|
+
be told, and `oats retire <instance>` completes it.
|
|
1356
|
+
|
|
1316
1357
|
<a id="self-retire-hook-retry"></a>**A completion retries a cleanup that only
|
|
1317
1358
|
retire hooks left incomplete** (oats-project/oats#1747), because a provider's
|
|
1318
1359
|
failure is often transient. When the retire ends with the home quarantined,
|
|
@@ -1804,8 +1845,8 @@ after the capability injects (`injects/instance-boundary.md`):
|
|
|
1804
1845
|
soul's instructions, and `instance.json` `soulDir` records the (read-only,
|
|
1805
1846
|
per-commit) soul directory every hook and dispatched command receives as
|
|
1806
1847
|
`OATS_SOUL`. Durable soul edits go through tracked paths under `work/` under
|
|
1807
|
-
the applicable review rules.
|
|
1808
|
-
|
|
1848
|
+
the applicable review rules. A knowledge proposal changes the external
|
|
1849
|
+
knowledge base, never soul files or skills.
|
|
1809
1850
|
|
|
1810
1851
|
Agents move between the two as the task needs; the boundary is what each
|
|
1811
1852
|
directory is for, not a place to settle in.
|
|
@@ -1836,6 +1877,41 @@ a `--repo` that is not a clone of the soul's repository starts at its `HEAD`.
|
|
|
1836
1877
|
The spawn result and `instance.json` record the start point as
|
|
1837
1878
|
`base: {ref, oid}`.
|
|
1838
1879
|
|
|
1880
|
+
<a id="checkout-filter-drivers"></a>
|
|
1881
|
+
**A checkout runs no filter driver of the repository.** Every Git command
|
|
1882
|
+
OATS runs that writes a tree's files (the spawn's `git worktree add` here,
|
|
1883
|
+
and the `git worktree add` and `git switch` of
|
|
1884
|
+
[`oats worktree add`](#extra-trees)) runs with every filter driver the
|
|
1885
|
+
repository's own configuration defines overridden to no command, so a
|
|
1886
|
+
`filter.<name>.smudge` or `.process` command that configuration names is
|
|
1887
|
+
never run and a file carrying the `filter` attribute is written as its
|
|
1888
|
+
committed bytes. The read of the configuration, the override and their
|
|
1889
|
+
limits are [a retire's](#retire-filter-drivers).
|
|
1890
|
+
|
|
1891
|
+
- A driver that the operator's global or system configuration defines is
|
|
1892
|
+
the operator's own and runs. Git LFS set up with `git lfs install` is one:
|
|
1893
|
+
its files are checked out as before. A driver of that name in the
|
|
1894
|
+
repository's configuration is replaced by the operator's values.
|
|
1895
|
+
- A driver only the repository's configuration defines does not run. With
|
|
1896
|
+
Git LFS set up by `git lfs install --local` alone, a tree OATS checks out
|
|
1897
|
+
holds the pointer files, not their content: run `git lfs install` for the
|
|
1898
|
+
operator, or `git lfs pull` in the tree.
|
|
1899
|
+
- A driver whose name cannot be passed on Git's command line (it holds `=`
|
|
1900
|
+
or is not UTF-8) cannot be overridden, so Git is not run: the spawn is
|
|
1901
|
+
refused with `E_WORK_INSPECTION_FAILED` and rolled back, and
|
|
1902
|
+
`oats worktree add` with `E_GIT_FAILED`, its tree removed.
|
|
1903
|
+
|
|
1904
|
+
<a id="no-file-monitor"></a>
|
|
1905
|
+
**No file monitor.** Every Git command OATS runs that reads or writes a work
|
|
1906
|
+
tree's files or its index runs with `core.fsmonitor=false`, so a file
|
|
1907
|
+
monitor command the repository's configuration names is never run: these
|
|
1908
|
+
checkouts and the fetch of `oats worktree add` between its two,
|
|
1909
|
+
`oats worktree remove`, a retire and its recovery copy, the status a spawn's
|
|
1910
|
+
baseline is taken from, the reads of `oats instance git` and
|
|
1911
|
+
`oats instance diff`, and the check `oats package add|remove` makes that
|
|
1912
|
+
`oats-workspace.yaml` is tracked in the checkout that holds it. The clone's Git hooks (`post-checkout` among them) are not part of
|
|
1913
|
+
this: they run in a checkout as they do for the operator's own Git.
|
|
1914
|
+
|
|
1839
1915
|
After the spawn hooks succeed, the spawn fires the
|
|
1840
1916
|
[`worktree` event](capabilities.md#the-worktree-event) for `work/`: the
|
|
1841
1917
|
`worktree` hook of each capability the soul composes runs once, with `work/`
|
|
@@ -2033,6 +2109,10 @@ git -C <home>/.work-<p> fetch --refmap= origin <base>
|
|
|
2033
2109
|
git -C <home>/.work-<p> switch -c <branch> <the fetched commit>
|
|
2034
2110
|
```
|
|
2035
2111
|
|
|
2112
|
+
- Neither checkout (`worktree add`, `switch`) runs a filter driver the
|
|
2113
|
+
repository's configuration defines: the files are written as their
|
|
2114
|
+
committed bytes ([a checkout runs no filter
|
|
2115
|
+
driver](#checkout-filter-drivers)).
|
|
2036
2116
|
- The tree starts from the remote's current state, never from a local branch
|
|
2037
2117
|
of the clone, which may be stale. A fetch that fails is
|
|
2038
2118
|
`E_REMOTE_UNREADABLE`; a HEAD that is not the fetched commit is
|
|
@@ -2120,7 +2200,8 @@ owner read, write and search access, and keeps `.git` until all other entries
|
|
|
2120
2200
|
are deleted, so a failed deletion can be retried.
|
|
2121
2201
|
An unreadable branch or a failed inspection keeps the tree and record.
|
|
2122
2202
|
|
|
2123
|
-
`remove` runs no
|
|
2203
|
+
`remove` runs no file monitor the repository's configuration names
|
|
2204
|
+
([no file monitor](#no-file-monitor)), and no filter driver it defines
|
|
2124
2205
|
(`filter.<name>.clean`, `.process`): its own status of the tree, the clean
|
|
2125
2206
|
check inside `git worktree remove` and the comparison of an unregistered
|
|
2126
2207
|
tree's surviving files are each preceded by one read of that configuration,
|
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.
|
|
10
|
-
The 0.69.
|
|
9
|
+
The latest version is **OATS 0.69.16** ([release notes](release-notes/v0.69.16.md)).
|
|
10
|
+
The 0.69.16 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.
|
|
13
|
+
0.69.16,** 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.
|
|
23
|
-
npm install -g @awebai/oats@0.69.
|
|
22
|
+
# 0. where the Desktop is installed: Desktop 0.69.16 first
|
|
23
|
+
npm install -g @awebai/oats@0.69.16 # 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
|
```
|
|
@@ -204,6 +204,17 @@ of the Desktop and the CLI, and an optional package pin. A change a script
|
|
|
204
204
|
must follow is in its release's Upgrade section whether or not it is listed
|
|
205
205
|
here.
|
|
206
206
|
|
|
207
|
+
- **[0.69.16](release-notes/v0.69.16.md#upgrade):** the catalog pins
|
|
208
|
+
oats.okf 6.0.1, oats.aweb 1.39.0 and oats.framework 1.24.0. A deployment
|
|
209
|
+
that takes oats.okf 6 removes the harvester's launch preference and spawn
|
|
210
|
+
flags, adds the `proposal-review` trigger beside `harvest-review`, and
|
|
211
|
+
retires its harvesters; aw 1.36.56 is the tested aw; pi homes keep
|
|
212
|
+
@awebai/claude-skills out of their pi folder; the team agent image is
|
|
213
|
+
rebuilt.
|
|
214
|
+
- **[0.69.15](release-notes/v0.69.15.md#upgrade):** Node 22.5.0 or later
|
|
215
|
+
before the CLI; on a shared host, `chmod -R go-rwx` each turn-record root;
|
|
216
|
+
a record root is written from one machine at a time; release a schedule
|
|
217
|
+
slot an earlier OATS left without its record (`oats doctor` lists it).
|
|
207
218
|
- **[0.69.14](release-notes/v0.69.14.md#upgrade):** 0.69.13 was tagged but
|
|
208
219
|
never published, so its steps (below) are this release's; the remaining
|
|
209
220
|
state-changing commands refuse a flag they do not define.
|
|
@@ -290,7 +301,8 @@ here.
|
|
|
290
301
|
- **[0.57.0](release-notes/v0.57.0.md#upgrade):** a retire plan taken before
|
|
291
302
|
the upgrade is refused once (`E_PLAN_STALE`); `oats worktree remove` may
|
|
292
303
|
refuse with `E_CHILDREN_RUNNING`; with oats.okf 5.2.0, new spawns carry the
|
|
293
|
-
harvest duty unless the soul opts out.
|
|
304
|
+
harvest duty unless the soul opts out (oats.okf 6 makes it the duty to
|
|
305
|
+
propose: [knowledge.md](knowledge.md#pin-and-select-the-package)).
|
|
294
306
|
- **[0.56.0](release-notes/v0.56.0.md#upgrade):** new refusal codes for
|
|
295
307
|
scripts; `open-workspace` in `tui.json` is `open`; a launch gets only its
|
|
296
308
|
capabilities' declared environment.
|
|
@@ -571,6 +583,14 @@ an upgrade that is a lock directory left by the earlier OATS
|
|
|
571
583
|
`oats` is running on the machine
|
|
572
584
|
([The sweep](execution-targets.md#the-sweep)).
|
|
573
585
|
|
|
586
|
+
`oats doctor` reports a schedule slot whose record cannot be read as a
|
|
587
|
+
`schedule-slot-unreadable` problem, naming the deployment, the job and the
|
|
588
|
+
remedy. After an upgrade that is a slot directory an earlier OATS left
|
|
589
|
+
without its `owner.json`. The tick reports that job invalid and runs the
|
|
590
|
+
deployment's other jobs. Check `oats schedule show <id>`; once its last run
|
|
591
|
+
is not running, `oats schedule reconcile <id> --clear` releases the slot
|
|
592
|
+
([Schedules](schedules.md#files)).
|
|
593
|
+
|
|
574
594
|
## After a change of Node version
|
|
575
595
|
|
|
576
596
|
Two paths are written into things that outlive a command: the kernel's, and
|
package/docs/workspaces.md
CHANGED
|
@@ -54,8 +54,8 @@ 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.
|
|
58
|
-
oats.okf:
|
|
57
|
+
oats.framework: v1.24.0 # bare version → resolves through the official catalog
|
|
58
|
+
oats.okf: v6.0.1
|
|
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
|
package/lib/claim.mjs
CHANGED
|
@@ -241,9 +241,8 @@ export function claimUnheld(path, opts, otherwise) {
|
|
|
241
241
|
|
|
242
242
|
/** Whether the holder a claim record names can still act, as processLiveness answers it, for the
|
|
243
243
|
* caller whose refusals are `opts`: gone when its `holderGone` says so, whatever the process reads
|
|
244
|
-
* as. The one reading of a holder for taking a claim (takeClaim) and for reading one (claimUnheld)
|
|
245
|
-
|
|
246
|
-
export function holderLiveness(holder, opts) {
|
|
244
|
+
* as. The one reading of a holder for taking a claim (takeClaim) and for reading one (claimUnheld). */
|
|
245
|
+
function holderLiveness(holder, opts) {
|
|
247
246
|
return opts.holderGone?.(holder) ? { state: "gone" } : processLiveness(holder);
|
|
248
247
|
}
|
|
249
248
|
|
package/lib/command-flags.mjs
CHANGED
|
@@ -12,6 +12,7 @@ export const SYNC_USAGE = "usage: oats sync [--dir <deployment>] [--plan] [--jso
|
|
|
12
12
|
export const APPROVAL_REMOVED = "package approval was removed; declaring a package in packages: is the trust decision";
|
|
13
13
|
export const TEAMS_USAGE = "usage: oats teams [--json] | oats teams add <label> --team <id> [--description <d>] [--no-default] | oats teams remove <label> | oats teams default <label> [--if-absent | --expect <label>] [--dir <deployment>] [--json]";
|
|
14
14
|
export const SOUL_LAUNCH_USAGE = "oats soul launch set <soul>|'*' (--launch-config <name>|none | --harness pi|claude|codex [--model <id>]) [--plan] [--dir <deployment>] [--json] | oats soul launch remove <soul>|'*'|<exact key> [--plan] [--dir <deployment>] [--json]";
|
|
15
|
+
export const HOST_RUN_USAGE = "usage: oats host run [--stop-grace <seconds>] [--plan] [--json]";
|
|
15
16
|
export const WORKTREE_USAGE = "usage: oats worktree add --purpose <p> --branch <b> --base <remote-branch> [--repo <member key|clone path>] [--preview] [--json] | oats worktree remove --purpose <p> [--json]";
|
|
16
17
|
|
|
17
18
|
const WORKTREE_REFUSED = Object.freeze({
|
|
@@ -136,9 +137,10 @@ export const COMMAND_FLAGS = Object.freeze([
|
|
|
136
137
|
schedule("disable"),
|
|
137
138
|
schedule("reconcile", ["--clear"]),
|
|
138
139
|
{ command: "schedule tick", operands: [], values: SCHEDULE_VALUES, switches: ["--dry-run", "--host", "--json"], usage: "usage: oats schedule tick [--dry-run] [--host] [--dir <workspace> | --server <id>] [--json]" },
|
|
139
|
-
{ command: "schedule host install", operands: [], values: ["--max-concurrent", "--triggers-max-concurrent", "--os", ...SCHEDULE_VALUES], switches: ["--print", "--json"],
|
|
140
|
-
usage: "usage: oats schedule host install [--max-concurrent <N|default>] [--triggers-max-concurrent <N|none>] | --print [--os darwin|linux] [--dir <workspace> | --server <id>] [--json]" },
|
|
140
|
+
{ command: "schedule host install", operands: [], values: ["--max-concurrent", "--triggers-max-concurrent", "--os", ...SCHEDULE_VALUES], switches: ["--register-only", "--print", "--json"],
|
|
141
|
+
usage: "usage: oats schedule host install [--register-only] [--max-concurrent <N|default>] [--triggers-max-concurrent <N|none>] | --print [--os darwin|linux] [--dir <workspace> | --server <id>] [--json]" },
|
|
141
142
|
{ command: "schedule host uninstall", operands: [], values: SCHEDULE_VALUES, switches: ["--json"], usage: "usage: oats schedule host uninstall [--dir <workspace> | --server <id>] [--json]" },
|
|
143
|
+
{ command: "host run", operands: [], values: ["--stop-grace"], switches: ["--plan", "--json"], usage: HOST_RUN_USAGE },
|
|
142
144
|
{ command: "trigger add", operands: [], values: ["--file", "--from", "--set", "--id", "--description", "--workspace", "--runs-on", "--owner", "--dir"], switches: ["--json"],
|
|
143
145
|
usage: "usage: oats trigger add (--file <trigger.json> | --from <package>:<template> [--set <name>=<value>]… [--id <id>]) [--description=<text>] [--workspace <member> --runs-on <host> --owner <host>/<login>] [--dir <deployment>] [--json]" },
|
|
144
146
|
{ command: "trigger poll", operands: ["id"], values: ["--dir", "--max-age"], switches: TRIGGER_RUN_SOURCE, usage: "usage: oats trigger poll <id> --run-source [--max-age <s>] [--dir <deployment>] [--json]" },
|