@unoverse-platform/studio 0.1.40 → 0.1.41

package/package.json

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

package/src/App.tsx

@@ -232,7 +232,9 @@ function Shell({
         {!theme ? (
           <div className="p-6 text-xs text-gray-500">Reading your theme…</div>
         ) : view === "apps" ? (
-          <TemplatesView theme={theme} themeName={variant} org={org} />
+          // Standalone Studio authors offline: open apps in MOCK (the defaultLive=true
+          // resting mode is Canvas's, where the universe is right there).
+          <TemplatesView theme={theme} themeName={variant} org={org} defaultLive={false} />
         ) : view === "components" ? (
           <ComponentsView theme={theme} org={org} />
         ) : view === "atoms" ? (

package/vendor/skills/unoverse-prompt-component/SKILL.md

@@ -166,6 +166,23 @@ the first read, never standing debt. This is implemented in
 `server/src/runtime/components/executor/briefService.ts`; a component that fights it burns
 every turn to `maxTurns` and returns an empty text output.
 
+### The agent node's system prompt stays ROLE-ONLY
+
+The service port already delivers everything else when the agent connects: the fill
+protocol (`briefService.ts` `getSchema.instructions` — survey once, batch fills, blanks
+are finished, stop when done — folded into the agent's system prompt by MCPServiceRouter),
+the content rules (each part's compiled brief), and the grounding law (injected into the
+schema description). A workflow agent's system prompt therefore carries ONE line of role
+("You fill the page from this run's documents; the service's instructions and each part's
+schema carry every rule") and nothing more.
+
+Anything longer is a defect with two failure modes, both observed live (2026-08-18,
+deal-page): content rules in the prompt DRIFT from the briefs the moment either is edited,
+and hand-written protocol CONTRADICTS the served protocol (a prompt demanding "one section
+per fill call" while the service instructs "batch into as few calls as possible"). When
+auditing a briefed-component workflow, read the agent node's `systemPrompt` and delete
+every sentence the schema or the service already carries.
+
 ---
 
 ## Checklist
@@ -178,3 +195,5 @@ every turn to `maxTurns` and returns an empty text output.
 5. Linter: 0 errors, and every warning read rather than silenced.
 6. Previewed in Studio, then filled once for real. Studio proves the layout; only a fill
    proves the prompt.
+7. Workflow door only: every agent node filling this component has a ROLE-ONLY system
+   prompt — no sentence the schema or the service instructions already carry.