dsh-home-hosted 0.4.2 → 0.4.4

package/docs/DESIGN.md

@@ -95,7 +95,10 @@ explicit `$HHOSTED_HOME` still wins, and a panel already living at
 every server look like it vanished), but otherwise the root is the instance's own
 `<stateDir>/panel`. Only a root with a `servers.config.json` counts, or a
 `run.json` whose pid is alive — a killed panel leaves a runtime file behind, and
-adopting on that would point a fresh install at somebody's dead root.
+adopting on that would point a fresh install at somebody's dead root. Adoption is
+also limited to an instance that already exists: the machine's own harness home,
+or a state dir that already holds settings. A scratch `DSH_HOME` or a test
+project must not reach over and drive the panel some other install owns.
 
 The boot artifact name follows the state root too, but keyed on the *machine*
 default: `home-hosted` only for `~/.dsh/dsh-home-hosted`, `home-hosted-<hash>`

package/lib/index.js

@@ -1989,10 +1989,23 @@ function resolveHomeHostedHome(stateDir, env = process.env, homeDir = os3.homedi
   const configured = env.HHOSTED_HOME?.trim();
   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 (hasLivePanel(legacy))
+  if (isEstablishedInstance(state, homeDir) && hasLivePanel(legacy))
     return { home: legacy, source: "legacy" };
-  return { home: path6.join(resolveUnder(stateDir, homeDir), "panel"), source: "instance" };
+  return { home: own, source: "instance" };
+}
+function isEstablishedInstance(stateDir, homeDir) {
+  if (stateDir === path6.join(homeDir, ".dsh", "dsh-home-hosted"))
+    return true;
+  try {
+    return fs7.statSync(path6.join(stateDir, "settings.json")).isFile();
+  } catch {
+    return false;
+  }
 }
 function hasLivePanel(home) {
   try {