@openparachute/hub 0.7.6 → 0.7.7-rc.13

package/src/root-serve.ts

@@ -0,0 +1,156 @@
+#!/usr/bin/env bun
+
+/**
+ * Serving the Parachute app AT the hub's origin root (`root_mode = serve-app`).
+ *
+ * When an operator flips the root mode to `serve-app` (or a fresh hub installs
+ * the app during setup), the hub answers its own origin root with the installed
+ * `@openparachute/parachute-app` bundle instead of 302-ing to `/admin`. This is
+ * the self-hosted mirror of the hosted door: hit your box's URL, land in the
+ * app — no redirect hop.
+ *
+ * Why this is asset-correct with no rebuild: the app's Vite build is ROOT-based
+ * (absolute `/assets/*`, PWA scope `/`, OAuth redirect URIs at the origin root).
+ * The `/app` service mount serves the SAME dist through the `notes-serve.ts`
+ * shim with a `/app` prefix-strip; here we serve that identical dist verbatim at
+ * `/`, which is exactly the origin the build assumes. So `serveAppAtRoot` and
+ * the `/app` mount hand back byte-identical bundle files — the only difference
+ * is the URL prefix.
+ *
+ * Precedence is the caller's job (hub-server.ts): the fresh-hub setup wizard
+ * funnel and the pre-admin 503 lockout run BEFORE the root `/` handler, and
+ * every hub-owned route (/admin, /oauth, /.well-known, /vault, /git, /api,
+ * service mounts) dispatches BEFORE the SPA-fallback tail. This module only
+ * decides "given an already-unclaimed GET, does the app dist answer it?".
+ *
+ * NO chrome injection ever rides a root-served response — the app owns its whole
+ * page (same posture as the public/surface chrome opt-out). We build the
+ * responses here directly rather than routing through `decorateWithChrome`.
+ */
+
+import { existsSync, statSync } from "node:fs";
+import { join } from "node:path";
+import { resolveNotesDistFrom } from "./notes-serve.ts";
+
+/** The npm package whose built `dist/` is the app front door. */
+export const APP_PACKAGE = "@openparachute/parachute-app";
+
+/**
+ * Namespaces that keep the hub's branded 404 even in serve-app mode. These are
+ * hub / protocol surfaces, never app client-side routes, so an SPA shell there
+ * would be wrong — and would mask a genuine 404 for an API/OAuth/well-known
+ * typo. (Real dist files never live under these prefixes anyway; this makes the
+ * "don't shell it" decision explicit rather than incidental.)
+ */
+export const ROOT_SERVE_RESERVED_PREFIXES: readonly string[] = [
+  "/api/",
+  "/oauth/",
+  "/.well-known/",
+];
+
+/**
+ * Build a resolver for the installed app's `dist/` directory.
+ *
+ * Resolution goes through the SAME `resolveNotesDistFrom` machinery the `/app`
+ * mount's static-serve shim uses (so root-serve and `/app` resolve to one dist).
+ * A SUCCESSFUL resolution is memoized for the process lifetime — a resolved dist
+ * path doesn't move while the hub runs, and re-walking `Bun.resolveSync` on every
+ * asset request would be needless work. A FAILURE is NOT cached: an operator who
+ * set `serve-app` before installing the app, then runs `parachute install app`,
+ * is picked up on the next request without a hub restart (dynamic recovery).
+ *
+ * `resolve` is the test seam (defaults to the real package resolution). Return
+ * value is the dist dir, or `null` when the app can't be resolved (not installed
+ * / ships no `dist/`).
+ */
+export function makeAppDistResolver(
+  resolve: () => string = () => resolveNotesDistFrom({ pkg: APP_PACKAGE }),
+): () => string | null {
+  let cached: string | null = null;
+  return () => {
+    if (cached !== null) return cached;
+    try {
+      cached = resolve();
+      return cached;
+    } catch {
+      return null;
+    }
+  };
+}
+
+/** MIME overrides Bun.file doesn't infer (mirrors notes-serve.ts). */
+function mimeFor(path: string): string | undefined {
+  // Without this the PWA install prompt sees text/html for the manifest + bails.
+  if (path.endsWith(".webmanifest")) return "application/manifest+json";
+  return undefined;
+}
+
+/**
+ * Answer an already-unclaimed request from the app's root-based `dist/`, or
+ * return `null` to tell the caller to fall through to its normal handling
+ * (the `/` 302 fallback, or the branded 404 tail).
+ *
+ * Contract:
+ *   - non-GET                                     → null (fall through)
+ *   - a reserved hub/protocol prefix              → null (keep the branded 404)
+ *   - GET + an existing file under dist           → that file (asset-correct MIME)
+ *   - GET `/` or a trailing-slash "dir" request   → dist/index.html (SPA shell)
+ *   - GET + no file + Accept: text/html           → dist/index.html (SPA deep link)
+ *   - GET + no file + non-HTML (API probe, etc.)  → null (branded 404)
+ *
+ * `dist` is a resolved directory (from `makeAppDistResolver`); if its
+ * `index.html` has since vanished (app uninstalled after a successful resolve)
+ * we return `null` rather than serving a broken shell.
+ */
+export function serveAppAtRoot(dist: string, req: Request, pathname: string): Response | null {
+  // Only GET is served (HEAD/POST/etc. keep the caller's default — a non-GET to
+  // an unclaimed path stays a 404, and a non-GET `/` keeps its 302).
+  if (req.method !== "GET") return null;
+
+  // Hub/protocol namespaces are never the app's — leave their 404 branded.
+  for (const prefix of ROOT_SERVE_RESERVED_PREFIXES) {
+    if (pathname.startsWith(prefix)) return null;
+  }
+
+  const indexHtml = join(dist, "index.html");
+  // The resolved bundle lost its shell (uninstalled mid-flight) → fall through.
+  if (!existsSync(indexHtml)) return null;
+
+  const spaShell = () =>
+    new Response(Bun.file(indexHtml), {
+      headers: { "content-type": "text/html; charset=utf-8" },
+    });
+
+  // Bare root or a trailing-slash "directory" request → the SPA shell.
+  if (pathname === "/" || pathname.endsWith("/")) return spaShell();
+
+  // An existing dist file: /assets/*, /icon.svg, /manifest.webmanifest, /sw.js …
+  // Malformed percent-encoding (e.g. `/foo%`, `/assets/%ZZ`) makes
+  // `decodeURIComponent` throw a URIError. Catch it and fall through to the
+  // branded 404 (redirect-mode parity) — WITHOUT the guard the throw escapes to
+  // the dispatch outer catch, which classifies a non-DB error as "other" and
+  // re-throws → a bare 500. This path is reachable pre-auth on a public expose,
+  // so a garbage-encoded asset URL must 404, never 500.
+  let decodedPath: string;
+  try {
+    decodedPath = decodeURIComponent(pathname);
+  } catch {
+    return null;
+  }
+  // Path-traversal guard: the joined path must stay strictly under dist/.
+  const filePath = join(dist, decodedPath);
+  if (filePath.startsWith(`${dist}/`) && existsSync(filePath) && statSync(filePath).isFile()) {
+    const mime = mimeFor(filePath);
+    return new Response(
+      Bun.file(filePath),
+      mime ? { headers: { "content-type": mime } } : undefined,
+    );
+  }
+
+  // No matching file. Serve the SPA shell ONLY for HTML navigations (a deep link
+  // like /some-note the app routes client-side). A browser navigation sends
+  // `Accept: text/html`; a non-HTML unclaimed request (API probe, a missing
+  // asset fetched with `Accept: */*`) falls through to the branded 404.
+  const wantsHtml = (req.headers.get("accept") ?? "").includes("text/html");
+  return wantsHtml ? spaShell() : null;
+}

package/src/scope-explanations.ts

@@ -46,7 +46,7 @@ export const SCOPE_EXPLANATIONS: Record<string, ScopeExplanation> = {
       "Read and write everything, plus admin: config & settings, triggers & automation, GitHub backup, and minting access tokens.",
     level: "admin",
   },
-  // Optional-module scopes (scribe / agent / surface). These are in
+  // Optional-module scopes (scribe / surface). These are in
   // FIRST_PARTY_SCOPES (= Object.keys(this map)) but the modules may not be
   // installed — so they're GATED in `OPTIONAL_MODULE_SCOPES` (oauth-handlers.ts)
   // and only advertised in `scopes_supported` when the service is in
@@ -61,10 +61,7 @@ export const SCOPE_EXPLANATIONS: Record<string, ScopeExplanation> = {
     label: "Manage Scribe configuration (provider keys, models, quotas).",
     level: "admin",
   },
-  "agent:send": {
-    label: "Post messages to your Agent.",
-    level: "send",
-  },
+
   // Surface Git Transport scopes (surface-host). `surface:read` = clone/fetch a
   // surface's hub-hosted git repo; `surface:write` = push to it. Named forms
   // (`surface:<name>:<verb>`) collapse to these via the 3→2-segment rule in
@@ -112,8 +109,34 @@ export const SCOPE_EXPLANATIONS: Record<string, ScopeExplanation> = {
     label: "Administer vaults on this host (create, configure, delete).",
     level: "admin",
   },
+  // Account scopes (Parachute App campaign, Phase 2 — the `/account/*` door
+  // contract). `account:<id>:admin` authorizes every account mutation
+  // (create/delete/import vaults, mint per-vault tokens, set caps); `:read`
+  // authorizes the read side (list vaults, read caps/usage). On a self-host
+  // hub `<id>` is the sentinel `self` (account ≡ box). These are minted ONLY
+  // by the cookie→bearer `POST /account/token` exchange, NEVER via the public
+  // OAuth flow — they're in NON_REQUESTABLE_SCOPES below, like the host scopes.
+  // Listed here (a) so `NON_REQUESTABLE_SCOPES ⊆ FIRST_PARTY_SCOPES` holds and
+  // (b) so scope-guard's `admin ⊇ read` inheritance recognizes the grammar
+  // (`account:self:admin` satisfies `account:self:read`).
+  "account:self:admin": {
+    label:
+      "Manage your Parachute account — create, delete, and configure your vaults, and mint access tokens for them.",
+    level: "admin",
+  },
+  "account:self:read": {
+    label: "View your Parachute account — list your vaults and read their settings and usage.",
+    level: "read",
+  },
 };
 
+/** Account scope strings (Parachute App campaign, Phase 2). Exported so the
+ * `POST /account/token` mint and the `/account/*` route gates reference the
+ * canonical constants rather than re-literaling the strings. `self` is the
+ * self-host account sentinel (account ≡ box). */
+export const ACCOUNT_SELF_ADMIN_SCOPE = "account:self:admin";
+export const ACCOUNT_SELF_READ_SCOPE = "account:self:read";
+
 /**
  * Sorted list of every first-party scope the hub recognizes. Used as the
  * baseline for `scopes_supported` in the OAuth-AS metadata; module-declared
@@ -170,6 +193,13 @@ export const NON_REQUESTABLE_SCOPES: ReadonlySet<string> = new Set([
   // Service-admin scopes: operator-only, never requestable via /oauth/authorize.
   "hub:admin",
   "scribe:admin",
+  // Account scopes (Parachute App campaign, Phase 2): cookie-minted only via
+  // `POST /account/token`, NEVER OAuth-requestable. A third-party app pointed
+  // at the hub AS must not be able to consent its way to account authority
+  // (create/delete vaults, mint per-vault tokens) — the account credential is
+  // exclusively the same-origin app's cookie→bearer exchange.
+  ACCOUNT_SELF_ADMIN_SCOPE,
+  ACCOUNT_SELF_READ_SCOPE,
 ]);
 
 /**

package/src/service-spec.ts

@@ -8,10 +8,16 @@ import type { ServiceEntry } from "./services-manifest.ts";
  *
  *   1939  parachute-hub      internal static + proxy, CLI-managed
  *   1940  parachute-vault    committed core
- *   1941  parachute-agent    exploration (renamed from parachute-channel)
+ *   1941  unassigned
  *   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
@@ -64,15 +70,27 @@ export interface PortReservation {
 export const PORT_RESERVATIONS: readonly PortReservation[] = [
   { port: 1939, name: "parachute-hub", status: "assigned" },
   { port: 1940, name: "parachute-vault", status: "assigned" },
-  { port: 1941, name: "parachute-agent", status: "assigned" },
+  { port: 1941, name: "unassigned", status: "reserved" },
   { 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,59 @@ 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 serves the app directly too, unless you've",
+      "already customized the root (`parachute hub set-root-mode` / `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 +401,7 @@ const NOTES_FALLBACK: FirstPartyFallback = {
  */
 export const FIRST_PARTY_FALLBACKS: Record<string, FirstPartyFallback> = {
   notes: NOTES_FALLBACK,
+  app: APP_FALLBACK,
 };
 
 /**
@@ -438,8 +511,8 @@ export const KNOWN_MODULES: Record<string, KnownModule> = {
     },
   },
   // NOTE (2026-07-01): `runner` was REMOVED from this registry (decision:
-  // Aaron 2026-07-01 — the module set of record is vault / hub / agent /
-  // scribe / surface). Runner is no longer offered, installable, or
+  // Aaron 2026-07-01 — the module set of record is vault / hub / scribe /
+  // surface). Runner is no longer offered, installable, or
   // lifecycle-addressable by short name from the hub's bootstrap registries.
   // Existing installs stay GRACEFUL: a legacy `parachute-runner` services.json
   // row is handled exactly like any unknown/third-party row — `parachute
@@ -448,29 +521,7 @@ export const KNOWN_MODULES: Record<string, KnownModule> = {
   // stamped and logs-and-skips otherwise. Deliberately NOT added to
   // RETIRED_MODULES: that registry GC-drops rows on load, which would break
   // routing for operators still running the runner daemon.
-  agent: {
-    short: "agent",
-    package: "@openparachute/agent",
-    manifestName: "parachute-agent",
-    canonicalPort: 1941,
-    displayName: "Agent",
-    // Mirrors agent's own module.json (the canonical fields below do too —
-    // keep in sync if agent's declaration changes). Renamed from `channel`
-    // 2026-06-17 (parachute-channel → parachute-agent); the module is the
-    // same webhook-fan-out + MCP bridge daemon, on the same port 1941.
-    tagline: "Chat with your Claude Code sessions — a channel per session.",
-    canonicalPaths: ["/agent"],
-    canonicalHealth: "/health",
-    canonicalStripPrefix: true,
-    extras: {
-      // Backward-compat startCmd for rows without installDir — same rationale
-      // as scribe / vault. The bare binary IS the daemon (agent's
-      // package.json bin maps `parachute-agent` → src/daemon.ts).
-      startCmd: () => ["parachute-agent"],
-      // Agent gates its endpoints behind hub-issued JWTs (agent:* scopes).
-      hasAuth: true,
-    },
-  },
+
   surface: {
     short: "surface",
     package: "@openparachute/surface",
@@ -520,39 +571,43 @@ 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`
-  // names were retired here on 2026-05-20 (the Claude-in-containers module).
-  // They are NOW RE-ASSIGNED to the renamed channel module (parachute-channel
-  // → parachute-agent). Keeping these as RETIRED entries would make
-  // `dropRetiredModuleRows` drop the NEW agent module's services.json row on
-  // load — breaking the live module. The names are no longer retired; they
-  // belong to the active agent module. The retired containers code now lives
-  // under `parachute-agent-legacy` (GitHub) and is not installable, so there
-  // is no live `agent` daemon to GC. (The historical `claw → agent`
-  // migration in services-manifest.ts still rewrites stale paraclaw rows to
-  // `name: "agent"` — they now resolve to the LIVE agent module's mount,
-  // 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`)",
-  },
+  agent: { retiredAt: "2026-07-15", replacement: "Vault and Surface" },
+  channel: { retiredAt: "2026-07-15", replacement: "Vault and Surface" },
+  "parachute-agent": { retiredAt: "2026-07-15", replacement: "Vault and Surface" },
+  "parachute-channel": { retiredAt: "2026-07-15", replacement: "Vault and Surface" },
+  // Agent was removed from Hub on 2026-07-15. All historical service-row
+  // identities are retired so normal manifest reads stop routing or supervising
+  // the deprecated daemon. Generic AI-agent authorization grants/tokens are a
+  // separate Hub capability and remain supported.
+  // 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,9 +687,9 @@ 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).
- *   - `experimental` — agent (legit preview; still OFFERED on a fresh install)
- *     + any unlisted third-party short.
+ *   - `core` — vault / scribe / hub / surface / app (the product surface;
+ *     `app` joined 2026-07-11, hub-parity P5 — the super-surface front door).
+ *   - `experimental` — any unlisted third-party short.
  *   - `deprecated` — notes (notes-daemon deprecated 2026-05-22; notes-ui moved
  *     into parachute-surface). Still RESOLVABLE (discoverableShorts unchanged)
  *     and SHOWN-IF-INSTALLED so an existing operator can manage/uninstall, but
@@ -650,7 +705,8 @@ const FOCUS_DEFAULTS: Record<string, ModuleFocus> = {
   scribe: "core",
   hub: "core",
   surface: "core",
-  agent: "experimental",
+  app: "core",
+
   notes: "deprecated",
 };
 
@@ -738,7 +794,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.
  *
@@ -847,11 +903,10 @@ export async function getSpecFromInstallDir(
  */
 const LEGACY_MANIFEST_ALIASES: Record<string, string> = {
   "parachute-lens": "notes",
-  "parachute-channel": "agent",
 };
 
 /** 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 {