@glyphteck/veyl 0.63.6 → 0.63.7

package/dist/cli.js

@@ -50263,7 +50263,7 @@ var package_default;
 var init_package2 = __esm(() => {
   package_default = {
     name: "veyl",
-    version: "0.63.6",
+    version: "0.63.7",
     packageManager: "bun@1.4.0",
     private: true,
     license: "UNLICENSED",

package/dist/index.js

@@ -50262,7 +50262,7 @@ var package_default;
 var init_package2 = __esm(() => {
   package_default = {
     name: "veyl",
-    version: "0.63.6",
+    version: "0.63.7",
     packageManager: "bun@1.4.0",
     private: true,
     license: "UNLICENSED",

package/examples/bot-fleet/readme.md

@@ -10,7 +10,7 @@ The secret-free version-2 manifest stores account indices, usernames, networks,
 - `echo` mirrors text, encrypted attachments, and payment requests with deterministic action ids. Group members derive exactly one source-specific eligible fleet echo from the encrypted roster for each source message; every other echo remains silent and only reads. Selection distributes independently across messages, so the same bot may legitimately win consecutive messages.
 - `faucet` pays valid requests through the public wallet API and journals caller operation ids.
 - `traffic` is an eligibility marker for an external local operator policy; it performs no work by itself.
-- `live` holds the account's normal encrypted live-room connection in each chat without advancing read state or sending messages.
+- `live` holds the account's normal encrypted live-room connection in each chat without advancing read state or sending messages. The concrete host supplies the same realm-matched portable live transport used by graphical clients; startup rejects this role when that client port is absent.
 - `typing` requires `live` and continually renews one stable composition through the same encrypted live state until the policy stops.
 
 Only response-capable fleet peers are loop-suppressed. Incoming transaction events and staggered fallback loops call the public wallet claim method. Startup replays a bounded visible window; an event checkpoint suppresses completed source messages, while the action journal suppresses completed effects and stops ambiguous payments for explicit reconciliation.

package/examples/bot-fleet/runtime.js

@@ -14,12 +14,30 @@ async function loadBotFleetPolicy(options) {
     return createBotFleetPolicy(options);
 }
 
+export async function resolveBotFleetClientOptions(source, profile) {
+    const options = typeof source === 'function'
+        ? await source(profile)
+        : source || {};
+    if (
+        profile?.roles?.includes('live')
+        && typeof options?.chat?.live?.connect !== 'function'
+    ) {
+        throw new Error(`live bot transport required: ${profile.profile}`);
+    }
+    return options;
+}
+
 export async function createExampleBotFleetRuntime(options = {}) {
     const eventOptions = options.eventOptions;
+    const clientOptions = options.clientOptions;
     let checkpoint = options.checkpoint || null;
     const owner = await openFleetOwner({
         ...options,
         bootConcurrency: options.bootConcurrency ?? 2,
+        clientOptions: (profile) => resolveBotFleetClientOptions(
+            clientOptions,
+            profile
+        ),
         policies: [],
         eventOptions: async (profile) => ({
             replay: true,

package/package.json

@@ -41,5 +41,5 @@
         "start": "node src/cli.js",
         "lint": "eslint src --quiet"
     },
-    "version": "0.63.6"
+    "version": "0.63.7"
 }