@ossclip/scenes 0.1.7 → 0.1.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ossclip/scenes",
-  "version": "0.1.7",
+  "version": "0.1.10",
   "description": "ossclip's scene library and stage geometry — React components shared by preview and render",
   "type": "module",
   "license": "MIT",
@@ -19,7 +19,7 @@
   ],
   "dependencies": {
     "zod": "^3.25.0",
-    "@ossclip/core": "0.1.7"
+    "@ossclip/core": "0.1.10"
   },
   "peerDependencies": {
     "react": ">=18",

package/src/SceneLayer.tsx

@@ -170,6 +170,18 @@ export const SceneLayer: React.FC<{ cues: SceneCue[]; theme: Theme }> = ({ cues,
         // Fill the slot instead of floating at natural size in it (§23). The
         // component lays out at contentW/scale and is then scaled up, so its
         // rendered width is exactly the content width while its type grows.
+        //
+        // Accepted v1 wrinkle (PLAN Task 2): `fitScale` sizes off `cue.props`
+        // alone — it has no visibility into which elements the user hid via
+        // `cue.elements[id].hidden`, so a scene with a hidden bubble/line/
+        // node still gets the SAME conservative scale as if everything were
+        // showing. The remaining siblings still close the gap correctly
+        // (`editStyle`'s `display:none` just removes a box from the flex/
+        // stack), they just aren't scaled up to use the space the hidden one
+        // freed. Teaching the fit models the edit layer would mean every
+        // metrics function taking `elements` alongside `props` for a v1
+        // feature whose actual ask was "let me delete one bubble," not
+        // "re-fit the layout around the gap" — deferred, not forgotten.
         const scale = fitScale(cue.component, cue.props, { widthPx: contentW, heightPx: contentH });
         return (
           <Sequence key={cue.id} from={from} durationInFrames={durationInFrames}>

package/src/editable.ts

@@ -1,8 +1,10 @@
 import type React from "react";
 
-/** Per-element nudges from the user's edit layer, keyed by `data-edit-id`. */
+/** Per-element nudges from the user's edit layer, keyed by `data-edit-id`.
+ * `hidden` (PLAN Task 2) is a soft-delete flag, not a nudge — see `editStyle`
+ * below for where it takes effect. */
 export type ElementEdits =
-  | Record<string, { dx?: number; dy?: number; scale?: number }>
+  | Record<string, { dx?: number; dy?: number; scale?: number; hidden?: boolean }>
   | undefined;
 
 /**
@@ -45,6 +47,17 @@ export function compensateEdits(edits: ElementEdits, renderScale: number): Eleme
 export function editStyle(edits: ElementEdits, id: string): React.CSSProperties {
   const e = edits?.[id];
   if (!e) return {};
+  // Soft-delete (PLAN Task 2), suppressed HERE — the one chokepoint every
+  // component's leaf renders its edit style through, so no per-component
+  // change is needed and the remaining siblings close the gap on their own
+  // (a flex/stack layout just has one fewer box; a scale-to-fill layout's
+  // sibling type still fills whatever it filled before — see SceneLayer.tsx
+  // for the one place `fitScale` does NOT yet account for this). Also
+  // suppresses ChatMock's synthetic CTA bubble (`message-0` in keyword
+  // mode, `chatBubbles` in fit.ts) if the user chooses to hide it — that's
+  // allowed, not special-cased away: it's their call what the CTA scene
+  // shows.
+  if (e.hidden) return { display: "none" };
   const parts = [`translate(${e.dx ?? 0}px, ${e.dy ?? 0}px)`];
   if (e.scale !== undefined && e.scale !== 1) parts.push(`scale(${e.scale})`);
   return { transform: parts.join(" ") };

package/src/fit.ts

@@ -527,6 +527,10 @@ export function flowMetrics(
  * chips end up visibly bigger than six, which is the point of §23. Solved by
  * bisection because the height model depends on the content width, which
  * depends on the scale.
+ *
+ * Sizes off `props` alone — blind to which elements the edit layer hid
+ * (PLAN Task 2's accepted v1 wrinkle; see the call site's own comment in
+ * `SceneLayer.tsx` for the full reasoning).
  */
 export function fitScale(
   component: SceneComponentId,