@byollm/conformance 0.1.0-alpha.40 → 0.1.0-alpha.41
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 +19 -2
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
> [!WARNING]
|
|
2
|
-
> **Alpha (`0.1.0-alpha.
|
|
2
|
+
> **Alpha (`0.1.0-alpha.41`) — under active development. Don't use this yet.**
|
|
3
3
|
>
|
|
4
4
|
> Install it deliberately: `npm install @byollm/conformance@alpha`.
|
|
5
5
|
>
|
|
@@ -79,7 +79,7 @@
|
|
|
79
79
|
> packages published and `@byollm/server` did not: a Sigstore
|
|
80
80
|
> transparency-log 409 on its provenance attestation. The workflow's
|
|
81
81
|
> "already published" guard correctly refuses to resume a partial publish,
|
|
82
|
-
> so `0.1.0-alpha.
|
|
82
|
+
> so `0.1.0-alpha.41` is that release, whole.
|
|
83
83
|
>
|
|
84
84
|
> If you run the Supabase adapter, `alpha.21` needs
|
|
85
85
|
> `20260819010000_completed_by_lease_id.sql`: alpha.19 shipped §3.6's
|
|
@@ -98,6 +98,23 @@ If you are running via `npx`, install properly first (`npm install -g
|
|
|
98
98
|
byollm@alpha`) — `install` refuses to supervise a copy in npx's cache, because
|
|
99
99
|
npm deletes that directory and the service would fail at some later boot.
|
|
100
100
|
|
|
101
|
+
<!-- release-note 0.1.0-alpha.41 -->
|
|
102
|
+
**`onNoRunner` takes a string.** Your fallback answer is your own value, not
|
|
103
|
+
wire data, and handing back a whole result record for it was ceremony — the
|
|
104
|
+
README's own example got the shape wrong, which is how this was found.
|
|
105
|
+
|
|
106
|
+
```ts
|
|
107
|
+
const { outcome, fallback } = await job.result({
|
|
108
|
+
onNoRunner: () => runOnHostedModel(transcript),
|
|
109
|
+
});
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
Whatever you return, `result()` labels it `fallback: true` — the stamp is
|
|
113
|
+
applied by the wait, not taken from you, so an answer that did not run on
|
|
114
|
+
somebody's machine cannot be reported as though it did (`FALLBACK_LABELED`).
|
|
115
|
+
Both delivery channels do it, polling and Supabase Realtime. Records still
|
|
116
|
+
work; they just get labelled too.
|
|
117
|
+
|
|
101
118
|
# `@byollm/conformance`
|
|
102
119
|
|
|
103
120
|
The compatibility contract. **A server is byollm-compatible when this kit
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@byollm/conformance",
|
|
3
|
-
"version": "0.1.0-alpha.
|
|
3
|
+
"version": "0.1.0-alpha.41",
|
|
4
4
|
"description": "The BYOLLM compatibility contract — drive a real daemon against any server and assert every protocol MUST.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|
|
@@ -25,12 +25,12 @@
|
|
|
25
25
|
"node": ">=22.14"
|
|
26
26
|
},
|
|
27
27
|
"dependencies": {
|
|
28
|
-
"@byollm/protocol": "0.1.0-alpha.
|
|
29
|
-
"byollm": "0.1.0-alpha.
|
|
28
|
+
"@byollm/protocol": "0.1.0-alpha.41",
|
|
29
|
+
"byollm": "0.1.0-alpha.41"
|
|
30
30
|
},
|
|
31
31
|
"devDependencies": {
|
|
32
32
|
"@supabase/supabase-js": "^2.112.2",
|
|
33
|
-
"@byollm/server": "0.1.0-alpha.
|
|
33
|
+
"@byollm/server": "0.1.0-alpha.41"
|
|
34
34
|
},
|
|
35
35
|
"publishConfig": {
|
|
36
36
|
"access": "public"
|