@cueframe/kernel 0.0.1 → 0.1.1

package/dist/_members/core/render/types.d.ts

@@ -1,6 +1,7 @@
 import type { Scene, GlobalEffects, EffectTarget } from '../../composition/ops/index.js';
 import type { ResolvedBrandKit } from '../../composition/projection/index.js';
 import type { Reframe } from '../../composition/reframe/index.js';
+import type { TrajectoryData } from '../../composition/reframe/trajectory.js';
 import type { CaptionWord as WireCaptionWord, CaptionStyle as WireCaptionStyle } from '../../composition/validators/index.js';
 export type OverlayTemplate = 'custom' | 'gif' | 'image' | 'lottie' | (string & {});
 export interface OverlayParams {
@@ -143,6 +144,25 @@ export interface CompositionClip {
      * consumer.
      */
     cropTrajectoryUrl?: string;
+    /**
+     * The same per-frame crop trajectory, IN MEMORY rather than behind a URL.
+     *
+     * The editor derives a clip's trajectory client-side — `deriveTrajectory` is
+     * pure, and the cached subject track it reads arrives presigned on the media
+     * row — so there is no object to fetch and nothing to presign. Handing the
+     * renderer a URL would mean minting a blob one per keystroke, into a
+     * module-level per-URL cache that never evicts.
+     *
+     * `CropFromTrajectory` has taken an in-memory trajectory since the still path
+     * needed one (`traj = trajectory ?? fetched`), so this is a channel to a prop
+     * that already exists, not a second rendering path. The server render keeps
+     * using `cropTrajectoryUrl`: its trajectory is written to R2 by an action, and
+     * inlining it would put a per-frame series in the render snapshot.
+     *
+     * Exactly one of the two is set. When both are, this wins — it is the fresher
+     * of the two by construction, since it was derived from the edit in hand.
+     */
+    cropTrajectory?: TrajectoryData;
     /**
      * Frame-packed CO-VIEW source for the captions-behind-speaker effect: ONE
      * opaque H.264 (BiRefNet-portrait) with the scene (top half) and the matte
@@ -271,6 +291,17 @@ export interface RenderInput {
     audioTracks?: CompositionAudioTrack[];
     effects?: CompositionEffect[];
     captionSegments?: CaptionWord[][];
+    /**
+     * The caption layer renders UNDER the speaker's silhouette
+     * (`composition.captions.zPlane === 'behind-subject'`). One choice for the
+     * whole layer, because it decides whether the SOURCE needs a matte — the
+     * $0.12/source-minute rung, not the $0.004 one, and a caption layer usually
+     * spans the whole video.
+     *
+     * Requested, not guaranteed: the renderer degrades to the front mount when no
+     * co-view is on the timeline (nothing to hide behind).
+     */
+    captionsBehind?: boolean;
     captionStyle?: Partial<CaptionStyle>;
     width: number;
     height: number;

package/dist/_members/mcp/curation.d.ts

@@ -52,7 +52,7 @@ export interface CuratedTool {
      * SSOT; this npm-shipped package can go stale, so it only controls listing):
      * 'expert' hides the tool from the public listing unless the expert layer is
      * on. Default 'stable'. Drift-gated against the server map in
-     * the backendapi/capabilities.drift.test.ts.
+     * the backend's capabilities drift test.
      */
     maturity?: 'stable' | 'expert';
     /**

package/dist/_members/plane/conformance.d.ts

@@ -2,7 +2,7 @@
  * THE LANE CONFORMANCE TABLE — one set of facts, executed by both lanes.
  *
  * WHY THIS FILE EXISTS. `preview_frame` is served twice: by the desktop plane
- * (`cueframe/src/plane/handlers.ts`, drawing through the webview) and by the
+ * (`apps/studio/src/plane/handlers.ts`, drawing through the webview) and by the
  * cloud route (`the `/v1/evidence` routes`, rendering through
  * Modal). Nothing made them agree. The only mechanism was review discipline —
  * comments like *"ALLOWED_KEYS TRACKS THAT SCHEMA … Add server-side keys here in

package/dist/_members/render-harness/localRender.d.ts

@@ -157,7 +157,7 @@ export interface RenderComponentAlphaOpts {
  * Bake an owned `.cueframe` component to an ALPHA (transparent) video via the
  * LOCAL Remotion bundle — the "trusted pixels" a cloud render later composites
  * (Task 2.6b) WITHOUT running the component's code in the shared render. Mirrors
- * the proven cueframe/scripts/spike-alpha renderMedia settings. Requires an
+ * the proven apps/studio/scripts/spike-alpha renderMedia settings. Requires an
  * installed Chrome via REMOTION_CHROME_EXECUTABLE. Output → the `.cueframe/` cache
  * (an R2-upload step for the cloud path is the 2.6b follow-up).
  */