@unoverse-platform/studio 0.1.7 → 0.1.8

package/package.json

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

package/screens/ComponentsView.tsx

@@ -9,7 +9,7 @@ import { UnoverseComponent, type ResolvedTheme } from "@unoverse/sdk";
 import { client, authedFetch, hasSourceAccess } from "studio-host";
 import { SourceView } from "./SourceView";
 import { stateActivation } from "./states";
-import { usePersistentState } from "studio-host";
+import { usePersistentState, useRegistryToggles, ToggleSwitch } from "studio-host";
 
 const CHAT_ID = "demo";
 
@@ -58,6 +58,7 @@ const VIEWPORTS: { id: string; label: string; w: number | null }[] = [
 export function ComponentsView({ theme, org = "all" }: { theme: ResolvedTheme; org?: string }) {
   const store = useMemo(() => new ComponentStore(), []);
   const [components, setComponents] = useState<ComponentDef[]>([]);
+  const available = useRegistryToggles("component");
   const [selected, setSelected] = usePersistentState<string | null>("wb:components:selected", null);
   const [values, setValues] = useState<Record<string, unknown>>({}); // typed values → store/render
   const [text, setText] = useState<Record<string, string>>({}); // raw editor strings (decoupled from the typed value)
@@ -500,11 +501,22 @@ export function ComponentsView({ theme, org = "all" }: { theme: ResolvedTheme; o
             {/* Spatial toggle — ONLY for spatial-capable components (manifest.json present).
                 Same two-level model as templates/skills: this is Level 1 (workbench
                 eligibility); the Content Engine's per-workflow toggle is Level 2. */}
-            {/* NO SPATIAL TOGGLE HERE. It wrote `plugin_state.enabled`, which the spatial catalogue
-                deliberately IGNORES (`routeRegistrySpatial`): published IS available. What is actually
-                on a map is the PER-WORKFLOW row, switched in Canvas's Content Library — spatial is
-                unique to each workflow, and this screen has no workflow. A control that reads as the
-                answer to "is this in spatial?" while writing where nothing reads is worse than none. */}
+            {/* AVAILABLE — the MASTER switch, and the first of two.
+                  Studio    available: is this offered to workflows at all? (here)
+                  A canvas  installed: is it on THIS workflow's map? (Content Library)
+                Studio decides the menu; each canvas orders from it. Both exist because
+                spatial is per workflow and an org can have hundreds of them carrying
+                different components.
+                It is NOT called "Spatial": two controls both called that, one of which the
+                catalogue ignored, is what made this switch look authoritative and do
+                nothing. This one is honoured — off means no canvas can install it. */}
+            {current?.spatial && (
+              <ToggleSwitch
+                on={available.isEnabled(current.name)}
+                onClick={() => available.toggle(current.name)}
+                label="Available"
+              />
+            )}
             {current?.spatial && (
               <button
                 onClick={() => setMetaOpen((o) => !o)}