create-principles-disciple 1.121.9 → 1.121.10

package/console/dist/server/routes/update.js

@@ -9,6 +9,7 @@ import { checkOpenClawGateway, stopOpenClawGateway, restartOpenClawGateway, } fr
 import { migrateLegacyExtensionBackups, reservePdBackupDestination, resolvePdBackupsRoot, } from '../utils/pd-backups.js';
 import { ActivationCompatibilityReadModel } from '@principles/core/runtime-v2';
 import { getInstallLayoutPaths, resolveInstallLayout } from '@principles/install-layout';
+import { collectFileDepLinkSpecs } from '../utils/update-links.js';
 /**
  * Legacy rule contract preflight (2026-08-19): refuse to swap the runtime
  * while an ACTIVE owner-approved rule still depends on a RuleHost contract
@@ -724,22 +725,35 @@ function depsMeaningfullyChanged(oldDeps, newDeps) {
     return aKeys.some((k, i) => bKeys[i] !== k || a[k] !== b[k]);
 }
 /**
- * Create the node_modules/@principles/host-runtime resolution links for the
- * installed console and pd-cli packages, if missing.
+ * Create the node_modules resolution links for the installed components, if
+ * missing.
  *
  * Mirrors installer.ts syncPdCli: junction on Windows (no elevation needed),
  * relative symlink elsewhere. Fresh installs get these links via npm install
- * (the bundled package.json rewrites the dep to file:../host-runtime); the
- * full update deliberately skips npm install, so it must create them itself.
- * Without the link, the updated console dist — which statically imports
- * @principles/host-runtime since 2026-08-21 (41cf97ee5) — crashes at startup
- * with ERR_MODULE_NOT_FOUND on installs created before the installer bundled
- * host-runtime (PRI-561).
+ * (the bundled package.json rewrites internal deps to file:../<component>);
+ * the full update deliberately skips npm install, so it must create them
+ * itself. Without a link, updated dists crash at startup with
+ * ERR_MODULE_NOT_FOUND (host-runtime: PRI-561, 2026-08-21).
+ *
+ * Two sources, both fail-closed on creation errors:
+ *   1. the explicit link list below (known-critical links: a missing one
+ *      means the updated console cannot start);
+ *   2. a data-driven pass that derives links from the STAGED manifests —
+ *      the freshly extracted release trees under tempDir. Their `file:`
+ *      declarations are the authoritative list of links the updated tree
+ *      needs. Reading the deployed (pre-update) manifests instead would
+ *      miss every dependency this release newly introduced: the running
+ *      console executes update logic from its own dist (one generation
+ *      behind the components it installs) — observed 2026-08-29 when the
+ *      1.221.2 console updated hosts to 1.222.5 but could not know about
+ *      the newly introduced install-layout component, leaving
+ *      host-runtime/node_modules/@principles/install-layout missing and
+ *      every pd-cli runtime command failing with ERR_MODULE_NOT_FOUND.
  *
  * Returns undefined on success, or an error message (rc-9: observable, never
  * silent — a missing link means the updated console cannot start).
  */
-function ensureRuntimeResolutionLinks(layout) {
+function ensureRuntimeResolutionLinks(layout, tempDir) {
     const links = [
         { linkPath: path.join(layout.consoleDir, 'node_modules', '@principles', 'host-runtime'), target: layout.hostRuntimeDir },
         { linkPath: path.join(layout.pdCliDir, 'node_modules', '@principles', 'host-runtime'), target: layout.hostRuntimeDir },
@@ -750,11 +764,43 @@ function ensureRuntimeResolutionLinks(layout) {
         { linkPath: path.join(layout.hostRuntimeDir, 'node_modules', '@principles', 'install-layout'), target: layout.installLayoutDir },
         { linkPath: path.join(layout.consoleDir, 'node_modules', 'principles-disciple'), target: layout.pluginDir },
     ];
-    for (const { linkPath, target } of links) {
-        if (!fs.existsSync(target))
-            continue;
+    // Data-driven pass: derive links from the STAGED component manifests (see
+    // the comment above — staged, never the deployed pre-update manifests).
+    const stagedComponents = [
+        { manifestDir: path.join(tempDir, 'console'), deployedDir: layout.consoleDir },
+        { manifestDir: path.join(tempDir, 'pd-cli'), deployedDir: layout.pdCliDir },
+        { manifestDir: path.join(tempDir, 'host-runtime'), deployedDir: layout.hostRuntimeDir },
+        { manifestDir: path.join(tempDir, 'install-layout'), deployedDir: layout.installLayoutDir },
+        { manifestDir: path.join(tempDir, 'core'), deployedDir: layout.coreDir },
+        { manifestDir: path.join(tempDir, 'plugin'), deployedDir: layout.pluginDir },
+    ];
+    const readStagedDependencies = (manifestDir) => {
+        try {
+            const pkgPath = path.join(manifestDir, 'package.json');
+            if (!fs.existsSync(pkgPath))
+                return {};
+            const parsed = JSON.parse(fs.readFileSync(pkgPath, 'utf8'));
+            if (!isRecord(parsed) || !isRecord(parsed.dependencies))
+                return {};
+            const out = {};
+            for (const [name, ref] of Object.entries(parsed.dependencies)) {
+                if (typeof ref === 'string')
+                    out[name] = ref;
+            }
+            return out;
+        }
+        catch {
+            // rc-9: an unreadable staged manifest degrades to "no derived links" —
+            // the explicit list above still covers the known-critical links.
+            return {};
+        }
+    };
+    const fileDepSpecs = collectFileDepLinkSpecs(stagedComponents, readStagedDependencies);
+    const createResolutionLink = (linkPath, target) => {
+        // Idempotent: never overwrite an existing link or directory (fresh
+        // installs have npm-created real dirs in these slots).
         if (fs.existsSync(linkPath))
-            continue;
+            return undefined;
         try {
             fs.mkdirSync(path.dirname(linkPath), { recursive: true });
             if (process.platform === 'win32') {
@@ -763,10 +809,32 @@ function ensureRuntimeResolutionLinks(layout) {
             else {
                 fs.symlinkSync(path.relative(path.dirname(linkPath), target), linkPath, 'dir');
             }
+            return undefined;
         }
         catch (error) {
             return `Failed to create runtime resolution link at ${linkPath}: ${error instanceof Error ? error.message : String(error)}`;
         }
+    };
+    // Pass 1 — explicit known-critical links, fail-closed BEFORE any byte is
+    // swapped (a link-creation failure aborts with the installed packages
+    // untouched: the PRI-561 ordering contract).
+    for (const { linkPath, target } of links) {
+        if (!fs.existsSync(target))
+            continue;
+        const error = createResolutionLink(linkPath, target);
+        if (error)
+            return error;
+    }
+    // Pass 2 — data-driven derived links. Their deployed target dir may be
+    // created by the copy steps that follow (a brand-new component's dir does
+    // not exist yet); each staged target's existence was already proven by the
+    // extraction, and the copies below run unconditionally.
+    for (const spec of fileDepSpecs) {
+        if (fs.existsSync(spec.linkPath))
+            continue;
+        const error = createResolutionLink(spec.linkPath, spec.target);
+        if (error)
+            return error;
     }
     return undefined;
 }
@@ -935,7 +1003,7 @@ async function doInlineFullUpdate(workspaceDir) {
             if (fs.existsSync(path.join(installLayoutSrc, 'package.json')) && fs.existsSync(path.join(installLayoutSrc, 'dist'))) {
                 copyDirRecursive(installLayoutSrc, layout.installLayoutDir, SKIP_DIRS);
             }
-            const linkError = ensureRuntimeResolutionLinks(layout);
+            const linkError = ensureRuntimeResolutionLinks(layout, tempDir);
             if (linkError) {
                 appendUpdateHistory(workspaceDir, {
                     fromVersion,

package/console/dist/server/utils/update-links.d.ts

@@ -0,0 +1,38 @@
+export type FileDepLinkSpec = {
+    linkPath: string;
+    /** Deployed layout dir the link points at; may be created by the copy
+     *  steps that run after derivation (see stagedTargetExists). */
+    target: string;
+    /** The staged sibling dir proving this component ships in this release. */
+    stagedTarget: string;
+};
+export type StagedComponent = {
+    /** Freshly extracted component dir under the update temp dir. */
+    manifestDir: string;
+    /** Deployed layout dir this component is (or will be) installed into. */
+    deployedDir: string;
+};
+/**
+ * Derive the node_modules link specs implied by each staged component's
+ * declared `file:` dependencies.
+ *
+ * - `readDependencies(manifestDir)` returns the component's dependency map
+ *   (name -> version-or-ref); return {} for unreadable/missing manifests.
+ * - A `file:` ref is resolved against its staged manifest dir to find the
+ *   staged sibling target; the deployed link target is taken from the same
+ *   staged->deployed pairing the caller provides — component identity is
+ *   the staged directory itself (normalized absolute path), NOT the
+ *   deployed directory's basename. In the legacy layout the deployed
+ *   plugin dir is named `principles-disciple` while the staged one is
+ *   `plugin`, so a basename lookup would silently drop the derived link
+ *   (review P1, PR #1457).
+ * - Deps whose staged target is not one of the layout components (e.g.
+ *   @principles/codex-adapter — a separate host install, not part of this
+ *   layout) are skipped.
+ *
+ * Note: `target` (the deployed dir) may not exist yet at derivation time —
+ * for components whose copy step runs after this call, the caller creates
+ * the directory right after deriving and creating these links. Use
+ * `stagedTarget` to verify the component actually ships in this release.
+ */
+export declare function collectFileDepLinkSpecs(stagedComponents: readonly StagedComponent[], readDependencies: (manifestDir: string) => Record<string, string>): FileDepLinkSpec[];

package/console/dist/server/utils/update-links.js

@@ -0,0 +1,71 @@
+/**
+ * Data-driven resolution-link derivation for the full-update pipeline.
+ *
+ * The deployed console performs full updates with the update logic baked
+ * into its own dist — one generation behind the components it installs. A
+ * hardcoded link list therefore goes stale the moment a release introduces
+ * a new internal `file:` dependency (observed 2026-08-29: the 1.221.2
+ * console could not know about the newly introduced install-layout
+ * component, so the 1.222.5 update left
+ * host-runtime/node_modules/@principles/install-layout missing and every
+ * pd-cli runtime command failed with ERR_MODULE_NOT_FOUND).
+ *
+ * The authoritative source for "which links does the UPDATED tree need" is
+ * the STAGED manifests under the update's temp dir (the freshly extracted
+ * release trees) — NOT the deployed pre-update manifests, which by
+ * definition do not declare newly added dependencies.
+ *
+ * Each staged component's `file:` refs resolve to a sibling staged
+ * component directory; the deployed link target is that sibling's entry in
+ * the same staged->deployed pairing.
+ */
+import * as path from 'node:path';
+/**
+ * Derive the node_modules link specs implied by each staged component's
+ * declared `file:` dependencies.
+ *
+ * - `readDependencies(manifestDir)` returns the component's dependency map
+ *   (name -> version-or-ref); return {} for unreadable/missing manifests.
+ * - A `file:` ref is resolved against its staged manifest dir to find the
+ *   staged sibling target; the deployed link target is taken from the same
+ *   staged->deployed pairing the caller provides — component identity is
+ *   the staged directory itself (normalized absolute path), NOT the
+ *   deployed directory's basename. In the legacy layout the deployed
+ *   plugin dir is named `principles-disciple` while the staged one is
+ *   `plugin`, so a basename lookup would silently drop the derived link
+ *   (review P1, PR #1457).
+ * - Deps whose staged target is not one of the layout components (e.g.
+ *   @principles/codex-adapter — a separate host install, not part of this
+ *   layout) are skipped.
+ *
+ * Note: `target` (the deployed dir) may not exist yet at derivation time —
+ * for components whose copy step runs after this call, the caller creates
+ * the directory right after deriving and creating these links. Use
+ * `stagedTarget` to verify the component actually ships in this release.
+ */
+export function collectFileDepLinkSpecs(stagedComponents, readDependencies) {
+    const deployedDirByStagedDir = new Map();
+    for (const component of stagedComponents) {
+        deployedDirByStagedDir.set(path.resolve(component.manifestDir), component.deployedDir);
+    }
+    const specs = [];
+    const seen = new Set();
+    for (const component of stagedComponents) {
+        for (const [name, ref] of Object.entries(readDependencies(component.manifestDir))) {
+            if (typeof ref !== 'string' || !ref.startsWith('file:'))
+                continue;
+            const stagedTarget = path.resolve(component.manifestDir, ref.slice('file:'.length));
+            const deployedTarget = deployedDirByStagedDir.get(stagedTarget);
+            if (deployedTarget === undefined)
+                continue;
+            // The link lives in the DEPLOYED component dir (what the updated dist
+            // resolves against) — never inside the throwaway temp dir.
+            const linkPath = path.join(component.deployedDir, 'node_modules', name);
+            if (seen.has(linkPath))
+                continue;
+            seen.add(linkPath);
+            specs.push({ linkPath, target: deployedTarget, stagedTarget });
+        }
+    }
+    return specs;
+}

package/core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@principles/core",
-  "version": "1.270.5",
+  "version": "1.74.1",
   "description": "Pure-logic core of Principles Disciple, an AI Agent Governance System - pain signal capture and principle proposal (no I/O)",
   "type": "module",
   "main": "./dist/index.js",

package/host-runtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@principles/host-runtime",
-  "version": "0.1.1",
+  "version": "0.1.0",
   "description": "Shared host-neutral orchestration for Principles Disciple MVP-Core hook paths.",
   "type": "module",
   "main": "./dist/index.js",

package/install-layout/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@principles/install-layout",
-  "version": "0.1.1",
+  "version": "0.1.0",
   "type": "module",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
@@ -10,17 +10,13 @@
       "default": "./dist/index.js"
     }
   },
-  "files": [
-    "dist"
-  ],
+  "files": ["dist"],
   "license": "MIT",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/csuzngjh/principles.git"
   },
-  "publishConfig": {
-    "access": "public"
-  },
+  "publishConfig": { "access": "public" },
   "scripts": {
     "build": "tsc",
     "test": "npm run build && vitest run"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-principles-disciple",
-  "version": "1.121.9",
+  "version": "1.121.10",
   "description": "Interactive CLI installer for Principles Disciple OpenClaw plugin",
   "type": "module",
   "bin": {

package/pd-cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@principles/pd-cli",
-  "version": "1.142.4",
+  "version": "1.74.1",
   "description": "PD CLI — Pain recording, sample management, and governance tasks for Principles Disciple",
   "type": "module",
   "bin": {

package/plugin/dist/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "principles-disciple",
   "name": "Principles Disciple",
   "description": "Principles Disciple is an AI Agent Governance System. Stop correcting the same AI behavior across sessions. Turn repeated Agent corrections into Owner-approved, observable, reversible behavior principles.",
-  "version": "1.222.5",
+  "version": "1.198.1",
   "activation": {
     "onCapabilities": [
       "hook"