owenloop 0.5.11 → 0.5.12

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 CHANGED
@@ -4,6 +4,13 @@ All notable changes to this project are documented here. The format is based on
4
4
  [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project
5
5
  adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
6
6
 
7
+ ## [0.5.12](https://github.com/typicalday/owenloop/compare/v0.5.11...v0.5.12) (2026-08-21)
8
+
9
+
10
+ ### Bug Fixes
11
+
12
+ * **engine:** count callsInputs wiring as a consumer in the dead-end lint ([#265](https://github.com/typicalday/owenloop/issues/265)) ([9d2df92](https://github.com/typicalday/owenloop/commit/9d2df92c5cd18418b5eaee170e2d7c9099521f18))
13
+
7
14
  ## [0.5.11](https://github.com/typicalday/owenloop/compare/v0.5.10...v0.5.11) (2026-08-21)
8
15
 
9
16
 
package/dist/src/defs.js CHANGED
@@ -1840,8 +1840,11 @@ function reachabilityErrors(def, danglingSteps) {
1840
1840
  * explicitly intended sinks. Stems declared under generates: are exempt.
1841
1841
  */
1842
1842
  function deadEndWarnings(def) {
1843
- // all stems consumed by any step
1844
- const consumed = new Set(def.steps.flatMap((l) => l.consumes.map((c) => c.stem)));
1843
+ // all stems consumed by any ordinary or child-workflow step
1844
+ const consumed = new Set(def.steps.flatMap((l) => [
1845
+ ...l.consumes.map((c) => c.stem),
1846
+ ...Object.values(l.callsInputs ?? {}),
1847
+ ]));
1845
1848
  // stems declared under generates: are intentionally unconsumed — lint-exempt
1846
1849
  const generatedStems = new Set(def.steps.flatMap((l) => (l.generates ?? []).map((p) => p.stem)));
1847
1850
  // stems declared in workflow outputs: are intentional public leaves — lint-exempt
@@ -61,11 +61,9 @@ const OUR_PROTOCOL_VERSION = '2025-06-18';
61
61
  //
62
62
  // Commit the charter edit and the regenerated baseline together.
63
63
  //
64
- // One run is one sample, not a measurement. Codex's score moves between runs
65
- // at a FIXED charter sha: 35773e2e scored 3/4, 4/4 and 4/4 on three runs
66
- // across fifteen minutes. Read the committed number as a point in a range, and
67
- // re-run before concluding an edit helped or hurt. The run history and the
68
- // per-arm ranges live in docs/mcp-charter-eval.md.
64
+ // The unchanged 35773e2e control has ten Claude 4/4 samples and Codex values
65
+ // 3, 4, 4, 2, 3, 2, 2, 3, 3, 3. No charter effect can be inferred from the
66
+ // Codex score; the full negative-result finding is in docs/mcp-charter-eval.md.
69
67
  //
70
68
  // search_workflows is deliberately NOT named here. The eval scores the first
71
69
  // tool call, and offering a second discovery verb in the charter competes with
package/docs/authoring.md CHANGED
@@ -451,6 +451,11 @@ if nothing consumes it. A stem under `generates:` is deliberately consumed by no
451
451
  are otherwise identical: schema-validated, fingerprinted, greenable, and visible in
452
452
  `status`/`show`.
453
453
 
454
+ Call steps are also consumers for this check. For `calls:` and `callsInterface:`, each
455
+ parent-artifact value in the child-input `inputs:` mapping counts as consumed even when
456
+ the step's ordinary `consumes:` list is empty; the mapping keys are child input names and
457
+ do not count.
458
+
454
459
  ## `bind:` — write an accepted artifact into run state
455
460
 
456
461
  A produce mapping may declare a `bind:` target. When that artifact is accepted,
package/docs/design.md CHANGED
@@ -628,7 +628,7 @@ A green, value-defined declared outcome may carry a status-bearing value (e.g. `
628
628
 
629
629
  #### §23.6.5 Gate fingerprint and re-arm
630
630
 
631
- The machine-green fingerprint covers `gateStems` (the parent artifacts wired into the child via `callsInputs`) plus, as of F4 (§23.6.8), a reserved `__child_outcome_version__` key pinning the child outcome's version. The cross-instance join/re-green trigger is handled by `maintainCalls`'s outcome-value, `workflowDone`, and version-pin checks, not by green-fingerprint invalidation in the pure forward cascade: a calls: step still declares `consumes: []`, and its live green fingerprint must not be compared with the gate-only dependency set. Maintenance does use `callsInputs` separately to find dead gate branches, structurally skip the calls output and its downstream branch, and revive an engine-authored cascade skip after the gate returns green with moved versions. Human or producer skips retain the child-outcome pin semantics in §23.6.8 and are not revived merely because the gate is green.
631
+ The machine-green fingerprint covers `gateStems` (the parent artifacts wired into the child via `callsInputs`) plus, as of F4 (§23.6.8), a reserved `__child_outcome_version__` key pinning the child outcome's version. The cross-instance join/re-green trigger is handled by `maintainCalls`'s outcome-value, `workflowDone`, and version-pin checks, not by green-fingerprint invalidation in the pure forward cascade: a calls: step still declares `consumes: []`, and its live green fingerprint must not be compared with the gate-only dependency set. Dead-end lint nevertheless treats every parent-artifact value in `callsInputs` as consumed; these values are lint consumers, not ordinary `consumes:` edges. Maintenance does use `callsInputs` separately to find dead gate branches, structurally skip the calls output and its downstream branch, and revive an engine-authored cascade skip after the gate returns green with moved versions. Human or producer skips retain the child-outcome pin semantics in §23.6.8 and are not revived merely because the gate is green.
632
632
 
633
633
  #### §23.6.6 Transaction composition
634
634
 
@@ -62,38 +62,107 @@ ordered calls, response evidence, classifications, and score. A charter edit
62
62
  changes the served-byte hash, so it creates a new attributable score rather
63
63
  than inheriting an old baseline.
64
64
 
65
- The committed [baseline](evals/mcp-charter-baseline.json) records a complete
66
- 2026-08-20 run for charter hash
67
- `35773e2e269844fbb81acec0c07774f5674d51aa47304f6e0346458a13f9a2a2`.
68
- Claude Code 2.1.236 using `claude-opus-5` passed 4/4 clear tasks, and Codex
69
- 0.147.0 using `gpt-5.6-sol` also passed 4/4.
70
-
71
- One run is one sample. Codex's score moves between runs at a fixed charter hash,
72
- so read any single number as a point in a range, and re-run before concluding
73
- that a charter edit helped or hurt. Six runs on 2026-08-20, all on the same
74
- harness versions and models:
75
-
76
- | charter hash | runs | Claude | Codex |
77
- | --- | --- | --- | --- |
78
- | `dfb67821` (previous charter) | 2 | 4/4, 4/4 | 1/4, 2/4 |
79
- | `bdbd33e3` (discarded wording) | 1 | 4/4 | 2/4 |
80
- | `35773e2e` (this charter) | 3 | 4/4, 4/4, 4/4 | 3/4, 4/4, 4/4 |
81
-
82
- Only the committed run's JSON lives in this repository. The other five were kept
83
- outside it and are quoted here for the range, not as artifacts you can re-read.
84
- Codex's range under this charter does not overlap its range under the previous
85
- one, which is the evidence that moving the catalog rule to the front of the
86
- charter changed behaviour. Three runs in an arm is a direction, not a
87
- significance claim.
88
-
89
- The retained no-match and ambiguous responses were reviewed. Claude calls the
90
- catalog first on all four and says plainly that no published playbook fits.
91
- Codex now calls the catalog first on both no-match tasks, which is what the
92
- score measures, but its prose is weaker: it names the mismatch on the finance
93
- task and simply asks for missing inputs on the operations one. On the unscored
94
- `ambiguous-launch` task Codex still makes no call at all, so the charter's
95
- every-request rule is not fully carried even in the runs that score 4/4. The
96
- prose review does not alter either harness's numeric score.
65
+ ## W3.3b negative result
66
+
67
+ W3.3b does **not** ship a compose-clause charter change. The pre-compose
68
+ charter and its generated baseline are restored because this evaluation provides
69
+ no evidence that the candidate clause helps. No further cohort, Node pinning,
70
+ charter wording iteration, or baseline generation is authorized in this unit.
71
+ The completed deliverable is this reproducible negative result and its separate
72
+ evaluator finding.
73
+
74
+ The committed [baseline](evals/mcp-charter-baseline.json) is restored exactly to
75
+ the generated pre-compose sample at
76
+ `35773e2e269844fbb81acec0c07774f5674d51aa47304f6e0346458a13f9a2a2`, generated
77
+ at 2026-08-20T13:53:53.975Z with Node v22.22.3. It is a historical generated
78
+ point and a hash-consistency anchor, not a stable both-harness floor. This unit
79
+ generated no new baseline and did not hand-edit or substitute report JSON.
80
+
81
+ ### Corrected control record
82
+
83
+ The earlier description of `35773e2e` as a both-harness 4/4 floor came from one
84
+ lucky draw and is corrected here. The full unchanged-control record supersedes
85
+ that claim: Claude Code scored 4/4 in all ten samples, while Codex scored
86
+ `3, 4, 4, 2, 3, 2, 2, 3, 3, 3`. The original both-harness 4/4 gate is therefore
87
+ unsatisfiable by the unmodified control as a reliable acceptance rule. The
88
+ builder correctly stopped on that gate; the problem was the instrument, not a
89
+ failure to complete an authorized clause iteration.
90
+
91
+ | charter | status | samples | Claude Code | Codex |
92
+ | --- | --- | ---: | --- | --- |
93
+ | `35773e2e` | unchanged pre-compose control | 10 | 4/4, 4/4, 4/4, 4/4, 4/4, 4/4, 4/4, 4/4, 4/4, 4/4 | 3/4, 4/4, 4/4, 2/4, 3/4, 2/4, 2/4, 3/4, 3/4, 3/4 |
94
+
95
+ This is aggregate historical evidence, not a same-environment
96
+ candidate/control cohort. Claude has no scored headroom to demonstrate an
97
+ improvement, while Codex's unchanged-control variation swamps a possible clause
98
+ effect. The candidate neither caused a Codex regression nor passed by avoiding
99
+ unsafe starts: its score differences cannot be attributed to the wording.
100
+
101
+ ### What the scorer measures
102
+
103
+ `discoveredFirst` and `scoreTask` in
104
+ `test/helpers/mcp-charter-eval.ts:475-503` require every non-ambiguous task to
105
+ start with `list_workflows({})`. Only after that check does the no-match branch
106
+ test `starts.length === 0`. A zero-call refusal consequently fails because
107
+ `calls[0]` is absent even when it made no unsafe `start_run`. The structured
108
+ trace is the score; refusal prose, catalog language, or a no-inline promise
109
+ cannot substitute for an observed first tool call or prove a zero-call trace.
110
+ Raw response evidence remains qualitative and separate from the score.
111
+
112
+ ### Fixed-fixture limitation
113
+
114
+ The ambiguous tasks cannot validate W3.3a composition. The fixture exposes only
115
+ `code-delivery` and `library-build`; it supplies no two compatible targets for
116
+ these requests and does not mount the plan skill or the compiler/approval
117
+ lifecycle. No ambiguous response proves that a composite compiled, parked,
118
+ released, or executed. Those tasks remain non-gating observations, and the
119
+ four-task denominator is unchanged.
120
+
121
+ ### Stopped protocol and historical-only reports
122
+
123
+ The earlier counterbalanced protocol is preserved as historical context, not as
124
+ an instruction to sample again. Its symmetric stop rule fired on a Node-version
125
+ treatment drift. All four completed reports are complete and scoreable, retain
126
+ the same fixture digest, reported models, and harness versions, and remain
127
+ trustworthy measurements of their actual executions. They are historical-only
128
+ because the cross-arm Node difference makes them invalid as a treatment
129
+ comparison; no report was dropped, replaced, normalized, or reinterpreted.
130
+
131
+ | report | charter | Node | Claude Code | Codex |
132
+ | --- | --- | --- | --- | --- |
133
+ | control-1 | control `35773e2e` | v26.5.0 | 4/4 | 3/4 |
134
+ | candidate-1 | candidate `8f08991d` | v22.22.3 | 4/4 | 2/4 |
135
+ | candidate-2 | candidate `8f08991d` | v22.22.3 | 4/4 | 3/4 |
136
+ | control-2 | control `35773e2e` | v26.5.0 | 4/4 | 3/4 |
137
+
138
+ `control-3` was interrupted with exit 130 and produced no report;
139
+ `candidate-3` never ran. The four verbatim raw reports and the original protocol
140
+ comment remain attached to PR #255 as evidence. Node drift is a secondary run
141
+ limitation, not a reason to authorize another cohort: pinning Node would not
142
+ give this fixture a discriminating acceptance gate.
143
+
144
+ ## FINDING: separate no-start safety from catalog-discovery adherence, and make the evaluator runtime treatment explicit
145
+
146
+ Two independent evaluator defects need a separately scoped follow-up unit:
147
+
148
+ - **Conflated no-match criterion.** The scorer combines “did not start an
149
+ unsupported workflow” and “called `list_workflows({})` first” into one pass.
150
+ A correct zero-call refusal is safe on the first dimension but fails the
151
+ combined score on the second. A future unit must decide and test these
152
+ dimensions explicitly instead of treating either as proof of the other.
153
+ - **Uncontrolled Node treatment.** The harness and protocol do not pin Node or
154
+ enforce arm-local Node provenance as a treatment invariant. Metadata exposed
155
+ v26.5.0 versus v22.22.3 only after the fact and did not prevent the drift.
156
+
157
+ This unit records the finding only. It makes no scorer, fixture, denominator,
158
+ classification, evaluator, runtime, or Node-pinning change.
159
+
160
+ ### Outcome
161
+
162
+ The compose clause and its candidate baseline are dropped. PR #255 remains open
163
+ as the reviewable negative-result deliverable: it preserves the raw evidence,
164
+ documents the evaluation's limits, and names the follow-up finding without
165
+ implementing it.
97
166
 
98
167
  ## Safety and baseline updates
99
168
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "owenloop",
3
- "version": "0.5.11",
3
+ "version": "0.5.12",
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.11",
3
+ "version": "0.5.12",
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"
@@ -7,7 +7,7 @@
7
7
  "mcp"
8
8
  ],
9
9
  "env": {
10
- "OWENLOOP_PLUGIN_VERSION": "0.5.11"
10
+ "OWENLOOP_PLUGIN_VERSION": "0.5.12"
11
11
  }
12
12
  }
13
13
  }
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "owenloop",
3
- "version": "0.5.11",
3
+ "version": "0.5.12",
4
4
  "description": "Codex plugin for the owenloop workflow engine.",
5
5
  "skills": "./skills/",
6
6
  "mcpServers": "./.mcp.json"
@@ -6,7 +6,7 @@
6
6
  "mcp"
7
7
  ],
8
8
  "env": {
9
- "OWENLOOP_PLUGIN_VERSION": "0.5.11"
9
+ "OWENLOOP_PLUGIN_VERSION": "0.5.12"
10
10
  },
11
11
  "env_vars": [
12
12
  "HOME",