@unoverse-platform/studio 0.1.58 → 0.1.59

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unoverse-platform/studio",
-  "version": "0.1.58",
+  "version": "0.1.59",
   "type": "module",
   "description": "Unoverse Studio: the local authoring app. Reads your own rx/ folder, no backend.",
   "scripts": {

package/src/host.ts

@@ -22,21 +22,19 @@ export const UNOVERSE_BASE = "";
 export const hasAuth = false;
 
 /**
- * The universe Studio is signed into (the header connection), or null when offline.
- * THE LIVE PREVIEW'S SERVER. One source of truth: the same selection App.tsx keeps
- * (`studio:universe` is its usePersistentState pointer into the saved universe list),
- * so it is impossible to be signed into one universe and silently previewing against
- * another. The shared screens fall back to the local dev platform only when no
- * universe is connected.
+ * THE LIVE PREVIEW'S SERVER: always null here, meaning the local dev platform.
+ *
+ * This used to read the universe picked in the header (`studio:universe`), written by
+ * the connect button. That chrome is gone (LOCAL_STUDIO.md §Publish is terminal-only) —
+ * and reading the stale localStorage value after removing the UI left Live mode aimed
+ * at a universe nobody could change or clear, failing with that universe's errors
+ * (seen live: "Unknown Unoverse template" from a universe the app was never published
+ * to). So local Studio's Live preview targets the local dev platform, full stop.
+ * Pointing Live at the workspace's own universe (unoverse.yaml) is future work and
+ * will come from the workspace, not from a browser store.
  */
 export function liveUniverseUrl(): string | null {
-  try {
-    const raw = localStorage.getItem("studio:universe");
-    const url = raw === null ? null : (JSON.parse(raw) as string | null);
-    return url || null;
-  } catch {
-    return null;
-  }
+  return null;
 }
 
 /**