@openparachute/hub 0.7.7-rc.7 → 0.7.7-rc.9

package/src/notes-serve.ts

@@ -1,15 +1,19 @@
 #!/usr/bin/env bun
 
 /**
- * Tiny static-file server for the @openparachute/notes PWA bundle.
+ * Tiny static-file server for a Parachute PWA bundle — originally written
+ * for @openparachute/notes, generalized in hub-parity P5 (2026-07-11) to
+ * also serve @openparachute/parachute-app (the super-surface front door,
+ * port 1944, mount `/app`) via the same shim. Any package matching this
+ * shape (a prebuilt SPA `dist/` with no server of its own) can reuse it.
  *
- * Notes is a SPA — no backend of its own. `parachute start notes` invokes
- * this shim with the installed `dist/` path so the PWA is served at a
- * known port and can be reverse-proxied by `parachute expose` alongside
- * the other services.
+ * A served bundle is a SPA — no backend of its own. `parachute start
+ * <svc>` invokes this shim with the installed `dist/` path so the PWA is
+ * served at a known port and can be reverse-proxied by `parachute expose`
+ * alongside the other services.
  *
  * Invoked as:
- *   bun <this-file> --port <n> [--dist <path>] [--mount <prefix>]
+ *   bun <this-file> --port <n> [--dist <path>] [--mount <prefix>] [--package <npmName>]
  *
  * `--mount` (default `/notes`) is the path prefix the reverse proxy hands
  * us. We strip it before resolving against `dist/` so a request for
@@ -17,27 +21,43 @@
  * `{dist}/notes/sw.js`. Without the strip, the SW + .webmanifest both
  * SPA-fall-back to index.html with content-type text/html, and the PWA
  * install prompt never fires. Pass `--mount ""` (or `--mount /`) when the
- * bundle is served at the origin root.
+ * bundle is served at the origin root. THIS IS LOAD-BEARING for every
+ * package served by this shim, not just notes — keep it exactly as-is.
  *
- * If --dist is omitted, we resolve @openparachute/notes's dist directory
- * via Bun.resolveSync. If that fails (package not installed globally, or
+ * `--package` (default `@openparachute/notes`, back-compat) names the npm
+ * package whose `dist/` we resolve when `--dist` is omitted. Passed by
+ * FIRST_PARTY_FALLBACKS entries whose startCmd composes this shim for a
+ * package other than notes (e.g. `app`'s `--package @openparachute/parachute-app`).
+ *
+ * If --dist is omitted, we resolve the package's dist directory via
+ * Bun.resolveSync. If that fails (package not installed globally, or
  * package doesn't ship dist/), exit 1 with a clear error.
+ *
+ * `/health` (post-mount-strip) always answers 2xx — the doctor/status
+ * probe (`probeModuleHealth`) only cares about the status code, but we
+ * answer explicitly rather than relying on the SPA-shell catch-all so a
+ * missing/corrupt `dist/index.html` can't take the health check down with it.
  */
 
 import { existsSync } from "node:fs";
 import { homedir } from "node:os";
 import { dirname, join, resolve } from "node:path";
 
+/** Back-compat default — the shim's original (and still primary) consumer. */
+const DEFAULT_PACKAGE = "@openparachute/notes";
+
 interface Args {
   port: number;
   dist?: string;
   mount: string;
+  pkg: string;
 }
 
 function parseArgs(argv: string[]): Args {
   let port = 5173;
   let dist: string | undefined;
   let mount = "/notes";
+  let pkg = DEFAULT_PACKAGE;
   for (let i = 0; i < argv.length; i++) {
     const a = argv[i];
     if (a === "--port") {
@@ -56,11 +76,15 @@ function parseArgs(argv: string[]): Args {
       const v = argv[++i];
       if (v === undefined) throw new Error("--mount requires a value");
       mount = normalizeMount(v);
+    } else if (a === "--package") {
+      const v = argv[++i];
+      if (!v) throw new Error("--package requires a value");
+      pkg = v;
     } else {
       throw new Error(`unknown argument: ${a}`);
     }
   }
-  return { port, dist, mount };
+  return { port, dist, mount, pkg };
 }
 
 export function normalizeMount(raw: string): string {
@@ -70,22 +94,22 @@ export function normalizeMount(raw: string): string {
 
 /**
  * Candidate base directories that `Bun.resolveSync` walks from when looking
- * for `@openparachute/notes/package.json`. Order matters:
+ * for `<package>/package.json`. Order matters:
  *
- *   1. `process.cwd()` — works when notes-serve is invoked from inside the
- *      notes checkout (e.g. via `installDir` cwd in lifecycle.ts) or from
- *      any project that depends on `@openparachute/notes`.
+ *   1. `process.cwd()` — works when the shim is invoked from inside the
+ *      package's own checkout (e.g. via `installDir` cwd in lifecycle.ts) or
+ *      from any project that depends on the package.
  *   2. `~/.bun/install/global/node_modules` — modern Bun's global-install
- *      layout. This is where `bun add -g @openparachute/notes` lands the
- *      package, and where `bun link @openparachute/notes` symlinks it.
+ *      layout. This is where `bun add -g <package>` lands the package, and
+ *      where `bun link <package>` symlinks it.
  *   3. `~/.bun/install/global` — defensive fallback for older Bun layouts.
  *
- * Hub itself does NOT depend on `@openparachute/notes`, so when
- * `parachute start notes` is run from the hub repo dir, the cwd-relative
- * resolve walks ancestral node_modules and finds nothing. Bun does not
- * auto-consult the global install dir, so bun-linked installs fail to
- * resolve without (2)/(3). hub#194: Aaron hit silent 502 on tailnet
- * `/notes/` because of this — fixed by trying the global install dirs.
+ * Hub itself does NOT depend on the served package, so when `parachute
+ * start <svc>` is run from the hub repo dir, the cwd-relative resolve walks
+ * ancestral node_modules and finds nothing. Bun does not auto-consult the
+ * global install dir, so bun-linked installs fail to resolve without
+ * (2)/(3). hub#194: Aaron hit silent 502 on tailnet `/notes/` because of
+ * this — fixed by trying the global install dirs.
  *
  * Exported (and parameterized via `cwd`/`home`) so tests can drive the
  * resolution order against a real fixture install without monkey-patching
@@ -98,6 +122,8 @@ export function notesDistCandidates(cwd: string, home: string): string[] {
 export interface ResolveNotesDistDeps {
   cwd?: string;
   home?: string;
+  /** npm package name to resolve. Defaults to `@openparachute/notes` (back-compat). */
+  pkg?: string;
   /** Override `Bun.resolveSync` for tests. */
   resolveSync?: (specifier: string, base: string) => string;
   existsSync?: (path: string) => boolean;
@@ -106,6 +132,7 @@ export interface ResolveNotesDistDeps {
 export function resolveNotesDistFrom(deps: ResolveNotesDistDeps = {}): string {
   const cwd = deps.cwd ?? process.cwd();
   const home = deps.home ?? homedir();
+  const pkg = deps.pkg ?? DEFAULT_PACKAGE;
   const resolveSync = deps.resolveSync ?? Bun.resolveSync;
   const exists = deps.existsSync ?? existsSync;
   const candidates = notesDistCandidates(cwd, home);
@@ -113,7 +140,7 @@ export function resolveNotesDistFrom(deps: ResolveNotesDistDeps = {}): string {
   for (const base of candidates) {
     let pkgPath: string;
     try {
-      pkgPath = resolveSync("@openparachute/notes/package.json", base);
+      pkgPath = resolveSync(`${pkg}/package.json`, base);
     } catch (err) {
       resolveErrors.push(`  - ${base}: ${err instanceof Error ? err.message : String(err)}`);
       continue;
@@ -126,18 +153,18 @@ export function resolveNotesDistFrom(deps: ResolveNotesDistDeps = {}): string {
       // other candidates — they'd resolve to the same package and report
       // the same problem.
       throw new Error(
-        `@openparachute/notes resolved at ${root} has no dist/ directory at ${dist}. The package may not ship a prebuilt bundle — ask the notes maintainer to add a prepublishOnly build step.`,
+        `${pkg} resolved at ${root} has no dist/ directory at ${dist}. The package may not ship a prebuilt bundle — ask the ${pkg} maintainer to add a prepublishOnly build step.`,
       );
     }
     return dist;
   }
   throw new Error(
-    `Could not resolve @openparachute/notes from any of:\n${resolveErrors.join("\n")}\nIs the package installed? Try \`bun add -g @openparachute/notes\` or \`parachute install notes\`.`,
+    `Could not resolve ${pkg} from any of:\n${resolveErrors.join("\n")}\nIs the package installed? Try \`bun add -g ${pkg}\` or the matching \`parachute install <short>\`.`,
   );
 }
 
-function resolveNotesDist(): string {
-  return resolveNotesDistFrom();
+function resolveNotesDist(pkg: string): string {
+  return resolveNotesDistFrom({ pkg });
 }
 
 function mimeFor(path: string): string | undefined {
@@ -160,6 +187,17 @@ export function notesFetch(dist: string, mount: string): (req: Request) => Respo
     if (mount && (pathname === mount || pathname.startsWith(`${mount}/`))) {
       pathname = pathname.slice(mount.length) || "/";
     }
+    if (pathname === "/health") {
+      // Explicit rather than falling through to the SPA shell: the doctor /
+      // status probe (`probeModuleHealth`) only checks for a 2xx status, but
+      // answering directly means a missing/corrupt `dist/index.html` can't
+      // take the health check down with it. Every FIRST_PARTY_FALLBACKS
+      // entry served by this shim declares `health` under its own mount
+      // (e.g. `/notes/health`, `/app/health`) — this answers all of them.
+      return new Response(JSON.stringify({ status: "ok" }), {
+        headers: { "content-type": "application/json" },
+      });
+    }
     if (pathname === "/" || pathname.endsWith("/")) {
       return spaShell();
     }
@@ -200,17 +238,21 @@ export function notesServeOptions(
 }
 
 if (import.meta.main) {
-  const { port, dist: distArg, mount } = parseArgs(process.argv.slice(2));
+  const { port, dist: distArg, mount, pkg } = parseArgs(process.argv.slice(2));
 
   let dist: string;
   try {
-    dist = distArg ?? resolveNotesDist();
+    dist = distArg ?? resolveNotesDist(pkg);
   } catch (err) {
-    console.error(`parachute-notes-serve: ${err instanceof Error ? err.message : String(err)}`);
+    console.error(
+      `parachute-static-serve (${pkg}): ${err instanceof Error ? err.message : String(err)}`,
+    );
     process.exit(1);
   }
 
   Bun.serve(notesServeOptions(port, dist, mount));
 
-  console.log(`notes static-serve listening on :${port} (dist=${dist}, mount=${mount || "/"})`);
+  console.log(
+    `static-serve listening on :${port} (pkg=${pkg}, dist=${dist}, mount=${mount || "/"})`,
+  );
 }

package/src/service-spec.ts

@@ -11,7 +11,13 @@ import type { ServiceEntry } from "./services-manifest.ts";
  *   1941  parachute-agent    exploration (renamed from parachute-channel)
  *   1942  parachute-notes    committed core (PWA bundle)
  *   1943  parachute-scribe   committed core
- *   1944–1949  unassigned
+ *   1944  parachute-app      the super-surface front door (PWA bundle,
+ *                            hub-parity P5) — see the PORT_RESERVATIONS
+ *                            comment below for why this is a DIFFERENT
+ *                            module from the pre-2026-05-27 `app`
+ *   1945  unassigned
+ *   1946  parachute-surface  UI host (renamed from `app` 2026-05-27)
+ *   1947–1949  unassigned
  *
  * Hub pins 1939: `parachute expose` composes hub targets as
  * `http://127.0.0.1:1939/` and that URL has to be stable across machines for
@@ -67,12 +73,24 @@ export const PORT_RESERVATIONS: readonly PortReservation[] = [
   { port: 1941, name: "parachute-agent", status: "assigned" },
   { port: 1942, name: "parachute-notes", status: "assigned" },
   { port: 1943, name: "parachute-scribe", status: "assigned" },
-  { port: 1944, name: "unassigned", status: "reserved" },
+  // hub-parity P5 (2026-07-11): parachute-app's canonical slot — the NEW
+  // super-surface front door (@openparachute/parachute-app), landing as a
+  // FIRST_PARTY_FALLBACKS entry (short "app") with its own hub-side static-
+  // serve shim (notes-serve.ts --package). This is a DIFFERENT, unrelated
+  // module from the pre-2026-05-27 `app` package described in the 1946
+  // comment below — the two just happen to share the name across a rename.
+  // Status `assigned` keeps the fallback-port walker (`assignPort` in
+  // port-assign.ts) from handing this port to a colliding third-party
+  // module.
+  { port: 1944, name: "parachute-app", status: "assigned" },
   { port: 1945, name: "unassigned", status: "reserved" },
-  // hub#323: parachute-app's canonical slot. Status `assigned` keeps the
-  // fallback-port walker (`assignPort` in port-assign.ts) from handing this
-  // port out to a colliding third-party module. The matching KNOWN_MODULES
-  // row carries the canonicalPort + paths for status/expose surfaces.
+  // hub#323 (historical): this WAS `parachute-app`'s canonical slot back
+  // when "app" meant the UI-host module. That module renamed to
+  // `parachute-surface` 2026-05-27 (patterns#102); port 1944 above is the
+  // different, new parachute-app (super-surface) from hub-parity P5. Status
+  // `assigned` keeps the fallback-port walker from handing 1946 to a
+  // colliding third-party module. The matching KNOWN_MODULES row carries
+  // the canonicalPort + paths for status/expose surfaces.
   { port: 1946, name: "parachute-surface", status: "assigned" },
   { port: 1947, name: "unassigned", status: "reserved" },
   { port: 1948, name: "unassigned", status: "reserved" },
@@ -278,9 +296,15 @@ export function composeServiceSpec(opts: {
 //     — its startCmd is composed from the services.json entry's port + mount,
 //     which is hub-side logic, not something notes itself runs. (The archive
 //     isn't done — notes-daemon Phase 3 retirement hasn't landed.)
+//   - app: the NEW super-surface front door (@openparachute/parachute-app,
+//     hub-parity P5, 2026-07-11) — same shape as notes: a frontend bundle
+//     with no server of its own, served by the SAME hub-side shim
+//     (`notes-serve.ts --package @openparachute/parachute-app`). Unrelated
+//     to the pre-2026-05-27 `app` package that renamed to `surface` (see
+//     the KNOWN_MODULES.surface tagline + the RETIRED_MODULES note below).
 //
-// The remaining entry keeps its "FALLBACK: Delete when …" marker so the
-// next cleanup pass is a one-grep operation.
+// Each entry keeps its "FALLBACK: Delete when …" marker so the next cleanup
+// pass is a one-grep operation.
 // ---------------------------------------------------------------------------
 
 // FALLBACK: Delete when @openparachute/notes ships .parachute/module.json AND
@@ -317,11 +341,58 @@ const NOTES_FALLBACK: FirstPartyFallback = {
   },
 };
 
+// FALLBACK: Delete when @openparachute/parachute-app ships
+// .parachute/module.json AND self-registers its services.json row at boot.
+// As of hub-parity P5 the app repo doesn't carry the real module.json yet —
+// only a stale `dist/.parachute/info` artifact (name: "parachute-notes")
+// left over from seeding the app off notes-ui, which is a DIFFERENT file
+// (module-manifest.ts's runtime `/.parachute/info`, not the static
+// `.parachute/module.json` contract this fallback stands in for) and
+// doesn't block this fallback path. parachute-app is a frontend bundle (the
+// super-surface front door) with no server of its own, so — same as notes —
+// its startCmd is hub-side logic composed from the services.json entry
+// (port + mount), running through the SAME `notes-serve.ts` shim
+// generalized in hub-parity P5 via `--package`.
+const APP_FALLBACK: FirstPartyFallback = {
+  package: "@openparachute/parachute-app",
+  manifest: {
+    name: "app",
+    manifestName: "parachute-app",
+    displayName: "Parachute",
+    tagline: "The Parachute app — your parachute's front door.",
+    port: 1944,
+    paths: ["/app"],
+    health: "/app/health",
+  },
+  extras: {
+    startCmd: (entry) => {
+      const first = entry.paths[0] ?? "/app";
+      const mount = first === "/" ? "" : first.replace(/\/+$/, "");
+      return [
+        "bun",
+        NOTES_SERVE_PATH,
+        "--port",
+        String(entry.port),
+        "--mount",
+        mount,
+        "--package",
+        "@openparachute/parachute-app",
+      ];
+    },
+    postInstallFooter: () => [
+      "",
+      "Open your Parachute at <origin>/app — it signs in with your hub account.",
+      "The hub's front page (`/`) now opens the app too, unless you've already",
+      "set a custom root redirect (`parachute hub set-root-redirect` or the admin SPA).",
+    ],
+  },
+};
+
 /**
  * Vendored manifests + extras for first-party modules that still need them.
  * Indexed by short name (the `parachute install <X>` token).
  *
- * Only notes remains — see the block comment above for the rationale
+ * notes + app remain — see the block comment above for the rationale
  * (vault/scribe/agent now self-register and ship their own
  * module.json). Other code paths consult both this table AND `KNOWN_MODULES`
  * (which carries the post-self-register-retirement entries) via the helpers
@@ -329,6 +400,7 @@ const NOTES_FALLBACK: FirstPartyFallback = {
  */
 export const FIRST_PARTY_FALLBACKS: Record<string, FirstPartyFallback> = {
   notes: NOTES_FALLBACK,
+  app: APP_FALLBACK,
 };
 
 /**
@@ -520,8 +592,15 @@ export const KNOWN_MODULES: Record<string, KnownModule> = {
  *     legacy operators. `notes` (the daemon) is the canonical
  *     "deprecating-but-not-retired" case as of 2026-05-22: do not add
  *     until its Phase 3 retirement lands.
- *   - Entries stay forever. Removing an entry would let a stale row
- *     reappear silently on legacy installs.
+ *   - Entries stay forever — UNLESS the retired name is later reclaimed by a
+ *     genuinely new, unrelated module that needs to self-register under it
+ *     for real (see the `app` / `parachute-app` un-retirement note below).
+ *     That's the one case where removal is correct: keeping a retirement
+ *     entry alongside a live FIRST_PARTY_FALLBACKS/KNOWN_MODULES entry of
+ *     the SAME name would make `dropRetiredModuleRows` GC the live module's
+ *     own services.json row on every read — an outright regression, not a
+ *     conservative default. Ordinary "this module is genuinely gone"
+ *     entries (no successor reusing the name) still stay forever.
  */
 export const RETIRED_MODULES: Record<string, { retiredAt: string; replacement?: string }> = {
   // NOTE (2026-06-17, channel→agent rename): the `agent` / `parachute-agent`
@@ -538,21 +617,24 @@ export const RETIRED_MODULES: Record<string, { retiredAt: string; replacement?:
   // which is harmless / arguably correct since paraclaw was the original
   // "agent".)
   //
-  // The `parachute-app` row name retires 2026-05-27 along with the
-  // app → surface rename (patterns#102). Operators upgrading from
-  // 0.5.13-stable will have a `parachute-app` row in services.json
-  // pointing at the now-removed @openparachute/app package; this entry
-  // drops it on load + steers them at `parachute install surface`.
-  // The short-name `app` form is included for legacy rows that used
-  // the short name as the `name` field.
-  app: {
-    retiredAt: "2026-05-27",
-    replacement: "parachute-surface (renamed from parachute-app — `parachute install surface`)",
-  },
-  "parachute-app": {
-    retiredAt: "2026-05-27",
-    replacement: "parachute-surface (renamed from parachute-app — `parachute install surface`)",
-  },
+  // NOTE (2026-07-11, hub-parity P5 — `app` / `parachute-app` UN-RETIRED):
+  // this table carried `app` + `parachute-app` (retired 2026-05-27, the
+  // app → surface rename, patterns#102) from hub#219 through hub-parity P4.
+  // They are REMOVED as of this note: a NEW, unrelated module — the real
+  // `@openparachute/parachute-app` super-surface front door (see
+  // FIRST_PARTY_FALLBACKS.app + PORT_RESERVATIONS' port-1944 comment) —
+  // claims the `parachute-app` manifestName (and the bare `app` short) for
+  // real. Keeping these entries would make `dropRetiredModuleRows`
+  // unconditionally GC the new module's services.json row on every read,
+  // breaking it outright — see the curation-rule exception above. An
+  // operator with a genuinely stale PRE-2026-05-27 `app`/`parachute-app` row
+  // (from the old, now-defunct @openparachute/app package) is handled the
+  // same as any other unrecognized row once un-retired: `parachute status`
+  // renders it, and `parachute serve` boots it via installDir's
+  // module.json if present and logs-and-skips otherwise — the same
+  // graceful fallback the `runner` registry removal (2026-07-01, see
+  // KNOWN_MODULES below) relies on. In practice the real parachute-app
+  // module's own first boot overwrites any stale row sharing its name.
 };
 
 /**
@@ -632,7 +714,8 @@ export function knownServices(): string[] {
  * manifest-declared `focus`; this map is the fallback when `module.json` omits
  * it (and the bootstrap value before a module is installed).
  *
- *   - `core` — vault / scribe / hub / surface (the product surface).
+ *   - `core` — vault / scribe / hub / surface / app (the product surface;
+ *     `app` joined 2026-07-11, hub-parity P5 — the super-surface front door).
  *   - `experimental` — agent (legit preview; still OFFERED on a fresh install)
  *     + any unlisted third-party short.
  *   - `deprecated` — notes (notes-daemon deprecated 2026-05-22; notes-ui moved
@@ -650,6 +733,7 @@ const FOCUS_DEFAULTS: Record<string, ModuleFocus> = {
   scribe: "core",
   hub: "core",
   surface: "core",
+  app: "core",
   agent: "experimental",
   notes: "deprecated",
 };
@@ -738,7 +822,7 @@ export function canonicalPortForManifest(manifestName: string): number | undefin
 /**
  * Resolve the runtime spec for a known short name.
  *
- * FIRST_PARTY_FALLBACKS shorts (notes) return a fully-composed
+ * FIRST_PARTY_FALLBACKS shorts (notes / app) return a fully-composed
  * spec with embedded manifest + extras — the vendored manifest is the
  * source of truth pre-install and the install path preserves it through.
  *
@@ -851,7 +935,7 @@ const LEGACY_MANIFEST_ALIASES: Record<string, string> = {
 };
 
 /** Short name for a given manifest name, e.g. `parachute-vault` → `vault`.
- *  Consults both FIRST_PARTY_FALLBACKS (notes) and KNOWN_MODULES
+ *  Consults both FIRST_PARTY_FALLBACKS (notes / app) and KNOWN_MODULES
  *  (vault / scribe / agent / surface — post-FALLBACK-retirement).
  *  Returns undefined for unknown manifests. */
 export function shortNameForManifest(manifestName: string): string | undefined {

package/src/services-manifest.ts

@@ -623,7 +623,8 @@ export function readManifestLenient(
     );
     return { services: [] };
   }
-  const afterRetired = dropRetiredModuleRows(raw, path);
+  const healed = healStaleUiHostAppRows(raw, path);
+  const afterRetired = dropRetiredModuleRows(healed.raw, path);
   const cleaned = dropLegacyShortNameRows(afterRetired.raw, path);
   // `typeof null === "object"` in JS, so the `!cleaned.raw` part of this
   // guard is load-bearing for the null case — not a typo or redundancy.
@@ -671,21 +672,28 @@ export function readManifest(path: string = SERVICES_MANIFEST_PATH): ServicesMan
       `failed to parse ${path}: ${err instanceof Error ? err.message : String(err)}`,
     );
   }
-  // Retired-module + legacy short-name row cleanup runs BEFORE shape
+  // Row-heal + retired-module + legacy short-name cleanup all run BEFORE shape
   // validation because the bugs they heal (rows that conflict on port with
   // a current row) would otherwise throw inside `validateManifest`'s
-  // duplicate-port gate. Order matters: drop retired-module rows FIRST so
-  // their absence can unmask a `parachute-<X>` ↔ `<X>` pair underneath that
-  // `dropLegacyShortNameRows` then handles. The reverse order would leave
-  // a retired row that the short-name pass doesn't recognize. Both passes
-  // mutate the raw JSON object's `services` array; we re-validate against
-  // the cleaned shape. See `dropRetiredModuleRows` + `dropLegacyShortNameRows`
-  // for the full discipline.
-  const afterRetired = dropRetiredModuleRows(raw, path);
+  // duplicate-port gate. Order matters:
+  //   1. `healStaleUiHostAppRows` FIRST — a pre-rename operator can carry BOTH
+  //      a `parachute-app` AND an `app` stale row (2026-05-22 double-write
+  //      reproducer); dropping by OLD-UI-host shape here clears both, whereas
+  //      `dropLegacyShortNameRows` would keep the `parachute-app` half. Runs
+  //      ahead of the retired-module pass too (the `app`/`parachute-app`
+  //      RETIRED_MODULES entries were removed in hub-parity P5 — the names are
+  //      the NEW app's now — so this shape-gated heal is their replacement).
+  //   2. `dropRetiredModuleRows` — drop genuinely-retired rows so their
+  //      absence can unmask a `parachute-<X>` ↔ `<X>` pair underneath that
+  //   3. `dropLegacyShortNameRows` then handles.
+  // Each pass mutates the raw JSON object's `services` array; we re-validate
+  // against the cleaned shape. See the three helpers for the full discipline.
+  const healed = healStaleUiHostAppRows(raw, path);
+  const afterRetired = dropRetiredModuleRows(healed.raw, path);
   const cleaned = dropLegacyShortNameRows(afterRetired.raw, path);
   const validated = validateManifest(cleaned.raw, path);
   const migrated = migrateClawToAgent(validated);
-  const changed = afterRetired.changed || cleaned.changed || migrated.changed;
+  const changed = healed.changed || afterRetired.changed || cleaned.changed || migrated.changed;
   if (changed) writeManifest(migrated.manifest, path);
   return migrated.manifest;
 }
@@ -745,6 +753,91 @@ function dropRetiredModuleRows(raw: unknown, where: string): { raw: unknown; cha
   };
 }
 
+/**
+ * Heal stale OLD-UI-host `app`/`parachute-app` rows on load (hub-parity P5,
+ * 2026-07-11).
+ *
+ * Context: the name `parachute-app` originally belonged to the UI-host module
+ * that renamed to `parachute-surface` on 2026-05-27 (patterns#102). Its
+ * retirement used to be handled by a `RETIRED_MODULES` entry that
+ * `dropRetiredModuleRows` GC'd unconditionally. Hub-parity P5 REUSES the
+ * `parachute-app` manifestName (+ the bare `app` short) for a genuinely NEW,
+ * unrelated module — the super-surface front door — so that retirement entry
+ * had to be removed (keeping it would GC the new module's own row on every
+ * read). This heal is the surgically narrow replacement for the ONE case the
+ * removed retirement still needs to cover: an operator upgrading DIRECTLY from
+ * a pre-rename release (~0.5.13-stable) who skipped every intermediate boot
+ * that would have GC'd their stale row. Without a heal, that stale row would:
+ *   - crash-loop on boot — `reconcilePortToCanonical` rewrites its port to
+ *     1944, then the supervisor spawns the app static-serve shim against a
+ *     `@openparachute/parachute-app` that isn't installed → exit 1 → a
+ *     forever-restarting "app" unit the operator never installed;
+ *   - hijack `/surface/*` if a real `parachute-surface` row is also present
+ *     (both claim `/surface`);
+ *   - and, after `parachute install app`, keep its stale `/surface` mount so
+ *     the app serves under `/surface` while the install's `root_redirect=/app/`
+ *     points the front page at a 404.
+ *
+ * Discriminant (structural — pinned against the OLD-UI-host row shape verified
+ * in `git show origin/main`'s retired-`app` + legacy-short-name test fixtures:
+ * `port: 1946`, `paths: ["/surface"]`, `health: "/surface/..."`):
+ *   - `name` is exactly `"app"` or `"parachute-app"`, AND
+ *   - it is NOT the NEW app's own row (the new app mounts at `/app` — never
+ *     healed regardless of port), AND
+ *   - it carries the OLD-UI-host signature: `paths[0]` is `/surface`-rooted OR
+ *     `port === 1946` (the old canonical slot; now `parachute-surface`'s).
+ *
+ * The NEW app row (`paths: ["/app"]`, port 1944) is structurally disjoint on
+ * BOTH clauses, so it is always left intact. Matches `dropRetiredModuleRows`'s
+ * behavior: a plain DROP + a stderr warning steering the operator to
+ * `parachute install surface` (the same replacement the retirement named).
+ *
+ * Operates on raw JSON (before `validateManifest`) because a stale row can
+ * collide on port 1946 with a real `parachute-surface` row and would otherwise
+ * trip the duplicate-port gate before this heal runs. Runs FIRST in the load
+ * pipeline (ahead of `dropRetiredModuleRows` / `dropLegacyShortNameRows`): a
+ * pre-rename operator can carry BOTH a `parachute-app` and an `app` stale row
+ * (the 2026-05-22 double-write reproducer) — dropping by shape here clears
+ * both, whereas `dropLegacyShortNameRows` would keep the `parachute-app` half.
+ */
+function healStaleUiHostAppRows(raw: unknown, where: string): { raw: unknown; changed: boolean } {
+  if (!raw || typeof raw !== "object") return { raw, changed: false };
+  const services = (raw as Record<string, unknown>).services;
+  if (!Array.isArray(services)) return { raw, changed: false };
+
+  const dropped: string[] = [];
+  const nextServices = services.filter((row) => {
+    if (!row || typeof row !== "object") return true;
+    const rec = row as Record<string, unknown>;
+    const name = rec.name;
+    if (name !== "app" && name !== "parachute-app") return true;
+    const paths = rec.paths;
+    const first = Array.isArray(paths) && typeof paths[0] === "string" ? paths[0] : undefined;
+    // NEW super-surface app mounts at `/app` (port 1944) — never heal it,
+    // whatever its port happens to be after a reconcile/collision walk.
+    if (first === "/app" || first?.startsWith("/app/")) return true;
+    const port = rec.port;
+    const oldSurfaceMount = first === "/surface" || first?.startsWith("/surface/") === true;
+    const oldCanonicalPort = port === 1946;
+    if (!oldSurfaceMount && !oldCanonicalPort) return true;
+    dropped.push(String(name));
+    return false;
+  });
+
+  if (dropped.length === 0) return { raw, changed: false };
+
+  for (const name of dropped) {
+    console.error(
+      `${where}: dropped stale pre-rename '${name}' row (the OLD UI-host module, renamed to parachute-surface 2026-05-27). The name now belongs to the new Parachute app (mount /app, port 1944). If an old daemon is still running, stop it; install the current UI host with \`parachute install surface\`.`,
+    );
+  }
+
+  return {
+    raw: { ...(raw as Record<string, unknown>), services: nextServices },
+    changed: true,
+  };
+}
+
 /**
  * Drop legacy short-name rows when a same-module manifestName row exists
  * on the same port. Handles the duplicate-row class introduced when a