@try-works/dsh-memory 0.1.19 → 0.1.20

package/cordis.patch.yml

@@ -1,69 +1,69 @@
-# dsh-memory bundle patch — the patch layer this package exports.
-#
-# Declared by `dsh.bundle.patch` in package.json. When the package is added to a profile, dsh
-# reconciles it into `dsh.profile.bundles` and composes this layer over the profile, so the
-# plugin mounts from the installed package rather than by absolute path.
-#
-# This layer does two things: it mounts dsh-memory, and it switches on the session history
-# search that a memory plugin is useless without. Both are described where they appear.
-#
-# Patch semantics, which the rest of this file depends on: a patch REPLACES the targeted row's
-# whole `config`, it does not merge into it. Every override below therefore restates EVERY key
-# it owns, or the omitted ones silently become undefined.
-- insert:
-    # dsh-memory itself.
-    #
-    # A single row naming the published package mounts the plugin on the profile root. The row id
-# stays dsh-memory, which is what the PROFILE patch addresses for config. It publishes the `memory`
-    # service, registers the memory_* tools into the host-owned tools registry, and keeps its
-    # browser half module-scoped — so, like the other memory-like plugins, it needs no `isolate`
-    # realm.
-    #
-    # The row carries NO config: the store root, the memory model and the git origin are set on
-    # Settings -> Memory, which writes a top-level `config:` row for this id into the PROFILE
-    # patch. That is why the mounted row must be addressable by id — the config editor finds a
-    # row by id at the top level, so a profile that configures memory ends up with both this
-    # insert and a sibling `- id: dsh-memory` config row after it.
-    - id: dsh-memory
-      # A scoped name MUST be quoted: YAML treats a leading @ as a reserved indicator.
-      name: '@try-works/dsh-memory'
-
-    # NOTE: the model-facing session history TOOLS are deliberately NOT mounted here.
-    #
-    # Not because they are unwanted, but because this is the wrong plane. A Web profile
-    # disables every base tool row and hands the tool plane to PRESETS, and its gate reads
-    # declared row ids WITHOUT regard to `disabled` — the web-app bundle keeps `tool-ralph`
-    # declared-but-disabled purely to hold it off the host plane and out of collision with
-    # every preset's rows. Inserting a live tool row here would put it on the host plane and
-    # in collision with that arrangement, which is a large side effect for a memory plugin to
-    # have on somebody else's tool surface. Enabling the index below is a config override, the
-    # kind the web-app bundle explicitly invites; owning a tool row is not.
-
-# ---------------------------------------------------------------------------------------------
-# Session search: switched on by installing this plugin.
-# ---------------------------------------------------------------------------------------------
-#
-# The base bundle mounts `session-query-sqlite` with `openAt: never`, and the web-app bundle
-# restates that. It is deliberate: ctx.sessionQuery stays available for exact reads and lineage
-# while SEARCH calls fail with SESSION_QUERY_SEARCH_DISABLED, so no deployment indexes gigabytes
-# of session logs without asking. The cost of that default is a system that cannot look back at
-# what happened — and memory that cannot be searched is half a memory. Installing a memory plugin
-# is the request that flag was waiting for, so this layer asks. The web-app bundle says so in as
-# many words: 'a deployment enabling content search overrides openAt to first-search in a later
-# patch layer'. This is that layer.
-#
-# `first-search` rather than `startup`: nothing is indexed until a search is actually made, so
-# the capability is present from install while the work still happens lazily, on a query.
-#
-# `path` is restated even though both bundles already set one, because a patch replaces the
-# whole config rather than merging: omitting it would drop the index to undefined and rebuild
-# it in memory on every process. A durable file under storages/ is what makes a several-gigabyte
-# corpus worth indexing once.
-#
-# Precedence is why this is safe to set here. Bundle layers compose FIRST and the profile's own
-# cordis.patch.yml applies AFTER, so a profile wanting `startup`, a different path, or `never`
-# simply says so there and wins. This layer supplies a default, not a mandate.
-- id: session-query-sqlite
-  config:
-    path: !!js dshHomePath('storages', 'session-search.sqlite')
-    openAt: first-search
+# dsh-memory bundle patch — the patch layer this package exports.
+#
+# Declared by `dsh.bundle.patch` in package.json. When the package is added to a profile, dsh
+# reconciles it into `dsh.profile.bundles` and composes this layer over the profile, so the
+# plugin mounts from the installed package rather than by absolute path.
+#
+# This layer does two things: it mounts dsh-memory, and it switches on the session history
+# search that a memory plugin is useless without. Both are described where they appear.
+#
+# Patch semantics, which the rest of this file depends on: a patch REPLACES the targeted row's
+# whole `config`, it does not merge into it. Every override below therefore restates EVERY key
+# it owns, or the omitted ones silently become undefined.
+- insert:
+    # dsh-memory itself.
+    #
+    # A single row naming the published package mounts the plugin on the profile root. The row id
+# stays dsh-memory, which is what the PROFILE patch addresses for config. It publishes the `memory`
+    # service, registers the memory_* tools into the host-owned tools registry, and keeps its
+    # browser half module-scoped — so, like the other memory-like plugins, it needs no `isolate`
+    # realm.
+    #
+    # The row carries NO config: the store root, the memory model and the git origin are set on
+    # Settings -> Memory, which writes a top-level `config:` row for this id into the PROFILE
+    # patch. That is why the mounted row must be addressable by id — the config editor finds a
+    # row by id at the top level, so a profile that configures memory ends up with both this
+    # insert and a sibling `- id: dsh-memory` config row after it.
+    - id: dsh-memory
+      # A scoped name MUST be quoted: YAML treats a leading @ as a reserved indicator.
+      name: '@try-works/dsh-memory'
+
+    # NOTE: the model-facing session history TOOLS are deliberately NOT mounted here.
+    #
+    # Not because they are unwanted, but because this is the wrong plane. A Web profile
+    # disables every base tool row and hands the tool plane to PRESETS, and its gate reads
+    # declared row ids WITHOUT regard to `disabled` — the web-app bundle keeps `tool-ralph`
+    # declared-but-disabled purely to hold it off the host plane and out of collision with
+    # every preset's rows. Inserting a live tool row here would put it on the host plane and
+    # in collision with that arrangement, which is a large side effect for a memory plugin to
+    # have on somebody else's tool surface. Enabling the index below is a config override, the
+    # kind the web-app bundle explicitly invites; owning a tool row is not.
+
+# ---------------------------------------------------------------------------------------------
+# Session search: switched on by installing this plugin.
+# ---------------------------------------------------------------------------------------------
+#
+# The base bundle mounts `session-query-sqlite` with `openAt: never`, and the web-app bundle
+# restates that. It is deliberate: ctx.sessionQuery stays available for exact reads and lineage
+# while SEARCH calls fail with SESSION_QUERY_SEARCH_DISABLED, so no deployment indexes gigabytes
+# of session logs without asking. The cost of that default is a system that cannot look back at
+# what happened — and memory that cannot be searched is half a memory. Installing a memory plugin
+# is the request that flag was waiting for, so this layer asks. The web-app bundle says so in as
+# many words: 'a deployment enabling content search overrides openAt to first-search in a later
+# patch layer'. This is that layer.
+#
+# `first-search` rather than `startup`: nothing is indexed until a search is actually made, so
+# the capability is present from install while the work still happens lazily, on a query.
+#
+# `path` is restated even though both bundles already set one, because a patch replaces the
+# whole config rather than merging: omitting it would drop the index to undefined and rebuild
+# it in memory on every process. A durable file under storages/ is what makes a several-gigabyte
+# corpus worth indexing once.
+#
+# Precedence is why this is safe to set here. Bundle layers compose FIRST and the profile's own
+# cordis.patch.yml applies AFTER, so a profile wanting `startup`, a different path, or `never`
+# simply says so there and wins. This layer supplies a default, not a mandate.
+- id: session-query-sqlite
+  config:
+    path: !!js dshHomePath('storages', 'session-search.sqlite')
+    openAt: first-search

package/package.json

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

package/scripts/check-package.mjs

@@ -1,76 +1,76 @@
-// Package invariants for dsh-memory. Run with: node scripts/check-package.mjs
-//
-// A plugin that is installed by name must declare everything the loader needs; when one of these
-// drifts the failure appears at MOUNT time in someone else's profile, which is the worst place to
-// discover it. This is a fast pre-flight, and test/package.test.js asserts the same invariants.
-import { readFileSync, existsSync } from 'node:fs'
-import { dirname, join } from 'node:path'
-import { fileURLToPath } from 'node:url'
-
-const root = join(dirname(fileURLToPath(import.meta.url)), '..')
-const problems = []
-const note = (ok, message) => { if (!ok) problems.push(message) }
-
-const manifest = JSON.parse(readFileSync(join(root, 'package.json'), 'utf8'))
-
-note(manifest.name === '@try-works/dsh-memory', 'package name must be "@try-works/dsh-memory", found ' + manifest.name)
-note(manifest.type === 'module', 'package must be ESM ("type": "module")')
-note(typeof manifest.main === 'string', 'package must declare "main"')
-note(existsSync(join(root, manifest.main)), 'main does not exist: ' + manifest.main)
-
-// The loader must be able to import the entry.
-const entry = await import(new URL('../' + manifest.main, import.meta.url))
-note(typeof entry.name === 'string' && entry.name === 'dsh-memory', 'entry must export name = "dsh-memory"')
-note(Array.isArray(entry.inject), 'entry must export inject')
-note(typeof entry.apply === 'function', 'entry must export apply')
-note(entry.Config !== undefined, 'entry must export Config')
-note(entry.default === undefined, 'entry must NOT export default (the loader does exports.default ?? exports, which would discard name/inject/Config)')
-
-// Bundle patch: what makes an install-by-name mount the plugin.
-const patchPath = manifest.dsh?.bundle?.patch
-note(typeof patchPath === 'string', 'dsh.bundle.patch must be declared for install-by-name')
-if (typeof patchPath === 'string') {
-  const full = join(root, patchPath.replace(/^\.\//, ''))
-  note(existsSync(full), 'bundle patch does not exist: ' + patchPath)
-  if (existsSync(full)) {
-    const text = readFileSync(full, 'utf8')
-    note(text.includes('id: dsh-memory'), 'bundle patch must insert an entry with id: dsh-memory')
-    note(text.includes("name: '@try-works/dsh-memory'"), 'bundle patch must mount the package by its published name')
-  }
-  note((manifest.files ?? []).some((f) => f.includes('cordis.patch.yml')), 'files[] must ship the bundle patch')
-}
-
-// Client half.
-const client = manifest.dsh?.client
-note(client !== undefined, 'dsh.client must be declared for the Settings page')
-if (client) {
-  note(client.platform === 'web', 'dsh.client.platform must be "web"')
-  const clientExport = manifest.exports?.['./client']
-  const target = typeof clientExport === 'string' ? clientExport : clientExport?.default
-  note(typeof target === 'string', 'exports["./client"] must resolve to a file')
-  if (typeof target === 'string') note(existsSync(join(root, target)), 'client half missing: ' + target)
-}
-
-// Everything the entry imports at load time must ship.
-note((manifest.files ?? []).includes('src'), 'files[] must ship src/')
-// The system document template is read at runtime from beside its module.
-note(existsSync(join(root, 'src', 'SYSTEM.template.md')), 'src/SYSTEM.template.md must exist (rendered into every store)')
-
-// Peers: a missing declaration means an unresolvable import in a clean profile.
-for (const peer of ['@deepseek-ai/cordis', '@deepseek-ai/dsh-tools', '@deepseek-ai/dsh-llm']) {
-  note(Object.hasOwn(manifest.peerDependencies ?? {}, peer), 'peerDependencies must declare ' + peer)
-}
-// schemastery is the exception, and it is deliberate: .volatile() exists only from 3.18.4, and a
-// PEER lets the profile supply 3.18.1, which throws at module load. As a dependency the version
-// is ours to pin. Declaring it as a peer is what broke the first registry install.
-note(!Object.hasOwn(manifest.peerDependencies ?? {}, '@deepseek-ai/schemastery'), 'schemastery must NOT be a peer dependency')
-note(/^\^3\.18\.[4-9]/.test((manifest.dependencies ?? {})['@deepseek-ai/schemastery'] ?? ''), 'schemastery must be a dependency pinned at 3.18.4 or newer, for .volatile()')
-{
-}
-
-if (problems.length > 0) {
-  console.error('dsh-memory package check FAILED:')
-  for (const problem of problems) console.error('  - ' + problem)
-  process.exit(1)
-}
-console.log('dsh-memory package check OK (' + manifest.name + '@' + manifest.version + ')')
+// Package invariants for dsh-memory. Run with: node scripts/check-package.mjs
+//
+// A plugin that is installed by name must declare everything the loader needs; when one of these
+// drifts the failure appears at MOUNT time in someone else's profile, which is the worst place to
+// discover it. This is a fast pre-flight, and test/package.test.js asserts the same invariants.
+import { readFileSync, existsSync } from 'node:fs'
+import { dirname, join } from 'node:path'
+import { fileURLToPath } from 'node:url'
+
+const root = join(dirname(fileURLToPath(import.meta.url)), '..')
+const problems = []
+const note = (ok, message) => { if (!ok) problems.push(message) }
+
+const manifest = JSON.parse(readFileSync(join(root, 'package.json'), 'utf8'))
+
+note(manifest.name === '@try-works/dsh-memory', 'package name must be "@try-works/dsh-memory", found ' + manifest.name)
+note(manifest.type === 'module', 'package must be ESM ("type": "module")')
+note(typeof manifest.main === 'string', 'package must declare "main"')
+note(existsSync(join(root, manifest.main)), 'main does not exist: ' + manifest.main)
+
+// The loader must be able to import the entry.
+const entry = await import(new URL('../' + manifest.main, import.meta.url))
+note(typeof entry.name === 'string' && entry.name === 'dsh-memory', 'entry must export name = "dsh-memory"')
+note(Array.isArray(entry.inject), 'entry must export inject')
+note(typeof entry.apply === 'function', 'entry must export apply')
+note(entry.Config !== undefined, 'entry must export Config')
+note(entry.default === undefined, 'entry must NOT export default (the loader does exports.default ?? exports, which would discard name/inject/Config)')
+
+// Bundle patch: what makes an install-by-name mount the plugin.
+const patchPath = manifest.dsh?.bundle?.patch
+note(typeof patchPath === 'string', 'dsh.bundle.patch must be declared for install-by-name')
+if (typeof patchPath === 'string') {
+  const full = join(root, patchPath.replace(/^\.\//, ''))
+  note(existsSync(full), 'bundle patch does not exist: ' + patchPath)
+  if (existsSync(full)) {
+    const text = readFileSync(full, 'utf8')
+    note(text.includes('id: dsh-memory'), 'bundle patch must insert an entry with id: dsh-memory')
+    note(text.includes("name: '@try-works/dsh-memory'"), 'bundle patch must mount the package by its published name')
+  }
+  note((manifest.files ?? []).some((f) => f.includes('cordis.patch.yml')), 'files[] must ship the bundle patch')
+}
+
+// Client half.
+const client = manifest.dsh?.client
+note(client !== undefined, 'dsh.client must be declared for the Settings page')
+if (client) {
+  note(client.platform === 'web', 'dsh.client.platform must be "web"')
+  const clientExport = manifest.exports?.['./client']
+  const target = typeof clientExport === 'string' ? clientExport : clientExport?.default
+  note(typeof target === 'string', 'exports["./client"] must resolve to a file')
+  if (typeof target === 'string') note(existsSync(join(root, target)), 'client half missing: ' + target)
+}
+
+// Everything the entry imports at load time must ship.
+note((manifest.files ?? []).includes('src'), 'files[] must ship src/')
+// The system document template is read at runtime from beside its module.
+note(existsSync(join(root, 'src', 'SYSTEM.template.md')), 'src/SYSTEM.template.md must exist (rendered into every store)')
+
+// Peers: a missing declaration means an unresolvable import in a clean profile.
+for (const peer of ['@deepseek-ai/cordis', '@deepseek-ai/dsh-tools', '@deepseek-ai/dsh-llm']) {
+  note(Object.hasOwn(manifest.peerDependencies ?? {}, peer), 'peerDependencies must declare ' + peer)
+}
+// schemastery is the exception, and it is deliberate: .volatile() exists only from 3.18.4, and a
+// PEER lets the profile supply 3.18.1, which throws at module load. As a dependency the version
+// is ours to pin. Declaring it as a peer is what broke the first registry install.
+note(!Object.hasOwn(manifest.peerDependencies ?? {}, '@deepseek-ai/schemastery'), 'schemastery must NOT be a peer dependency')
+note(/^\^3\.18\.[4-9]/.test((manifest.dependencies ?? {})['@deepseek-ai/schemastery'] ?? ''), 'schemastery must be a dependency pinned at 3.18.4 or newer, for .volatile()')
+{
+}
+
+if (problems.length > 0) {
+  console.error('dsh-memory package check FAILED:')
+  for (const problem of problems) console.error('  - ' + problem)
+  process.exit(1)
+}
+console.log('dsh-memory package check OK (' + manifest.name + '@' + manifest.version + ')')