@unoverse-platform/studio 0.1.56 → 0.1.58

package/src/ConnectUniverse.tsx

@@ -1,232 +0,0 @@
-/**
- * Connect to a universe: the "when you are ready" step.
- *
- * Everything before this point is offline. A developer builds components, templates and
- * nodes against their own folders with no account and no network. This screen is where
- * they choose somewhere to publish, and it is deliberately the only place Studio asks
- * for anything.
- *
- * The flow is: type an address, Studio asks that universe who authenticates it, then
- * signs in against whatever the answer was. Studio names no provider.
- *
- * See docs/architecture/LOCAL_STUDIO.md.
- */
-import { useState } from "react";
-import { useAuth } from "react-oidc-context";
-import {
-  normaliseUrl,
-  defaultLabel,
-  discover,
-  loginReady,
-  canPublish,
-  loadUniverses,
-  saveUniverse,
-  removeUniverse,
-  type Universe,
-} from "./universes";
-
-/** Decode a JWT payload without verifying it. Display only: the universe verifies. */
-function claimsOf(accessToken: string | undefined): Record<string, unknown> | null {
-  if (!accessToken) return null;
-  try {
-    return JSON.parse(atob(accessToken.split(".")[1] ?? ""));
-  } catch {
-    return null;
-  }
-}
-
-/**
- * Sign out of the connected universe.
- *
- * `removeUser` clears the local session only: it does not sign you out of the identity
- * provider, so signing in again may return the same account without prompting. That is the
- * provider's decision, not ours, and a full federated logout needs a logout URL configured
- * per universe. Local is the honest scope for a tool.
- */
-function SignOut({ auth }: { auth: ReturnType<typeof useAuth> }) {
-  return (
-    <button
-      onClick={() => auth?.removeUser()}
-      className="text-xs text-gray-500 underline-offset-2 hover:text-gray-300 hover:underline"
-    >
-      Sign out
-    </button>
-  );
-}
-
-export function ConnectUniverse({
-  active,
-  onSelect,
-  onClose,
-}: {
-  active: Universe | null;
-  onSelect: (universe: Universe | null) => void;
-  onClose: () => void;
-}) {
-  const [universes, setUniverses] = useState<Universe[]>(() => loadUniverses());
-  const [address, setAddress] = useState("");
-  const [busy, setBusy] = useState(false);
-  const [error, setError] = useState<string | null>(null);
-
-  // Undefined when no provider is mounted, which is the normal offline case.
-  const auth = useAuth();
-  const claims = claimsOf(auth?.user?.access_token);
-  const signedIn = Boolean(auth?.isAuthenticated);
-
-  async function connect() {
-    setError(null);
-    setBusy(true);
-    try {
-      const url = normaliseUrl(address);
-      const config = await discover(url);
-      const universe: Universe = {
-        url,
-        label: defaultLabel(url),
-        config,
-        connectedAt: new Date().toISOString(),
-      };
-      setUniverses(saveUniverse(universe));
-      setAddress("");
-      onSelect(universe);
-    } catch (e: any) {
-      // These messages are written to be actionable (universes.ts), so show them as-is.
-      setError(e?.message ?? String(e));
-    } finally {
-      setBusy(false);
-    }
-  }
-
-  function forget(url: string) {
-    setUniverses(removeUniverse(url));
-    if (active?.url === url) onSelect(null);
-  }
-
-  const readiness = active ? loginReady(active.config) : null;
-  const allowed = active && claims ? canPublish(claims, active.config) : false;
-  /** The signed-in address. Namespace-aware: Auth0 emits `email` ONLY namespaced on an
-   *  access token, so a plain `claims.email` is undefined and the id leaks into the UI. */
-  const email = (() => {
-    const direct = (claims as any)?.email;
-    if (typeof direct === "string") return direct;
-    const key = Object.keys(claims ?? {}).find((k) => k.endsWith("/email") || k.endsWith("/claims/email"));
-    const value = key ? (claims as any)[key] : undefined;
-    return typeof value === "string" ? value : null;
-  })();
-
-  /** What the token says, for the message below. Trimmed, as the checks are. */
-  const permissionList: string[] = (() => {
-    const direct = (claims as any)?.permissions;
-    const nsKey = Object.keys(claims ?? {}).find((k) => k.endsWith("/permissions"));
-    const list = Array.isArray(direct) ? direct : ((claims as any)?.[nsKey ?? ""] ?? []);
-    return Array.isArray(list) ? list.map((p) => String(p).trim()) : [];
-  })();
-
-  return (
-    <div className="fixed inset-0 z-50 flex items-start justify-center bg-black/60 p-8" onClick={onClose}>
-      <div
-        className="w-full max-w-lg rounded-xl border border-gray-800 bg-[#151b22] p-6 text-gray-200 shadow-2xl"
-        onClick={(e) => e.stopPropagation()}
-      >
-        <h2 className="text-base font-semibold text-gray-100">Publish to a universe</h2>
-        <p className="mt-1 text-xs text-gray-400">
-          Studio works offline. Connect a universe when you are ready to publish.
-        </p>
-
-        {/* Add one */}
-        <div className="mt-5 flex gap-2">
-          <input
-            value={address}
-            onChange={(e) => setAddress(e.target.value)}
-            onKeyDown={(e) => e.key === "Enter" && !busy && connect()}
-            placeholder="your-universe.com"
-            className="flex-1 rounded border border-gray-700 bg-[#1b2129] px-3 py-2 text-sm text-gray-200 placeholder:text-gray-600 focus:border-gray-500 focus:outline-none"
-          />
-          <button
-            onClick={connect}
-            disabled={busy || !address.trim()}
-            className="rounded bg-gray-100 px-4 py-2 text-sm font-medium text-gray-900 hover:bg-white disabled:opacity-30"
-          >
-            {busy ? "Checking..." : "Connect"}
-          </button>
-        </div>
-        {error && <p className="mt-2 text-xs text-red-400">{error}</p>}
-
-        {/* The ones this developer has connected to. There is no central directory of
-            universes and there cannot be: each is independent with its own provider. */}
-        {universes.length > 0 && (
-          <ul className="mt-5 space-y-2">
-            {universes.map((u) => (
-              <li
-                key={u.url}
-                className={`flex items-center justify-between rounded-md border px-3 py-2 text-sm ${
-                  active?.url === u.url
-                    ? "border-gray-500 bg-white/5"
-                    : "border-gray-800 hover:border-gray-700"
-                }`}
-              >
-                <button className="text-left" onClick={() => onSelect(u)}>
-                  <span className="font-medium">{u.label}</span>
-                  <span className="ml-2 text-gray-500">{u.url}</span>
-                </button>
-                <button className="text-xs text-gray-500 hover:text-red-400" onClick={() => forget(u.url)}>
-                  Forget
-                </button>
-              </li>
-            ))}
-          </ul>
-        )}
-
-        {/* Sign-in state for the selected universe. Every branch says what to do next. */}
-        {active && (
-          <div className="mt-5 border-t border-gray-800 pt-4 text-sm">
-            {readiness && !readiness.ok ? (
-              // A universe with auth off, or one misconfigured. Publishing is not
-              // possible, and saying so beats a redirect to a provider that is not there.
-              <p className="text-xs text-amber-400">{readiness.reason}</p>
-            ) : !signedIn ? (
-              <button
-                onClick={() => auth?.signinRedirect()}
-                className="rounded bg-gray-100 px-4 py-2 text-sm font-medium text-gray-900 hover:bg-white"
-              >
-                Sign in to {active.label}
-              </button>
-            ) : allowed ? (
-              <div className="flex items-center justify-between gap-3">
-                {/* The fact, not the identifier. A raw `auth0|692be24b…` is noise: it is not
-                    how anyone thinks of themselves, and it appeared only because `email` is a
-                    NAMESPACED claim that a plain read misses (AUTH_TOKEN_FLOW.md names this
-                    exact footgun). Read properly it is an address; absent, the sentence is
-                    better without it. */}
-                <p className="text-sm font-medium text-emerald-400">
-                  Ready to publish{email ? <span className="font-normal text-gray-400"> as {email}</span> : null}
-                </p>
-                <SignOut auth={auth} />
-              </div>
-            ) : (
-              // Signed in but without the permission. Said HERE, not at the first push,
-              // so nobody builds for an hour and then finds out.
-              <div>
-                <p className="text-xs text-amber-400">
-                  Signed in, but your account does not have{" "}
-                  <code>{active.config.publishPermission}</code> on this universe. Ask whoever
-                  administers it to grant it.
-                </p>
-                {/* WHAT THE TOKEN ACTUALLY CARRIES. Kept, in a reduced form, because "you do not
-                    have this permission" is unhelpful when the identity provider visibly
-                    says you do. Printing the claim turns a guess into a fact: it is how a
-                    leading space in an Auth0 permission (" marketplace:publish") was found,
-                    after the screens, the token and the label had all agreed it was correct. */}
-                <p className="mt-2 text-xs text-gray-500">
-                  Your token carries: <code>{permissionList.join(", ") || "no permissions claim"}</code>
-                </p>
-                <div className="mt-2">
-                  <SignOut auth={auth} />
-                </div>
-              </div>
-            )}
-          </div>
-        )}
-      </div>
-    </div>
-  );
-}

package/src/PublishDialog.tsx

@@ -1,309 +0,0 @@
-/**
- * Publish a project to the connected universe.
- *
- * PLAN, THEN SEND. Publishing writes rows that every workflow in a universe can use, so
- * "what am I about to do" is answered before anything moves. Blind publishing is how a
- * project half-lands and nobody can tell by looking.
- *
- * The plan runs the moment this opens, unasked: it reads disk and dry-runs against the
- * universe, writing nothing. Only the second press sends. An empty dialog with a button
- * marked "check" made the developer ask for the answer they opened the dialog to get.
- *
- * The work happens in Studio's local host (`local/plugin.ts`), not here: it reads the
- * developer's disk, which a browser cannot. This screen collects a decision and shows a
- * result. It calls the same functions as `unoverse publish assets`, so the two cannot
- * disagree about what a publish is.
- *
- * See docs/architecture/DECLARATIVE_NODES.md §9.
- */
-import { useEffect, useRef, useState } from "react";
-import { useAuth } from "react-oidc-context";
-import { canPublish, type Universe } from "./universes";
-
-interface Item {
-  kind: string;
-  name: string;
-  why?: string;
-  mode?: string;
-}
-interface Plan {
-  create: Item[];
-  update: Item[];
-  unchanged: Item[];
-  refused: Item[];
-}
-interface Problem {
-  level: string;
-  file: string;
-  line?: number;
-  msg: string;
-}
-
-/** Decode a JWT payload without verifying it. Display only: the universe verifies. */
-function claimsOf(token: string | undefined): Record<string, unknown> | null {
-  if (!token) return null;
-  try {
-    return JSON.parse(atob(token.split(".")[1] ?? ""));
-  } catch {
-    return null;
-  }
-}
-
-export function PublishDialog({
-  project,
-  universe,
-  onClose,
-}: {
-  project: string;
-  universe: Universe;
-  onClose: () => void;
-}) {
-  const auth = useAuth();
-  const token = auth?.user?.access_token;
-
-  const [plan, setPlan] = useState<Plan | null>(null);
-  const [problems, setProblems] = useState<Problem[]>([]);
-  const [blocked, setBlocked] = useState<Problem[] | null>(null);
-  const [sent, setSent] = useState<{ sent: Item[]; failed: Item[] } | null>(null);
-  const [busy, setBusy] = useState(false);
-  const [error, setError] = useState<string | null>(null);
-
-  const allowed = canPublish(claimsOf(token), universe.config);
-
-  async function call(step: "plan" | "send") {
-    setError(null);
-    setBusy(true);
-    try {
-      const res = await fetch(`/publish/${step}`, {
-        method: "POST",
-        headers: { "content-type": "application/json" },
-        body: JSON.stringify({ project, universe: universe.url, token }),
-      });
-      const body = await res.json();
-      if (body.error) throw new Error(body.error);
-      // Errors STOP the publish. Reported as findings rather than a failure, because the
-      // developer's next action is to fix a file, not to retry.
-      if (body.blocked) {
-        setBlocked(body.errors);
-        return;
-      }
-      setProblems(body.problems ?? []);
-      setPlan(body.plan);
-      if (step === "send") setSent({ sent: body.sent ?? [], failed: body.failed ?? [] });
-    } catch (e: any) {
-      setError(e?.message ?? String(e));
-    } finally {
-      setBusy(false);
-    }
-  }
-
-  /**
-   * PLAN ON OPEN. The dialog's whole job is to answer "what am I about to publish", so it
-   * answers it without being asked. Planning reads disk and dry-runs against the universe;
-   * it writes nothing, which is what makes running it unprompted safe.
-   *
-   * The guard is a ref rather than the usual empty dep array: `call` closes over state that
-   * changes, and a second plan on a re-render would be a wasted round trip and a flicker.
-   */
-  const planned = useRef(false);
-  useEffect(() => {
-    if (planned.current || !allowed || !token) return;
-    planned.current = true;
-    call("plan");
-  }, [allowed, token]);
-
-  const toSend = (plan?.create.length ?? 0) + (plan?.update.length ?? 0);
-  const warnings = problems.filter((p) => p.level === "warn").length;
-
-  /**
-   * ONE ROW PER ITEM. A comma-joined list per status cannot be scanned: the question a
-   * developer opens this with is "which of MY things is about to move", and that is a
-   * property of the item, not of a group heading. So every item gets a line carrying its
-   * own status, and the statuses sort so the ones that will move sit at the top.
-   *
-   * The kind is singular here, because a row is one thing. `bpp` is a style set and
-   * `bpp-chat-layout` is an app; without that word they read as five apps, which is how a
-   * developer concludes their components were never collected when they were.
-   */
-  const KIND_LABEL: Record<string, string> = {
-    component: "component",
-    atom: "atom",
-    style: "styles",
-    template: "app",
-    node: "node",
-    skill: "skill",
-    "prompt-block": "prompt block",
-    recipe: "recipe",
-  };
-
-  /**
-   * Contrast is the whole job here. Dark text on a dark panel made a five row list
-   * unreadable, so the name carries full weight, the status carries colour, and only the
-   * kind is allowed to recede.
-   */
-  const STATUS = {
-    create: { label: "new", pill: "bg-emerald-400/15 text-emerald-300 ring-emerald-400/30", order: 0 },
-    update: { label: "changed", pill: "bg-amber-400/15 text-amber-300 ring-amber-400/30", order: 1 },
-    refused: { label: "refused", pill: "bg-red-400/15 text-red-300 ring-red-400/30", order: 2 },
-    unchanged: { label: "unchanged", pill: "bg-gray-500/10 text-gray-400 ring-gray-500/30", order: 3 },
-  } as const;
-  type Status = keyof typeof STATUS;
-
-  /** Every item, flattened, carrying its status. Sorted by what will move, then by name. */
-  const rows: Array<Item & { status: Status }> = plan
-    ? (Object.keys(STATUS) as Status[])
-        .flatMap((status) => plan[status].map((i) => ({ ...i, status })))
-        .sort(
-          (a, b) =>
-            STATUS[a.status].order - STATUS[b.status].order ||
-            a.kind.localeCompare(b.kind) ||
-            a.name.localeCompare(b.name),
-        )
-    : [];
-
-  return (
-    <div className="fixed inset-0 z-50 flex items-start justify-center bg-black/60 p-8" onClick={onClose}>
-      <div
-        className="w-full max-w-xl rounded-xl border border-gray-800 bg-[#151b22] p-6 text-gray-200 shadow-2xl"
-        onClick={(e) => e.stopPropagation()}
-      >
-        <h2 className="text-base font-semibold text-gray-100">
-          Publish <span className="text-gray-400">{project}</span> to {universe.label}
-        </h2>
-
-        {/* Said HERE, before any work, not at the first push. */}
-        {!allowed && (
-          <p className="mt-3 text-xs text-amber-400">
-            Your account does not have <code>{universe.config.publishPermission}</code> on this
-            universe. Ask whoever administers it to grant it.
-          </p>
-        )}
-
-        {error && <p className="mt-3 text-xs text-red-400">{error}</p>}
-
-        {busy && !plan && !blocked && (
-          <p className="mt-4 text-sm text-gray-500">Reading {project}…</p>
-        )}
-
-        {/* Lint errors: nothing was sent, and the file and line are what fixes it. */}
-        {blocked && (
-          <div className="mt-4">
-            <p className="text-xs text-red-400">
-              {blocked.length} error{blocked.length === 1 ? "" : "s"} in {project}. Nothing was sent.
-            </p>
-            <ul className="mt-2 max-h-48 space-y-1 overflow-y-auto text-xs">
-              {blocked.slice(0, 12).map((p, i) => (
-                <li key={i} className="text-gray-400">
-                  <span className="text-gray-500">
-                    {p.file}
-                    {p.line ? `:${p.line}` : ""}
-                  </span>{" "}
-                  {p.msg}
-                </li>
-              ))}
-            </ul>
-          </div>
-        )}
-
-        {plan && !blocked && (
-          <div className="mt-4">
-            {/* The count sentence answers "how much", the list answers "which". Both, always. */}
-            <p className="text-xs font-medium uppercase tracking-wide text-gray-400">
-              {[
-                plan.create.length && `${plan.create.length} new`,
-                plan.update.length && `${plan.update.length} changed`,
-                plan.unchanged.length && `${plan.unchanged.length} unchanged`,
-                plan.refused.length && `${plan.refused.length} refused`,
-              ]
-                .filter(Boolean)
-                .join(", ") || "nothing to publish"}
-            </p>
-
-            <div className="mt-3 max-h-72 divide-y divide-white/5 overflow-y-auto rounded-lg border border-white/10 bg-black/20">
-              {rows.map((r) => (
-                <div key={`${r.kind}/${r.name}`} className="flex items-baseline gap-3 px-3 py-2 hover:bg-white/5">
-                  <span
-                    className={`w-[74px] shrink-0 rounded px-1.5 py-0.5 text-center text-[11px] font-semibold uppercase tracking-wide ring-1 ${STATUS[r.status].pill}`}
-                  >
-                    {STATUS[r.status].label}
-                  </span>
-                  <span
-                    className={`flex-1 truncate text-sm font-medium ${
-                      r.status === "unchanged" ? "text-gray-400" : "text-white"
-                    }`}
-                  >
-                    {r.name}
-                  </span>
-                  {/* The kind sits last and quiet: it labels the name rather than competing with it. */}
-                  <span className="shrink-0 text-xs text-gray-500">{KIND_LABEL[r.kind] ?? r.kind}</span>
-                  {/* The reason belongs ON the refused row: it is the only row it explains. */}
-                  {r.why && <span className="shrink-0 text-xs text-red-300">{r.why}</span>}
-                </div>
-              ))}
-            </div>
-            {/*
-              Said once, in the place where its absence gets noticed. The Components tab
-              lists the design system alongside this project's own, so a plan holding two
-              components where the tab showed eighteen reads as a collection bug.
-            */}
-            <p className="pt-3 text-xs leading-relaxed text-gray-500">
-              Only {project} publishes. Design system components, atoms and styles belong to
-              the universe already.
-            </p>
-            {/*
-              A COUNT ALONE IS USELESS. "2 warnings" tells a developer something is wrong
-              and gives them no way to find it, which is worse than silence: it is a nag
-              with no address. The file, line and message are what fixes it, so they are
-              here, one click away rather than one grep away.
-            */}
-            {warnings > 0 && (
-              <details className="pt-1">
-                <summary className="cursor-pointer text-xs text-amber-300/80 hover:text-amber-300">
-                  {warnings} warning{warnings === 1 ? "" : "s"}, not blocking
-                </summary>
-                <ul className="mt-2 max-h-40 space-y-2 overflow-y-auto text-xs">
-                  {problems
-                    .filter((p) => p.level === "warn")
-                    .map((p, i) => (
-                      <li key={i} className="leading-relaxed">
-                        <span className="text-gray-500">
-                          {p.file?.replace(/^.*\/design\//, "")}
-                          {p.line ? `:${p.line}` : ""}
-                        </span>
-                        <br />
-                        <span className="text-gray-400">{p.msg}</span>
-                      </li>
-                    ))}
-                </ul>
-              </details>
-            )}
-          </div>
-        )}
-
-        {sent && (
-          <p className={`mt-4 text-sm ${sent.failed.length ? "text-red-400" : "text-emerald-400"}`}>
-            {sent.sent.length} published{sent.failed.length ? `, ${sent.failed.length} failed` : ""}
-          </p>
-        )}
-
-        <div className="mt-6 flex items-center gap-2">
-          {plan && !sent && toSend > 0 && (
-            <button
-              onClick={() => call("send")}
-              disabled={busy}
-              className="rounded bg-emerald-500 px-4 py-2 text-sm font-semibold text-emerald-950 hover:bg-emerald-400 disabled:opacity-30"
-            >
-              {busy ? "Publishing…" : `Publish ${toSend} item${toSend === 1 ? "" : "s"}`}
-            </button>
-          )}
-          {plan && !sent && toSend === 0 && (
-            <p className="text-sm text-emerald-400">{project} is already up to date</p>
-          )}
-          <button onClick={onClose} className="rounded px-3 py-2 text-sm text-gray-400 hover:text-gray-200">
-            {sent ? "Done" : "Cancel"}
-          </button>
-        </div>
-      </div>
-    </div>
-  );
-}

package/src/UniverseSession.tsx

@@ -1,121 +0,0 @@
-/**
- * The signed-in session for ONE universe.
- *
- * Local Studio is offline and unauthenticated by default, and that must not change:
- * building a component needs no account, no network and no provider. Authentication
- * appears only when a developer connects to a universe in order to publish.
- *
- * So the provider is mounted CONDITIONALLY. With no universe selected, or one that has
- * auth switched off, children render exactly as they did before this file existed.
- *
- * THE CONFIG COMES FROM THE UNIVERSE, NOT FROM HERE. Canvas reads its issuer and client
- * id from `window.__GRAVITY_CONFIG__` injected into its own page; Studio runs on the
- * developer's machine and cannot, so it asks (`universes.ts` → discover). That is what
- * keeps the tooling provider-agnostic: nothing in Studio names Auth0.
- *
- * See docs/architecture/LOCAL_STUDIO.md.
- */
-import type { ReactNode } from "react";
-import { AuthProvider, AuthContext, type AuthContextProps } from "react-oidc-context";
-import { WebStorageStateStore } from "oidc-client-ts";
-import { loginReady, type Universe } from "./universes";
-
-/**
- * The OIDC settings for one universe. Mirrors Canvas's `oidcConfig`
- * (`apps/canvas/src/App.jsx`) so a token minted for Studio looks the same to the
- * platform as one minted for Canvas, with one difference: every value is read from the
- * universe rather than from this app's build.
- */
-function oidcConfigFor(universe: Universe) {
-  const { issuer, clientId, audience } = universe.config;
-  return {
-    authority: issuer as string,
-    client_id: clientId as string,
-    // Studio's own origin. The universe's identity provider must list this as an allowed
-    // callback, which is the one setup step a customer does on their side.
-    redirect_uri: window.location.origin,
-    scope: "openid profile email",
-    // Auth0 and friends only mint an API access token when an audience is asked for.
-    // Without it the login succeeds and the token is useless against the universe.
-    ...(audience ? { extraQueryParams: { audience } } : {}),
-    // sessionStorage, not localStorage: the token dies with the tab. Studio's standing
-    // rule is that it never persists a secret (local/keys.ts), and a token is a secret.
-    userStore: new WebStorageStateStore({ store: window.sessionStorage }),
-    // Same reason Canvas disables it: a stored user carries the redirect_uri it was
-    // minted with, and a silent renew against a different universe reuses the wrong one.
-    automaticSilentRenew: false,
-    onSigninCallback: () => {
-      window.history.replaceState({}, document.title, window.location.pathname);
-    },
-  };
-}
-
-/**
- * A signed-out session, for when Studio is not connected to a universe.
- *
- * Cast because `AuthContextProps` also carries the oidc-client-ts settings and event
- * surface, none of which exists without a provider and none of which the screens touch.
- * The honest alternative is a fake settings object, which would be a bigger lie than this.
- */
-const OFFLINE_SESSION = {
-  isAuthenticated: false,
-  isLoading: false,
-  user: undefined,
-  error: undefined,
-  activeNavigator: undefined,
-  signinRedirect: offline("signinRedirect"),
-  signinPopup: offline("signinPopup"),
-  signinSilent: offline("signinSilent"),
-  signoutRedirect: offline("signoutRedirect"),
-  signoutPopup: offline("signoutPopup"),
-  signoutSilent: offline("signoutSilent"),
-  removeUser: offline("removeUser"),
-  clearStaleState: offline("clearStaleState"),
-  querySessionStatus: offline("querySessionStatus"),
-  revokeTokens: offline("revokeTokens"),
-  startSilentRenew: () => {},
-  stopSilentRenew: () => {},
-} as unknown as AuthContextProps;
-
-/** Reject loudly: calling this means a caller forgot Studio has no universe connected. */
-function offline(name: string) {
-  return async () => {
-    throw new Error(`${name} needs a universe. Connect one first (Studio is offline).`);
-  };
-}
-
-export function UniverseSession({
-  universe,
-  children,
-}: {
-  universe: Universe | null;
-  children: ReactNode;
-}) {
-  // No universe, or one that cannot be logged into: the offline case, and the normal one.
-  //
-  // The shared screens call `useAuth()` unconditionally and cope with having no session.
-  // But react-oidc-context warns whenever the context VALUE is falsy:
-  //
-  //     const context = React.useContext(AuthContext);
-  //     if (!context) console.warn("AuthProvider context is undefined, ...");
-  //
-  // so mounting the provider with `undefined` warns exactly as loudly as mounting nothing
-  // (both were tried). With TemplatesView re-rendering it is a stream of warnings about a
-  // state that is fully supported.
-  //
-  // So hand it a real value meaning SIGNED OUT. Everything the screens read is present and
-  // false; the sign-in actions throw rather than no-op, because reaching one from here
-  // would mean a code path forgot there is no universe, and silence would hide that.
-  if (!universe || !loginReady(universe.config).ok) {
-    return <AuthContext.Provider value={OFFLINE_SESSION}>{children}</AuthContext.Provider>;
-  }
-
-  // `key` forces a fresh provider when the universe changes. Without it the library keeps
-  // the previous authority and client id, and a developer switching universes would stay
-  // signed in to the old one while appearing to be on the new.
-  return (
-    <AuthProvider key={universe.url} {...oidcConfigFor(universe)}>
-      {children}
-    </AuthProvider>
-  );
-}