@byollm/protocol 0.1.0-alpha.66 → 0.1.0-alpha.67

package/README.md

@@ -1,5 +1,5 @@
 > [!WARNING]
-> **Alpha (`0.1.0-alpha.66`) — under active development. Don't use this yet.**
+> **Alpha (`0.1.0-alpha.67`) — under active development. Don't use this yet.**
 >
 > Install it deliberately: `npm install @byollm/protocol@alpha`.
 >
@@ -83,7 +83,7 @@
 > packages published and `@byollm/server` did not: a Sigstore
 > transparency-log 409 on its provenance attestation. The workflow's
 > "already published" guard correctly refuses to resume a partial publish,
-> so `0.1.0-alpha.66` is that release, whole.
+> so `0.1.0-alpha.67` is that release, whole.
 >
 > If you run the Supabase adapter, `alpha.21` needs
 > `20260819010000_completed_by_lease_id.sql`: alpha.19 shipped §3.6's

package/dist/index.d.ts

@@ -2110,6 +2110,7 @@ declare const Capability: z.ZodObject<{
         process: "process";
     }>;
     model: z.ZodString;
+    knownModels: z.ZodOptional<z.ZodArray<z.ZodString>>;
     offerScope: z.ZodEnum<{
         private: "private";
         team: "team";
@@ -2149,6 +2150,7 @@ declare const CapabilityMatrix: z.ZodArray<z.ZodObject<{
         process: "process";
     }>;
     model: z.ZodString;
+    knownModels: z.ZodOptional<z.ZodArray<z.ZodString>>;
     offerScope: z.ZodEnum<{
         private: "private";
         team: "team";
@@ -2255,6 +2257,7 @@ declare const PairStartRequest: z.ZodObject<{
             process: "process";
         }>;
         model: z.ZodString;
+        knownModels: z.ZodOptional<z.ZodArray<z.ZodString>>;
         offerScope: z.ZodEnum<{
             private: "private";
             team: "team";
@@ -2344,6 +2347,7 @@ declare const PairRequest: z.ZodDiscriminatedUnion<[z.ZodObject<{
             process: "process";
         }>;
         model: z.ZodString;
+        knownModels: z.ZodOptional<z.ZodArray<z.ZodString>>;
         offerScope: z.ZodEnum<{
             private: "private";
             team: "team";
@@ -2390,6 +2394,7 @@ declare const ClaimRequest: z.ZodObject<{
             process: "process";
         }>;
         model: z.ZodString;
+        knownModels: z.ZodOptional<z.ZodArray<z.ZodString>>;
         offerScope: z.ZodEnum<{
             private: "private";
             team: "team";
@@ -2477,6 +2482,7 @@ declare const HeartbeatRequest: z.ZodObject<{
             process: "process";
         }>;
         model: z.ZodString;
+        knownModels: z.ZodOptional<z.ZodArray<z.ZodString>>;
         offerScope: z.ZodEnum<{
             private: "private";
             team: "team";

package/dist/index.js

@@ -1817,6 +1817,26 @@ var Capability = z11.object({
   backendId: BackendIdSchema,
   backendClass: BackendClass,
   model: z11.string().min(1),
+  /**
+   * Models this device's CLI knows about — byollm_017 ruling 3.
+   *
+   * **Suggestions, not a vocabulary.** Free text is always allowed: the
+   * promise is that a model released this morning works this morning, and a
+   * frozen list anywhere a person picks from breaks that on the first day
+   * it matters. What makes free text safe is ruling 2 — a model is probed
+   * before it is stored, so "found is not works" is answered by the device
+   * rather than by a list.
+   *
+   * Announced with the capability rather than kept in the dashboard,
+   * because the answer is "what does THIS device's CLI know" and only the
+   * device can say. A list held cloud-side would be one more thing to
+   * update on release day, and wrong for anybody who had not upgraded.
+   *
+   * Optional, and empty is legal. A backend with nothing to suggest — a
+   * local server serving one model — is not a backend in an error state,
+   * and a reader must not render an absent list as "no models available".
+   */
+  knownModels: z11.array(z11.string().min(1)).optional(),
   offerScope: OfferScope
 }).strict();
 var CapabilityMatrix = z11.array(Capability);