@heixui/dsh-session-suite 0.5.0 → 0.5.1

package/client.js

@@ -272,6 +272,7 @@ window.__ModuleLoader__.load({
         'memory.extractionNotRegistered': 'HOOK NOT REGISTERED',
         'memory.extractionNoTrace': 'no extraction trace recorded by this Host',
         'memory.diagTitle': 'Extraction diagnostics:',
+        'memory.diagSteps': '{ok}/{total} hooks installed',
         'memory.accept': 'Keep',
         'memory.reject': 'Discard',
         'memory.accepted': 'Kept',
@@ -520,6 +521,7 @@ window.__ModuleLoader__.load({
         'memory.extractionNotRegistered': '钩子未注册',
         'memory.extractionNoTrace': '本次运行没有记录到提取痕迹',
         'memory.diagTitle': '提取诊断：',
+        'memory.diagSteps': '{ok}/{total} 个钩子已装',
         'memory.accept': '保留',
         'memory.reject': '丢弃',
         'memory.accepted': '已保留',
@@ -1047,6 +1049,7 @@ window.__ModuleLoader__.load({
   font-weight: 600;
   color: var(--dsw-alias-label-primary, #1f1f1f);
 }
+.dss-diag-steps { color: var(--dsw-alias-label-secondary, #6b6b6b); }
 /* The summary charts. Two narrow panels for composition and health, one wide panel
    for tags: composition and health are short lists, tags can run long. Bars are divs,
    not SVG, so they inherit the theme and stay legible in both palettes. */
@@ -3449,6 +3452,10 @@ window.__ModuleLoader__.load({
       // unremarkable" from "every memory model failed" or "a filter ate the
       // result". When there is nothing pending, say why.
       const extraction = status?.extraction
+      // Which optional hooks installed. Reported separately from the extraction trace
+      // because a hook that never installed cannot write a trace — that is the whole
+      // point: "no trace" has two causes and this separates them.
+      const installStatus = Array.isArray(status?.install) ? status.install : []
       const pendingBlock =
         pending.length > 0
           ? h(
@@ -3565,6 +3572,23 @@ window.__ModuleLoader__.load({
                         : t('memory.extractionNotRegistered'),
                     )
                   : null,
+                // The registration ledger: which optional hooks installed and which
+                // threw. This is the only way to see a step that never ran, because the
+                // code that would have reported it is the code that failed.
+                installStatus.length > 0
+                  ? h(
+                      'span',
+                      { className: 'dss-diag-steps' },
+                      t('memory.diagSteps', {
+                        ok: installStatus.filter(step => step.ok).length,
+                        total: installStatus.length,
+                      }),
+                      installStatus
+                        .filter(step => !step.ok)
+                        .map(step => ` · ${step.label}: ${step.error ?? 'failed'}`)
+                        .join(''),
+                    )
+                  : null,
               ),
             )
 

package/cordis.patch.yml

@@ -54,12 +54,19 @@
         # says otherwise.
         recallLimit: 6
         # How much of the conversation before the current message is folded into the
-        # retrieval query. A follow-up like "那它为什么慢？" has no referent for "它", so
-        # searching those characters alone cannot find the memory that answers it.
-        # The previous user turns are appended BEFORE the current question, so the
-        # question's own terms still dominate the score. 0 disables the behaviour and
-        # searches the current message exactly as before.
-        contextQueryChars: 160
+        # retrieval query. DEFAULT 0 = OFF.
+        #
+        # Why off by default: the model already receives the full conversation history,
+        # so it knows what 「它」 refers to. Folding earlier turns into the query only
+        # helps the RETRIEVAL step pick a better memory; it does not make the model
+        # understand the question better. That is a real but small gain, and it costs a
+        # little accuracy on self-contained questions that get padded unnecessarily.
+        #
+        # Turn it on when the prompt is short by design — a workflow that deliberately
+        # keeps requests small (an agent that works from a compact brief rather than a
+        # long transcript) benefits, because there the history is NOT in the prompt.
+        # 160 characters across 3 previous turns is a reasonable starting point.
+        contextQueryChars: 0
         contextQueryTurns: 3
         # How many of the most important memories ride along regardless of the
         # question. Without a resident layer, an ordinary follow-up like "继续"

package/index.js

@@ -97,6 +97,10 @@ export function apply(ctx, config = {}) {
     try {
       const installed = installMemory({ ctx, root, config, log })
       service.longTerm = installed.engine
+      // Kept separately: the engine is the memory store, and this is the record of
+      // which optional registrations succeeded. Exposed through the status endpoint so
+      // a missing feature can be traced to a step that never installed.
+      service.memoryInstallStatus = installed.installStatus
       log('long-term memory engine ready')
     } catch (error) {
       log('long-term memory failed to install; continuing without it', error)

package/lib/api.js

@@ -303,8 +303,14 @@ async function respond(service, deps, action, input) {
       })
     case 'longterm.maintain':
       return json({ ok: true, data: await service.longTerm.maintain(workspaceOf(input)) })
-    case 'longterm.status':
-      return json({ ok: true, data: await service.longTerm.status() })
+    case 'longterm.status': {
+      // The engine's own status plus the registration ledger. Two sources on purpose:
+      // the engine cannot report a hook that never installed, because the code that
+      // would have written it is the code that failed.
+      const status = await service.longTerm.status()
+      const install = typeof service.memoryInstallStatus === 'function' ? service.memoryInstallStatus() : []
+      return json({ ok: true, data: { ...status, install } })
+    }
     case 'longterm.workspaces':
       return json({ ok: true, data: await service.longTerm.workspaces() })
     case 'longterm.models':

package/lib/memory-host.js

@@ -91,13 +91,21 @@ export function installMemory({ ctx, root, config, log }) {
    * Run one optional registration; a failure is reported and skipped so a single
    * incompatible hook can never disable the rest of the bundle.
    *
+   * Every step records its outcome. The silent-catch was the reason a broken step was
+   * invisible: "the queue is empty" could mean the hook was never installed, and
+   * nothing on screen said so. The steps list is published through status() so the
+   * settings page can show which registrations succeeded.
+   *
    * @param {string} label what is being installed
    * @param {() => void} install registration body
    */
+  const steps = []
   const safe = (label, install) => {
     try {
       install()
+      steps.push({ label, ok: true })
     } catch (error) {
+      steps.push({ label, ok: false, error: error instanceof Error ? error.message : String(error) })
       log(`long-term memory: ${label} failed to install`, error)
     }
   }
@@ -410,6 +418,9 @@ export function installMemory({ ctx, root, config, log }) {
   return {
     engine,
     dispose: () => {},
+    // The outcome of every optional registration, so "the queue is empty" can be
+    // traced to a specific step that never installed.
+    installStatus: () => [...steps],
     // Exposed so the settings page and the status endpoint can report whether the
     // last recall rebuild failed. Without this the failure is silent: the model
     // simply acts as if the memory is not there.
@@ -535,8 +546,17 @@ function contextualQuery(messages, limits = {}) {
   const current = lastUserText(messages)
   if (!current) return ''
 
-  const maxChars = limits.chars ?? 160
-  const maxTurns = limits.turns ?? 3
+  // 0 is the default, and it means disabled.
+  //
+  // Why: the model already receives the conversation history, so it knows what a
+  // pronoun refers to. Folding earlier turns into the retrieval query only improves
+  // which MEMORY is picked — a real but small gain — and it costs a little accuracy
+  // on self-contained questions that get padded unnecessarily. It matters for a
+  // workflow that deliberately keeps the prompt small, where the history is not there
+  // to be read; that is the case this exists for, and it is opt-in.
+  const maxChars = typeof limits.chars === 'number' ? limits.chars : 0
+  const maxTurns = typeof limits.turns === 'number' ? limits.turns : 3
+  if (maxChars <= 0) return current
 
   // A self-contained question needs no help. The test is NOT length alone: a short
   // question that names its own subject ("导出的图片为什么断链") is self-contained,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@heixui/dsh-session-suite",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "Session checkpoints for DSH: rewind a conversation with its files and memory, permanent session deletion, and shareable exports",
   "type": "module",
   "main": "./index.js",