owenloop 0.5.7 → 0.5.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/CHANGELOG.md +41 -0
- package/README.md +7 -8
- package/dist/packages/work/src/agent/capability-model.d.ts +64 -82
- package/dist/packages/work/src/agent/capability-model.js +94 -91
- package/dist/packages/work/src/agent/loop.d.ts +55 -26
- package/dist/packages/work/src/agent/loop.js +144 -50
- package/dist/packages/work/src/bundle/types.d.ts +3 -3
- package/dist/packages/work/src/consumed-verifier.js +6 -17
- package/dist/packages/work/src/exec/loop.d.ts +1 -1
- package/dist/packages/work/src/exec/loop.js +206 -35
- package/dist/packages/work/src/exec/receipt.d.ts +7 -7
- package/dist/packages/work/src/exec/receipt.js +6 -6
- package/dist/packages/work/src/harness/child-env.js +4 -5
- package/dist/packages/work/src/harness/claude.js +100 -0
- package/dist/packages/work/src/harness/codex.js +3 -4
- package/dist/packages/work/src/harness/session-store.d.ts +63 -3
- package/dist/packages/work/src/harness/session-store.js +104 -9
- package/dist/packages/work/src/hub/client.d.ts +19 -4
- package/dist/packages/work/src/hub/client.js +7 -3
- package/dist/packages/work/src/hub/types.d.ts +87 -3
- package/dist/packages/work/src/main.js +1 -0
- package/dist/packages/work/src/roles/agent-run.js +46 -43
- package/dist/packages/work/src/roles/exec.js +2 -0
- package/dist/packages/work/src/roles/sessions.d.ts +3 -2
- package/dist/packages/work/src/roles/sessions.js +9 -2
- package/dist/packages/work/src/roles/settings.js +3 -1
- package/dist/packages/work/src/roles/shift.js +14 -2
- package/dist/packages/work/src/roles/util.d.ts +1 -0
- package/dist/packages/work/src/roles/util.js +10 -0
- package/dist/packages/work/src/settings/hub-roster-cache.d.ts +68 -0
- package/dist/packages/work/src/settings/hub-roster-cache.js +370 -0
- package/dist/packages/work/src/settings/roster.d.ts +105 -0
- package/dist/packages/work/src/settings/roster.js +439 -0
- package/dist/packages/work/src/settings/serving.d.ts +17 -0
- package/dist/packages/work/src/settings/serving.js +79 -0
- package/dist/packages/work/src/settings/settings.d.ts +25 -24
- package/dist/packages/work/src/settings/settings.js +29 -33
- package/dist/packages/work/src/shift/loop.d.ts +108 -5
- package/dist/packages/work/src/shift/loop.js +299 -51
- package/dist/packages/work/src/shift/protocol.d.ts +7 -5
- package/dist/packages/work/src/shift/runtime.d.ts +15 -0
- package/dist/packages/work/src/shift/runtime.js +95 -13
- package/dist/packages/work/src/shift/server.js +2 -0
- package/dist/packages/work/src/shift/spawn.d.ts +18 -50
- package/dist/packages/work/src/shift/spawn.js +30 -65
- package/dist/packages/work/src/shift/state.d.ts +29 -2
- package/dist/packages/work/src/shift/state.js +45 -15
- package/dist/packages/work/src/usage.d.ts +1 -1
- package/dist/packages/work/src/usage.js +10 -5
- package/dist/packages/work/src/util/modifier-init.d.ts +7 -0
- package/dist/packages/work/src/util/modifier-init.js +73 -0
- package/dist/src/bundle/tar.d.ts +9 -4
- package/dist/src/bundle/tar.js +9 -4
- package/dist/src/capabilities.d.ts +50 -0
- package/dist/src/capabilities.js +38 -0
- package/dist/src/cli.d.ts +15 -1
- package/dist/src/cli.js +1099 -32
- package/dist/src/config-dir.d.ts +14 -19
- package/dist/src/config-dir.js +16 -24
- package/dist/src/credentials.d.ts +1 -1
- package/dist/src/credentials.js +1 -1
- package/dist/src/crypto/index.d.ts +1 -1
- package/dist/src/crypto/index.js +1 -1
- package/dist/src/crypto/org-root.d.ts +30 -12
- package/dist/src/crypto/org-root.js +162 -14
- package/dist/src/crypto/records.d.ts +3 -0
- package/dist/src/crypto/records.js +8 -0
- package/dist/src/crypto/trust-roots.d.ts +2 -2
- package/dist/src/crypto/trust-roots.js +2 -2
- package/dist/src/defs.d.ts +6 -1
- package/dist/src/defs.js +203 -8
- package/dist/src/engine.d.ts +55 -6
- package/dist/src/engine.js +172 -22
- package/dist/src/global-config.d.ts +4 -7
- package/dist/src/global-config.js +4 -7
- package/dist/src/hub.d.ts +207 -5
- package/dist/src/hub.js +263 -3
- package/dist/src/index.d.ts +5 -5
- package/dist/src/index.js +3 -3
- package/dist/src/mcp/serve.d.ts +22 -0
- package/dist/src/mcp/serve.js +88 -8
- package/dist/src/model.d.ts +2 -0
- package/dist/src/model.js +32 -25
- package/dist/src/order-resolver.d.ts +1 -0
- package/dist/src/order-resolver.js +8 -1
- package/dist/src/schemas/index.d.ts +19 -0
- package/dist/src/schemas/order.v1.schema.json +13 -2
- package/dist/src/store/pre-commit-verifier.js +1 -1
- package/dist/src/store.d.ts +5 -0
- package/dist/src/store.js +43 -8
- package/dist/src/types.d.ts +64 -7
- package/dist/src/work-settings.d.ts +2 -4
- package/dist/src/work-settings.js +2 -4
- package/docs/agent-runner.md +2 -2
- package/docs/authoring.md +90 -2
- package/docs/bundles.md +29 -3
- package/docs/cli.md +456 -120
- package/docs/crypto.md +32 -16
- package/docs/design.md +70 -1
- package/docs/routing.md +762 -0
- package/docs/shift-logs.md +37 -10
- package/docs/wire-contracts.md +50 -7
- package/examples/workflows/delivery.yaml +31 -14
- package/examples/workflows/ship.yaml +10 -2
- package/package.json +1 -1
- package/plugins/claude-code/plugin/.claude-plugin/plugin.json +1 -1
- package/plugins/claude-code/plugin/.mcp.json +1 -1
- package/plugins/claude-code/plugin/skills/author/SKILL.md +1 -2
- package/plugins/codex/plugins/owenloop/.codex-plugin/plugin.json +1 -1
- package/plugins/codex/plugins/owenloop/.mcp.json +1 -1
- package/plugins/codex/plugins/owenloop/skills/author/SKILL.md +1 -2
package/docs/shift-logs.md
CHANGED
|
@@ -27,13 +27,37 @@ Do not collapse these — the rest of this page depends on telling them apart.
|
|
|
27
27
|
stderr are what `<run>.log` holds.
|
|
28
28
|
3. **The command a worker runs** — the `command:` text of a command step,
|
|
29
29
|
executed by the worker under `/bin/sh -c`. **Its** streams are captured into
|
|
30
|
-
the
|
|
30
|
+
the `CommandReceipt`. On success, the worker submits that receipt to the hub;
|
|
31
|
+
on failure, it sends the receipt as diagnostic context on an `ask` and
|
|
32
|
+
submits no artifact. In both cases the worker relays the captured tail (≤4
|
|
33
|
+
KiB) into its own output so a copy reaches `<run>.log`.
|
|
34
|
+
|
|
35
|
+
The worker never **inherits** the command's streams. Every relayed line carries
|
|
36
|
+
the literal ` | ` prefix. The receipt and `<run>.log` contain the captured
|
|
37
|
+
tail; for a failed command, the receipt is ask context rather than an artifact.
|
|
38
|
+
Full streams are represented only by the receipt's output hash and stdout/stderr
|
|
39
|
+
byte counts.
|
|
40
|
+
|
|
41
|
+
| Command outcome | Worker channel | Header |
|
|
42
|
+
| --- | --- | --- |
|
|
43
|
+
| exit 0 and no machinery error | stdout | `… the command for step 'X' succeeded; its output follows` |
|
|
44
|
+
| anything else | stderr | `… the command for step 'X' exited N` / `was killed by …` / `could not be run (…)`; `its last output follows` |
|
|
45
|
+
|
|
46
|
+
An ordinary command that fails raises an `ask` on its first owed path with the
|
|
47
|
+
receipt and captured output as diagnostics. Nothing is greened, and the owed
|
|
48
|
+
artifact waits for a human retry; additional owed paths remain debts because
|
|
49
|
+
`ask` closes the run.
|
|
50
|
+
|
|
51
|
+
Under shift dispatch fd 1 and fd 2 both point at the same file, so the header —
|
|
52
|
+
not the channel — is what tells these outcomes apart in `<run>.log`. The two
|
|
53
|
+
channels still matter: stderr is what a reader treats as trouble, and routine
|
|
54
|
+
success output there would make every green step look like a problem.
|
|
31
55
|
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
shift-logs-acceptance.test.ts` asserts
|
|
36
|
-
|
|
56
|
+
A command that printed nothing gets ` (the command produced no output)` on both
|
|
57
|
+
paths, because a gate that prints nothing is itself a diagnosis. The relay is
|
|
58
|
+
unconditional and has no off switch.
|
|
59
|
+
`packages/work/test/shift-logs-acceptance.test.ts` asserts that the marker
|
|
60
|
+
appears in `<run>.log` exactly once, as ` | <marker>`.
|
|
37
61
|
|
|
38
62
|
## Where the directory is
|
|
39
63
|
|
|
@@ -163,9 +187,9 @@ Two properties an uploader can rely on:
|
|
|
163
187
|
| `reaped` | `workflow`, `run`, `kind`, `pid` | a worker exited and was collected |
|
|
164
188
|
| `failed` | `workflow`, `run`, `step`, `kind`, `message`, and — from the exit path only — `executable`, `exitStatus`, `signal`, optional `harness` | a worker died or could not be spawned; **two producers, two shapes** — see below |
|
|
165
189
|
| `capacity` | `inFlight`, `cap` | no free slot, so the `whats_next` sweep was deferred — explains a shift running nothing new while work is outstanding. **Edge-triggered**, and emitted only on a *changed* wake — see below |
|
|
166
|
-
| `hub-error` | `op` (`wake`\|`whats_next`), `message`, optional `workflow` | a hub call failed. `workflow` present = the targeted `whats_next` for that one workflow; `workflow` absent with `op: 'whats_next'` = the untargeted inbox call, which aborts the whole sweep. **File-only** — see below |
|
|
190
|
+
| `hub-error` | `op` (`wake`\|`whats_next`\|`roster_sync`\|`release`), `message`, optional `workflow` | a hub call failed. `workflow` present = the targeted `whats_next` or release for that one workflow; `workflow` absent with `op: 'whats_next'` = the untargeted inbox call, which aborts the whole sweep. `op: 'roster_sync'` records the non-fatal startup or periodic hub-roster refresh failure. `op: 'release'` means returning an undispatchable claim failed, so it will instead wait for pickup expiry. **File-only** — see below |
|
|
167
191
|
| `bundle-miss` | `workflow`, `def` | a legacy order named a def with no cached bundle |
|
|
168
|
-
| `order-dropped` | `workflow`, `run`, `step`, `reason`, `message` | the shift refused one order and
|
|
192
|
+
| `order-dropped` | `workflow`, `run`, `step`, `reason`, `message` | the shift refused one order; capacity and expiry reasons return the claim to the hub while malformed and unsupported reasons leave it for pickup |
|
|
169
193
|
| `event-queue-overflow` | `dropped` | the socket FIFO evicted events; see below |
|
|
170
194
|
| `ended` | — | an operator ran `owenloop shift end` |
|
|
171
195
|
| `gate` | optional `workflow`, `run`, `name`, `question` | reserved; not emitted today |
|
|
@@ -234,8 +258,11 @@ one.
|
|
|
234
258
|
|
|
235
259
|
`order-dropped.reason` is the stable machine discriminator and is one of
|
|
236
260
|
`malformed-digest`, `malformed-worker`, `unsupported-worker`,
|
|
237
|
-
`verification-failed`, `metadata-unavailable
|
|
238
|
-
|
|
261
|
+
`verification-failed`, `metadata-unavailable`, `agent-lane-closed`,
|
|
262
|
+
`dispatch-cap-full`, `agent-cap-full`, or `claim-expired`. The capacity,
|
|
263
|
+
expiry, and `agent-lane-closed` reasons return the claim to the hub; malformed
|
|
264
|
+
and unsupported reasons leave it for the pickup window. `message` is human
|
|
265
|
+
text — match on `reason`, display `message`.
|
|
239
266
|
|
|
240
267
|
### The first record is self-describing
|
|
241
268
|
|
package/docs/wire-contracts.md
CHANGED
|
@@ -295,17 +295,20 @@ Required fields are `run`, `workflow`, `step`, `key`, `defDigest`, `inputs`,
|
|
|
295
295
|
`outputs`, `consumes`, and `owes`.
|
|
296
296
|
|
|
297
297
|
Optional fields are `index`, `workdir`, `model`, `worker`, `judge`, `spec`, `x`,
|
|
298
|
-
`consumedFingerprint`, `consumesProof`,
|
|
299
|
-
|
|
300
|
-
|
|
301
|
-
|
|
298
|
+
`consumedFingerprint`, `consumesProof`, `cause`, `capabilities`, `crews`,
|
|
299
|
+
`reroutedFrom`, `modifier`, and `escalated`. `workdir` may be authored as a
|
|
300
|
+
literal `workdir:` or resolved by the engine from a step's `workdirFrom:`, whose
|
|
301
|
+
stem names either a consumed artifact or a declared input; the Order wire shape
|
|
302
|
+
remains unchanged. No proof field covers `workdir` in any case.
|
|
302
303
|
|
|
303
304
|
`defDigest` is a non-empty opaque reference. `inputs` and `outputs` are string
|
|
304
305
|
arrays. `consumes` is an open artifact-path map; `spec` and `x` are opaque
|
|
305
306
|
objects carried through without engine interpretation. `owes` contains the owed
|
|
306
307
|
path, an optional target `version` (the version the next successful commit for
|
|
307
308
|
that path lands, issued inside the claim transaction), judgment/schema rejection
|
|
308
|
-
counters, reason entries, and an optional opaque `proof` string.
|
|
309
|
+
counters, reason entries, and an optional opaque `proof` string. A reason entry
|
|
310
|
+
may also carry optional `requested`, the validated replacement value requested
|
|
311
|
+
when rejecting an artifact bound to the run's modifier. `cause`, when present, is
|
|
309
312
|
`inputsGreen`, `allGreen`, or `idle`.
|
|
310
313
|
|
|
311
314
|
**Decision A — version cross-check without fingerprint recomputation.** The
|
|
@@ -381,8 +384,48 @@ out of the `CommandReceipt`; malformed or over-cap JSON produces
|
|
|
381
384
|
`payloadError` and no `payload`, while leaving the command exit code unchanged.
|
|
382
385
|
When the hub supplies authoritative output-version metadata and the driver can
|
|
383
386
|
sign, the parsed payload is part of the receipt value covered by the DSSE
|
|
384
|
-
submission proof. Current producer command receipts are unsigned
|
|
385
|
-
deployed hub does not supply a retry-safe target version.
|
|
387
|
+
submission proof. Current successful producer command receipts are unsigned
|
|
388
|
+
because the deployed hub does not supply a retry-safe target version.
|
|
389
|
+
|
|
390
|
+
An ordinary command submits its complete `CommandReceipt` only when it exits
|
|
391
|
+
successfully without a machinery error. A non-zero exit or machinery error is
|
|
392
|
+
not submitted as an artifact; the worker escalates it through `ask` on the
|
|
393
|
+
first owed path instead:
|
|
394
|
+
|
|
395
|
+
```json
|
|
396
|
+
{
|
|
397
|
+
"workflow": "<workflow>",
|
|
398
|
+
"run": "<run>",
|
|
399
|
+
"path": "<owed artifact path>",
|
|
400
|
+
"question": "<operator-facing failure diagnosis>",
|
|
401
|
+
"context": "<JSON-encoded CommandReceipt>"
|
|
402
|
+
}
|
|
403
|
+
```
|
|
404
|
+
|
|
405
|
+
The question identifies the command, exit code or signal, machinery error when
|
|
406
|
+
present, output byte counts, output hash, and captured output tail. The receipt
|
|
407
|
+
in `context` is diagnostic data, not a submitted value. A successful `ask`
|
|
408
|
+
freezes the owed artifact and closes the run; a human answers with the
|
|
409
|
+
artifact's retry path. Only the first owed path is escalated because `ask`
|
|
410
|
+
closes the run, so additional owed paths remain debts.
|
|
411
|
+
|
|
412
|
+
When a valid payload contains a plain-step `reject`, the command worker sends
|
|
413
|
+
the directive's `text` as the reject reason and, when command output is
|
|
414
|
+
available, appends the captured tail in this form:
|
|
415
|
+
|
|
416
|
+
```text
|
|
417
|
+
<text>
|
|
418
|
+
|
|
419
|
+
--- command output (last <N> bytes) ---
|
|
420
|
+
<tail>
|
|
421
|
+
```
|
|
422
|
+
|
|
423
|
+
The tail is the last 4 KiB of combined stdout-then-stderr output, decoded as
|
|
424
|
+
lossy UTF-8, with trailing newline characters removed before the byte count is
|
|
425
|
+
computed. `N` is the UTF-8 byte count of that trimmed tail. An empty tail leaves
|
|
426
|
+
the directive's text unchanged. The payload marker line is not removed from
|
|
427
|
+
the tail. This augmentation applies to payload rejects; judge rejects retain
|
|
428
|
+
their existing text-selection behavior.
|
|
386
429
|
|
|
387
430
|
A worker rejects an artifact through the `reject` verb. The request is exactly:
|
|
388
431
|
|
|
@@ -1,23 +1,40 @@
|
|
|
1
|
-
# Software-delivery wiring.
|
|
1
|
+
# Software-delivery wiring — a TEACHING EXAMPLE, not a production workflow.
|
|
2
2
|
#
|
|
3
|
-
#
|
|
4
|
-
#
|
|
5
|
-
#
|
|
6
|
-
#
|
|
7
|
-
#
|
|
8
|
-
#
|
|
3
|
+
# This file exists to show the engine's core dynamics in the fewest possible
|
|
4
|
+
# steps. It is NOT the delivery line this project's authors actually run, and
|
|
5
|
+
# it is not a copy of any deployed definition. The real one is a separately
|
|
6
|
+
# published workflow bundle named `owenloop-delivery`: an order of magnitude
|
|
7
|
+
# larger, with provisioner/deprovisioner lifecycle steps, a merge gate, mentor
|
|
8
|
+
# consults, capability routing and run modifiers. For an in-repo definition
|
|
9
|
+
# shaped like a real production line, read `ship.yaml` next door.
|
|
10
|
+
#
|
|
11
|
+
# What this one teaches: a linear pipeline where each step consumes the
|
|
12
|
+
# previous one's output and owes the next. The interesting dynamics are the
|
|
13
|
+
# *knock-backs* — the reviewer can reject the PR (re-arming the builder), and
|
|
14
|
+
# any upstream change cascades forward: a re-planned `plan` invalidates the
|
|
15
|
+
# `pr`, its `verdict`, and the `merge` automatically (the forward cascade, §7).
|
|
16
|
+
# The `merge` is terminal: once green it is a destructive completion and can
|
|
17
|
+
# never be re-armed (§15.2).
|
|
18
|
+
#
|
|
19
|
+
# Drive it (play every Step Agent yourself):
|
|
20
|
+
# export OWENLOOP_DEFS=examples/workflows
|
|
21
|
+
# export OWENLOOP_DB=/tmp/owenloop-delivery-demo.db
|
|
9
22
|
#
|
|
10
|
-
# Drive it (the "wiring" / worker step):
|
|
11
23
|
# wf=$(owenloop create delivery --provide proposal='{"text":"add dark mode"}' | jq -r .workflow)
|
|
12
|
-
# owenloop tick $wf
|
|
13
|
-
# owenloop green $wf
|
|
14
|
-
#
|
|
24
|
+
# run=$(owenloop tick $wf | jq -r '.orders[0].run') # -> the `planner` order
|
|
25
|
+
# owenloop green $wf $run plan --value '{"plan":"..."}'
|
|
26
|
+
# owenloop close $wf $run
|
|
27
|
+
# ... # tick/green/close down the chain
|
|
15
28
|
# owenloop reject $wf pr --by reviewer --text "tests missing" # knock-back
|
|
16
|
-
# owenloop status $wf # debts / eligible / blocked
|
|
29
|
+
# owenloop status $wf # done / debts / eligible / blocked / pending / inFlight
|
|
17
30
|
|
|
18
31
|
name: delivery
|
|
19
|
-
title: Software delivery
|
|
20
|
-
description:
|
|
32
|
+
title: Software delivery (teaching example)
|
|
33
|
+
description: >-
|
|
34
|
+
Plan → build → review → merge, with reviewer knock-backs. A minimal wiring
|
|
35
|
+
written to teach the engine's dynamics — not the production delivery line
|
|
36
|
+
(that is the separately published `owenloop-delivery` bundle); see ship.yaml
|
|
37
|
+
for a production-shaped definition.
|
|
21
38
|
outputs: [merge]
|
|
22
39
|
|
|
23
40
|
inputs:
|
|
@@ -6,8 +6,9 @@
|
|
|
6
6
|
# plan + provision → build → review → document → check → merge → clean up
|
|
7
7
|
#
|
|
8
8
|
# This is the grown-up sibling of delivery.yaml (which teaches the wiring in
|
|
9
|
-
# four steps). It's the line the authors actually run their own
|
|
10
|
-
# genericized: full artifact schemas, tiered models,
|
|
9
|
+
# four steps). It's modeled on the line the authors actually run their own
|
|
10
|
+
# changes down, genericized and trimmed: full artifact schemas, tiered models,
|
|
11
|
+
# honest escalation, and —
|
|
11
12
|
# the part most pipelines get wrong — the machine lifecycle as first-class
|
|
12
13
|
# steps. `provisioner` stands up the branch/worktree BEFORE the builder starts
|
|
13
14
|
# and owns it as the `workspace` artifact; `deprovisioner` reclaims it AFTER
|
|
@@ -342,6 +343,9 @@ steps:
|
|
|
342
343
|
branch: { type: string, minLength: 1 }
|
|
343
344
|
worktreePath: { type: string }
|
|
344
345
|
on: [inputsGreen] # fires exactly once when merge (terminal) AND workspace are green
|
|
346
|
+
onCancel:
|
|
347
|
+
consumes: [workspace] # cancelling must still reclaim the machine. merge is deliberately
|
|
348
|
+
# absent: it is terminal and never greens on a cancelled run.
|
|
345
349
|
model: fast # mechanical git teardown
|
|
346
350
|
reapTtl: 15m
|
|
347
351
|
body: |
|
|
@@ -369,3 +373,7 @@ steps:
|
|
|
369
373
|
time, so the artifact would be born-rejected on every firing. With
|
|
370
374
|
inputsGreen the fingerprint matches and, once green, re-firing is
|
|
371
375
|
suppressed because `merge` is terminal — so this runs exactly once.)
|
|
376
|
+
|
|
377
|
+
(Cancellation note: `onCancel:` is inert in the standalone engine. A
|
|
378
|
+
control plane that supports cancellation reads it to dispatch this
|
|
379
|
+
cleanup step with only the declared cancel-path inputs.)
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "owenloop",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.9",
|
|
4
4
|
"description": "Deterministic rails for agentic workflows. Declare steps and dependencies; the engine guarantees order, redoes what changes invalidate, and stops what keeps failing — instead of hoping the agent follows through.",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"author": "typicalday",
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "owenloop",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.9",
|
|
4
4
|
"description": "Claude Code driver for owenloop — cross-harness shift and conduct skills driven by the owenloop CLI, plus one hub control-plane MCP server backing an author skill and a fallback worker, for conducting and authoring workflows against your hosted owenloop server.",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Typical Day"
|
|
@@ -66,8 +66,7 @@ x:
|
|
|
66
66
|
```
|
|
67
67
|
|
|
68
68
|
`id` is optional. When `id` is absent, the runtime may select the registered
|
|
69
|
-
default adapter; `--harness`
|
|
70
|
-
over the definition. Keep policy in `x.harness` even when `id` is absent.
|
|
69
|
+
default adapter; a selected crew-roster candidate takes precedence; `--harness` is a local debug override. Keep policy in `x.harness` even when `id` is absent.
|
|
71
70
|
|
|
72
71
|
When a producer declares native `judges:`, put `x.harness` on the producer
|
|
73
72
|
step, not on each judge entry. Every synthesized judge automatically inherits
|
|
@@ -66,8 +66,7 @@ x:
|
|
|
66
66
|
```
|
|
67
67
|
|
|
68
68
|
`id` is optional. When `id` is absent, the runtime may select the registered
|
|
69
|
-
default adapter; `--harness`
|
|
70
|
-
over the definition. Keep policy in `x.harness` even when `id` is absent.
|
|
69
|
+
default adapter; a selected crew-roster candidate takes precedence; `--harness` is a local debug override. Keep policy in `x.harness` even when `id` is absent.
|
|
71
70
|
|
|
72
71
|
When a producer declares native `judges:`, put `x.harness` on the producer
|
|
73
72
|
step, not on each judge entry. Every synthesized judge automatically inherits
|