@unoverse-platform/studio 0.1.6 → 0.1.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unoverse-platform/studio",
-  "version": "0.1.6",
+  "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

@@ -31,7 +31,8 @@ interface ComponentDef {
   whenToUse?: string;
   category?: string;
   /** Spatial-CAPABLE: the component folder carries a manifest.json (server-projected).
-   *  Only capable components show the Spatial toggle — a basic component shows nothing. */
+   *  Capability, not activation: a capable component can be put on a workflow's map from
+   *  Canvas's Content Library. It gates the Meta panel here, nothing more. */
   spatial?: boolean;
   props?: Record<string, PropDef>;
   /** The node's input prop keys, derived server-side (= the node's configSchema).
@@ -56,8 +57,8 @@ 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 spatial = useRegistryToggles("component");
   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,7 +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. */}
-            {current?.spatial && <ToggleSwitch on={spatial.isEnabled(current.name)} onClick={() => spatial.toggle(current.name)} label="Spatial" />}
+            {/* 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)}

package/screens/SkillsView.tsx

@@ -11,7 +11,7 @@
  */
 import { useEffect, useState } from "react";
 import { fetchUnoverse } from "studio-host";
-import { usePersistentState, useRegistryToggles, ToggleSwitch } from "studio-host";
+import { usePersistentState } from "studio-host";
 import { IdentityHeader } from "./IdentityHeader";
 
 interface SkillSummary {
@@ -37,7 +37,6 @@ export function SkillsView() {
   const [detail, setDetail] = useState<SkillDetail | null>(null);
   const [loadingDetail, setLoadingDetail] = useState(false);
   const [error, setError] = useState<string | null>(null);
-  const spatial = useRegistryToggles("skill");
 
   // Load the library list once.
   useEffect(() => {
@@ -108,7 +107,6 @@ export function SkillsView() {
                 }`}
               >
                 <div className="flex items-center gap-1.5 text-sm font-medium">
-                  {spatial.isEnabled(s.name) && <span className="h-1.5 w-1.5 rounded-full bg-emerald-400" title="Spatial on" />}
                   {s.name}
                 </div>
                 <div className="truncate text-[11px] text-gray-500">{s.description}</div>
@@ -130,9 +128,8 @@ export function SkillsView() {
               version={detail?.version}
               description={detail?.description}
               whenToUse={detail?.whenToUse}
-              right={<ToggleSwitch on={spatial.isEnabled(selected)} onClick={() => spatial.toggle(selected)} label="Spatial" />}
             />
-            <p className="mb-3 text-[11px] text-gray-500">When Spatial is on, this skill is embedded as-is into the spatial engine on the next train.</p>
+            <p className="mb-3 text-[11px] text-gray-500">Whether this skill is on a map is switched per workflow, in Canvas’s Content Library: spatial is unique to each workflow.</p>
 
             {detail?.triggers && detail.triggers.length > 0 && (
               <div className="mb-5 flex flex-wrap gap-1.5">

package/screens/TemplatesView.tsx

@@ -9,7 +9,7 @@
  */
 import { useCallback, useEffect, useMemo, useState, useSyncExternalStore } from "react";
 import { useAuth } from "react-oidc-context";
-import { usePersistentState, useRegistryToggles, ToggleSwitch } from "studio-host";
+import { usePersistentState } from "studio-host";
 import { ComponentStore } from "@unoverse/sdk";
 import { StreamedUnoverseTemplate, useUnoverseConnection, computeAppWidth, resolveActiveLayout, type ResolvedTheme, type UseVoiceServiceConfig } from "@unoverse/sdk";
 import { NativeAppHost } from "./NativeAppHost";
@@ -166,7 +166,6 @@ export function TemplatesView({
     useCallback((cb) => store.subscribe(cb), [store]),
     useCallback(() => store.getVersion(), [store]),
   );
-  const spatial = useRegistryToggles("template");
   const [seeded, setSeeded] = useState<string[]>([]);
   const [metaOpen, setMetaOpen] = usePersistentState<boolean>("wb:templates:meta", false); // MCP details panel
   const [copiedUri, setCopiedUri] = useState(false);
@@ -636,7 +635,11 @@ export function TemplatesView({
               })}
             </div>
           )}
-          {selected && <ToggleSwitch on={spatial.isEnabled(selected)} onClick={() => spatial.toggle(selected)} label="Spatial" />}
+          {/* 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. */}
           {selected && (
             <button
               onClick={() => setMetaOpen((o) => !o)}