3 Commits

Author	SHA1	Message	Date
saravanakumardb1	d838cd658b	feat(cowork-service): IPC LLM interception — Rust runtime delegates LLM calls to multi-provider router ... Add reverse-IPC protocol support: Rust runtime can send intercept_llm requests to cowork-service, which routes them through @bytelyst/llm-router. Changes: - ipc-bridge.ts: handleLine now detects incoming requests (has 'method' field) vs normal responses. New handleIncoming() + sendResponse() for reverse IPC. New onIncomingRequest() to register the handler. - server.ts: Wires intercept_llm handler — validates messages, calls getLlmRouter().chat(), records spend for budget tracking, logs provider/model. - ipc-bridge.test.ts: 5 new tests for reverse IPC (handler registration, routing, error handling, request vs response disambiguation). - server.test.ts: Updated IPC bridge mock with onIncomingRequest. Test count: 85 (was 80)	2026-04-03 01:11:34 -07:00
saravanakumardb1	2191427605	fix(cowork-service): 3 bugs — flag names, IPC call guard, health status ... BUG 1: feature-flags.ts had 3 wrong flag names + missing 3 from seed.ts - Removed: browser_extension_enabled, institutional_knowledge_enabled - Renamed: connectors_enabled → mcp_connectors_enabled - Added: llm_multi_model_enabled, telemetry_enabled, platform_auth_required - Fixed defaults to match seed.ts (marketplace_enabled=true, dispatch_api_enabled=true) - Now 13 flags exactly matching platform-service/src/modules/flags/seed.ts BUG 2: ipc-bridge.ts call() had 'initialize' exemption that allowed null deref - If call('initialize') was invoked externally without start(), the guard passed but this.child!.stdin!.write() would crash with null dereference - During normal start(), child.stdin.writable is true so no exemption needed - Removed the method !== 'initialize' exemption BUG 3: health routes didn't factor IPC bridge into overall health status - allOk only checked platform-service reachability - Now allOk = depsOk && ipcConnected — service reports 503 when bridge is down - IPC bridge disconnection makes health 'degraded' (correct — fallback mode works) 24 tests passing, typecheck clean.	2026-04-02 22:20:52 -07:00
saravanakumardb1	19674c7ef7	feat(cowork-service): ecosystem alignment + IPC bridge to Rust runtime ... ECOSYSTEM GAPS CLOSED — cowork-service now matches the pattern used by all other product backends (FlowMonk, ActionTrail, NoteLett, etc.): New lib files (6): - lib/product-config.ts — canonical product identity (PRODUCT_ID, productConfig) - lib/auth.ts — @bytelyst/fastify-auth createAuthMiddleware - lib/request-context.ts — getUserId(), getRequestProductId() - lib/telemetry.ts — @bytelyst/backend-telemetry buffer - lib/feature-flags.ts — @bytelyst/backend-flags with 12 cowork flags - lib/ipc-bridge.ts — IpcBridge class: spawn Rust child, JSON-RPC, 13 methods Updated files: - lib/config.ts — extends @bytelyst/backend-config baseBackendConfigSchema - server.ts — JWT context, bootstrap endpoint, IPC startup, graceful shutdown - modules/tasks/routes.ts — IPC bridge forwarding with in-memory fallback - modules/health/routes.ts — productId from product-config, IPC status - package.json — 7 new @bytelyst/* workspace deps IPC bridge features: - Spawns cowork-orchestrator --ipc-bridge as child process - JSON-RPC 2.0 over stdin/stdout (line-delimited) - 13 convenience methods matching Rust IpcHandler - Timeout + pending request tracking - Graceful shutdown with SIGTERM - Singleton pattern with setIpcBridge() for testing 24 tests passing (was 8), typecheck clean.	2026-04-02 22:14:24 -07:00