@awebai/oats 0.47.0 → 0.49.0
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/bin/oats.mjs +293 -41
- package/docs/capabilities.md +264 -8
- package/docs/capability-manifest.schema.json +18 -5
- package/docs/configuration.md +7 -1
- package/docs/desktop-cli-api.md +439 -40
- package/docs/desktop.md +72 -5
- package/docs/execution-targets.md +19 -1
- package/docs/implementation.md +81 -1
- package/docs/integrations.md +7 -5
- package/docs/knowledge.md +167 -197
- package/docs/official-catalog.md +6 -5
- package/docs/packages.md +14 -14
- package/docs/release-notes/v0.48.0.md +106 -0
- package/docs/release-notes/v0.49.0.md +770 -0
- package/docs/schedules.md +62 -39
- package/docs/servers.md +7 -0
- package/docs/souls-and-instances.md +395 -52
- package/docs/workspaces.md +18 -3
- package/injects/work-checkout.md +17 -11
- package/injects/work-worktree.md +19 -13
- package/lib/capability-contract.mjs +100 -11
- package/lib/capability-show.mjs +5 -2
- package/lib/core.mjs +1147 -319
- package/lib/instance-events.mjs +6 -3
- package/lib/instance-git.mjs +11 -5
- package/lib/instance-inspect.mjs +14 -3
- package/lib/instance-lifecycle.mjs +106 -16
- package/lib/instance-resolution.mjs +15 -3
- package/lib/launch-prompt-policy.mjs +17 -3
- package/lib/packages.mjs +1 -0
- package/lib/real-path.mjs +27 -0
- package/lib/resolve.mjs +4 -4
- package/lib/retire-output.mjs +6 -1
- package/lib/schedule.mjs +1 -0
- package/lib/servers.mjs +32 -6
- package/lib/teams-verbs.mjs +40 -9
- package/lib/tree-copy.mjs +18 -7
- package/lib/triggers.mjs +201 -65
- package/lib/workspace.mjs +20 -5
- package/lib/worktree-hooks.mjs +392 -0
- package/lib/worktree.mjs +655 -0
- package/package-catalog.json +12 -5
- package/package.json +1 -1
- package/skills/oats-getting-started/SKILL.md +1 -1
|
@@ -0,0 +1,106 @@
|
|
|
1
|
+
# OATS 0.48.0
|
|
2
|
+
|
|
3
|
+
2026-10-08
|
|
4
|
+
|
|
5
|
+
## Added
|
|
6
|
+
|
|
7
|
+
- **Conditional team default and mapping-only add (#771), feature
|
|
8
|
+
`teams-conditional-default`.** `oats teams default <label> --if-absent`
|
|
9
|
+
sets the local default only where the deployment has no effective default;
|
|
10
|
+
`--expect <label0>` only where the effective default (local, or inherited
|
|
11
|
+
from the workspace) is `<label0>`. A failed condition is
|
|
12
|
+
`E_TEAM_DEFAULT_MISMATCH {expected, observed}` and writes nothing.
|
|
13
|
+
`oats teams add <label> --team <id> --no-default` writes the mapping without
|
|
14
|
+
touching `defaultTeam`; the same label and id already declared is reuse
|
|
15
|
+
(`changed: false, reused: true`). `E_TEAM_EXISTS` also carries `observed:
|
|
16
|
+
{label, team, from}`. Every `oats teams` write holds
|
|
17
|
+
`<deployment>/.agents/locks/local.lock`, so the later of two racing
|
|
18
|
+
conditional writes sees the earlier one and refuses with
|
|
19
|
+
`E_TEAM_DEFAULT_MISMATCH`; a lock still held after 5 s is `E_LOCAL_BUSY`,
|
|
20
|
+
with nothing written. `teamsApi`
|
|
21
|
+
stays 2: the `oats teams --json` shape is unchanged. Callers check the
|
|
22
|
+
feature before passing the flags, because older kernels ignore them, and
|
|
23
|
+
there `--if-absent` is an unconditional set.
|
|
24
|
+
|
|
25
|
+
## Changed
|
|
26
|
+
|
|
27
|
+
- **The Desktop accepts OATS CLIs `>=0.25.8 <0.49.0`.** The compatibility band
|
|
28
|
+
admits 0.48; existing feature gates remain unchanged.
|
|
29
|
+
|
|
30
|
+
- **`oats teams` refuses flags it does not take.** Each form (`oats teams`,
|
|
31
|
+
`add`, `remove`, `default`) answers an unknown flag with `E_USAGE {flag}`,
|
|
32
|
+
naming it and the usage, before anything is read or written. Before, they
|
|
33
|
+
were ignored. `--server` on `oats teams` is now refused too: teams has never
|
|
34
|
+
been routed to a server. A script that passes stray flags must drop them.
|
|
35
|
+
|
|
36
|
+
- **The workspace pins oats.framework 1.8.0 and oats.engineering 1.9.0.**
|
|
37
|
+
The official catalog resolves bare `oats.framework` versions to
|
|
38
|
+
`oats-framework/v1.8.0` (oats.support 1.0.0, the support desk role), and
|
|
39
|
+
`oats.engineering` to `v1.9.0`. That adds oats.maintainer's
|
|
40
|
+
`/support-maintainer` skill: a maintainer that serves the support desk's
|
|
41
|
+
tickets. The capability mirrors under `mirrors/` are regenerated from the
|
|
42
|
+
v1.9.0 tag and their trees equal the tag's. Running instances keep what
|
|
43
|
+
they were spawned with; new spawns pick these up after `oats sync`.
|
|
44
|
+
|
|
45
|
+
- **The workspace and official catalog pin oats.aweb 1.23.2.** The generated
|
|
46
|
+
`mirrors/oats-aweb` payload equals the provider v1.23.2 tag tree. This adds
|
|
47
|
+
verified LOCAL join mapping/default readback and explicit LOCAL identity
|
|
48
|
+
selectors at launch and preview (1.23.1), and GLOBAL grant metadata that
|
|
49
|
+
records the app snapshot from each successful native mint receipt: Comms
|
|
50
|
+
labels it as the at-spawn snapshot, inspect shows the current recorded
|
|
51
|
+
metadata, and preview warnings say whether it is retained or unknown
|
|
52
|
+
pending renewal (1.23.2). That snapshot is not a live app acceptance. Existing captured homes
|
|
53
|
+
do not adopt the changes automatically; this pin does not perform sync,
|
|
54
|
+
restart or live acceptance.
|
|
55
|
+
|
|
56
|
+
- **oats.apps 1.0.0 is a new official package.** It exports `oats.folio` and
|
|
57
|
+
`oats.library`, additive guidance capabilities for the aweb Folio and Library
|
|
58
|
+
apps (`aw >=1.36.26`; OATS 0.47.0 or later), and the catalog aliases both
|
|
59
|
+
ids to the package. The generated `mirrors/oats-folio` and
|
|
60
|
+
`mirrors/oats-library` equal the v1.0.0 tag's payload trees. The workspace
|
|
61
|
+
adds `awebai/oats-apps` as a member (its expert soul `oats-apps-expert`) and
|
|
62
|
+
pins `oats.apps: git:github.com/awebai/oats-apps@v1.0.0`: an installed CLI
|
|
63
|
+
resolves bare versions through the catalog it shipped with, and 0.47.0's has
|
|
64
|
+
no `oats.apps`, so the pin goes bare once every deployment's CLI carries
|
|
65
|
+
this entry. No soul selects either capability yet, and no workspace default
|
|
66
|
+
is added.
|
|
67
|
+
|
|
68
|
+
## Fixed
|
|
69
|
+
|
|
70
|
+
- **Every `oats retire` stops recorded children first, as its plan says
|
|
71
|
+
(#778).** `oats retire <name> --plan` has always said that recorded child
|
|
72
|
+
instances "are stopped first (bounded SIGTERM, never escalated) and
|
|
73
|
+
retained" and that "a child still running after the grace refuses the
|
|
74
|
+
retirement", but before 0.48.0 only the guarded apply (`--plan-revision`
|
|
75
|
+
with `--idempotency-key`, what the Desktop sends) did it. A plain
|
|
76
|
+
`oats retire <name>` and a `--self` retirement left the children running,
|
|
77
|
+
attached ones on a work tree that had just been removed, with no stop
|
|
78
|
+
event.
|
|
79
|
+
- **Behavior change.** A plain `oats retire` and `--self` now stop recorded
|
|
80
|
+
children first and keep them. They refuse, retiring nothing, when one
|
|
81
|
+
won't stop or its session can't be established: `E_CHILDREN_RUNNING
|
|
82
|
+
{childrenStopped}`, exit 1, and the text names each child and its code
|
|
83
|
+
(`children still running: <name> (<code>); nothing retired`). `--force`
|
|
84
|
+
does not bypass it: end the child's session yourself (the receipt's
|
|
85
|
+
`stillRunning` names its processes), then retry.
|
|
86
|
+
- The receipt lists the children as `childrenStopped[]` (absent when there
|
|
87
|
+
are none), and the text prints `child <name>: stopped` or
|
|
88
|
+
`already idle` for each.
|
|
89
|
+
- `--self` stops the children recorded when the retirement was scheduled
|
|
90
|
+
(skipping any retired since), in its detached completion before it stops
|
|
91
|
+
the caller. A refusal leaves the caller's window and home in place and
|
|
92
|
+
writes `E_CHILDREN_RUNNING` with `childrenStopped` and the `retry` command
|
|
93
|
+
to the result file that `oats status` reports.
|
|
94
|
+
- The guarded apply is unchanged for the Desktop. It now stops children
|
|
95
|
+
only after the retire's own read-only refusals, so a retire refused
|
|
96
|
+
there leaves its children running.
|
|
97
|
+
|
|
98
|
+
- **A home without its session receipt says what was looked for and what to
|
|
99
|
+
do (#762).** `session inspect`, `start` and `restart` refused such a home
|
|
100
|
+
with a bare `ENOENT`. The `E_RUNTIME_ENDPOINT_UNKNOWN` refusal now names
|
|
101
|
+
the receipt path it looked for, says to address the home exactly as
|
|
102
|
+
`oats status` prints it (a different spelling of the path looks for the
|
|
103
|
+
receipt elsewhere), and otherwise names the causes and the remedy: stop its
|
|
104
|
+
session yourself if one runs, then `oats retire <name> --plan` and
|
|
105
|
+
`oats retire <name>`, and respawn. The code is unchanged. The receipt's key
|
|
106
|
+
for a differently spelled path is #780.
|