@pellux/goodvibes-tui 0.19.4 → 0.19.7

package/CHANGELOG.md

@@ -4,6 +4,48 @@ All notable changes to GoodVibes TUI.
 
 ---
 
+## [0.19.7] - 2026-04-18
+
+### Changed
+- Bumped `@pellux/goodvibes-sdk` from 0.21.10 to 0.21.12.
+
+### Investigation: No TUI-side changes required
+
+SDK 0.21.12 ships three additive changes to the daemon:
+
+1. **`kind: 'message'` at `POST /api/sessions/:id/messages`** now calls `sessionBroker.submitMessage()` (previously called `appendCompanionMessage` + `publishConversationFollowup` only). A real turn is started and the full agent event chain (TURN_STARTED, STREAM_DELTA, TURN_COMPLETED) streams back.
+
+2. **`kind: 'followup'`** — new kind value that always spawns an agent. Full agent event chain streams to companion SSE.
+
+3. **`GET /api/sessions/:id/events`** — new session-scoped SSE endpoint for companion consumption.
+
+4. **`'turn'` added to `DEFAULT_DOMAINS`** in the control-plane gateway — turn events are now auto-delivered to all SSE subscribers.
+
+Investigation of the TUI's `COMPANION_MESSAGE_RECEIVED` subscription in `src/runtime/bootstrap-core.ts` found **no double-render risk**: SDK 0.21.12 emits `COMPANION_MESSAGE_RECEIVED` _before_ calling `submitMessage`, so the user message is shown once (via the existing subscription), and the AI response streams in via the existing `uiServices.events.turns` path. These are distinct content on distinct code paths. No deduplication needed.
+
+The `'turn'` addition to `DEFAULT_DOMAINS` affects external SSE subscribers (companion app). The TUI consumes turn events in-process via the runtime bus — unaffected.
+
+Updated `docs/foundation-artifacts/operator-contract.json` SDK version field to `0.21.12`.
+
+---
+
+## [0.19.6] - 2026-04-18
+
+### Fixed
+- Bumped `@pellux/goodvibes-sdk` to 0.21.10 (up from 0.21.8 which was pinned by mistake in 0.19.5). 0.19.5 subscribed to the `COMPANION_MESSAGE_RECEIVED` runtime event but remained on an SDK version that didn't emit it, so the "companion main-chat messages render in TUI" fix from 0.19.5 didn't actually work. 0.19.6 corrects the dep so the subscription is live against an SDK that emits the event. Removed the `as Parameters<typeof runtimeBus.on>[0]` type cast that was hiding the version gap.
+
+---
+
+## [0.19.5] - 2026-04-18
+
+### Fixed
+- Companion-app messages sent via POST `/api/sessions/:id/messages` (kind `message`) are now rendered in the TUI conversation view immediately upon receipt. Previously the 202 was acknowledged and the message was persisted (SDK 0.21.9), but the TUI conversation never displayed it. The fix subscribes to the new `COMPANION_MESSAGE_RECEIVED` runtime bus event (emitted by the daemon's HTTP router after persistence, added in SDK 0.21.10) and calls `conversation.addUserMessage()` to surface the message inline.
+
+### Changed
+- SDK dependency remains `@pellux/goodvibes-sdk@0.21.8` (published); the `COMPANION_MESSAGE_RECEIVED` event type is cast at the call-site until SDK 0.21.10 is available on npm.
+
+---
+
 ## [0.19.4] - 2026-04-18
 
 ### Changed

package/README.md

@@ -2,7 +2,7 @@
 
 [![CI](https://github.com/mgd34msu/goodvibes-tui/actions/workflows/ci.yml/badge.svg)](https://github.com/mgd34msu/goodvibes-tui/actions/workflows/ci.yml)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
-[![Version](https://img.shields.io/badge/version-0.19.4-blue.svg)](https://github.com/mgd34msu/goodvibes-tui)
+[![Version](https://img.shields.io/badge/version-0.19.7-blue.svg)](https://github.com/mgd34msu/goodvibes-tui)
 
 A terminal-native AI coding, operations, automation, knowledge, and integration console with a typed runtime, omnichannel surfaces, structured memory/knowledge, and a raw ANSI renderer.
 

package/docs/foundation-artifacts/operator-contract.json

@@ -3,7 +3,7 @@
   "product": {
     "id": "goodvibes",
     "surface": "operator",
-    "version": "0.21.8"
+    "version": "0.21.12"
   },
   "auth": {
     "modes": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pellux/goodvibes-tui",
-  "version": "0.19.4",
+  "version": "0.19.7",
   "description": "Terminal-native GoodVibes product for coding, operations, automation, knowledge, channels, and daemon-backed control-plane workflows.",
   "type": "module",
   "main": "src/main.ts",
@@ -89,7 +89,7 @@
     "@anthropic-ai/vertex-sdk": "^0.16.0",
     "@ast-grep/napi": "^0.42.0",
     "@aws/bedrock-token-generator": "^1.1.0",
-    "@pellux/goodvibes-sdk": "0.21.8",
+    "@pellux/goodvibes-sdk": "0.21.12",
     "bash-language-server": "^5.6.0",
     "fuse.js": "^7.1.0",
     "graphql": "^16.13.2",

package/src/runtime/bootstrap-core.ts

@@ -16,6 +16,7 @@ import type { MutableRuntimeState } from '@pellux/goodvibes-sdk/platform/runtime
 import type { BootstrapOptions } from './context.ts';
 import { createFeatureFlagManager } from '@pellux/goodvibes-sdk/platform/runtime/feature-flags/index';
 import { RuntimeEventBus } from '@pellux/goodvibes-sdk/platform/runtime/events/index';
+import type { SessionEvent } from '@pellux/goodvibes-sdk/platform/runtime/events/index';
 import { createRuntimeStore, createDomainDispatch, type RuntimeStore } from './store/index.ts';
 import { ForensicsCollector, ForensicsRegistry } from '@pellux/goodvibes-sdk/platform/runtime/forensics/index';
 import {
@@ -285,6 +286,23 @@ export async function initializeBootstrapCore(
     wrfcController: services.wrfcController,
   });
 
+  // Subscribe to companion follow-up messages received from the daemon's HTTP layer.
+  // The daemon emits COMPANION_MESSAGE_RECEIVED on the runtime bus (SDK 0.21.10+).
+  // In SDK 0.21.12, kind='message' at POST /api/sessions/:id/messages now also calls
+  // sessionBroker.submitMessage(), starting a real turn. COMPANION_MESSAGE_RECEIVED
+  // still fires BEFORE submitMessage so the user message appears immediately in the
+  // conversation view, and the AI response streams in via the normal turn path.
+  // No double-render: COMPANION_MESSAGE_RECEIVED adds the user message once; the turn
+  // path adds the AI response. Both paths are correctly wired with no changes required.
+  // after persisting the message, so the TUI conversation view can render it immediately.
+  runtimeUnsubs.push(runtimeBus.on<Extract<SessionEvent, { type: 'COMPANION_MESSAGE_RECEIVED' }>>(
+    'COMPANION_MESSAGE_RECEIVED',
+    ({ payload }) => {
+      conversation.addUserMessage(payload.body);
+      requestRender();
+    },
+  ));
+
   providerRegistry.startWatching(runtimeBus);
 
   const webhookUrls = (configManager.getCategory('notifications') as { webhookUrls?: string[] }).webhookUrls ?? [];

package/src/version.ts

@@ -6,7 +6,7 @@ import { join } from 'node:path';
 // The prebuild script updates the fallback value before compilation.
 // Uses import.meta.dir (Bun) to locate package.json relative to this file,
 // which is correct regardless of the process working directory.
-let _version = '0.19.4';
+let _version = '0.19.7';
 try {
   const pkg = JSON.parse(readFileSync(join(import.meta.dir, '..', 'package.json'), 'utf-8'));
   _version = pkg.version ?? _version;