@try-works/dsh-memory 0.1.0 → 0.1.2

package/STATUS.md

@@ -154,6 +154,24 @@ Kept because the pattern matters more than the list: every one of these was foun
 | A gate that proved nothing | it asserted guidance present only when a backfill is in the batch |
 | `memory_recover` returned invalid JSON | the harness rejected it; the tests called `execute()` directly and never checked the shape |
 | A test edit silently discarded | my own script re-read and overwrote the file before writing |
+## Published
+
+**`@try-works/dsh-memory@0.1.0`** on npm. The unscoped name `dsh-memory` was already taken by an
+unrelated DeepSeek Harness memory plugin, so the package publishes under the existing `@try-works`
+scope.
+
+What did NOT change, deliberately: the Cordis plugin name (`export const name = 'dsh-memory'`) and
+the bundle row id (`id: dsh-memory`). Config is addressed by ROW ID, so an existing profile's
+`memoryRoot` row survives the rename untouched. Only the package name and the module specifier in
+`cordis.patch.yml` moved.
+
+Verified after publishing: a clean install in a temp directory resolves 0.1.0, ships 49 files and
+42 src modules with no test directory, and the installed entry exports `name`, `inject`, `apply`,
+`Config` and `hostExtras`.
+
+Note for a first publish of any new name: npm creates a `0.0.0-stage` placeholder while the real
+version is staged, so an immediate registry check 404s. It took about three minutes to appear.
+
 ## Layout
 
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@try-works/dsh-memory",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Git-backed, workspace-scoped memory for the DeepSeek Harness (global layer + per-workspace layers)",
   "type": "module",
   "main": "src/index.js",
@@ -37,10 +37,9 @@
     "check": "node scripts/check-package.mjs"
   },
   "peerDependencies": {
-    "@deepseek-ai/cordis": "*",
-    "@deepseek-ai/schemastery": "*",
-    "@deepseek-ai/dsh-tools": "*",
-    "@deepseek-ai/dsh-llm": "*"
+    "@deepseek-ai/cordis": "^4.0.1",
+    "@deepseek-ai/dsh-tools": "^0.2.0-rc.2",
+    "@deepseek-ai/dsh-llm": "^0.2.0-rc.2"
   },
   "dsh": {
     "bundle": {
@@ -56,5 +55,8 @@
   },
   "engines": {
     "node": ">=24.0.0"
+  },
+  "dependencies": {
+    "@deepseek-ai/schemastery": "^3.18.4"
   }
 }

package/scripts/check-package.mjs

@@ -57,9 +57,16 @@ note((manifest.files ?? []).includes('src'), 'files[] must ship src/')
 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/schemastery', '@deepseek-ai/dsh-tools', '@deepseek-ai/dsh-llm']) {
+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:')