dsh-home-hosted 0.4.3 → 0.4.5

package/docs/DESIGN.md

@@ -175,7 +175,7 @@ channel).
 `onPortConflict: kill` arrived in home-hosted 0.6.0 and `persistent` in 0.6.3, and
 an older panel handed either key can refuse to *boot* from the config. The plugin
 used to consult the answering panel's version and refuse or drop them
-(`KILL_UNSUPPORTED`). That is gone on purpose: it pins `home-hosted@^0.6.7` and
+(`KILL_UNSUPPORTED`). That is gone on purpose: it pins `home-hosted@^0.6.8` and
 autostarts its own copy, so a panel older than those keys is only reachable by
 deliberately preferring an old global install — and this is pre-1.0. Supporting
 older panels again means bringing that check back from history, not re-deriving

package/lib/index.js

@@ -1990,10 +1990,13 @@ function resolveHomeHostedHome(stateDir, env = process.env, homeDir = os3.homedi
   if (configured)
     return { home: resolveUnder(configured, homeDir), source: "env" };
   const state = resolveUnder(stateDir, homeDir);
+  const own = path6.join(state, "panel");
+  if (fs7.existsSync(own))
+    return { home: own, source: "instance" };
   const legacy = path6.join(homeDir, ".home-hosted");
   if (isEstablishedInstance(state, homeDir) && hasLivePanel(legacy))
     return { home: legacy, source: "legacy" };
-  return { home: path6.join(state, "panel"), source: "instance" };
+  return { home: own, source: "instance" };
 }
 function isEstablishedInstance(stateDir, homeDir) {
   if (stateDir === path6.join(homeDir, ".dsh", "dsh-home-hosted"))
@@ -2175,7 +2178,7 @@ import { createRequire } from "node:module";
 import fs10 from "node:fs";
 import path8 from "node:path";
 import process5 from "node:process";
-var EXPECTED_RANGE = "^0.6.7";
+var EXPECTED_RANGE = "^0.6.8";
 var MIN_SUPPORTED_VERSION = "0.4.1";
 function pinnedManifestPath() {
   try {