@rivus/agent 0.4.0 → 0.4.1

package/README.md

@@ -1059,7 +1059,7 @@ const bootstrap = await Effect.runPromise(
 );
 ```
 
-The configured preparation helper creates a blue streaming CardKit entity, replies to the inbound Feishu message, and binds the run to the card target before any stream action is published. The running card includes a “Stop generating” button carrying `{ rivus_action: "cancel_run", run_id, session_key }`; completed, failed, and cancelled cards remove it. The configured publisher coalesces consecutive `update_text` actions by run, flushes the latest text before a terminal action, and exposes `flush(runId?)` for explicit worker-driven flushing. `createConfiguredRivusDaemonBootstrap` adds the event log, history restore helper, status reporter, optional status transport, WebSocket transport, worker loop, and managed process around those same pieces; `restoreConfiguredRivusDaemonBootstrap` first replays that event log as restored harness events so read models and same-session loop input are hydrated after restart. Local tests can use `createInMemoryFeishuCardTargetRegistry`; daemon processes should prefer `createJsonFileFeishuCardTargetRegistry` so run-to-card bindings survive restarts and malformed registry files fail loudly instead of being treated as empty state.
+The configured preparation helper creates a blue streaming CardKit entity, replies to the inbound Feishu message, and binds the run to the card target before any stream action is published. The running card includes a “Stop generating” button carrying `{ rivus_action: "cancel_run", run_id, session_key }`; completed, failed, and cancelled cards remove it. The configured publisher coalesces consecutive `update_text` actions by run, flushes the latest text before a terminal action, and exposes `flush(runId?)` for explicit worker-driven flushing. `createConfiguredRivusDaemonBootstrap` flushes pending text at `config.feishu.streamMinIntervalMs` by default; pass `flushIntervalMs` only to override that cadence. It also adds the event log, history restore helper, status reporter, optional status transport, WebSocket transport, worker loop, and managed process around those same pieces; `restoreConfiguredRivusDaemonBootstrap` first replays that event log as restored harness events so read models and same-session loop input are hydrated after restart. Local tests can use `createInMemoryFeishuCardTargetRegistry`; daemon processes should prefer `createJsonFileFeishuCardTargetRegistry` so run-to-card bindings survive restarts and malformed registry files fail loudly instead of being treated as empty state.
 
 ## Design Notes
 

package/dist/index.js

@@ -3131,7 +3131,7 @@ function createConfiguredRivusDaemonBootstrap(options) {
 		...options.initialEvents ? { initialEvents: options.initialEvents } : {},
 		...options.initialRunStates ? { initialRunStates: options.initialRunStates } : {},
 		loop: options.loop,
-		...periodicFlush ? { periodicFlush } : {},
+		periodicFlush,
 		prepareRun,
 		publish: (action) => publisher.publish(action),
 		runIds: options.runIds
@@ -3183,10 +3183,9 @@ function createConfiguredRivusDaemonBootstrap(options) {
 	};
 }
 function createPeriodicFlush(options, publisher) {
-	if (options.flushIntervalMs === void 0) return;
 	return createFeishuPeriodicFlush({
 		flush: () => publisher.flush(),
-		intervalMs: options.flushIntervalMs,
+		intervalMs: options.flushIntervalMs ?? options.config.feishu.streamMinIntervalMs,
 		sleep: options.sleep
 	});
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rivus/agent",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "A local agent daemon core built around a usable agent harness and domain events.",
   "type": "module",
   "license": "MIT",