@awebai/oats 0.48.0 → 0.50.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 +326 -28
- package/docs/capabilities.md +425 -8
- package/docs/capability-manifest.schema.json +60 -5
- package/docs/configuration.md +103 -0
- package/docs/desktop-cli-api.md +542 -47
- package/docs/desktop.md +85 -5
- package/docs/execution-targets.md +50 -9
- package/docs/implementation.md +74 -1
- package/docs/integrations.md +7 -5
- package/docs/knowledge.md +167 -197
- package/docs/official-catalog.md +4 -4
- package/docs/packages.md +28 -14
- package/docs/release-lane.md +41 -0
- package/docs/release-notes/v0.49.0.md +770 -0
- package/docs/release-notes/v0.50.0.md +279 -0
- package/docs/schedules.md +289 -53
- package/docs/servers.md +7 -0
- package/docs/souls-and-instances.md +450 -60
- package/docs/workspaces.md +3 -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 +18 -2
- package/lib/core.mjs +1374 -394
- package/lib/instance-events.mjs +9 -10
- package/lib/instance-git.mjs +19 -10
- package/lib/instance-inspect.mjs +58 -18
- 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/refused-text.mjs +17 -0
- package/lib/resolve.mjs +4 -4
- package/lib/retained-after-retire.mjs +387 -0
- package/lib/retire-output.mjs +6 -1
- package/lib/schedule.mjs +9 -2
- package/lib/servers.mjs +32 -6
- package/lib/tree-copy.mjs +18 -7
- package/lib/trigger-sources.mjs +234 -0
- package/lib/triggers.mjs +705 -108
- package/lib/workspace.mjs +20 -5
- package/lib/worktree-hooks.mjs +392 -0
- package/lib/worktree.mjs +655 -0
- package/package-catalog.json +3 -3
- package/package.json +1 -1
- package/skills/oats-getting-started/SKILL.md +1 -1
package/docs/release-lane.md
CHANGED
|
@@ -216,3 +216,44 @@ re-checks a published inventory against the source and its origin; it attests
|
|
|
216
216
|
what the remote advertised when queried, so released tags must never move.
|
|
217
217
|
`--generate --source <clone>` captures a working tree for development and
|
|
218
218
|
always records `release.status: pending`.
|
|
219
|
+
|
|
220
|
+
## Releasing `oats.framework`
|
|
221
|
+
|
|
222
|
+
The distribution package in `oats-package/` (`oats.core`, `oats.setup`,
|
|
223
|
+
`oats.support`, `oats.knowledge-theory`) is not published by `release.yml` or
|
|
224
|
+
by this lane. A deployment takes it from this repository at the tag
|
|
225
|
+
`oats-framework/v<version>`, through the catalog ref or its workspace pin. A
|
|
226
|
+
skill changed under `oats-package/` therefore reaches deployments only when
|
|
227
|
+
that tag moves, whatever kernel version carried the change.
|
|
228
|
+
|
|
229
|
+
**A kernel release whose pull requests touched `oats-package/` ships a
|
|
230
|
+
framework release with it.** To see whether one is owed:
|
|
231
|
+
|
|
232
|
+
```bash
|
|
233
|
+
git diff --stat "$(git describe --tags --abbrev=0 --match 'oats-framework/v*' origin/main)" origin/main -- oats-package
|
|
234
|
+
```
|
|
235
|
+
|
|
236
|
+
When the diff is not empty:
|
|
237
|
+
|
|
238
|
+
1. **The framework prep PR.** Bump `version` in the `oats.json` of each
|
|
239
|
+
changed capability and in `oats-package/oats-package.json`, and add the
|
|
240
|
+
release-notes entry. Read the skill lines added since the last tag: a
|
|
241
|
+
command or behaviour that an older kernel the capability still admits does
|
|
242
|
+
not have names the version it starts in. Guidance text alone does not
|
|
243
|
+
raise a capability's `compatibility.oats`.
|
|
244
|
+
2. **The tag.** After the PR merges, put the annotated tag
|
|
245
|
+
`oats-framework/v<version>` on its merge commit and push it. No workflow
|
|
246
|
+
runs on this tag.
|
|
247
|
+
3. **The pin**, in the kernel release-prep PR: `package-catalog.json`
|
|
248
|
+
(`ref`), `oats-workspace.yaml`, and the version literals in
|
|
249
|
+
`docs/official-catalog.md`, `docs/packages.md`, `docs/workspaces.md`,
|
|
250
|
+
`skills/oats-getting-started/SKILL.md` and
|
|
251
|
+
`test/release-packaging.test.mjs`. The pin does not ride the first PR:
|
|
252
|
+
the tag needs the bumped manifest on `main` first, and CI reads the
|
|
253
|
+
catalog's ref from the remote. Two tests in
|
|
254
|
+
`test/hook-events-forward-tolerant.test.mjs` sync a deployment that takes
|
|
255
|
+
the official catalog's packages, so the pin's CI fails with
|
|
256
|
+
`E_REMOTE_UNREADABLE` until the tag is pushed. (The clean-room smoke does
|
|
257
|
+
not read it: it tags its own copy of `oats-package/`.) A green CI proves
|
|
258
|
+
that the tag exists, not which commit it names: the pin's reviewer
|
|
259
|
+
confirms on the remote that it names the first PR's merge commit.
|