@openparachute/vault 0.6.4-rc.8 → 0.6.4-rc.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openparachute/vault",
-  "version": "0.6.4-rc.8",
+  "version": "0.6.4-rc.9",
   "description": "Agent-native knowledge graph. Notes, tags, links over MCP.",
   "module": "src/cli.ts",
   "type": "module",

package/src/cli.ts

@@ -1674,11 +1674,11 @@ function cmdRemove(args: string[]) {
   // out of the parachute-vault row immediately — the same selfRegister
   // refresh cmdCreate does (#208). Without this, the hub's well-known
   // fan-out kept advertising the deleted vault until the next server boot.
-  // Note: with zero vaults remaining, selfRegister falls back to the
-  // manifest's canonical paths (`/vault/default`) — the same row a
-  // subsequent boot would write — so CLI-remove and boot agree on the
-  // zero-vault registration shape. Warnings go to stderr; status lines stay
-  // ours.
+  // Note: with zero vaults remaining, selfRegister emits paths: [] (#478) —
+  // the row stays present (so the hub still sees the module as installed)
+  // but advertises no /vault/<name> path. The hub must tolerate empty-paths
+  // rows and skip them rather than resolving a phantom "default". Warnings
+  // go to stderr; status lines stay ours.
   selfRegister({
     version: pkg.version,
     warn: (msg) => console.error(`Warning: ${msg}`),

package/src/self-register.test.ts

@@ -61,10 +61,8 @@ function captureLogs(): {
 }
 
 describe("self-register", () => {
-  test("buildVaultServicePaths — no vaults yet → manifest fallback", () => {
-    expect(buildVaultServicePaths(undefined, [], ["/vault/default"])).toEqual([
-      "/vault/default",
-    ]);
+  test("buildVaultServicePaths — no vaults yet → empty paths (no phantom /vault/default, #478)", () => {
+    expect(buildVaultServicePaths(undefined, [], ["/vault/default"])).toEqual([]);
   });
 
   test("buildVaultServicePaths — default vault sorts first", () => {
@@ -108,7 +106,9 @@ describe("self-register", () => {
       const row = parsed.services[0] as Record<string, unknown>;
       expect(row.name).toBe("parachute-vault");
       expect(row.port).toBe(1940);
-      expect(row.paths).toEqual(["/vault/default"]);
+      // Zero vaults → paths: [] (no phantom /vault/default, #478).
+      // Health still well-formed: paths[0] ?? "/vault/default" fallback.
+      expect(row.paths).toEqual([]);
       expect(row.health).toBe("/vault/default/health");
       expect(row.version).toBe("0.4.8-rc.3");
       expect(row.installDir).toBe("/fake/install/dir");

package/src/self-register.ts

@@ -56,8 +56,13 @@ import { listVaults, readGlobalConfig, DEFAULT_PORT } from "./config.ts";
  *
  * Mirrors `buildVaultServicePaths` in `cli.ts` so the self-register pass
  * produces the same multi-vault path advertisement as `parachute-vault
- * init` / `vault create`. With no vaults yet, falls back to the manifest's
- * canonical `paths[0]` so early-boot registration is still well-formed.
+ * init` / `vault create`.
+ *
+ * At zero vaults, returns an empty array (`paths: []`). The row remains
+ * present in services.json (name, port, health, version, installDir intact
+ * — so the module is still detected as installed), but it advertises no
+ * `/vault/<name>` path and the hub must not resolve it to a phantom
+ * `/vault/default`. Closes #478.
  *
  * Exported for tests; not part of the public module surface.
  */
@@ -66,7 +71,7 @@ export function buildVaultServicePaths(
   vaults: readonly string[],
   fallbackFromManifest: readonly string[],
 ): string[] {
-  if (vaults.length === 0) return [...fallbackFromManifest];
+  if (vaults.length === 0) return [];
   if (defaultVault && vaults.includes(defaultVault)) {
     return [
       `/vault/${defaultVault}`,

package/src/vault-remove.test.ts

@@ -141,13 +141,12 @@ describe("vault remove — last-vault auto_create marker", () => {
     // resurrection of a freshly-credentialed "default".
     expect(bootAutoCreateAllowed(config)).toBe(false);
 
-    // services.json was still refreshed: with zero vaults the row falls back
-    // to the manifest's canonical paths — the SAME row a subsequent boot's
-    // selfRegister writes, so CLI-remove and boot agree on the zero-vault
-    // registration shape (and the hub still sees the module as installed).
+    // services.json was still refreshed: with zero vaults the row carries
+    // paths: [] (#478) — the row stays present so the hub sees the module as
+    // installed, but advertises no /vault/<name> path (no phantom default).
     const vault = readServices(home).find((s) => s.name === "parachute-vault");
     expect(vault).toBeDefined();
-    expect(vault!.paths).toEqual(["/vault/default"]);
+    expect(vault!.paths).toEqual([]);
   });
 
   test("removing a NON-last vault does not write the marker", () => {