@khorsheed/dsh-ankh-guard 0.3.0 → 0.3.2

package/lib/types/preflight-runner.js

@@ -131,7 +131,7 @@ class PreflightInfraError extends Error {
  * bundle layers in `dsh.profile.bundles` order, the profile user layer, the
  * home-level user layer, `--patch` overlays, the agent-presets roots overlay
  * (rc host line only; the 0.1.2 line's preset package self-ships its root),
- * then the telemetry switch. Two host API generations are mirrored and
+ * then the telemetry switch. Three host API generations are mirrored and
  * feature-detected per run — see the `hostLine` branch below. Exported so
  * the drift tripwire can compare this assembly against the launcher's own
  * dump without booting anything.
@@ -158,6 +158,8 @@ export async function composePreflightPatches(profile, patchFiles, root, home, b
     }
     const composeEntries = appBoot.composeEntries;
     const healProfilesModuleFallback = appBoot.healProfilesModuleFallback;
+    const createProfileResolutionGeneration = appBoot.createProfileResolutionGeneration;
+    const createRuntimeResolution = appBoot.createRuntimeResolution;
     const loadOptionalPatches = appBoot.loadOptionalPatches;
     const loadOverlayPatches = appBoot.loadOverlayPatches;
     const loadProfile = appBoot.loadProfile;
@@ -174,12 +176,21 @@ export async function composePreflightPatches(profile, patchFiles, root, home, b
     // the profile composition: the heal moved behind the async options API and
     // below the profile load (see HealProfilesModuleFallback), and the launcher
     // dropped its agent-presets shipped-root overlay because the preset package
-    // now self-ships its root. DEFAULT_PROFILE_PATCH_RELOAD is a value export
-    // only the new line carries, so it is the feature marker; a version parse
-    // would break on exactly the unreleased builds this runner must dry-run.
-    // Both lines stay supported: prod hosts run the rc line until 0.1.2 lands
-    // on npm.
-    const hostLine = 'DEFAULT_PROFILE_PATCH_RELOAD' in appBoot ? '0.1.2' : 'rc';
+    // now self-ships its root. The 0.1.6 line flipped the default resolution
+    // mode from link to runtime: its compose computes an immutable resolution
+    // generation instead of materializing fallback links, and it removed
+    // DEFAULT_PROFILE_PATCH_RELOAD — the 0.1.2 line's marker. The 0.1.7 line
+    // deleted the fallback projections outright (in-memory runtime resolution
+    // interception): its compose calls createRuntimeResolution and carries
+    // neither older marker, so the markers must be probed newest-first. Each
+    // marker is a value export only its line carries; a version parse would
+    // break on exactly the unreleased builds this runner must dry-run. All
+    // lines stay supported: prod hosts run 0.1.5 until the next npm line lands.
+    const hostLine = 'createRuntimeResolution' in appBoot
+        ? '0.1.7'
+        : 'createProfileResolutionGeneration' in appBoot
+            ? '0.1.6'
+            : 'DEFAULT_PROFILE_PATCH_RELOAD' in appBoot ? '0.1.2' : 'rc';
     if (hostLine === 'rc')
         healProfilesModuleFallback(anchor, resolvedHome);
     const composed = loadProfile(NAME, profile, anchor, resolvedHome, { userLayer: true });
@@ -189,11 +200,57 @@ export async function composePreflightPatches(profile, patchFiles, root, home, b
     // the dry-run would otherwise fail on exactly the tree a first boot
     // composes fine.
     writeFileSync(join(composed.dir, PROFILE_ROOT_FILENAME), PROFILE_ROOT_CONFIG);
+    let pluginPackagesConfig;
     if (hostLine === '0.1.2') {
         await healProfilesModuleFallback({ installAnchor: anchor, profile: composed, home: resolvedHome });
     }
+    else if (hostLine === '0.1.6') {
+        // The launcher compose's runtime-mode step (apps/cli composeProfile):
+        // compute the generation AFTER the profile load and root-config rewrite,
+        // materializing nothing. Awaited, so a resolution-graph failure rejects
+        // the compose instead of escaping as an unhandled rejection. The explicit
+        // home keeps the recorded profilesDir on the deployment under check. The
+        // generation is kept: the launcher hands it to the boot's PluginPackages
+        // mount (`{ generation }`), and so must the dry-run — computing it and
+        // dropping it leaves profile-tree imports to native Node resolution,
+        // which finds nothing in a tarball profile's node_modules.
+        const generation = await createProfileResolutionGeneration({ installAnchor: anchor, profile: composed, home: resolvedHome });
+        pluginPackagesConfig = { generation };
+    }
+    else if (hostLine === '0.1.7') {
+        // The 0.1.7 launcher compose (apps/cli composeProfile): the resolution is
+        // computed in memory right after the profile load and root-config rewrite
+        // — the older lines' fallback projections are gone for good, so this
+        // interception is the ONLY way profile-tree imports resolve. Awaited, so
+        // a resolution-graph failure rejects the compose instead of escaping as
+        // an unhandled rejection. The resolution is kept for the boot's
+        // PluginPackages mount (`{ resolution }`), exactly as the launcher's
+        // runProfile hands it over; discarding it is the tarball-profile false
+        // FAIL (every official entry reports "failed to import" on a profile
+        // whose real boot is clean).
+        const resolution = await createRuntimeResolution({ installAnchor: anchor, profile: composed });
+        pluginPackagesConfig = { resolution };
+    }
     const homePatches = loadOptionalPatches(NAME, join(resolvedHome, HOME_PATCH_FILENAME)) ?? [];
     const overlays = patchFiles.flatMap(file => loadOverlayPatches(NAME, resolve(file)));
+    // The launcher provides a data-only profileContext service before the tree
+    // mounts (since 0.1.6-alpha.2; the heal-based lines had no such service).
+    // The 0.1.7 settings service injects it, so a dry-run without it leaves
+    // `settings` — and everything injecting it — pending: applies the contract
+    // promises to exercise never run, on a profile the real boot runs clean.
+    const profileContext = hostLine === '0.1.6' || hostLine === '0.1.7'
+        ? {
+            name: profile,
+            dir: composed.dir,
+            patchPath: composed.patchPath,
+            installAnchor: anchor,
+            startedBundles: composed.layers.map(layer => layer.packageName),
+            cwd: process.cwd(),
+            home: resolvedHome,
+            overlays,
+            telemetryDisabledEnv: process.env.DSH_TELEMETRY_DISABLED,
+        }
+        : undefined;
     const bundlePatches = composed.layers.flatMap(layer => layer.patches);
     const patches = [...bundlePatches, ...composed.patches, ...homePatches, ...overlays];
     const rows = new Map();
@@ -231,6 +288,15 @@ export async function composePreflightPatches(profile, patchFiles, root, home, b
             },
         });
     }
+    if (profileContext !== undefined && rows.has('hmr')) {
+        // Providing profileContext satisfies the hmr row's disable expression
+        // (`!ctx.get('profileContext')`) on the runtime-resolution lines. A
+        // dry-run is one-shot — no HMR, no user-patch watchers: the boot's own
+        // tree write-back would queue a config refresh on hmr's operations queue,
+        // and dispose then awaits a queue that never drains (observed: preflight
+        // hung past boot and the process exited 13 on an unsettled await).
+        composedOverlays.push({ id: 'hmr', disabled: true });
+    }
     if (rows.has('ankh-guard')) {
         // The guard plugin writes state at apply (the instance-launch record,
         // snapshots). A dry-run is NOT the real instance — isolate its state to a
@@ -252,7 +318,13 @@ export async function composePreflightPatches(profile, patchFiles, root, home, b
     if (telemetryPatch !== undefined)
         composedOverlays.push(telemetryPatch);
     patches.push(...composedOverlays);
-    return { patches, rows, profileDir: composed.dir };
+    return {
+        patches,
+        rows,
+        profileDir: composed.dir,
+        ...(profileContext === undefined ? {} : { profileContext }),
+        ...(pluginPackagesConfig === undefined ? {} : { pluginPackagesConfig }),
+    };
 }
 /**
  * The launcher's readiness signal, mirrored: 0.1.2's runProfile provides an
@@ -336,6 +408,7 @@ export async function runPreflight(profile, patchFiles = [], root = resolveHarne
     const loadLayeredEnv = appBoot.loadLayeredEnv;
     const launchEnvironmentKey = launchEnvironment.DSH_LAUNCH_ENVIRONMENT_KEY;
     const provideCmdline = cmdline.provideCmdline;
+    const PluginPackages = appBoot.PluginPackages;
     let environment;
     try {
         environment = loadLayeredEnv(NAME);
@@ -362,8 +435,26 @@ export async function runPreflight(profile, patchFiles = [], root = resolveHarne
         const appReady = createAppReadyStub();
         // Cloned for the same insert-aliasing reason the launcher documents: boot
         // application mutates rows by reference.
-        const ctx = await boot(NAME, rootConfig, structuredClone(patches), (hostCtx) => {
+        const ctx = await boot(NAME, rootConfig, structuredClone(patches), async (hostCtx) => {
+            // Mirror runProfile's prepare order: profileContext, launch environment,
+            // PluginPackages, cmdline — all before boot() mounts the root include.
+            if (composed.profileContext !== undefined)
+                hostCtx.provide?.('profileContext', composed.profileContext);
             hostCtx.provide?.(launchEnvironmentKey, environment);
+            // On the runtime-resolution lines the composed resolution/generation
+            // must be mounted in-process through PluginPackages BEFORE the config
+            // tree mounts — boot() awaits prepare before the root include, so every
+            // entry import resolves through the interception. Skipping the mount is
+            // not a neutral shortcut: without it Node resolves profile-tree imports
+            // natively, a tarball profile's node_modules holds no official packages,
+            // and the dry-run reports a wall of "failed to import" on a tree the
+            // real launcher boots clean.
+            if (composed.pluginPackagesConfig !== undefined) {
+                if (PluginPackages === undefined || hostCtx.plugin === undefined) {
+                    throw new Error('host line requires a PluginPackages mount but the loaded app-boot does not export PluginPackages');
+                }
+                await hostCtx.plugin(PluginPackages, composed.pluginPackagesConfig);
+            }
             provideCmdline(hostCtx, { args: [], exit: () => { }, ready: appReady.service });
         });
         // The launcher commits readiness once boot and host setup settle; a

package/locale/en.json

@@ -0,0 +1,6 @@
+{
+  "meta": {
+    "title": "Ankh Guard",
+    "description": "Gate self-modification restarts on a green build and test credential."
+  }
+}

package/locale/zh.json

@@ -0,0 +1,6 @@
+{
+  "meta": {
+    "title": "重启守卫",
+    "description": "先证明构建与测试通过，才放行自我修改的重启。"
+  }
+}

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@khorsheed/dsh-ankh-guard",
   "description": "Hard gate for self-modification restarts: a green-build credential bound to the git HEAD, checked before any restart of the running instance",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "type": "module",
   "main": "lib/index.js",
   "types": "lib/types/index.d.ts",
@@ -25,7 +25,8 @@
       "types": "./lib/types/client/index.d.ts",
       "default": "./lib/client.js"
     },
-    "./package.json": "./package.json"
+    "./package.json": "./package.json",
+    "./locale/*.json": "./locale/*.json"
   },
   "files": [
     "lib/*.js",
@@ -37,12 +38,14 @@
     "scripts/install-systemd.sh",
     "skills/**/*.md",
     "cordis.patch.yml",
+    "locale/*.json",
     "CHANGELOG.md"
   ],
   "license": "MIT",
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.1",
     "@deepseek-ai/dsh-agent": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-agent-preset-registry": "^0.1.0-rc.6",
     "@deepseek-ai/dsh-agent-presets": "^0.1.0-rc.6",
     "@deepseek-ai/dsh-client-connection": "^0.1.0-rc.6",
     "@deepseek-ai/dsh-host-webserver": "^0.1.0-rc.6",
@@ -52,6 +55,12 @@
     "@deepseek-ai/schemastery": "^3.18.1"
   },
   "peerDependenciesMeta": {
+    "@deepseek-ai/dsh-agent-preset-registry": {
+      "optional": true
+    },
+    "@deepseek-ai/dsh-agent-presets": {
+      "optional": true
+    },
     "@deepseek-ai/dsh-client-connection": {
       "optional": true
     },
@@ -59,21 +68,6 @@
       "optional": true
     }
   },
-  "devDependencies": {
-    "@deepseek-ai/cordis": "^4.0.1",
-    "@deepseek-ai/cordis-plugin-loader": "^1.0.2",
-    "@deepseek-ai/dsh-agent": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-agent-presets": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-invariants": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-llm": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-session-persistence": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-skill": "^0.1.5-rc.1",
-    "@deepseek-ai/schemastery": "^3.18.1",
-    "@types/node": "^22.0.0",
-    "tsdown": "^0.22.2",
-    "typescript": "^5.9.0",
-    "vitest": "^3.0.0"
-  },
   "keywords": [
     "dsh",
     "dsh-plugin",
@@ -96,8 +90,8 @@
     },
     "compat": {
       "minHost": "0.1.5-rc.1",
-      "notes": "composition-preflight runs via the standalone preflight-runner and degrades to a notice when no live harness checkout resolves; original-tab browser handoff feature-probes optional WebServer/connection auth seams; reversible state quarantine was exercised in a live 0.1.1-rc.2 to 0.1.2-alpha.4 cutover",
-      "verifiedHost": "0.1.5-rc.1"
+      "notes": "0.1.5-rc.1 full-line boot-verified 2026-09-25 (42 packages including capture) through the three compat layers: preset-registry dual-name probe, dual-shape typert codecs, and typert faces carrying zod@4; 0.1.7-rc.2 is the 3080 production-verified line; composition-preflight runs via the standalone preflight-runner and degrades to a notice when no live harness checkout resolves; original-tab browser handoff feature-probes optional WebServer/connection auth seams; reversible state quarantine was exercised in a live 0.1.1-rc.2 to 0.1.2-alpha.4 cutover",
+      "verifiedHost": "0.1.7-rc.2"
     }
   }
 }

package/skills/dsh-self-restart-guard/SKILL.md

@@ -52,6 +52,8 @@ $GUARD verify --repo <repo> --state-dir "$DSH_HOME/state"
 
 For a classified pure same-launch restart, run only the `verify` line first. If it reports either a fresh green credential or `proven deployment valid`, continue without rerunning the expensive command. The reusable proof exists only after this guard version has observed a complete watchdog restart and canary; `last-good-boot.json` by itself, an older guard state, or a matching HEAD without the runtime fingerprint does not qualify. `schedule-exit` recomputes the fingerprint and pins the selected evidence SHA into the short-lived restart marker, and the successor watchdog revalidates it before accepting canary. A refusal is not bypassable: run the full evidence command above.
 
+Scope the evidence command to the change being proved, and run it against the repo that change lives in. When the change lives OUTSIDE the credential repo — plugin packages shipped to a profile as tarballs, say — the credential repo's monorepo-wide suite proves nothing about the change and may carry unrelated red (a 35k-test suite with hundreds of pre-existing failures in experimental packages takes ~11 minutes to fail and records nothing); that is the deployment driver's job (e.g. `pnpm deploy:3080` records trust-command evidence from its own green gate — see below). Hand `record --run` is for changes inside the credential repo itself, scoped to the suites the change touches whenever that is honest. And because `record` clears the old credential and the reusable proof before running, a failed evidence command leaves the gate with zero valid evidence — `verify` first, record only what you must.
+
 `--trust-command --command "..."` is reserved for an external orchestrator that already observed the command's real exit status (for example, the repository's deployment driver). It is not an agent shortcut.
 
 4. **Composition preflight** — `restart`, `schedule-exit`, and `reconfigure` each run this gate internally exactly once and refuse before stopping the healthy host. For an ordinary same-launch restart, call the stop-capable verb directly; use the standalone verb only to diagnose an already-observed failure, never as a speculative duplicate immediately before that verb: