@adhdev/daemon-core 0.9.82-rc.545 → 0.9.82-rc.546

package/package.json

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

package/src/commands/router.ts

@@ -186,6 +186,15 @@ const MESH_FORWARDABLE_SESSION_COMMANDS = new Set([
     'set_mode',
     'change_model',
     'set_thought_level',
+    // set_conversation_prefs (per-session user Hide/Mute) is session-scoped: the daemon-owned
+    // userHidden/userMuted lives on the OWNING session's live instance (med-family handler
+    // getInstance → updateSettings). When the target is a REMOTE worker session the coordinator
+    // has no local instance, so without forwarding the handler returns 'Session not found', the
+    // dashboard's useConversationPrefs silently rolls back, and the stale worker surfaceHidden is
+    // re-stamped every snapshot tick (the "restore does nothing + flicker" defect, mission
+    // 6938892f). Forwarding to the owning worker lets it actually clear userHidden/userMuted and
+    // report a fresh surfaceHidden=false — which also resolves the re-stamp flicker at the source.
+    'set_conversation_prefs',
     // agent_command (send_chat / clear_history / stop) is session-scoped too: a command
     // explicitly naming a targetSessionId MUST reach that session wherever it lives, never a
     // different local session. Without forwarding, a misrouted/relayed send_chat for a REMOTE

package/src/mesh/mesh-work-queue.ts

@@ -948,6 +948,17 @@ export function enqueueTask(
     } & MeshQueueMutationOptions,
 ): MeshWorkQueueEntry {
     requireMeshHostQueueOwner(opts);
+    // DELIVERY-MSG-GUARD (upstream defence): a task whose message is undefined /
+    // non-string / blank must never reach the queue. Left unchecked it persists a
+    // message-less payload that later crashes insertSessionDelivery's NOT NULL at
+    // claim/dispatch time (the DB-level `message ?? ''` fallback still exists as
+    // depth-in-defence, but silently dispatching an empty prompt is itself a bug).
+    // Normalise and hard-reject at the single entry point so no caller can slip a
+    // blank task past the schema's nominal `required`.
+    message = String(message ?? '').trim();
+    if (!message) {
+        throw new Error('mesh task message must be a non-empty string');
+    }
     const readonly = opts?.readonly === true;
     const modeValidation = validateMeshTaskModeRequest(opts?.taskMode, message, readonly);
     if (!modeValidation.valid) {
@@ -1069,6 +1080,14 @@ export function recordDirectDispatchTask(
     if (!missionId) return null;
     const taskId = typeof opts.id === 'string' ? opts.id.trim() : '';
     if (!taskId) return null;
+    // DELIVERY-MSG-GUARD (upstream defence): the direct-dispatch path materialises the
+    // same message-carrying queue entry AND writes a session delivery (createSessionDelivery
+    // below), so a blank/undefined message would hit the same NOT NULL crash. Normalise and
+    // hard-reject before we record anything — consistent with enqueueTask.
+    message = String(message ?? '').trim();
+    if (!message) {
+        throw new Error('mesh task message must be a non-empty string');
+    }
     const readonly = opts.readonly === true;
     const modeValidation = validateMeshTaskModeRequest(opts.taskMode, message, readonly);
     if (!modeValidation.valid) {