@unoverse-platform/studio 0.1.87 → 0.1.88

package/package.json

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

package/vendor/sdk/lib/app.tsx

@@ -331,11 +331,11 @@ export function StreamedUnoverseApp({ client, store, uri, onAction, theme: theme
    */
   const tstate = store.getAppState() as Record<string, unknown>;
   const dismissedRaw = tstate.latchDismissed;
-  const held = def ? resolveLatch(def, store, typeof dismissedRaw === "string" ? dismissedRaw : undefined) : null;
+  const held = def ? resolveLatch(def, store, ladder.view, typeof dismissedRaw === "string" ? dismissedRaw : undefined) : null;
   useEffect(() => {
     if (dismissedRaw === true) {
       // Resolve the bare flag against whoever holds it RIGHT NOW, then re-derive.
-      const current = def ? resolveLatch(def, store) : null;
+      const current = def ? resolveLatch(def, store, ladder.view) : null;
       store.mergeAppState({ latchDismissed: current ? current.key : "" });
       return;
     }
@@ -353,6 +353,7 @@ export function StreamedUnoverseApp({ client, store, uri, onAction, theme: theme
     held?.key,
     held?.latch,
     dismissedRaw,
+    ladder.view,
     def,
     store,
     tstate.latched,

package/vendor/sdk/lib/core/apps.ts

@@ -279,11 +279,17 @@ export function resolveActiveView(
  * holder or null, so two latches are not a bug to prevent but a state that cannot be
  * represented.
  *
- * SAME WALK AS `resolveActiveView`, deliberately: the ladder is the ladder. A latchable
- * slice must be sitting in one of the template's declared states to hold the latch, and
- * the highest-ranked one wins, ties going to the most recent write. So a page retracted to
- * `inline` (superseded by an arrival, released by `cancelBelow`, closed by the guest)
- * silently stops holding it rather than leaving a pill pointing at something off-surface.
+ * THE HOLDER MUST BE THE STATE ON SCREEN, which is why `active` is a required argument
+ * rather than something derived again here. Being ON the ladder is not enough: an app whose
+ * ladder is [page, perfect-day] shows `page` the moment a card arrives wearing that face,
+ * and the composed page — still live, still ranked, just not showing — went on holding the
+ * latch. The guest then reads a pill naming a page that is nowhere on screen and types into
+ * it (observed live 2026-08-31: three search cards took the surface and "Your Perfect Day"
+ * stayed up over them). A pill is a promise about what the words will reach.
+ *
+ * SAME WALK AS `resolveActiveView` otherwise: the highest-ranked wins, ties going to the
+ * most recent write. So a page retracted to `inline` (superseded by an arrival, released by
+ * `cancelBelow`, closed by the guest) silently stops holding it too.
  *
  * Returns the FULL key. `chatId` alone reaches the turn, not the component inside it: a
  * turn carrying two components would hydrate the wrong one.
@@ -291,12 +297,18 @@ export function resolveActiveView(
 export function resolveLatch(
   def: UnoverseDefinition | null | undefined,
   store: ComponentStore,
+  /** The state the app is ACTUALLY showing (`resolveActiveView().view`). Empty = nothing is
+   *  surfaced, so nothing can be addressed. */
+  active: string,
   dismissed?: string,
 ): { key: string; chatId: string; nodeId: string; latch: { title: string; icon?: string }; view: string } | null {
   const order = def?.stateOrder?.length ? def.stateOrder : undefined;
   if (!order) return null; // no ladder, no ranking — abstain rather than guess a holder
   const latches = def?.latches;
   if (!latches || !Object.keys(latches).length) return null; // no state is addressable here
+  // WHAT IS ON SCREEN, first: an addressable state that is not the active one is not being
+  // shown, and a pill over someone else's surface points at nothing the guest can see.
+  if (!active || !latches[active]) return null;
   // `key` is the component key this candidate came from, carried so the return can name the
   // FULL key (line 269) rather than re-deriving it from chatId, which reaches the turn and
   // not the component inside it.
@@ -316,9 +328,11 @@ export function resolveLatch(
       if (!view) continue;
       const rank = order.indexOf(view);
       if (rank < 0) continue; // not on the surface (inline/retracted): holds nothing
-      // THE STATE DECIDES. Same lookup for every instance, so nothing has to be told it is
-      // addressable and nothing has to be untold — the face it currently wears is the whole
-      // question, and a face with no `latch:` is simply not in this map.
+      // THE STATE DECIDES, and it must be the state SHOWING. Same lookup for every instance,
+      // so nothing has to be told it is addressable and nothing has to be untold — the face
+      // it currently wears is the whole question, and a face that is not the active one is
+      // not on screen to be addressed.
+      if (view !== active) continue;
       const latch = latches[view];
       if (!latch) continue;
       const at = store.touchOf(p);