@try-works/dsh-memory 0.1.5 → 0.1.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@try-works/dsh-memory",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "description": "Git-backed, workspace-scoped memory for the DeepSeek Harness (global layer + per-workspace layers)",
   "type": "module",
   "main": "src/index.js",

package/src/client/index.js

@@ -618,38 +618,48 @@ window.__ModuleLoader__.load({
           name: 'tool.call.toolview',
           key: 'memory_map',
         }, MemoryMapCard)))
-        // The Memory tab. Data arrives through a registered standard hook, because a
-        // conversation view is a slot and slots are fed by hooks, not by direct reads.
-        // The Trajectory target is the shipped assembly of this session's nodes, so the
-        // source re-derives the memory snapshot from it on every projection.
-        ctx.effect(() => ctx.uiSession.provide({
-          hooks: ['memoryMap'],
-          resolve: (binding) => {
-            const target = ctx.uiConversation.binding(binding).target('trajectory')
-            return {
-              hooks: {
-                memoryMap: {
-                  getSnapshot: () => findMemorySnapshot(target.getSnapshot()),
-                  subscribe: (listener) => target.subscribe(listener),
-                },
-              },
-            }
-          },
-        }), 'dsh-memory: memory map hook')
-        disposers.push(ctx.slots.inject('conversation.view', () => ctx.slots.register({
-          name: 'conversation.view',
-          id: 'memory',
-          // ui-chat holds 0 and ui-trajectory 10, so Memory sits after both without
-          // reordering anyone else's tab.
-          order: 20,
-          label: 'Memory',
-        }, MemoryTabView)))
+        // The settings page registers FIRST, and deliberately. It is the established surface;
+        // the tab below is newer and depends on two services the page does not need. Ordering
+        // the proven surface before the unproven one means a failure in the tab cannot take the
+        // settings page down with it - both halves share one file and one apply().
         disposers.push(ctx.slots.inject('settings.section', () => ctx.slots.register({
           name: 'settings.section',
           id: 'memory',
           order: 80,
           label: 'Memory',
         }, () => react.createElement(MemorySettings))))
+        // The Memory tab. Data arrives through a registered standard hook, because a
+        // conversation view is a slot and slots are fed by hooks, not by direct reads.
+        // The Trajectory target is the shipped assembly of this session's nodes, so the
+        // source re-derives the memory snapshot from it on every projection.
+        try {
+          ctx.effect(() => ctx.uiSession.provide({
+            hooks: ['memoryMap'],
+            resolve: (binding) => {
+              const target = ctx.uiConversation.binding(binding).target('trajectory')
+              return {
+                hooks: {
+                  memoryMap: {
+                    getSnapshot: () => findMemorySnapshot(target.getSnapshot()),
+                    subscribe: (listener) => target.subscribe(listener),
+                  },
+                },
+              }
+            },
+          }), 'dsh-memory: memory map hook')
+          disposers.push(ctx.slots.inject('conversation.view', () => ctx.slots.register({
+            name: 'conversation.view',
+            id: 'memory',
+            // ui-chat holds 0 and ui-trajectory 10, so Memory sits after both without
+            // reordering anyone else's tab.
+            order: 20,
+            label: 'Memory',
+          }, MemoryTabView)))
+        } catch (error) {
+          // Loud, not silent. A tab that fails to register is invisible by definition, so this
+          // warning is the only trace the failure can leave.
+          ctx.logger.warn('dsh-memory: Memory tab unavailable: ' + (error && error.message ? error.message : String(error)))
+        }
         return () => { for (const dispose of disposers) dispose() }
       }, 'dsh-memory: settings section')
     }