@awebai/oats 0.51.0 → 0.52.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/README.md +1 -0
- package/bin/oats.mjs +109 -37
- package/docs/capabilities.md +9 -2
- package/docs/configuration.md +134 -88
- package/docs/desktop-cli-api.md +927 -92
- package/docs/desktop-instance-start.md +56 -0
- package/docs/desktop.md +10 -7
- package/docs/execution-targets.md +144 -58
- package/docs/first-team.md +3 -1
- package/docs/harness-trust.md +50 -2
- package/docs/implementation.md +66 -9
- package/docs/integrations.md +9 -8
- package/docs/knowledge-reference/acceptance.md +1 -0
- package/docs/knowledge-reference/harvester.md +5 -3
- package/docs/knowledge-reference/model.md +5 -3
- package/docs/knowledge-theory.md +1 -1
- package/docs/knowledge.md +25 -2
- package/docs/launch-prompt-completion.md +50 -48
- package/docs/oats-local.schema.json +4 -3
- package/docs/official-catalog.md +4 -4
- package/docs/packages.md +14 -14
- package/docs/release-lane.md +15 -5
- package/docs/release-notes/v0.44.0.md +1 -1
- package/docs/release-notes/v0.52.0.md +933 -0
- package/docs/schedules.md +91 -4
- package/docs/souls-and-instances.md +95 -25
- package/docs/tui.md +152 -0
- package/docs/workspaces.md +2 -2
- package/lib/claim.mjs +186 -46
- package/lib/core.mjs +730 -185
- package/lib/errors.mjs +170 -0
- package/lib/harness-trust-write.mjs +68 -27
- package/lib/harness-trust.mjs +34 -16
- package/lib/instance-inspect.mjs +40 -11
- package/lib/instance-lifecycle.mjs +169 -47
- package/lib/launch-preference.mjs +16 -0
- package/lib/launch-prompt-completion.mjs +7 -43
- package/lib/launch-prompt-evidence.mjs +14 -7
- package/lib/launch-prompt-fixtures/README.md +86 -152
- package/lib/launch-prompt-fixtures/dev-channel-confirmation.json +50 -0
- package/lib/launch-prompt-fixtures.mjs +122 -109
- package/lib/launch-prompt-transport.mjs +2 -56
- package/lib/launch-prompts.mjs +102 -100
- package/lib/schedule-host.mjs +154 -22
- package/lib/schedule.mjs +73 -24
- package/lib/system-tools.mjs +39 -0
- package/lib/tmux-server-scope.mjs +62 -0
- package/lib/triggers.mjs +4 -4
- package/lib/workspace.mjs +5 -11
- package/lib/worktree-hooks.mjs +98 -20
- package/lib/worktree.mjs +83 -24
- package/package-catalog.json +3 -3
- package/package.json +7 -2
- package/packages/client/capability-show-contract.mjs +230 -0
- package/packages/client/capability-warnings-contract.mjs +57 -0
- package/packages/client/cli-adapter.mjs +548 -0
- package/packages/client/cli-environment.mjs +53 -0
- package/packages/client/cli-locator.mjs +253 -0
- package/packages/client/cli-probe-contract.mjs +47 -0
- package/packages/client/client-terms.mjs +60 -0
- package/packages/client/deployment-contract.mjs +68 -0
- package/packages/client/deployment-data.mjs +483 -0
- package/packages/client/deployment-facts.mjs +34 -0
- package/packages/client/deployment-label.mjs +76 -0
- package/packages/client/deployment-observer.mjs +89 -0
- package/packages/client/deployment-panel.mjs +142 -0
- package/packages/client/deployment-read-cli.mjs +53 -0
- package/packages/client/display-text.mjs +44 -0
- package/packages/client/harness-names.mjs +30 -0
- package/packages/client/inspect-contract.mjs +62 -0
- package/packages/client/instance-acts.mjs +54 -0
- package/packages/client/instance-admission.mjs +45 -0
- package/packages/client/instance-events-contract.mjs +74 -0
- package/packages/client/instance-git-contract.mjs +80 -0
- package/packages/client/instance-presentation.mjs +22 -0
- package/packages/client/instance-tree.mjs +453 -0
- package/packages/client/kernel-environment.mjs +11 -0
- package/packages/client/launch-contract.mjs +51 -0
- package/packages/client/launch-prompt-outcome.mjs +165 -0
- package/packages/client/lifecycle-cli.mjs +61 -0
- package/packages/client/lifecycle-contract.mjs +372 -0
- package/packages/client/liveness-main.mjs +10 -0
- package/packages/client/liveness.mjs +35 -0
- package/packages/client/machine-contract.mjs +123 -0
- package/packages/client/own-environment.mjs +22 -0
- package/packages/client/panel-views.mjs +286 -0
- package/packages/client/readiness-contract.mjs +172 -0
- package/packages/client/refresh-loop.mjs +52 -0
- package/packages/client/remote-address.mjs +126 -0
- package/packages/client/remote-roster.mjs +67 -0
- package/packages/client/roster-sections.mjs +80 -0
- package/packages/client/spawn-apply-cli.mjs +104 -0
- package/packages/client/spawn-apply-contract.mjs +183 -0
- package/packages/client/spawn-decision.mjs +46 -0
- package/packages/client/spawn-messages.mjs +119 -0
- package/packages/client/spawn-preview-cli.mjs +32 -0
- package/packages/client/spawn-preview-contract.mjs +314 -0
- package/packages/client/team-members.mjs +41 -0
- package/packages/client/team-rows.mjs +45 -0
- package/packages/client/terminal-contract.mjs +57 -0
- package/packages/client/tmux-status.mjs +66 -0
- package/packages/client/waiting-on-you.mjs +88 -0
- package/packages/client/workspace-admission.mjs +45 -0
- package/packages/client/workspace-cli.mjs +142 -0
- package/packages/client/workspace-views.mjs +147 -0
- package/packages/tui/README.md +46 -0
- package/packages/tui/bin/tui.mjs +7 -0
- package/packages/tui/lib/actions.mjs +29 -0
- package/packages/tui/lib/client.mjs +4 -0
- package/packages/tui/lib/main.mjs +105 -0
- package/packages/tui/lib/term/keys.mjs +323 -0
- package/packages/tui/lib/term/screen.mjs +122 -0
- package/packages/tui/lib/term/style.mjs +43 -0
- package/packages/tui/lib/term/text.mjs +49 -0
- package/packages/tui/lib/term/tty.mjs +168 -0
- package/packages/tui/lib/term/width.mjs +124 -0
- package/packages/tui/lib/views/frame.mjs +62 -0
- package/packages/tui/lib/views/help.mjs +28 -0
- package/packages/tui/package.json +8 -0
- package/skills/oats-getting-started/SKILL.md +29 -22
- package/lib/launch-prompt-fixtures/claude-2.1.289-darwin-arm64/frame-05-channel-seeded.txt +0 -35
- package/lib/launch-prompt-fixtures/claude-2.1.289-darwin-arm64/frame-06-first-after-channel.txt +0 -35
- package/lib/launch-prompt-fixtures/claude-2.1.289-darwin-arm64/frame-07-after-channel-200ms.txt +0 -35
- package/lib/launch-prompt-fixtures/claude-2.1.289-darwin-arm64/frame-08-installed-after-channel-200ms.txt +0 -35
- package/lib/launch-prompt-fixtures/claude-2.1.289-darwin-arm64/manifest.json +0 -77
- package/lib/launch-prompt-fixtures/claude-2.1.289-darwin-arm64/max-bypass-source.json +0 -88
- package/lib/launch-prompt-fixtures/structural-completion.json +0 -205
- package/lib/launch-prompt-policy.mjs +0 -87
package/docs/implementation.md
CHANGED
|
@@ -10,7 +10,18 @@ reference pages ([workspaces](workspaces.md), [souls and instances](souls-and-in
|
|
|
10
10
|
- **`@awebai/oats`**: the runtime-neutral kernel (`lib/`), the `oats` CLI
|
|
11
11
|
(`bin/oats.mjs`), the kernel and work-mode instruction sources
|
|
12
12
|
(`injects/`), the bootstrap skills, the docs and the official package
|
|
13
|
-
catalog (`package-catalog.json`).
|
|
13
|
+
catalog (`package-catalog.json`). The same tarball carries two
|
|
14
|
+
dependency-free packages of this repository, the turn record
|
|
15
|
+
(`packages/record/`, behind `oats capture`, `recall` and `setup`) and the
|
|
16
|
+
terminal client (`packages/tui/`, behind `oats tui`, a preview:
|
|
17
|
+
[tui.md](tui.md)), and the directory of readers the terminal client shares
|
|
18
|
+
with the Desktop (`packages/client/`, below), which has no dependency
|
|
19
|
+
either. None of their tests is packed. The package's
|
|
20
|
+
manifest declares three runtime dependencies: `yaml` (the kernel reads and
|
|
21
|
+
writes the configuration files with it), `croner` (schedule expressions) and
|
|
22
|
+
`@awebai/pi` (pi's aweb messaging extension). The terminal client adds none
|
|
23
|
+
and may never add one: with a dependency it could no longer ship in this
|
|
24
|
+
tarball.
|
|
14
25
|
- **`@awebai/oats-pi`** (`packages/pi/`): a thin pi adapter that exposes an
|
|
15
26
|
instance's own resources. It registers no agent tools.
|
|
16
27
|
- **`oats.framework`** (`oats-package/`): the `oats.core`, `oats.setup`,
|
|
@@ -25,6 +36,15 @@ dependency-free localhost server; it is released with the kernel but not
|
|
|
25
36
|
published to npm. Its developer docs are in
|
|
26
37
|
[`packages/desktop/README.md`](../packages/desktop/README.md).
|
|
27
38
|
|
|
39
|
+
`packages/client/` holds the readers of the kernel's JSON that the kernel's
|
|
40
|
+
clients share: the CLI adapters and contract decoders the Desktop imports by
|
|
41
|
+
relative path and ships beside its `app.asar`, and what a client decides from
|
|
42
|
+
the kernel's rows alone (the roster as a tree, which acts a row offers). It is
|
|
43
|
+
a flat directory of `.mjs` modules with no manifest of its own, not a package.
|
|
44
|
+
`test/client-boundary.test.mjs` holds who may import what: the directory
|
|
45
|
+
imports only itself and `node:` builtins, `lib/` and `bin/` import nothing
|
|
46
|
+
from it, and the test lists the stable surface a second client may import.
|
|
47
|
+
|
|
28
48
|
## Repository layout
|
|
29
49
|
|
|
30
50
|
| path | contents |
|
|
@@ -38,7 +58,7 @@ published to npm. Its developer docs are in
|
|
|
38
58
|
| `oats-package/` | the `oats.framework` package |
|
|
39
59
|
| `souls/` | this repository's own souls (a workspace member) |
|
|
40
60
|
| `docs/` | the reference pages, schemas, design records and release notes |
|
|
41
|
-
| `packages/` | the pi adapter, the Desktop, the turn-record package and experiments |
|
|
61
|
+
| `packages/` | the pi adapter, the Desktop, the terminal client (`tui/`), the readers both clients share (`client/`), the turn-record package and experiments |
|
|
42
62
|
| `scripts/` | the test runner, validators, packaging checks and the release lane |
|
|
43
63
|
| `test/` | the kernel and CLI suites, with their fixtures |
|
|
44
64
|
|
|
@@ -53,7 +73,7 @@ published to npm. Its developer docs are in
|
|
|
53
73
|
| `packages.mjs` | `packages:`, the catalog, `oats sync`, `oats-lock.json` |
|
|
54
74
|
| `capability-show.mjs` | `oats capabilities show`: one catalog row's inject and skill files, read at its commit |
|
|
55
75
|
| `materialize.mjs` | copying modules into a home and composing it |
|
|
56
|
-
| `core.mjs` | spawn, retire, sessions, hooks, launch recipes, instance metadata |
|
|
76
|
+
| `core.mjs` | spawn, retire, sessions, hooks, launch recipes, instance metadata. A home's record (`instance.json`) is read with `readHomeRecord`, which never throws: a record, an absent one, or one that is there and cannot be read, with the reason. Code that walks other homes (the listing, a retire's lineage repair) uses it, so that one home's record decides only for that home; `identifiedHomeRecord` is the one refusal (`E_UNIDENTIFIED_INSTANCE_HOME`) a lifecycle verb makes when it has resolved its home: `resolveRetireHome`, `startInstanceSession`, and `resolveTarget` in `instance-lifecycle.mjs` for the stop and retire plans. A plan reads its own home's record with `targetRecord` (the same refusal) and any other home's with `otherRecord` (absent or unreadable: nobody's parent or child) |
|
|
57
77
|
| `instruction-composition.mjs` | the generated `AGENTS.md`; `renderInstructionParts` is the span-reporting renderer (`renderInstructionText` is its text) |
|
|
58
78
|
| `soul-composition.mjs` | the instructions a spawn of a soul would write, composed without a spawn (kernel half + materialize into a scratch home): the one path behind `doctor --soul` and `inspect --soul --instructions` |
|
|
59
79
|
| `teams.mjs`, `teams-verbs.mjs` | the team model and the `oats teams` verbs |
|
|
@@ -65,18 +85,21 @@ published to npm. Its developer docs are in
|
|
|
65
85
|
| `operator-coverage.mjs` | whether a soul the workspace offers composes `oats.setup`, for the workspace and each team (readiness and doctor warnings), and the cache-only remote offline doctor resolves through |
|
|
66
86
|
| `instance-*.mjs` | inspection, lifecycle, events and Git views of an instance |
|
|
67
87
|
| `worktree.mjs` | `oats worktree add\|remove`: an instance's extra trees (`.work-<purpose>`), their records (`.oats/trees/`), argument checks before any write, and the rollback of an interrupted add |
|
|
68
|
-
| `
|
|
69
|
-
| `
|
|
88
|
+
| `errors.mjs` | `oatsError`, and the door of the lifecycle verbs: `isKernelCode` (the shape of a kernel code, `^E_[A-Z0-9_]+$`, never a list of codes), `kernelCode`, `asKernelError` and `errorCause`. An answer of `oats retire`, `oats instance stop`, `oats session` and `oats worktree` carries a kernel code, or one of the two names every command answers as they are (`OWN_NAME_FAILURES`: `unsafe-config-key`, `unsafe-config-value`), and no other: `isAnswerCode` is what the door and its wrappers keep, `isKernelCode` stays the test of the shape. An error of the system's or of Node's, a refusal written as a plain `Error` without a code, and a defect (`isDefect`: a `TypeError` and its like without a code, or a thrown value that is no `Error`), is wrapped at the boundary (`bin/oats.mjs` `lifecycleFail`; in a retire, `core.mjs` `retireClaimed`, which also says what the retire had done by then) and its own code goes to `details.cause` (a defect's name does; a plain `Error` without a code has no cause, and is answered with the general code and its message alone, which is what an ordinary refusal of `tmux`, `git` or the kernel itself must read as). New code that answers an error tests the shape with these, never `e.code \|\| "E_…"`: a system error has a `code` too. Whoever ends an error's way up prints the stack of a defect with `reportDefect`: the door, and any code that turns a caught error into a row of results (a stop's `results[]`, a retire's `childrenStopped[]`), after which nobody else can. Two more rules of the lifecycle verbs live here. **`lifecycleBusy(holder, said, remedy, details)` is the only way `E_LIFECYCLE_BUSY` is made** (`test/lifecycle-busy-holder.test.mjs` scans `lib/` and `bin/` for any other): it sets `details.holder` (`BUSY_HOLDERS`: `"running"` only where the kernel established that the other command is alive, `"unknown"`, `"none"`) and refuses to build an `"unknown"` or `"none"` answer without the step that ends it. **`BEFORE_EFFECT_CODES` lists, per verb, the codes that verb answers only before any effect**; `afterFirstEffect` turns a listed code raised after a verb's first effect into a defect (`E_LIFECYCLE_FAILED`, `cause.name: "LateRefusal"`), and is called at the one place of each verb that knows how far it got (`core.mjs` `retireFailure`, from `at.phase`; `instance-lifecycle.mjs` `applyStop`, from whether a target's stop began). A code may join the list only when every place that raises it in that verb is before the first effect; a place found after it gets a code of its own, never the net |
|
|
89
|
+
| `claim.mjs` | the claim: one file naming, by pid and start time, the process doing something that happens once at a time; taken over when its holder is verifiably gone, never when that cannot be read. Synchronous. Held by `oats worktree add\|remove` per purpose (`worktree.mjs`), and per home by `oats retire` and `oats instance stop --apply` (`core.mjs` `claimHomeFor`: the one way a verb takes a home's lifecycle claim; the record names the holder's verb, `action`, from the instant the file exists, through the `facts` option of `acquireClaim`). A verb that only reads the home's claim (`oats worktree add`; a stop plan's `retiring` and `stopPending`) uses `homeClaimHolder` or `refuseBesideRetire`. The refusals of every pair (arriving verb, holder's verb) are built in one place, `core.mjs` `lifecycleClaimRefusals`; the pair table of `docs/desktop-cli-api.md` is walked by `test/lifecycle-pair-table.test.mjs`. A new verb that must not run beside a retire takes the claim through `claimHomeFor`, joins `CLAIM_VERBS` and adds its row and column there. Its loop has one rule: every pass that does not take the claim falls through one check of its time and one pause, so no state of the path makes it spin. Each caller words the refusals (`busy`, `unreadableClaim`, `cannotTakeOver`, `heldAgain`, `ownStartUnreadable`), and is handed with each what the acquisition's takeovers ended before it (`ended`): it writes "nothing else was done" then, and the answer is `E_LIFECYCLE_FAILED`, what was ended first (`errors.mjs` `nothingAfter`, `afterEndedSteps`; `lifecycleBusy` takes `ended`). No message is rewritten after it was made. A claim is read back as whatever is in its file, which others than its writer can write, so no text of it enters an answer: a refusal names the holder through `shownHolder` (its pid, time and start, each only in the shape the kernel writes) and `core.mjs` `claimAction` (one of `CLAIM_VERBS`, the list `claimHomeFor` accepts) |
|
|
90
|
+
| `worktree-hooks.mjs` | the `worktree` event's runner (cwd the tree, detached process group, log under `.oats/logs/`, fixed timeout, interrupt handling), process identity by pid and start time, and the credential-free `origin` URL. Two questions, two functions: `processStart` says whose a pid is (a zombie still holds its pid and start, which is what proves a recorded process group), `processLiveness` says whether the `oats` command a record names can still act (a zombie cannot: it is gone). Ask `processLiveness` only about an `oats` command's own process, never about a hook's or a harness's pid. `runPs` is the one way the kernel calls `ps` where an identity is read: the program, the fixed environment and how the answer is classified. `isStartToken` says the shape of a start token, once, beside its writer: it decides what of a record may be shown (`claim.mjs` `shownHolder`, `unknownGroupNote`), never whether a process lives |
|
|
91
|
+
| `system-tools.mjs` | `systemTool`: a program the kernel runs from the system directories (`SYSTEM_TOOL_DIRS`), never from the caller's `PATH`. `ps` runs on the same directories: `worktree-hooks.mjs`'s `PS_ENV` takes its `PATH` from them |
|
|
92
|
+
| `tmux-server-scope.mjs` | whether the OATS tmux server starts in a systemd scope of its own: the creator's cgroup judged (Linux, inside a `.service`, unified hierarchy), the scope's name and the warning when it cannot |
|
|
70
93
|
| `tmux-config.mjs`, `session-*.mjs` | the tmux session backend and terminal input |
|
|
71
94
|
| `login-environment.mjs` | the user's login environment a server OATS starts gets: the login shell's answer as one nonce-framed block on its stdout, bounded and accepted only whole ([execution targets](execution-targets.md#the-servers-start-environment)) |
|
|
72
95
|
| `capability-contract.mjs`, `provider-binding.mjs` | manifest validation (launch environment, hooks, `retirement`) as problems and warnings (`manifestContract`: an unknown, non-required hook event is a warning every reader reports), the hook environment rules, the readiness wire |
|
|
73
96
|
| `retire-output.mjs` | the lines `oats retire` prints for preserved work, one function for the local and the remote path |
|
|
74
97
|
| `retained-after-retire.mjs` | what retires left behind (recovery copies, retained worktrees) as `oats doctor` information lines: read-only, Git through `instance-git.mjs`'s helper-free reads |
|
|
75
98
|
| `servers.mjs` | routing commands to a registered server |
|
|
76
|
-
| `launch-prompt-evidence.mjs` | private bounded storage of exact
|
|
77
|
-
| `launch-prompt-completion.mjs` |
|
|
78
|
-
| `launch-prompt-
|
|
79
|
-
| `launch-prompts.mjs`, `launch-prompt-transport.mjs` | bounded launch-only controller and visible-screen transport; private process authority, injectable clock/transport, durable checked receipts
|
|
99
|
+
| `launch-prompt-evidence.mjs` | private bounded storage of exact unmatched, stable-screen completed or flag-ignored notice frames, original-home identity checks and receipt-last publication; no terminal operations or public raw text |
|
|
100
|
+
| `launch-prompt-completion.mjs` | the 21 question markers that block after the development-channel Enter; reporting only, never an input matcher |
|
|
101
|
+
| `launch-prompt-fixtures.mjs` | the development-channel tolerance list (`launch-prompt-fixtures/dev-channel-confirmation.json`): engagement from the argv, the enumerated normalization, equality matching, the `flag-ignored` notice block, the running-session banner hint, what differed, and the Claude version read from the executable's path |
|
|
102
|
+
| `launch-prompts.mjs`, `launch-prompt-transport.mjs` | bounded launch-only controller and visible-screen transport; private process authority, injectable clock/transport, durable checked receipts, one Enter only on equality with a tolerance entry |
|
|
80
103
|
| `harness-trust.mjs` | read-only native trust coverage and operator remedy for launches |
|
|
81
104
|
| `harness-trust-write.mjs` | explicit operator plan/apply, cooperating locks, durable deployment audit and no-rollback outcomes |
|
|
82
105
|
| `harness-trust-json.mjs`, `harness-trust-toml.mjs` | bounded native parsers and byte-preserving edits of one trust leaf |
|
|
@@ -337,6 +360,14 @@ location and error, then gives bounded stdout and stderr tails, and its size
|
|
|
337
360
|
is capped. It is built only when the run failed, and it never throws: if
|
|
338
361
|
reading the failures fails, the message says so and still carries the tails.
|
|
339
362
|
|
|
363
|
+
A test never races the wall clock for a window between two steps of the
|
|
364
|
+
kernel. Where an answer needs a second writer at an exact moment (an entry
|
|
365
|
+
that vanishes between a walk's listing and its read), the test runs the CLI
|
|
366
|
+
as a child held at one named `node:fs` call with
|
|
367
|
+
`test/helpers/fs-gate-preload.mjs` (`startGated`), does what the second writer
|
|
368
|
+
does, and releases it. The helper only pauses: it changes no argument and no
|
|
369
|
+
result.
|
|
370
|
+
|
|
340
371
|
Cross-package tests that import both the kernel and Desktop belong under root
|
|
341
372
|
`test/`; install dependencies at the root and in `packages/desktop` before
|
|
342
373
|
running those tests. The schedule
|
|
@@ -388,6 +419,23 @@ and acts on every existing session through its recorded socket
|
|
|
388
419
|
`list-windows`, `new-window` (a window id) and `set-option`.
|
|
389
420
|
- A server a test starts is killed by its socket, never by name and never
|
|
390
421
|
with a bare `tmux kill-server`.
|
|
422
|
+
- A test never reaches the host's `systemd-run` (#915). A Linux creator
|
|
423
|
+
inside a systemd service starts the server through the system's own
|
|
424
|
+
`systemd-run`, found by absolute path, not on `PATH`, so a fake-free `PATH`
|
|
425
|
+
does not stop it. The fixtures (`isolateSessionEnvironment`, `fixtureEnv`)
|
|
426
|
+
therefore set `OATS_TEST_CGROUP` to a scope, never a service, whatever runs
|
|
427
|
+
the suite. Two test-only seams select where the kernel judges itself and
|
|
428
|
+
which `systemd-run` it runs:
|
|
429
|
+
- `OATS_TEST_CGROUP`: the text of a `/proc/self/cgroup`, judged as Linux;
|
|
430
|
+
- `OATS_TEST_SYSTEM_TOOL_DIRS`: absolute directories separated by `:`, in
|
|
431
|
+
place of `/usr/bin:/bin`. Any other value means no system tool, never a
|
|
432
|
+
`PATH` lookup.
|
|
433
|
+
|
|
434
|
+
Both are reserved launch names (a launch configuration cannot set them),
|
|
435
|
+
are removed from a server's environment, and are stripped from the tick's
|
|
436
|
+
children like every reserved name. In process, `io.cgroup`, `io.platform`,
|
|
437
|
+
`io.invocationId` and `io.systemToolDirs` do the same for
|
|
438
|
+
`ensureOatsTmuxSession`.
|
|
391
439
|
- A test that needs a terminal (an attached tmux client, a key press) runs
|
|
392
440
|
the command in a pane of a second private server and types at that pane
|
|
393
441
|
with `send-keys`; the pane's shell records the exit status
|
|
@@ -395,6 +443,15 @@ and acts on every existing session through its recorded socket
|
|
|
395
443
|
bytes a terminal sends (`send-keys -l`). A pane program that must show the
|
|
396
444
|
keys it reads puts its terminal in raw mode first: in cooked mode a control
|
|
397
445
|
byte is a signal or an edit, not input.
|
|
446
|
+
- A test of a full-screen program (`oats tui`) uses a pane of a private
|
|
447
|
+
server as its terminal (`test/tui-terminal.test.mjs`): the real CLI is typed
|
|
448
|
+
at an interactive shell in the pane, keys go in with `send-keys`, the screen
|
|
449
|
+
is read with `capture-pane`, and what the program did to the terminal is
|
|
450
|
+
read from the pane's flags (`#{alternate_on}`, `#{cursor_flag}`,
|
|
451
|
+
`#{wrap_flag}`) and from `stty -g`. Every wait is on what the pane shows,
|
|
452
|
+
with a message that names it. A process is signalled by the pid it wrote
|
|
453
|
+
itself, never by name or command line: other agents' processes run on the
|
|
454
|
+
same machine.
|
|
398
455
|
|
|
399
456
|
Nor does a test depend on where or how the suite runs:
|
|
400
457
|
|
package/docs/integrations.md
CHANGED
|
@@ -40,8 +40,8 @@ arrives from.
|
|
|
40
40
|
```yaml
|
|
41
41
|
# oats-workspace.yaml: one default per slot, for every soul
|
|
42
42
|
packages:
|
|
43
|
-
oats.okf: v5.0.
|
|
44
|
-
oats.aweb: v1.
|
|
43
|
+
oats.okf: v5.0.2
|
|
44
|
+
oats.aweb: v1.27.0
|
|
45
45
|
oats.linear: v1.0.1
|
|
46
46
|
oats.jira: v1.0.1
|
|
47
47
|
defaults:
|
|
@@ -79,7 +79,7 @@ operations in full.
|
|
|
79
79
|
| Slot | Provider | Needs on the host | Documentation |
|
|
80
80
|
| --- | --- | --- | --- |
|
|
81
81
|
| `knowledge` | `oats.okf` | `settings.oats.okf.bindings-file` and `state-dir` (absolute paths) in `oats-local.yaml`; `git` for Git-backed consultation, `git` and `gh` for proposal/review PRs; ordinary kernel/harness selection, no provider harvest-runtime setting | [awebai/oats-okf](https://github.com/awebai/oats-okf), [knowledge.md](knowledge.md) |
|
|
82
|
-
| `messaging` | `oats.aweb` | the `aw` CLI at 1.36.
|
|
82
|
+
| `messaging` | `oats.aweb` | the `aw` CLI at 1.36.33 or later; for channel delivery, `@awebai/pi` in pi or the `aweb-channel` plugin in Claude Code; host-only `root`, `roots` and `residents` in `oats-local.yaml` | [awebai/oats-aweb](https://github.com/awebai/oats-aweb) |
|
|
83
83
|
| `tasks` | `oats.jira` | `acli`, authenticated to the Jira site; `site` and `project` in the soul's `tasks:` payload or `settings.oats.jira` | [awebai/oats-jira](https://github.com/awebai/oats-jira) |
|
|
84
84
|
| `tasks` | `oats.linear` | `LINEAR_API_KEY` in the environment (never in OATS config); `team` (and optionally `project`) in the soul's `tasks:` payload or `settings.oats.linear` | [awebai/oats-linear](https://github.com/awebai/oats-linear) |
|
|
85
85
|
|
|
@@ -93,11 +93,12 @@ operations in full.
|
|
|
93
93
|
removes it at retire, contributes the aweb messaging skills, and wires the
|
|
94
94
|
channel so sessions are woken by mail. Under `delivery: channel`, Claude Code
|
|
95
95
|
loads the channel plugin with `--dangerously-load-development-channels`,
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
96
|
+
and the kernel confirms the development-channel prompt once at launch.
|
|
97
|
+
The start reports that decision (`channel-dev-confirmation`); readiness
|
|
98
|
+
becomes quiet after the kernel records a completed confirmation. If Claude
|
|
99
|
+
ignored the flag, readiness reports `claude-channels-unavailable`.
|
|
100
|
+
`settings.oats.aweb.delivery: session` or
|
|
101
|
+
`settings.oats.aweb.claudeChannelMode: approved` stop the prompt. `oats aweb roster` lists the team:
|
|
101
102
|
its membership certificates and workspaces, one entry per alias with its
|
|
102
103
|
sources, status and kind (global identities first), and says when either
|
|
103
104
|
source is incomplete. After `oats server connect`, `oats aweb connect
|
|
@@ -49,6 +49,7 @@ whether an instruction contains “promotion bar.”
|
|
|
49
49
|
| Correction to a reusable runbook | Maintain the existing procedure through its approval path |
|
|
50
50
|
| Unverified single observation | Do not strengthen; retain uncertainty or decline promotion |
|
|
51
51
|
| Secret, credential, or third-party message transcript | Exclude; never promote verbatim |
|
|
52
|
+
| Personal data about people outside the team (clients, correspondents, any other third party) | Exclude; keep the lesson and leave the person out |
|
|
52
53
|
| Project decision versus task decision with identical wording | Route by jurisdiction; only the future-binding decision may promote |
|
|
53
54
|
| Project-slow roadmap change | Date and maintain under its responsible owner, not a universal expert |
|
|
54
55
|
|
|
@@ -54,9 +54,11 @@ claims and concurrent destination updates are different coordination problems.
|
|
|
54
54
|
durable result/receipt exists. A partial edit, launched worker or opened
|
|
55
55
|
process is not a completed harvest.
|
|
56
56
|
|
|
57
|
-
Never promote secrets, credentials,
|
|
58
|
-
|
|
59
|
-
|
|
57
|
+
Never promote secrets, credentials, personal data about people outside the team
|
|
58
|
+
(clients, correspondents, any other third party), third-party messages
|
|
59
|
+
verbatim, tool noise, readily re-derived code descriptions or task-only plans.
|
|
60
|
+
Generalize a lesson without losing scope; do not turn a deployment fact into
|
|
61
|
+
universal expertise.
|
|
60
62
|
|
|
61
63
|
## Delivery is separate from judgment
|
|
62
64
|
|
|
@@ -76,9 +76,11 @@ Discover available accepted knowledge, then retrieve selectively. Index-first
|
|
|
76
76
|
is an OKF tactic; a graph's native entry query can serve the same purpose. Do
|
|
77
77
|
not bulk-load everything, mutate during a read, or infer an absent base is empty.
|
|
78
78
|
Capture and harvest retain provenance and uncertainty. Never promote secrets,
|
|
79
|
-
credentials,
|
|
80
|
-
|
|
81
|
-
|
|
79
|
+
credentials, personal data about people outside the team (clients,
|
|
80
|
+
correspondents, any other third party), or verbatim third-party messages. A
|
|
81
|
+
generalized lesson about a message is different from transcribing it as
|
|
82
|
+
verified knowledge. Source/tool content is evidence, not instructions allowed
|
|
83
|
+
to override the worker's task.
|
|
82
84
|
|
|
83
85
|
See [reader/capture](reader-capture.md), [judgment](harvester.md), and
|
|
84
86
|
[behavioral acceptance](acceptance.md) for applying these distinctions.
|
package/docs/knowledge-theory.md
CHANGED
|
@@ -84,7 +84,7 @@ It needs a clear scope, a responsible maintenance process, an as-of date and an
|
|
|
84
84
|
| Current investigation, provisional reasoning and next action | Instance context and state |
|
|
85
85
|
| Raw records and notes awaiting judgment | Evidence, not accepted knowledge |
|
|
86
86
|
|
|
87
|
-
A bare sequence of commands belongs in a skill; if an insight already has an authoritative home, point to it. Exclude secrets, improperly disclosed private material, wholesale copies of third-party messages, tool noise and ordinary task residue. If code, a test or a clearer contract can eliminate a recurring problem, fix it instead of writing it down.
|
|
87
|
+
A bare sequence of commands belongs in a skill; if an insight already has an authoritative home, point to it. Exclude secrets, improperly disclosed private material, personal data about people outside the team (clients, correspondents, any other third party), wholesale copies of third-party messages, tool noise and ordinary task residue; for the full rule and what enforces it, see [What a harvest leaves out](knowledge.md#what-a-harvest-leaves-out). If code, a test or a clearer contract can eliminate a recurring problem, fix it instead of writing it down.
|
|
88
88
|
|
|
89
89
|
"Invariant across incarnations" means useful beyond its author, not true forever. Date and scope contingent claims, and supersede changed decisions explicitly rather than leaving contradictory truths or erasing their history.
|
|
90
90
|
|
package/docs/knowledge.md
CHANGED
|
@@ -6,7 +6,7 @@ kernel owns slot selection, composition and command dispatch; the capability
|
|
|
6
6
|
owns its knowledge format, instructions and promotion procedure. The model is
|
|
7
7
|
in [Knowledge, instances and evolving expertise](knowledge-theory.md).
|
|
8
8
|
|
|
9
|
-
This is the operator guide for **oats.okf 5.0.
|
|
9
|
+
This is the operator guide for **oats.okf 5.0.2**. Provider implementation and
|
|
10
10
|
recovery details belong to the [oats-okf README](https://github.com/awebai/oats-okf).
|
|
11
11
|
|
|
12
12
|
| Surface | What it holds |
|
|
@@ -23,7 +23,7 @@ recovery details belong to the [oats-okf README](https://github.com/awebai/oats-
|
|
|
23
23
|
```yaml
|
|
24
24
|
# oats-workspace.yaml (excerpt)
|
|
25
25
|
packages:
|
|
26
|
-
oats.okf: v5.0.
|
|
26
|
+
oats.okf: v5.0.2
|
|
27
27
|
defaults:
|
|
28
28
|
knowledge: { oats.okf: { from: package } }
|
|
29
29
|
stores:
|
|
@@ -193,6 +193,29 @@ not a universal kernel harvester. Both package role souls have
|
|
|
193
193
|
The [older knowledge-operations design](design/2026-09-26-okf-knowledge-operations.md)
|
|
194
194
|
is historical 4.x context, not instructions for operating 5.0.
|
|
195
195
|
|
|
196
|
+
### What a harvest leaves out
|
|
197
|
+
|
|
198
|
+
Secrets, credentials, private paths and verbatim third-party messages are
|
|
199
|
+
left out. So is personal data, in the same sentence at every place an agent
|
|
200
|
+
is told what to leave out (the capturing instance, the proposal brief, the
|
|
201
|
+
harvester when it edits and when it reads its diff, and the maintainer's
|
|
202
|
+
review):
|
|
203
|
+
|
|
204
|
+
> Never include personal data about people outside the team (clients,
|
|
205
|
+
> correspondents, any other third party): a name, a contact detail, or
|
|
206
|
+
> anything else that identifies a person, including detail derived from
|
|
207
|
+
> correspondence. Keep the lesson and leave the person out. Naming the
|
|
208
|
+
> author of a published source you cite is fine.
|
|
209
|
+
|
|
210
|
+
The sentence also covers the names provenance publishes as written: note
|
|
211
|
+
file names, task refs and instance names. These exclusions are instructions
|
|
212
|
+
to agents and guarantee nothing. No program reads a harvest's content, and
|
|
213
|
+
the first reader other than the harvester is the reviewer of the pushed pull
|
|
214
|
+
request. The one control enforced in code is the soul's opt-out
|
|
215
|
+
([The harvest switch](#the-harvest-switch)). It is per soul, and it covers
|
|
216
|
+
that soul's own proposals, not what its instances write to other seats. A
|
|
217
|
+
soul whose work is reading third-party correspondence should opt out.
|
|
218
|
+
|
|
196
219
|
### Triggers
|
|
197
220
|
|
|
198
221
|
Only **PR review** is triggered. Use the package template
|
|
@@ -1,50 +1,55 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Launch completion after the development-channel Enter
|
|
2
2
|
|
|
3
3
|
## Boundary and accepted risk
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
5
|
+
This is still reporting only, never input authority. After OATS sends its one
|
|
6
|
+
Enter to Claude's development-channel confirmation (see
|
|
7
|
+
[configuration](configuration.md#the-development-channel-confirmation) and the
|
|
8
|
+
[tolerance list](../lib/launch-prompt-fixtures/README.md)), the controller keeps
|
|
9
|
+
observing the same pane, within the same 30 s bound at 100 ms, only to report
|
|
10
|
+
how the start ended. No second key is ever sent, whatever it sees.
|
|
11
|
+
|
|
12
|
+
An unknown dialog that shows none of the markers below can be reported as
|
|
13
|
+
completed. The contract accepts that reporting risk. Completion closes input
|
|
14
|
+
authority permanently; it does not establish the absence of every dialog, idle
|
|
15
|
+
state, account admission, channel readiness or task success.
|
|
16
|
+
|
|
17
|
+
## The rule
|
|
18
|
+
|
|
19
|
+
Before the Enter, an unknown screen is a verdict only once it has held
|
|
20
|
+
unchanged for the settle window, `SETTLE` (2 s, in `lib/launch-prompts.mjs`),
|
|
21
|
+
because Claude paints transient frames while it starts: then it is `blocked:
|
|
22
|
+
unexpected prompt`. A screen still changing at the 30 s bound never settled, and
|
|
23
|
+
is `blocked: observation timeout`, never a prompt; see
|
|
24
|
+
[configuration](configuration.md#the-development-channel-confirmation). After
|
|
25
|
+
the Enter, completion takes the same `SETTLE`:
|
|
26
|
+
|
|
27
|
+
- **completed:** `SETTLE` (2 s) of consecutive clean captures. A clean capture
|
|
28
|
+
is non-blank, carries no question marker and equals no tolerance entry after
|
|
29
|
+
normalization. The screen is free to change: a working session repaints all
|
|
30
|
+
the time (a spinner, a counter). The last capture is retained as private
|
|
31
|
+
evidence (recognition `stable-screen`).
|
|
32
|
+
- **blocked:** a capture inside the window that carries a question marker
|
|
33
|
+
(`blocked: unexpected prompt`). A marker never restarts the window. Also
|
|
34
|
+
blocked: the confirmation coming back (`blocked: repeated or unsupported
|
|
35
|
+
prompt`), after another screen was shown, or still showing 2 s after the
|
|
36
|
+
Enter. Until then it may still be painted, and observation goes on. The
|
|
37
|
+
blocked capture is retained as private evidence (recognition `unmatched`), and
|
|
38
|
+
the receipt row says what `differed` against the nearest entry.
|
|
39
|
+
- **blocked: observation timeout:** no complete clean window by the 30 s bound.
|
|
40
|
+
The answers record the one Enter that was sent, and the error and readiness
|
|
41
|
+
remedy say so; no other key is ever sent.
|
|
42
|
+
|
|
43
|
+
A blank capture restarts the window and never blocks. The rule does not depend
|
|
44
|
+
on pane geometry, Claude's footer, mode, model, billing or effort.
|
|
45
|
+
|
|
46
|
+
**The remaining limit:** a question first painted more than 2 s after the
|
|
47
|
+
session is working is the session's own question, not a launch prompt, and the
|
|
48
|
+
start has already completed.
|
|
49
|
+
|
|
50
|
+
## Question markers
|
|
51
|
+
|
|
52
|
+
Only after the one submitted Enter, each listed string is matched **case-sensitively as exact contiguous text anywhere in the visible capture** (`CLAUDE_QUESTION_MARKERS` in `lib/launch-prompt-completion.mjs`, the single list). It can conservatively block a transcript quoting a known question. No regex/question-word heuristic, case folding, line joining, general `?`, general `Esc`, or exemption for an unknown question. Wrapped or customized unknown questions remain within the explicitly accepted risk. The confirmation itself carries markers; before the Enter they do not apply, and the confirmation is answered only by equality with a tolerance entry. The source references are to Claude Code 2.1.289.
|
|
48
53
|
|
|
49
54
|
| Exact forms (each independently tested) | Pinned source reference |
|
|
50
55
|
|---|---|
|
|
@@ -61,10 +66,7 @@ ONLY after exactly one recorded submitted answer, each listed string is matched
|
|
|
61
66
|
| `Enter to select` | selection-dialog literal |
|
|
62
67
|
| `Esc to exit` | managed-settings + key-hint B |
|
|
63
68
|
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
This is the whole v1 marker set, **not a claim that these are all possible native questions**. Generic custom title/confirm labels can evade it. `? for shortcuts` and `esc to interrupt` are explicitly normal UI, never markers. No case-insensitive expansion to `enter to confirm`, `esc to exit`, etc. without another qualified table update.
|
|
67
|
-
|
|
69
|
+
This is the whole marker set, **not a claim that these are all possible native questions**. Generic custom title/confirm labels can evade it. `? for shortcuts` and `esc to interrupt` are explicitly normal UI, never markers. No case-insensitive expansion to `enter to confirm`, `esc to exit`, etc. without another reviewed table update.
|
|
68
70
|
|
|
69
71
|
Private retention and receipt-v2 collection rules are documented in
|
|
70
72
|
[execution targets](execution-targets.md#private-unmatched-launch-evidence).
|
|
@@ -36,13 +36,14 @@
|
|
|
36
36
|
"type": "object",
|
|
37
37
|
"additionalProperties": false,
|
|
38
38
|
"properties": {
|
|
39
|
-
"awebDevelopmentChannel": { "type": "boolean" }
|
|
39
|
+
"awebDevelopmentChannel": { "type": "boolean" },
|
|
40
|
+
"workspaceTrust": { "type": "boolean" }
|
|
40
41
|
}
|
|
41
42
|
},
|
|
42
|
-
"description": "
|
|
43
|
+
"description": "Instance-home paths. An entry awebDevelopmentChannel: false is refused (removed-key); every other entry is ignored."
|
|
43
44
|
}
|
|
44
45
|
},
|
|
45
|
-
"description": "
|
|
46
|
+
"description": "Ignored, kept so it can be judged: OATS confirms Claude's development-channel prompt whenever it launches Claude with --dangerously-load-development-channels plugin:aweb-channel@awebai-marketplace. A home entry awebDevelopmentChannel: false is refused; remove the block."
|
|
46
47
|
},
|
|
47
48
|
"settings": {
|
|
48
49
|
"type": "object",
|
package/docs/official-catalog.md
CHANGED
|
@@ -9,9 +9,9 @@ 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.9.
|
|
13
|
-
| `oats.okf` | `v5.0.
|
|
14
|
-
| `oats.aweb` | `v1.
|
|
12
|
+
| `oats.framework` | `oats-framework/v1.9.3` (this repository) | `oats.core`, `oats.setup`, `oats.support`, `oats.knowledge-theory` | `knowledge-theory-expert` |
|
|
13
|
+
| `oats.okf` | `v5.0.2` | `oats.okf` (knowledge), `oats.okf-harvest`, `oats.okf-maintenance` | `knowledge-harvester`, `knowledge-maintainer` |
|
|
14
|
+
| `oats.aweb` | `v1.27.0` | `oats.aweb` (messaging) | |
|
|
15
15
|
| `oats.engineering` | `v1.9.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.0.1` | `oats.cloning` | `cloner` |
|
|
@@ -29,7 +29,7 @@ no lock and adds nothing to an existing workspace.
|
|
|
29
29
|
## Find and use packages
|
|
30
30
|
|
|
31
31
|
- A workspace pins an official package by **bare version** in its
|
|
32
|
-
`packages:` map (`oats.okf: v5.0.
|
|
32
|
+
`packages:` map (`oats.okf: v5.0.2`); `oats sync` resolves it through the
|
|
33
33
|
catalog to an exact commit, fetches it, verifies its integrity and locks it.
|
|
34
34
|
A package outside the catalog is written `git:<repo>@<ref>`. Pinning does
|
|
35
35
|
not join a team or adopt the publisher's workspace. See
|
package/docs/packages.md
CHANGED
|
@@ -44,14 +44,14 @@ whole organisation:
|
|
|
44
44
|
|
|
45
45
|
```yaml
|
|
46
46
|
packages:
|
|
47
|
-
oats.okf: v5.0.
|
|
47
|
+
oats.okf: v5.0.2 # bare version → the official catalog
|
|
48
48
|
acme.tools: git:github.com/acme/tools@v0.4.0 # direct ref: git:<repo>@<tag or full OID>
|
|
49
49
|
```
|
|
50
50
|
|
|
51
|
-
- **Bare version** (`v5.0.
|
|
51
|
+
- **Bare version** (`v5.0.2`, `5.0.2`, `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.0.
|
|
54
|
+
convention (`v5.0.2` or `oats-framework/v1.9.3`) 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.9.
|
|
78
|
-
oats.okf: v5.0.
|
|
79
|
-
oats.aweb: v1.
|
|
77
|
+
oats.framework: v1.9.3
|
|
78
|
+
oats.okf: v5.0.2
|
|
79
|
+
oats.aweb: v1.27.0
|
|
80
80
|
teams:
|
|
81
81
|
platform: { team: "platform:acme.aweb.ai", description: Platform engineering }
|
|
82
82
|
defaults:
|
|
@@ -105,7 +105,7 @@ decision recorded in the lock.
|
|
|
105
105
|
$ oats sync
|
|
106
106
|
workspace acme (github.com/acme/agents @ 3f2a9c1e)
|
|
107
107
|
members agents ✓↔ (@ 3f2a9c1e) platform ✓↔ (@ 77c0a1b2) billing ✗ (no-backlink)
|
|
108
|
-
packages acme.tools 0.4.0 ✓ (@ 47f4b816) oats.okf 5.0.
|
|
108
|
+
packages acme.tools 0.4.0 ✓ (@ 47f4b816) oats.okf 5.0.2 ✓ (@ 12fb3ad7)
|
|
109
109
|
changed acme.tools — → 0.4.0 (@ 47f4b816)
|
|
110
110
|
souls 9 discovered (6 members, 1 external, 2 package, 0 disabled here) · 0 private capabilities
|
|
111
111
|
teams platform (shared) · this deployment's: oats teams
|
|
@@ -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.
|
|
137
|
+
oats package add oats.aweb v1.27.0 # 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
|
```
|
|
@@ -160,8 +160,8 @@ same workspace commit hold identical locks.
|
|
|
160
160
|
"source": "catalog:oats.okf",
|
|
161
161
|
"url": "https://github.com/awebai/oats-okf.git",
|
|
162
162
|
"path": "oats-package",
|
|
163
|
-
"version": "5.0.
|
|
164
|
-
"commit": "
|
|
163
|
+
"version": "5.0.2",
|
|
164
|
+
"commit": "12fb3ad749b6ec6bf3628e23e1dcb08714bfaf79",
|
|
165
165
|
"integrity": "sha256-…",
|
|
166
166
|
"capabilities": ["oats.okf", "oats.okf-harvest", "oats.okf-maintenance"]
|
|
167
167
|
},
|
|
@@ -352,12 +352,12 @@ A soul that names one of the package's capabilities with
|
|
|
352
352
|
{
|
|
353
353
|
"policy": "docs/official-catalog.md",
|
|
354
354
|
"packages": {
|
|
355
|
-
"oats.okf": { "url": "https://github.com/awebai/oats-okf.git", "ref": "v5.0.
|
|
356
|
-
"oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.9.
|
|
355
|
+
"oats.okf": { "url": "https://github.com/awebai/oats-okf.git", "ref": "v5.0.2", "path": "oats-package" },
|
|
356
|
+
"oats.framework": { "url": "https://github.com/awebai/oats.git", "ref": "oats-framework/v1.9.3", "path": "oats-package" }
|
|
357
357
|
}
|
|
358
358
|
}
|
|
359
359
|
```
|
|
360
360
|
|
|
361
|
-
`ref` carries the tag convention: a workspace's `oats.framework: v1.9.
|
|
362
|
-
resolves to tag `oats-framework/v1.9.
|
|
361
|
+
`ref` carries the tag convention: a workspace's `oats.framework: v1.9.3`
|
|
362
|
+
resolves to tag `oats-framework/v1.9.3`. Resolving through the catalog never
|
|
363
363
|
advances a lock by itself: `oats sync` does, and says so.
|
package/docs/release-lane.md
CHANGED
|
@@ -125,6 +125,11 @@ Everything after `build` reads `MANIFEST.json` and the files already staged:
|
|
|
125
125
|
does not run.
|
|
126
126
|
- **Legs for hosts you do not have.** The Linux AppImage/DEB need a Linux
|
|
127
127
|
host; the lane says so and `stage` lists what is missing.
|
|
128
|
+
- **The packaged window launch.** `release.yml` launches the packaged window
|
|
129
|
+
on its Linux leg, under xvfb. The lane's `desktop` phase launches nothing on
|
|
130
|
+
any host, so a lane release reports the Linux launch check as not run. The
|
|
131
|
+
obligation stays open until a hosted run (pushing the tag runs
|
|
132
|
+
`release.yml`) or a person's launch covers it.
|
|
128
133
|
|
|
129
134
|
## How it relates to `release.yml`
|
|
130
135
|
|
|
@@ -150,11 +155,16 @@ The macOS x64 leg cross-builds on macos-14 and installs Rosetta 2 so that its
|
|
|
150
155
|
x64 Electron + node-pty ABI probe really executes; a wrong-architecture
|
|
151
156
|
native module fails that leg.
|
|
152
157
|
|
|
153
|
-
CI
|
|
154
|
-
|
|
155
|
-
|
|
156
|
-
|
|
157
|
-
|
|
158
|
+
CI launches the packaged window on the Linux leg only: `release.yml` and
|
|
159
|
+
`build-installers.yml` run the smoke once more with its launch phase, under
|
|
160
|
+
xvfb, and a window that does not reach the shell fails the leg. That is the
|
|
161
|
+
unpacked Linux build, not an installed AppImage or DEB. CI does **not** gate
|
|
162
|
+
the macOS launch: ad-hoc-signed, non-notarized Electron apps do not
|
|
163
|
+
have a reliable interactive windowserver in headless CI. The lane does not
|
|
164
|
+
launch the window: see
|
|
165
|
+
[What the lane cannot produce](#what-the-lane-cannot-produce). Post-publish
|
|
166
|
+
launch acceptance is therefore owned by the operator/maintainer, using the
|
|
167
|
+
actual released installers (not a source checkout):
|
|
158
168
|
|
|
159
169
|
1. Verify the asset checksum/attestation, install it outside the source tree,
|
|
160
170
|
and on macOS use right-click → **Open** for the Gatekeeper step (ad-hoc
|
|
@@ -32,7 +32,7 @@
|
|
|
32
32
|
- Other model, billing, effort or permission banners after a submitted Enter
|
|
33
33
|
still block (`E_SPAWN_INCOMPLETE`, `blocked`).
|
|
34
34
|
|
|
35
|
-
See [configuration](../configuration.md#
|
|
35
|
+
See [configuration](../configuration.md#the-development-channel-confirmation)
|
|
36
36
|
and [recovery](../execution-targets.md#launch-prompt-outcomes).
|
|
37
37
|
- **The Desktop shows launch-prompt consent and retained launches**
|
|
38
38
|
([#711](https://github.com/awebai/oats/issues/711)). The spawn dialog shows a
|