@adhdev/daemon-core 0.9.82-rc.439 → 0.9.82-rc.440

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adhdev/daemon-core",
-  "version": "0.9.82-rc.439",
+  "version": "0.9.82-rc.440",
   "description": "ADHDev daemon core — CDP, IDE detection, providers, command execution",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -46,7 +46,7 @@
   "author": "vilmire",
   "license": "AGPL-3.0-or-later",
   "dependencies": {
-    "@adhdev/mesh-shared": "0.9.82-rc.439",
+    "@adhdev/mesh-shared": "0.9.82-rc.440",
     "@adhdev/session-host-core": "*",
     "@agentclientprotocol/sdk": "^0.16.1",
     "ajv": "^8.20.0",

package/src/commands/med-family/mesh-crud.ts

@@ -732,6 +732,29 @@ export const meshCrudHandlers: Record<string, MedFamilyHandler> = {
                 // keeps showing up in the dashboard graph until the cache
                 // ages out on its own.
                 if (removed) ctx.invalidateAggregateMeshStatus(meshId);
+                // MESH-INLINE-NODE-RESURRECTION: removeInlineMeshNode only mutates
+                // the in-memory inlineMeshCache + tombstones — it does NOT touch
+                // the file-backed config (meshes.json). When the SAME node also
+                // lives in meshes.json (a worktree node that was persisted to the
+                // file config, then resolved through the inline cache on removal),
+                // the file record survives. On daemon restart the in-memory
+                // tombstone is lost, getMesh falls back to the file config, and
+                // mesh-status renders the dead node again. So a node present in
+                // BOTH the inline cache AND meshes.json must be spliced+saved from
+                // the file config here too. Pure-inline meshes (no matching file
+                // mesh/node) are untouched — getMesh returns undefined and we skip.
+                try {
+                    const { getMesh, removeNode } = await import('../../config/mesh-config.js');
+                    const fileMesh = getMesh(meshId);
+                    const fileNode = fileMesh?.nodes?.find((n: any) => meshNodeIdMatches(n, nodeId));
+                    if (fileNode?.id) {
+                        const fileRemoved = removeNode(meshId, fileNode.id);
+                        if (fileRemoved) {
+                            removed = true;
+                            ctx.invalidateAggregateMeshStatus(meshId);
+                        }
+                    }
+                } catch { /* file config absent / unreadable — inline-only mesh, nothing to durably delete */ }
                 // Node was already absent from the inline mesh (e.g. removed by a
                 // prior refine cleanup). Treat as removed so caller gets removed:true.
                 if (!removed && !node) removed = true;

package/src/providers/native-history/hermes-cli-transcript.ts

@@ -70,10 +70,17 @@ function openDb(): any | null {
 }
 
 function loadMessagesForSession(db: any, sessionId: string): NativeHistoryMessage[] {
+    // Assistant turns whose finish_reason='tool_calls' persist an EMPTY
+    // `content` — their payload lives in the `tool_calls` column. Filtering on
+    // `content != ''` alone drops those rows, so a turn whose terminal message
+    // is a tool call surfaces zero assistant bubbles. Accept a row when either
+    // `content` OR `tool_calls` is non-empty, and project `tool_calls` into the
+    // content slot when `content` is empty so the bubble still carries text.
     const rows: any[] = db.prepare(
-        `SELECT id, role, content, timestamp
+        `SELECT id, role, COALESCE(NULLIF(content, ''), tool_calls) AS content, timestamp
          FROM messages
-         WHERE session_id = ? AND content IS NOT NULL AND content != ''
+         WHERE session_id = ?
+           AND ((content IS NOT NULL AND content != '') OR (tool_calls IS NOT NULL AND tool_calls != ''))
          ORDER BY timestamp ASC, id ASC`,
     ).all(sessionId);
     const out: NativeHistoryMessage[] = [];
@@ -115,10 +122,16 @@ export function readSession(sessionPath: string, requestedSessionId?: string): N
                 sessionId = pinned;
             } else {
                 // No bound id yet (discovery): pick the newest source='cli'
-                // session that has at least one persisted message.
+                // session that has at least one persisted message. Use an
+                // EXISTS check against `messages` rather than the denormalized
+                // `message_count` column — a freshly-started session already
+                // has message rows while `message_count` (DEFAULT 0) can still
+                // lag at 0, and the old predicate excluded exactly that
+                // just-created session, resolving to nothing.
                 const row: any = db.prepare(
                     `SELECT id, started_at FROM sessions
-                     WHERE source = 'cli' AND message_count > 0
+                     WHERE source = 'cli'
+                       AND EXISTS (SELECT 1 FROM messages m WHERE m.session_id = sessions.id)
                      ORDER BY started_at DESC LIMIT 1`,
                 ).get();
                 if (!row) return null;
@@ -185,7 +198,8 @@ export async function listSessions(_watchPath: string): Promise<NativeHistorySes
             const rows: any[] = db.prepare(
                 `SELECT id, started_at, ended_at, message_count, title
                  FROM sessions
-                 WHERE source = 'cli' AND message_count > 0
+                 WHERE source = 'cli'
+                   AND EXISTS (SELECT 1 FROM messages m WHERE m.session_id = sessions.id)
                  ORDER BY started_at DESC LIMIT 100`,
             ).all();
             const mtime = statMtimeMs(HERMES_STATE_DB);