dsh-plugin-shop 0.8.3 → 0.8.4-beta.0

package/lib/types/host/profile.d.ts

@@ -3,6 +3,10 @@
 export interface UserLayerRow {
     id: string;
     disabled: boolean;
+    /** The module the entry mounts, when the caller knows it. A user-layer row
+     * that names a DIFFERENT module is one the harness skips
+     * (applyEntryPatches), so only this name lets a named row be written. */
+    name?: string;
 }
 /**
  * Find the profile directory that owns `startPath`.
@@ -19,10 +23,10 @@ export declare function discoverProfile(startPath: string, baseDir?: string): {
     dir: string;
 };
 /**
- * Upsert one row of the profile's user layer (`cordis.patch.yml`). Enabling
- * removes the row so the bundle default rules again; disabling writes
- * `{ id, disabled: true }` (§8: the CLI's watchUserPatches applies the change
- * hot through HMR). Existing rows for other ids are preserved verbatim.
+ * Set one entry's `disabled` key in the profile's user layer
+ * (`cordis.patch.yml`) — {@link setUserLayerRows} for a single row, with the
+ * same rules: one key changes and nothing else does (§8: the CLI's
+ * watchUserPatches applies the change hot through HMR).
  */
 export declare function setUserLayerRow(options: {
     profileDir: string;
@@ -35,6 +39,31 @@ export declare function setUserLayerRow(options: {
  * {@link ownedEntryIds}), and they toggle together: writing them one at a
  * time would read-modify-write the file once per entry, so a crash between
  * two writes would leave the package half disabled.
+ *
+ * The edit changes one key and nothing else (design
+ * 2026-09-26-market-borrowings §2). The layer is validated by the harness's
+ * own parser first, so one it cannot load still throws and is never
+ * rewritten; it is then edited as a YAML document, which keeps every comment,
+ * every other row, every other key and every `!!js` scalar as the user wrote
+ * them. The whole-file rewrite this replaced dropped each toggled id's row —
+ * and with it a `config:` override the user had put there — and dumped the
+ * list back through a library that models no comments, so the first toggle
+ * erased the header dsh writes into every new profile.
+ *
+ * For each entry the row written is the LAST one carrying its id, when the
+ * harness is sure to apply it: applyEntryPatches applies rows in order and
+ * each key replaces the entry's value, so the last row that sets `disabled`
+ * decides it. A row with `insert` is an insertion into a group, never an
+ * override; a row naming another module is skipped by the harness; a named
+ * row whose module the caller did not say cannot be judged. In each of those
+ * cases a row is appended instead, which the harness applies last whatever
+ * came before it — so appending is never wrong, only less tidy.
+ *
+ * An enable writes `disabled: false` rather than deleting the row, which is
+ * what lost a user's row or the comment above it; it is also the harness's
+ * own convention for this file from 0.1.7. The file keeps its permission bits
+ * across the rename (a new one is created owner-only, as the harness's writer
+ * does), because a config override can hold a credential.
  */
 export declare function setUserLayerRows(options: {
     profileDir: string;
@@ -65,6 +94,34 @@ export declare function ownedEntryIds(options: {
     profileDir: string;
     packageName: string;
 }): string[];
+/** One loader entry a package's bundle patch inserts: its id, and the module
+ * it mounts when the patch names one as a plain string. */
+export interface OwnedEntry {
+    id: string;
+    name: string | undefined;
+}
+/**
+ * {@link ownedEntryIds} with the module each entry mounts beside its id. The
+ * name is what the harness judges a NAMED user-layer row by — a row naming a
+ * different module is skipped (applyEntryPatches) — so it is what lets the
+ * toggle write a user's own named row rather than append one beside it. It is
+ * read through the harness's parser, so a relative name arrives anchored to a
+ * file URL exactly as the composed entry carries it; an `!!js` name has no
+ * plain value and reads as undefined. Throws where `ownedEntryIds` does.
+ */
+export declare function ownedEntries(options: {
+    profileDir: string;
+    packageName: string;
+}): OwnedEntry[];
+/**
+ * An installed package's own `dsh.bundle.patch`, exactly as declared, or
+ * undefined when the package, its manifest or the field is absent — or the
+ * manifest cannot be read, which no post-install check can judge either.
+ */
+export declare function declaredBundlePatch(options: {
+    profileDir: string;
+    packageName: string;
+}): unknown;
 /**
  * Does a live loader entry id belong to the package that owns `owned`?
  *

package/lib/types/host/restart.d.ts

@@ -12,9 +12,13 @@
 /** `shop/restart` result: committed, or a typed refusal issued BEFORE
  * anything is torn down. Once `ok` is returned the old process WILL exit —
  * the client monitors the new server and reports a failed boot with the
- * manual command. */
+ * manual command and `logFile`, the file the new process's output goes to:
+ * where a boot that died explains itself, at a path that depends on DSH_HOME
+ * and the shop row's `cacheDir`, which only the host knows. A host older than
+ * the field answers without it, so the client reads it as optional. */
 export type RestartOutcome = {
     ok: true;
+    logFile?: string;
 } | {
     ok: false;
     detail: string;

package/lib/types/host/types.d.ts

@@ -56,8 +56,34 @@ export interface CatalogEntry {
     };
     /** The date this entry first appeared in the catalog (YYYY-MM-DD). */
     added?: string;
-    /** The package's declared peer dependency names (schemaVersion 6). */
+    /** The names of the package's REQUIRED peer dependencies — a peer its
+     * author marks optional in `peerDependenciesMeta` is left out at harvest.
+     * Additive and optional, so it rides every schemaVersion: the version-6
+     * gate this comment used to name came off on 2026-09-03 without ever being
+     * opened. Present on npm entries. Not on github entries yet: the registry
+     * harvests their peers from 2026-09-24 but withholds them from the catalog
+     * (`withholdRepoPeers`) until `SHOP_EMIT_REPO_PEERS` flips, in the release
+     * commit that first promotes a shop refining peers against the browser's
+     * module table to `latest` (design 2026-09-01-harness-compatibility §9.8).
+     * An absent list forms no peer verdict. */
     peers?: string[];
+    /** The author's own `dsh.compatibility` declaration, when they published
+     * one. A REQUIREMENT, never a verdict: the host compares it against the
+     * running installation (`ShopCatalogResult.incompatibleHarness`). Additive
+     * and optional, so it rides every schemaVersion. */
+    compatibility?: {
+        dsh?: string;
+        profiles?: string[];
+    };
+    /** The package's peers on the harness itself (`@deepseek-ai/dsh` and
+     * `@deepseek-ai/dsh-*`) with their ranges verbatim, optional ones and empty
+     * ranges included — what dsh 0.1.7 refuses an install on. The host hands
+     * them to the running dsh's own check (`peerVerdictsOf`). npm entries only:
+     * dsh keys the exemption that clears its refusal by the installed
+     * manifest's version, which a github entry's catalog version is not
+     * (registry `Entry.dshPeers`). Absent when the package declares none, or
+     * when its catalog predates the field. */
+    dshPeers?: Record<string, string>;
     /** Wire-compatibility key, not a field to read — see {@link installSize},
      * which the catalog parse fills from this one. It names npm's OWN quantity
      * (`dist.unpackedSize`), so it is npm-only and the parse REFUSES one on a

package/lib/types/own-version.d.ts

@@ -4,10 +4,26 @@
  * both the source tree (tests) and the bundled `lib/index.js` sit exactly
  * one level below the package root, so the same relative URL resolves in
  * both. */
-export declare function ownVersion(): string;
+/**
+ * Read a version once and keep it: the answer to "which code is this".
+ *
+ * The file cannot answer that question later. A profile installs hoisted, so
+ * a self-update rewrites package.json in the directory the RUNNING code was
+ * loaded from, and every read after it names the version that will run after
+ * the next restart — which the version row then printed as the one running
+ * (design §7.3, 2026-09-27 amendment).
+ *
+ * A first read that throws is not kept: the module import must not fail over
+ * a version string, so the answer falls back to reading on demand, which is
+ * what the row always did.
+ */
+export declare function versionAtLoad(read: () => string): () => string;
+/** The version of the code in this process, read when the module was first
+ * evaluated — at boot, before any self-update could rewrite the file. */
+export declare const runningVersion: () => string;
 /**
  * The peer ranges this build declares — the input to the load-time harness
- * self-check. Read from the same shipped manifest as `ownVersion`, so the
+ * self-check. Read from the same shipped manifest as `runningVersion`, so the
  * ranges checked are the ones this build was actually published with, never
  * a second copy that can drift from them.
  *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-plugin-shop",
-  "version": "0.8.3",
+  "version": "0.8.4-beta.0",
   "description": "The DeepSeek Harness plugin shop: browse, install, enable, and update dsh plugins from a git-auditable catalog.",
   "keywords": [
     "dsh-plugin",
@@ -75,6 +75,7 @@
   "dependencies": {
     "js-yaml": "^4.2.0",
     "semver": "^7.6.3",
+    "yaml": "^2.5.1",
     "zod": "^4.4.3"
   },
   "peerDependencies": {