@elevasis/ui 2.71.0 → 2.73.0

package/dist/features/content/index.d.ts

@@ -18,7 +18,9 @@ declare const OntologyScopeSchema: z.ZodDefault<z.ZodObject<{
         aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
         properties: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
         storage: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-    }, z.core.$loose>>>>;
+        rowSchema: z.ZodOptional<z.ZodString>;
+        stateCatalogId: z.ZodOptional<z.ZodString>;
+    }, z.core.$strict>>>>;
     linkTypes: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
         id: z.ZodString;
         label: z.ZodOptional<z.ZodString>;
@@ -29,7 +31,7 @@ declare const OntologyScopeSchema: z.ZodDefault<z.ZodObject<{
         to: z.ZodString;
         cardinality: z.ZodOptional<z.ZodString>;
         via: z.ZodOptional<z.ZodString>;
-    }, z.core.$loose>>>>;
+    }, z.core.$strict>>>>;
     actionTypes: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
         id: z.ZodString;
         label: z.ZodOptional<z.ZodString>;
@@ -39,7 +41,11 @@ declare const OntologyScopeSchema: z.ZodDefault<z.ZodObject<{
         actsOn: z.ZodOptional<z.ZodDefault<z.ZodArray<z.ZodString>>>;
         input: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
         effects: z.ZodOptional<z.ZodArray<z.ZodRecord<z.ZodString, z.ZodUnknown>>>;
-    }, z.core.$loose>>>>;
+        resourceId: z.ZodOptional<z.ZodString>;
+        invocations: z.ZodOptional<z.ZodArray<z.ZodUnknown>>;
+        lifecycle: z.ZodOptional<z.ZodString>;
+        legacyActionId: z.ZodOptional<z.ZodString>;
+    }, z.core.$strict>>>>;
     catalogTypes: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
         id: z.ZodString;
         label: z.ZodOptional<z.ZodString>;
@@ -49,7 +55,10 @@ declare const OntologyScopeSchema: z.ZodDefault<z.ZodObject<{
         kind: z.ZodOptional<z.ZodString>;
         appliesTo: z.ZodOptional<z.ZodString>;
         entries: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-    }, z.core.$loose>>>>;
+        legacyCatalogKey: z.ZodOptional<z.ZodString>;
+        legacyPipelineKey: z.ZodOptional<z.ZodString>;
+        legacyEntityKey: z.ZodOptional<z.ZodString>;
+    }, z.core.$strict>>>>;
     eventTypes: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
         id: z.ZodString;
         label: z.ZodOptional<z.ZodString>;
@@ -57,7 +66,7 @@ declare const OntologyScopeSchema: z.ZodDefault<z.ZodObject<{
         ownerSystemId: z.ZodOptional<z.ZodString>;
         aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
         payload: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-    }, z.core.$loose>>>>;
+    }, z.core.$strict>>>>;
     interfaceTypes: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
         id: z.ZodString;
         label: z.ZodOptional<z.ZodString>;
@@ -65,7 +74,7 @@ declare const OntologyScopeSchema: z.ZodDefault<z.ZodObject<{
         ownerSystemId: z.ZodOptional<z.ZodString>;
         aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
         properties: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-    }, z.core.$loose>>>>;
+    }, z.core.$strict>>>>;
     valueTypes: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
         id: z.ZodString;
         label: z.ZodOptional<z.ZodString>;
@@ -73,7 +82,7 @@ declare const OntologyScopeSchema: z.ZodDefault<z.ZodObject<{
         ownerSystemId: z.ZodOptional<z.ZodString>;
         aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
         primitive: z.ZodOptional<z.ZodString>;
-    }, z.core.$loose>>>>;
+    }, z.core.$strict>>>>;
     sharedProperties: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
         id: z.ZodString;
         label: z.ZodOptional<z.ZodString>;
@@ -83,7 +92,7 @@ declare const OntologyScopeSchema: z.ZodDefault<z.ZodObject<{
         valueType: z.ZodOptional<z.ZodString>;
         searchable: z.ZodOptional<z.ZodBoolean>;
         pii: z.ZodOptional<z.ZodBoolean>;
-    }, z.core.$loose>>>>;
+    }, z.core.$strict>>>>;
     groups: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
         id: z.ZodString;
         label: z.ZodOptional<z.ZodString>;
@@ -91,7 +100,7 @@ declare const OntologyScopeSchema: z.ZodDefault<z.ZodObject<{
         ownerSystemId: z.ZodOptional<z.ZodString>;
         aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
         members: z.ZodOptional<z.ZodDefault<z.ZodArray<z.ZodString>>>;
-    }, z.core.$loose>>>>;
+    }, z.core.$strict>>>>;
     endpoints: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
         id: z.ZodString;
         label: z.ZodOptional<z.ZodString>;
@@ -99,8 +108,8 @@ declare const OntologyScopeSchema: z.ZodDefault<z.ZodObject<{
         ownerSystemId: z.ZodOptional<z.ZodString>;
         aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
         route: z.ZodOptional<z.ZodString>;
-    }, z.core.$loose>>>>;
-}, z.core.$strip>>;
+    }, z.core.$strict>>>>;
+}, z.core.$strict>>;
 type OntologyScope = z.infer<typeof OntologyScopeSchema>;
 
 declare const SystemApiInterfaceSchema: z.ZodObject<{
@@ -198,11 +207,24 @@ declare const ContentPipelineStepActorSchema: z.ZodEnum<{
     vendor: "vendor";
 }>;
 type ContentPipelineStepActor = z.infer<typeof ContentPipelineStepActorSchema>;
-/** D5: how a human reviews a content pipeline step's output. */
+/**
+ * D5: whether a human decision gates this step's output.
+ *
+ * Two values, deliberately. This field used to be `'live' | 'queued' | 'none'`,
+ * which encoded two independent facts in one enum -- whether a person reviews,
+ * and where they do it. `'live'` and `'queued'` differed only in the second, and
+ * the second was already stored as `workspaceRoute`. One fact written twice in
+ * two vocabularies is what let two review rules disagree on exactly one value
+ * and render a false warning on a live tenant.
+ *
+ * Where review happens is now derived rather than declared -- see
+ * `resolveContentReviewVenue`. Kept a string enum rather than a boolean so a
+ * genuine third mode later (an automated check that gates progression without a
+ * person) is an added member rather than a second schema break on this field.
+ */
 declare const ContentPipelineStepReviewModeSchema: z.ZodEnum<{
+    required: "required";
     none: "none";
-    live: "live";
-    queued: "queued";
 }>;
 type ContentPipelineStepReviewMode = z.infer<typeof ContentPipelineStepReviewModeSchema>;
 /** D17: one entry in a step's template-declared serializable payload field list. */
@@ -220,6 +242,17 @@ declare const ContentPayloadFieldDeclarationSchema: z.ZodObject<{
     required: z.ZodOptional<z.ZodBoolean>;
 }, z.core.$strip>;
 type ContentPayloadFieldDeclaration = z.infer<typeof ContentPayloadFieldDeclarationSchema>;
+/**
+ * Where the human decision a step gates on is actually made. Derived from
+ * `reviewMode` plus the resolved Workspace route -- see
+ * `resolveContentReviewVenue`. Never declared in a catalog.
+ *
+ * - `'none'`    -- nobody is owed a decision on this step.
+ * - `'queue'`   -- the shared review queue. The platform's own surfaces clear it.
+ * - `'workspace'` -- the tenant's own screen, named by `workspaceRoute`. The
+ *   shared surfaces display state and link out; they do not clear it.
+ */
+type ContentReviewVenue = 'none' | 'queue' | 'workspace';
 /** One step in a resolved content pipeline, as returned by `getContentBuildTemplates`. */
 interface ContentPipelineStepEntry {
     /** Matches the catalog entry id (the step's local id within its step catalog). */
@@ -232,8 +265,21 @@ interface ContentPipelineStepEntry {
     order: number;
     /** D5: who/what executes this step. */
     actor: ContentPipelineStepActor;
-    /** D5: how a human reviews this step's output. */
+    /** D5: whether a human decision gates this step's output. */
     reviewMode: ContentPipelineStepReviewMode;
+    /**
+     * Where that decision is made -- **derived, never authored.** Resolved once by
+     * `getContentBuildTemplates` via `resolveContentReviewVenue`, at the one
+     * boundary where a raw catalog becomes a resolved template and both the
+     * pipeline and the step are in hand. `ContentPipelineStepDeclarationSchema`
+     * has no such field, so no tenant can declare it and no second encoding of it
+     * can exist.
+     *
+     * Read this rather than re-deriving from `reviewMode` + `workspaceRoute` at a
+     * call site; recombining those two with `&&` at the point of use is the exact
+     * defect the content-review consolidation removed.
+     */
+    reviewVenue: ContentReviewVenue;
     /** D5: the step key this step advances to. Absent on a terminal step. */
     advancesTo?: string;
     /**
@@ -241,6 +287,12 @@ interface ContentPipelineStepEntry {
      * implements the step yet. See `ContentPipelineStepDeclarationSchema`.
      */
     actionId?: string;
+    /**
+     * Per-step override of the pipeline's Workspace route. Absent on almost every
+     * step. Resolve it with `resolveContentWorkspaceRoute`, never by reading this
+     * field directly -- the fallback to the pipeline's route is the whole point.
+     */
+    workspaceRoute?: string;
     /** D17: the template-declared serializable field list for this step's payload. */
     payloadFields: ContentPayloadFieldDeclaration[];
 }
@@ -250,6 +302,12 @@ interface ContentPipelineTemplate {
     label: string;
     description?: string;
     color?: string;
+    /**
+     * Route into the tenant's Workspace surface for this pipeline. Absent when the
+     * tenant has declared none, which is the case `ContentItemReviewPage`'s
+     * fallback action bar exists to serve. See `ContentWorkspaceRouteSchema`.
+     */
+    workspaceRoute?: string;
     steps: ContentPipelineStepEntry[];
 }
 /** One entry in a resolved `content-stage` catalog (status / pillar / platform), as returned by `getContentStageCatalog`. */
@@ -262,6 +320,15 @@ interface ContentStageCatalogEntry {
     description: string;
     order: number;
     color?: string;
+    /**
+     * The entry's own `semanticClass` -- `'open' | 'active' | 'completed'` on the
+     * status catalog, absent on catalogs that do not declare one.
+     *
+     * Carried through so a consumer can ask "is this item finished?" without
+     * hardcoding which status ids mean finished. A tenant renaming `distributed`
+     * or adding a fifth status keeps working; a hardcoded id list would not.
+     */
+    semanticClass?: string;
 }
 
 declare const OrganizationModelSchema: z.ZodObject<{
@@ -714,7 +781,9 @@ declare const OrganizationModelSchema: z.ZodObject<{
             aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
             properties: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
             storage: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-        }, z.core.$loose>>>>;
+            rowSchema: z.ZodOptional<z.ZodString>;
+            stateCatalogId: z.ZodOptional<z.ZodString>;
+        }, z.core.$strict>>>>;
         linkTypes: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
             id: z.ZodString;
             label: z.ZodOptional<z.ZodString>;
@@ -725,7 +794,7 @@ declare const OrganizationModelSchema: z.ZodObject<{
             to: z.ZodString;
             cardinality: z.ZodOptional<z.ZodString>;
             via: z.ZodOptional<z.ZodString>;
-        }, z.core.$loose>>>>;
+        }, z.core.$strict>>>>;
         actionTypes: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
             id: z.ZodString;
             label: z.ZodOptional<z.ZodString>;
@@ -735,7 +804,11 @@ declare const OrganizationModelSchema: z.ZodObject<{
             actsOn: z.ZodOptional<z.ZodDefault<z.ZodArray<z.ZodString>>>;
             input: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
             effects: z.ZodOptional<z.ZodArray<z.ZodRecord<z.ZodString, z.ZodUnknown>>>;
-        }, z.core.$loose>>>>;
+            resourceId: z.ZodOptional<z.ZodString>;
+            invocations: z.ZodOptional<z.ZodArray<z.ZodUnknown>>;
+            lifecycle: z.ZodOptional<z.ZodString>;
+            legacyActionId: z.ZodOptional<z.ZodString>;
+        }, z.core.$strict>>>>;
         catalogTypes: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
             id: z.ZodString;
             label: z.ZodOptional<z.ZodString>;
@@ -745,7 +818,10 @@ declare const OrganizationModelSchema: z.ZodObject<{
             kind: z.ZodOptional<z.ZodString>;
             appliesTo: z.ZodOptional<z.ZodString>;
             entries: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-        }, z.core.$loose>>>>;
+            legacyCatalogKey: z.ZodOptional<z.ZodString>;
+            legacyPipelineKey: z.ZodOptional<z.ZodString>;
+            legacyEntityKey: z.ZodOptional<z.ZodString>;
+        }, z.core.$strict>>>>;
         eventTypes: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
             id: z.ZodString;
             label: z.ZodOptional<z.ZodString>;
@@ -753,7 +829,7 @@ declare const OrganizationModelSchema: z.ZodObject<{
             ownerSystemId: z.ZodOptional<z.ZodString>;
             aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
             payload: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-        }, z.core.$loose>>>>;
+        }, z.core.$strict>>>>;
         interfaceTypes: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
             id: z.ZodString;
             label: z.ZodOptional<z.ZodString>;
@@ -761,7 +837,7 @@ declare const OrganizationModelSchema: z.ZodObject<{
             ownerSystemId: z.ZodOptional<z.ZodString>;
             aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
             properties: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-        }, z.core.$loose>>>>;
+        }, z.core.$strict>>>>;
         valueTypes: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
             id: z.ZodString;
             label: z.ZodOptional<z.ZodString>;
@@ -769,7 +845,7 @@ declare const OrganizationModelSchema: z.ZodObject<{
             ownerSystemId: z.ZodOptional<z.ZodString>;
             aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
             primitive: z.ZodOptional<z.ZodString>;
-        }, z.core.$loose>>>>;
+        }, z.core.$strict>>>>;
         sharedProperties: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
             id: z.ZodString;
             label: z.ZodOptional<z.ZodString>;
@@ -779,7 +855,7 @@ declare const OrganizationModelSchema: z.ZodObject<{
             valueType: z.ZodOptional<z.ZodString>;
             searchable: z.ZodOptional<z.ZodBoolean>;
             pii: z.ZodOptional<z.ZodBoolean>;
-        }, z.core.$loose>>>>;
+        }, z.core.$strict>>>>;
         groups: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
             id: z.ZodString;
             label: z.ZodOptional<z.ZodString>;
@@ -787,7 +863,7 @@ declare const OrganizationModelSchema: z.ZodObject<{
             ownerSystemId: z.ZodOptional<z.ZodString>;
             aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
             members: z.ZodOptional<z.ZodDefault<z.ZodArray<z.ZodString>>>;
-        }, z.core.$loose>>>>;
+        }, z.core.$strict>>>>;
         endpoints: z.ZodOptional<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
             id: z.ZodString;
             label: z.ZodOptional<z.ZodString>;
@@ -795,8 +871,8 @@ declare const OrganizationModelSchema: z.ZodObject<{
             ownerSystemId: z.ZodOptional<z.ZodString>;
             aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
             route: z.ZodOptional<z.ZodString>;
-        }, z.core.$loose>>>>;
-    }, z.core.$strip>>>;
+        }, z.core.$strict>>>>;
+    }, z.core.$strict>>>;
     resources: z.ZodDefault<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodDiscriminatedUnion<[z.ZodObject<{
         id: z.ZodString;
         order: z.ZodDefault<z.ZodNumber>;
@@ -1251,6 +1327,13 @@ declare const OrganizationModelSchema: z.ZodObject<{
 type OrganizationModel = z.infer<typeof OrganizationModelSchema>;
 type OrganizationModelResourceKind = z.infer<typeof ResourceKindSchema>;
 
+/** Response-side crop: unknown keys are stripped, not rejected, like every other response schema here. */
+declare const ContentAssetCropSchema: z.ZodObject<{
+    x: z.ZodNumber;
+    y: z.ZodNumber;
+    width: z.ZodNumber;
+    height: z.ZodNumber;
+}, z.core.$strip>;
 declare const ContentItemResponseSchema: z.ZodObject<{
     id: z.ZodString;
     organizationId: z.ZodString;
@@ -1262,6 +1345,29 @@ declare const ContentItemResponseSchema: z.ZodObject<{
     pipelineId: z.ZodNullable<z.ZodString>;
     clientId: z.ZodNullable<z.ZodString>;
     sourceAssetId: z.ZodNullable<z.ZodString>;
+    sourceAssets: z.ZodOptional<z.ZodArray<z.ZodObject<{
+        id: z.ZodString;
+        organizationId: z.ZodString;
+        contentItemId: z.ZodString;
+        sourceAssetId: z.ZodString;
+        position: z.ZodNumber;
+        crop: z.ZodNullable<z.ZodObject<{
+            x: z.ZodNumber;
+            y: z.ZodNumber;
+            width: z.ZodNumber;
+            height: z.ZodNumber;
+        }, z.core.$strip>>;
+        altText: z.ZodNullable<z.ZodString>;
+        derivativePath: z.ZodNullable<z.ZodString>;
+        derivativeCrop: z.ZodNullable<z.ZodObject<{
+            x: z.ZodNumber;
+            y: z.ZodNumber;
+            width: z.ZodNumber;
+            height: z.ZodNumber;
+        }, z.core.$strip>>;
+        derivativeRenderedAt: z.ZodNullable<z.ZodString>;
+        createdAt: z.ZodString;
+    }, z.core.$strip>>>;
     processingState: z.ZodRecord<z.ZodString, z.ZodObject<{
         status: z.ZodEnum<{
             error: "error";
@@ -1284,7 +1390,35 @@ declare const ContentItemResponseSchema: z.ZodObject<{
     createdAt: z.ZodString;
     updatedAt: z.ZodString;
 }, z.core.$strip>;
+declare const ContentSourceAssetResponseSchema: z.ZodObject<{
+    id: z.ZodString;
+    organizationId: z.ZodString;
+    kind: z.ZodString;
+    title: z.ZodString;
+    externalUrl: z.ZodNullable<z.ZodString>;
+    storagePath: z.ZodNullable<z.ZodString>;
+    durationSeconds: z.ZodNullable<z.ZodNumber>;
+    metadata: z.ZodUnknown;
+    payload: z.ZodUnknown;
+    processingState: z.ZodRecord<z.ZodString, z.ZodObject<{
+        status: z.ZodEnum<{
+            error: "error";
+            success: "success";
+            running: "running";
+            no_result: "no_result";
+            skipped: "skipped";
+        }>;
+        attemptId: z.ZodString;
+        executionId: z.ZodNullable<z.ZodString>;
+        attemptedAt: z.ZodString;
+        data: z.ZodOptional<z.ZodUnknown>;
+    }, z.core.$loose>>;
+    createdAt: z.ZodString;
+    updatedAt: z.ZodString;
+}, z.core.$strip>;
+type ContentAssetCrop = z.infer<typeof ContentAssetCropSchema>;
 type ContentItemResponse = z.infer<typeof ContentItemResponseSchema>;
+type ContentSourceAssetResponse = z.infer<typeof ContentSourceAssetResponseSchema>;
 
 /**
  * `deriveContentBoard` -- a pure function of `(items, pipeline, now)`. No React, no
@@ -1306,8 +1440,15 @@ type ContentItemResponse = z.infer<typeof ContentItemResponseSchema>;
  *    item -- `'running'` falls out of this rule unchanged: a step mid-flight is not
  *    `'success'`, so it holds the item at that column exactly like `'error'` or
  *    `'skipped'` already do.
- * 3. If every declared step has a `'success'` entry, `stepKey` is `null` and the card
- *    goes in `done`.
+ * 3. If every declared step has a `'success'` entry the item has finished the pipeline --
+ *    but it reaches `done` only once its review gate is cleared. When the LAST step
+ *    declares a `reviewMode` other than `'none'` and the item's `reviewedAt` is still
+ *    `null`, the item is held at that last step (`bucket: 'column'`) so the gate it has
+ *    not passed keeps counting it. Otherwise `stepKey` is `null` and the card goes in
+ *    `done`. Without the hold, a producer writing `'success'` on the final step removed
+ *    the item from every column and the gate's `waitingCount` dropped to zero with
+ *    nobody having reviewed anything -- `'success'` is the only status that advances an
+ *    item, so the gate could not survive its own producer completing.
  * 4. If `processingState` is empty (`{}`), the item sits at the first step -- nothing
  *    has run yet.
  * 5. A card goes in `unplaced` only when `processingState` is non-empty AND none of its
@@ -1325,15 +1466,23 @@ interface ContentBoardCard {
     awaitingReview: boolean;
 }
 interface ContentBoardGate {
-    /** The review mode of the step this gate follows. Never 'none' -- a 'none' step has no gate. */
-    reviewMode: Exclude<ContentPipelineStepReviewMode, 'none'>;
+    /**
+     * Where this gate's review happens. Never `'none'` -- a step nobody reviews
+     * has no gate at all.
+     *
+     * This replaced a `reviewMode` field when the enum collapsed to
+     * `'none' | 'required'`, which would have left every gate reporting the same
+     * constant. Venue is the fact a consumer actually renders: the CLI's board
+     * label and the UI's column header both need to say *where*, not *whether*.
+     */
+    venue: Exclude<ContentReviewVenue, 'none'>;
     /** How many cards in the preceding column are awaiting review. */
     waitingCount: number;
 }
 interface ContentBoardColumn {
     step: ContentPipelineStepEntry;
     cards: ContentBoardCard[];
-    /** Present when this step's reviewMode is 'live' or 'queued'. Absent on a 'none' step. */
+    /** Present when this step's `reviewVenue` is not `'none'`. A step nobody reviews has no gate. */
     gate?: ContentBoardGate;
 }
 interface ContentBoard {
@@ -1369,6 +1518,39 @@ declare function deriveContentBoard(items: ContentItemResponse[], pipeline: Cont
  */
 declare function getContentItemIdentity(item: Pick<ContentItemResponse, 'title' | 'body' | 'payload'>, payloadFields?: ContentPayloadFieldDeclaration[], maxLength?: number): string;
 
+/**
+ * Storage-neutral file descriptor.
+ *
+ * Dropbox and Google Drive (the foreseeable second provider) both ship
+ * their own file/metadata shapes. Consumers on both sides of the wire —
+ * a UI file browser and the API route that talks to the provider — need
+ * to agree on one normalized shape, which is why it lives here instead
+ * of being duplicated in each consumer.
+ *
+ * Adapters (`createDropboxAdapter`, a future Drive adapter) stay concrete
+ * and keep their own provider-shaped responses. Normalization into this
+ * type happens at the route/hook boundary — a few lines per provider,
+ * not behind a shared `CloudStorageAdapter` interface.
+ */
+interface CloudStorageFile {
+    id: string;
+    name: string;
+    kind: 'file' | 'folder';
+    path?: string;
+    mimeType?: string;
+    sizeBytes?: number;
+    width?: number;
+    height?: number;
+    /** ISO 8601 timestamp the asset was captured (e.g. photo EXIF date), when the provider exposes one. */
+    capturedAt?: string;
+    /**
+     * Optional on purpose. Dropbox does not produce a thumbnail for HEIC or
+     * for anything over 20 MB — "no thumbnail" is a normal state a consumer
+     * renders a fallback for, not an error.
+     */
+    thumbnailUrl?: string;
+}
+
 type SystemSidebarComponent = ComponentType;
 type SystemIconComponent = ComponentType<{
     size?: number;
@@ -1438,7 +1620,7 @@ interface ContentPipelinesPageSlots {
  */
 declare function ContentPipelinesPage({ headerActions }?: ContentPipelinesPageSlots): react_jsx_runtime.JSX.Element;
 
-interface ContentPipelineWorkspacePageSlots {
+interface ContentPipelineBoardPageSlots {
     /** Optional content rendered after the page title. Default: nothing rendered. */
     headerActions?: ReactNode;
 }
@@ -1446,9 +1628,9 @@ interface ContentPipelineWorkspacePageSlots {
  * Pipeline workspace -- tabbed via `?tab=`, matching how `LeadGenListDetailPage`
  * (`../../../lead-gen/pages/list-detail/ListDetailPage.tsx`) already does it.
  */
-declare function ContentPipelineWorkspacePage({ pipelineId, headerActions }: {
+declare function ContentPipelineBoardPage({ pipelineId, headerActions }: {
     pipelineId: string;
-} & ContentPipelineWorkspacePageSlots): react_jsx_runtime.JSX.Element;
+} & ContentPipelineBoardPageSlots): react_jsx_runtime.JSX.Element;
 
 interface ContentDistributionsPageSlots {
     /** Optional content rendered after the page title. Default: nothing rendered. */
@@ -1473,14 +1655,19 @@ interface ContentDistributionDetailPageSlots {
 }
 /**
  * Distribution detail -- ported from `/acquisition/content/distribution/$distributionId`.
- * The four writes the original made through Supabase-direct hooks (checklist toggle,
- * platform-content edit, media delete, general field update) all collapse into
- * `useUpdateContentDistribution`, since each was a partial write of `checklist`,
- * `platformContent`, or `mediaUrls` and the PATCH route accepts all three plus the
- * general fields. Surfaces the four columns that have never been rendered anywhere:
- * `metrics`, `metricsUpdatedAt`, `publishMethod`, `platformPostId` -- `publishMethod` is
- * where D7's manual-publish state becomes visible (a row with `publishedAt` set and no
+ * Surfaces the four columns that have never been rendered anywhere: `metrics`,
+ * `metricsUpdatedAt`, `publishMethod`, `platformPostId` -- `publishMethod` is where D7's
+ * manual-publish state becomes visible (a row with `publishedAt` set and no
  * `platformPostId`).
+ *
+ * **Display-only.** This page used to be an editor: status, platform URL, checklist,
+ * platform content, and media delete all wrote through `useUpdateContentDistribution`.
+ * Every one of those was removed when the content System split its UI -- tenants own the
+ * surfaces where content is operated on, the platform owns the surfaces where it is
+ * observed, and a distribution page is an observation. `useUpdateContentDistribution` is
+ * still exported for tenants that want to build their own editing screen; nothing shared
+ * calls it. Do not reintroduce a write here -- the absence is the contract, and it is the
+ * same absence that keeps `reviewItem` out of `ContentToolMap`.
  */
 declare function ContentDistributionDetailPage({ distributionId, headerActions }: {
     distributionId: string;
@@ -1501,8 +1688,15 @@ interface ContentPageOverrides {
     itemReview?: ContentItemReviewPageSlots;
     /** Slot props injected into `ContentPipelinesPage`. */
     pipelines?: ContentPipelinesPageSlots;
-    /** Slot props injected into `ContentPipelineWorkspacePage`. */
-    pipelineWorkspace?: ContentPipelineWorkspacePageSlots;
+    /**
+     * Slot props injected into `ContentPipelineBoardPage`.
+     *
+     * The key stays `pipelineWorkspace` although the page it points at was renamed to
+     * Board on 2026-08-15 (Decision 6). It is part of the published manifest surface, so
+     * renaming it is a second breaking change on the same minor, and unlike the page name
+     * this one is never read by anyone looking at a sidebar. Revisit on a later minor.
+     */
+    pipelineWorkspace?: ContentPipelineBoardPageSlots;
 }
 /**
  * Extended `SystemModule` for the content feature that carries optional page overrides
@@ -1758,6 +1952,15 @@ interface ContentReviewCardProps {
     onAction: (actionId: string, feedback?: string) => void;
     /** True while a submitted action is in flight. Disables the action bar and the body. */
     actionsPending?: boolean;
+    /**
+     * Render the piece without any way to change it: the body is not editable and the
+     * alternates panel is hidden, since picking an alternate rewrites the body. Distinct
+     * from `actionsPending`, which is a transient in-flight disable -- this one is a
+     * statement about who owns editing. Used by the shared review page when the pipeline
+     * declares a `workspaceRoute`, so the tenant's own screen is the only place the piece
+     * can be changed.
+     */
+    readOnly?: boolean;
 }
 /**
  * The generic content review card. Generalizes three things that exist separately
@@ -1765,7 +1968,307 @@ interface ContentReviewCardProps {
  * nirvana's `DraftCard`, and the attempt-lineage / processing-state surfaces that had
  * no reader at all. Keyed off `reviewMode` rather than any tenant-specific vocabulary.
  */
-declare function ContentReviewCard({ title, body, onBodyChange, originalBody, onReset, payload, payloadFields, fidelity, checkFirst, hookOptions, closeOptions, onMoreHooks, onMoreCloses, alternatesRunning, alternatesElapsed, processingSteps, actions, onAction, actionsPending }: ContentReviewCardProps): react_jsx_runtime.JSX.Element;
+declare function ContentReviewCard({ title, body, onBodyChange, originalBody, onReset, payload, payloadFields, fidelity, checkFirst, hookOptions, closeOptions, onMoreHooks, onMoreCloses, alternatesRunning, alternatesElapsed, processingSteps, actions, onAction, actionsPending, readOnly }: ContentReviewCardProps): react_jsx_runtime.JSX.Element;
+
+interface SelectedAssetStripProps {
+    /**
+     * The selection, in carousel order. Index 0 is the cover slide -- there is no
+     * separate `isCover` flag to keep in sync, because the planned
+     * `content_item_source_assets` link table persists this same array as a `position`
+     * column where `position = 0` IS the cover by definition.
+     */
+    assets: CloudStorageFile[];
+    /** Fires with the full reordered array whenever the user drags a slide to a new position. */
+    onReorder: (assets: CloudStorageFile[]) => void;
+}
+/**
+ * Ordered strip of the assets selected for a multi-asset content item (an Instagram
+ * carousel post's slides). Presentational -- data in via `assets`, order changes out
+ * via `onReorder`, no fetching. Drag-reorder uses native HTML5 drag events, matching
+ * the pattern already established for `KanbanBoard` / `DealKanbanCard` rather than
+ * introducing a new drag-and-drop dependency for one strip.
+ */
+declare function SelectedAssetStrip({ assets, onReorder }: SelectedAssetStripProps): react_jsx_runtime.JSX.Element;
+
+interface SourceAssetsPanelProps {
+    /** The content item whose membership this panel reads and writes. */
+    itemId: string;
+}
+/**
+ * Operator surface for a content item's ordered source-asset membership -- the
+ * carousel. Reads `content_item_source_assets` and drives all four membership
+ * writes: link, unlink, reorder, and per-slide alt text.
+ *
+ * This exists because the membership write path had no surface at all: it is not on
+ * the CLI, the external API-key routes were deliberately not extended (Open Decision
+ * 10), and the seed workflow still creates items through the legacy singular
+ * `sourceAssetId`. Everything below the hooks was therefore covered by unit tests
+ * only and had never been executed end to end. A basic table is enough to fix that,
+ * and a tenant that wants a picture-first carousel editor builds its own on the same
+ * hooks.
+ *
+ * Two ordering surfaces on purpose. `SelectedAssetStrip` is the picture-first one and
+ * is what tenants get from the `./features/content` subpath, so it is mounted here
+ * against real persisted membership rather than left to render only under test. The
+ * table underneath keeps move up / move down because drag is unusable by keyboard and
+ * unavailable to a screen reader. Both send the identical complete ordered list.
+ *
+ * The strip takes `CloudStorageFile`, which a membership is not -- the mapping below is
+ * the whole adapter. Content source assets carry no thumbnail yet (that arrives with
+ * Dropbox intake), so every tile renders the strip's no-thumbnail fallback today.
+ *
+ * The crop column opens `AssetCropEditor` against the original's bytes, resolved
+ * one file at a time while the modal is open. Only an asset carrying a
+ * cloud-storage reference can be cropped -- there is nothing to crop against
+ * otherwise -- so a seeded or text-backed asset shows the button disabled.
+ *
+ * Positions are shown as stored, not as row indexes. Non-contiguous positions are
+ * legal -- only uniqueness within an item is enforced -- so an item assembled by
+ * individual links can legitimately have no `position` 0, and the cover is the lowest
+ * position present rather than a literal 0.
+ */
+declare function SourceAssetsPanel({ itemId }: SourceAssetsPanelProps): react_jsx_runtime.JSX.Element;
+
+/**
+ * A carousel aspect option. `ratio` is width / height in PIXELS -- `null` means
+ * "whatever the source already is", which is the only option that never crops.
+ */
+interface CropAspectOption {
+    value: string;
+    label: string;
+    ratio: number | null;
+}
+/**
+ * The three shapes a photo post actually takes, plus the uncropped original.
+ * Portrait 4:5 leads because it is the tallest a feed will show without
+ * cropping the image itself, so it is the default for a carousel.
+ */
+declare const CROP_ASPECT_OPTIONS: CropAspectOption[];
+interface AssetCropEditorProps {
+    /**
+     * The FULL-RESOLUTION image. A thumbnail will not do: the crop is stored as
+     * fractions of the source, and a downsampled copy shows the operator a
+     * different frame from the one that gets published.
+     */
+    imageUrl: string | null;
+    /** The stored crop, or `null` for "uncropped". */
+    value: ContentAssetCrop | null;
+    /** Fires on every committed change. `null` clears the crop back to the full frame. */
+    onChange: (crop: ContentAssetCrop | null) => void;
+    /** Which aspect the control starts on. Defaults to the source's own shape. */
+    defaultAspect?: string;
+    /** Locks the aspect selector -- a carousel wants one ratio across every slide. */
+    aspect?: string;
+    disabled?: boolean;
+    /** Shown above the frame, e.g. `Slide 1`. */
+    label?: string;
+}
+/**
+ * Picks the crop box out of a normalized frame, over the image itself.
+ *
+ * The emitted value is exactly what `ContentAssetCropInputSchema` validates:
+ * `{ x, y, width, height }` as fractions of the source, `0,0` at the top-left.
+ * Fractions rather than pixels because the same crop has to survive a resized
+ * derivative, which is also why this needs the original rather than a thumbnail.
+ *
+ * **Aspect is expressed in pixels and stored in fractions**, and the two are not
+ * the same number on a non-square image -- a 1:1 crop of a 4000x3000 photo is
+ * `width: 0.75, height: 1`. `fitBox` is the whole of that conversion.
+ *
+ * Two controls, not a free-form rubber band: an aspect and a size, with the frame
+ * dragged into place. A free rectangle lets an operator produce a shape no feed
+ * will render, and the failure only shows up after posting.
+ */
+declare function AssetCropEditor({ imageUrl, value, onChange, defaultAspect, aspect, disabled, label }: AssetCropEditorProps): react_jsx_runtime.JSX.Element;
+
+/** One slide, in carousel order. */
+interface PostPreviewSlide {
+    /** Stable per-slide key -- the source asset id, or the storage file id before one exists. */
+    id: string;
+    /** The full-resolution image. `null` renders the empty frame rather than a broken one. */
+    imageUrl: string | null;
+    /** The stored crop, or `null` for the uncropped original. */
+    crop?: ContentAssetCrop | null;
+    altText?: string | null;
+}
+interface PostPreviewProps {
+    slides: PostPreviewSlide[];
+    /** The caption as it would post. `null` renders the "no caption yet" line. */
+    caption?: string | null;
+    hashtags?: string[];
+    /** Frame shape, width / height in pixels. Defaults to the 4:5 portrait a carousel uses. */
+    aspectRatio?: number;
+    /** Shown above the frame, e.g. the item title. */
+    title?: string;
+}
+/**
+ * The carousel as it will actually post: slides in position order, each one
+ * showing only the part its crop keeps, with the caption underneath.
+ *
+ * **The crop is applied here, not baked into any file.** Nothing in this
+ * pipeline writes a cropped derivative -- `content_item_source_assets.crop` is
+ * a normalized box, and every surface that renders a slide applies it. This
+ * component is the reference implementation of that, and the reason it is
+ * shared rather than page-local.
+ *
+ * The technique is an oversized absolutely-positioned image inside an
+ * overflow-hidden frame: an image scaled to `1 / crop.width` of the frame and
+ * offset by `-crop.x / crop.width` puts exactly the kept region in view, in
+ * pure CSS and with no canvas step. `object-fit: cover` stays on so a slide
+ * whose crop aspect does not match the frame is trimmed rather than stretched.
+ */
+declare function PostPreview({ slides, caption, hashtags, aspectRatio, title }: PostPreviewProps): react_jsx_runtime.JSX.Element;
+/**
+ * Positions the image so the frame shows only the crop's region.
+ *
+ * Exported for the unit test: the arithmetic is the one part of this component
+ * that can be silently wrong, and asserting it through a rendered style string
+ * is what catches an inverted sign.
+ */
+declare function cropStyle(crop: ContentAssetCrop | null): React.CSSProperties;
+
+/**
+ * Rendering a crop to an actual file.
+ *
+ * `cropStyle` in `PostPreview` renders the same crop with CSS, which is right for
+ * a preview and useless for posting: the cropped image never exists as bytes, so
+ * there is nothing to download and nothing to hand a platform. This module is the
+ * other half -- the same four normalized numbers, resolved into a JPEG.
+ *
+ * It runs in the browser on purpose. The pixels are already decoded there (the
+ * crop editor and the preview share one download of the original), the source is
+ * a short-lived provider link the server would have to re-fetch, and no image
+ * library exists anywhere in this monorepo -- putting this on the server would
+ * mean adding the first native image binary to a service whose build is a no-op.
+ * A spike on 2026-08-19 confirmed Dropbox's temporary-link hosts send permissive
+ * CORS, so the canvas is not tainted and `toBlob` succeeds.
+ */
+/** The private, org-scoped, RLS-gated bucket derivatives live in. */
+declare const CONTENT_DERIVATIVES_BUCKET = "content-derivatives";
+/**
+ * Widest edge a derivative is encoded at.
+ *
+ * 1080 is what Instagram renders a feed image at; anything wider is downsampled on
+ * upload, so the extra bytes buy nothing. A crop smaller than this is never
+ * upscaled to reach it -- see `renderCropToJpeg`.
+ */
+declare const DERIVATIVE_MAX_WIDTH = 1080;
+/** JPEG quality. 0.9 measured at 84-104 KB for a 1080x1350 slide. */
+declare const DERIVATIVE_JPEG_QUALITY = 0.9;
+/**
+ * Object key for one slide's derivative, WITHOUT the `{organizationId}/` prefix --
+ * `StorageService.buildPath` prepends that server-side, and the `storage.objects`
+ * policies read the org back out of it.
+ *
+ * Keyed by item and source asset rather than by membership id so a re-render
+ * overwrites the previous derivative instead of accumulating one file per edit.
+ * The pair is unique within an item by database constraint, which is what makes
+ * that safe.
+ */
+declare function derivativeObjectKey(contentItemId: string, sourceAssetId: string): string;
+/**
+ * Whether the stored derivative no longer matches the crop it is supposed to show.
+ *
+ * Derived, never stored: a `derivativeIsStale` column would be a second encoding of
+ * what these two values already say, and the two could disagree. A membership with
+ * no crop has nothing to render, and one with no derivative is missing rather than
+ * stale -- both return false, because neither is a file that needs replacing.
+ */
+declare function isDerivativeStale(crop: ContentAssetCrop | null, derivativeCrop: ContentAssetCrop | null, derivativePath: string | null): boolean;
+interface RenderCropOptions {
+    /** Widest edge to encode at. Defaults to `DERIVATIVE_MAX_WIDTH`. */
+    maxWidth?: number;
+    /** JPEG quality, 0-1. Defaults to `DERIVATIVE_JPEG_QUALITY`. */
+    quality?: number;
+}
+/**
+ * Render a crop box against its source image and return the cropped JPEG.
+ *
+ * `crop` is normalized fractions of the source, exactly as stored -- so this
+ * survives the source being a different pixel size than it was when the crop was
+ * drawn. A `null` crop renders the whole frame, which still does real work: it
+ * normalizes the format and caps the size.
+ *
+ * The output is never upscaled past the cropped region's own pixel count. A tight
+ * crop of a small original produces a smaller file rather than a blurry 1080px
+ * one, and a platform that wants 1080 will upscale it either way.
+ *
+ * Throws rather than returning null on a tainted canvas or an unloadable URL:
+ * silently storing no derivative is indistinguishable from never having tried.
+ */
+declare function renderCropToJpeg(imageUrl: string, crop: ContentAssetCrop | null, options?: RenderCropOptions): Promise<Blob>;
+
+/** The `content:catalog/photo-carousel-steps` entry this panel drives. */
+declare const CAPTION_STEP_KEY = "caption-generation";
+/** The OM Resource bound to `content:action/caption-generation`. */
+declare const CAPTION_WORKFLOW_ID = "cnt-caption-generation-workflow";
+interface CaptionPanelProps {
+    itemId: string;
+    /** The item's current `body`, so the panel can mark which attempt is the live caption. */
+    body?: string | null;
+    /**
+     * Called on every keystroke with the unsaved caption text.
+     *
+     * This exists so a preview rendered beside the editor updates as the operator
+     * types rather than one autosave later. Consumers that only care about the
+     * persisted value can ignore it and read `body` as before.
+     */
+    onDraftChange?: (draft: string) => void;
+}
+/**
+ * Generate a caption for a carousel, regenerate it, and pick which one becomes
+ * the item's body.
+ *
+ * **Regeneration does not overwrite.** Every run of
+ * `cnt-caption-generation-workflow` writes its own `content_item_attempts` row,
+ * so a second caption competes with the first rather than replacing it, and the
+ * one the operator liked stays reachable after they try something else. Nothing
+ * here is promoted automatically: `content_items.body` changes only when someone
+ * presses Use, which is exactly what the step's `reviewMode: 'required'` means.
+ *
+ * The workflow runs asynchronously and the panel polls its execution, because
+ * a vision-informed caption over several slides regularly outruns the API's
+ * 60-second synchronous request timeout.
+ */
+declare function CaptionPanel({ itemId, body, onDraftChange }: CaptionPanelProps): react_jsx_runtime.JSX.Element;
+
+/** The OM Resource bound to `content:action/image-analysis`. */
+declare const IMAGE_ANALYSIS_WORKFLOW_ID = "cnt-image-analysis-workflow";
+interface SlideAnalysisPanelProps {
+    itemId: string;
+}
+/**
+ * What `cnt-image-analysis-workflow` writes to `content_source_assets.metadata.analysis`.
+ * Every field is read defensively: the column is free-form jsonb, so an older row, a
+ * hand-edited one, or one written by a future version of the workflow may carry
+ * anything at all.
+ */
+interface StoredSlideAnalysis {
+    description?: string;
+    subjects?: string[];
+    setting?: string;
+    mood?: string;
+    textInImage?: string;
+    altText?: string;
+    model?: string;
+    generatedAt?: string;
+}
+/** Reads the analysis off an asset, or `null` when it has never been analysed. */
+declare function readStoredAnalysis(asset: ContentSourceAssetResponse | undefined): StoredSlideAnalysis | null;
+/**
+ * Runs image analysis over a carousel's slides and shows what came back.
+ *
+ * **The analysis lives on the ASSET, not on the membership** (Open Decision 14).
+ * It describes the photograph, so it is written once per photo and every item
+ * that uses that photo reads the same description -- and a re-crop does not
+ * invalidate it. The per-slide fields beside it (`crop`, `altText`) stay on the
+ * membership, where a slide's role in one particular carousel belongs.
+ *
+ * Re-running is a plain overwrite here, unlike captions: there is no competing
+ * "which description is better" judgement to preserve, and an analysis is an
+ * input to the caption rather than something anyone publishes.
+ */
+declare function SlideAnalysisPanel({ itemId }: SlideAnalysisPanelProps): react_jsx_runtime.JSX.Element;
 
 /** A single tenant-facing noun with singular and plural forms, e.g. `{ singular: 'Post', plural: 'Posts' }`. */
 interface ContentNoun {
@@ -1914,19 +2417,25 @@ interface NavItem {
 
 interface ContentSidebarProps {
     /**
-     * Tenant-authored authoring surfaces for the `Create` section, forwarded to
+     * Tenant-authored operating surfaces for the `Workspace` section, forwarded to
      * `ContentSidebarMiddle`. Ignored when `children` is supplied, since that replaces the
-     * middle outright. This is the one-line path for a tenant adding its own creator:
+     * middle outright. This is the one-line path for a tenant adding its own screen:
      *
      * ```tsx
-     * const sidebar = () => <ContentSidebar createItems={[{ label: 'Draft a Post', to: '/content/write', icon: IconPencil, exact: false }]} />
+     * const sidebar = () => <ContentSidebar workspaceItems={[{ label: 'Draft a Post', to: '/content/write', icon: IconPencil, exact: false }]} />
      * ```
      */
+    workspaceItems?: NavItem[];
+    /**
+     * @deprecated Renamed to {@link ContentSidebarProps.workspaceItems}. Kept as an alias
+     * for one minor so the rename is non-breaking for tenants; `workspaceItems` wins when
+     * both are passed.
+     */
     createItems?: NavItem[];
     /** Replace the default `ContentSidebarMiddle` with custom middle content. Leave unset for the default layout. */
     children?: ReactNode;
 }
-declare const ContentSidebar: ({ createItems, children }?: ContentSidebarProps) => react_jsx_runtime.JSX.Element;
+declare const ContentSidebar: ({ workspaceItems, createItems, children }?: ContentSidebarProps) => react_jsx_runtime.JSX.Element;
 
 /**
  * Static two-entry default, built from {@link DEFAULT_CONTENT_VOCABULARY}. Exists for
@@ -1937,14 +2446,21 @@ declare const ContentSidebar: ({ createItems, children }?: ContentSidebarProps)
 declare const CONTENT_ITEMS: NavItem[];
 interface ContentSidebarMiddleProps {
     /**
-     * Tenant-authored authoring surfaces, rendered under the `Create` section above the
-     * pipeline nav. Empty or omitted -> the section renders its "nothing declared" hint
-     * instead of nav entries; the section header itself is always present.
+     * Tenant-authored operating surfaces, rendered under the `Workspace` section above
+     * the pipeline nav. Empty or omitted -> the section renders its "nothing declared"
+     * hint instead of nav entries; the section header itself is always present.
      *
-     * This is the seam for a tenant's own content creator -- a LinkedIn drafting screen,
-     * a brief builder, whatever the tenant authors -- without it having to restate the
-     * pipeline entries. Prefer this over {@link ContentSidebarMiddleProps.items}, which
-     * replaces the pipeline list wholesale and stops tracking the tenant's vocabulary.
+     * This is the seam for the screens where a tenant *operates* on content -- creating
+     * it and clearing its review gates, which may well be one screen -- without having to
+     * restate the pipeline entries. Prefer this over {@link ContentSidebarMiddleProps.items},
+     * which replaces the pipeline list wholesale and stops tracking the tenant's vocabulary.
+     */
+    workspaceItems?: NavItem[];
+    /**
+     * @deprecated Renamed to {@link ContentSidebarMiddleProps.workspaceItems}. Kept as an
+     * alias for one minor so the rename is non-breaking for tenants; `workspaceItems` wins
+     * when both are passed. The prop was named for a section that only held authoring, and
+     * that section now holds review too.
      */
     createItems?: NavItem[];
     /** Override the pipeline nav items. Defaults to the two-entry nav built from the tenant's declared vocabulary. */
@@ -1953,22 +2469,26 @@ interface ContentSidebarMiddleProps {
 /**
  * The content subshell nav, in two labeled sections.
  *
- * `Create` sits on top and is where content gets made; the pipeline section below is
- * where it gets reviewed and tracked. The split exists because authoring is
- * tenant-specific by nature (every tenant writes a different kind of thing, through a
- * different screen) while the pipeline underneath is the same shared system for all of
- * them.
+ * `Workspace` sits on top and is where content is *operated on* -- both made and
+ * signed off; the pipeline section below is where it is *observed*. The split exists
+ * because operating on content is tenant-specific by nature (every tenant writes a
+ * different kind of thing, and reviews it against different criteria, through
+ * different screens) while the pipeline underneath is the same shared system for all
+ * of them.
+ *
+ * The section was called `Create` until 2026-08-15. It was renamed because clearing a
+ * review gate is not creation, and the tenant screen that does one usually does both.
  *
  * **Both section labels are fixed platform vocabulary, not tenant-declared.** The nav
  * entries inside them still are — a tenant that renames its pipelines to "Campaigns"
  * gets `Content Pipeline > Campaigns`. The sections name the two halves of the System
  * itself, which every tenant has; only what they contain varies.
  *
- * There is deliberately no section header above `Create`: the subshell is already
+ * There is deliberately no section header above `Workspace`: the subshell is already
  * reached through the `Content` nav entry, so a third `Content` header only repeated
  * what the breadcrumb and the left rail both already say.
  */
-declare const ContentSidebarMiddle: ({ createItems, items }?: ContentSidebarMiddleProps) => react_jsx_runtime.JSX.Element;
+declare const ContentSidebarMiddle: ({ workspaceItems, createItems, items }?: ContentSidebarMiddleProps) => react_jsx_runtime.JSX.Element;
 
 interface MyReviewQueuePanelProps {
     onItemClick: (itemId: string) => void;
@@ -1981,8 +2501,8 @@ interface MyReviewQueuePanelProps {
  * cross-pipeline "what needs review" view rather than a panel beside a table browser.
  *
  * The `/content/items` route accepts no "pending review" filter (only `reviewedBy`, not
- * a reviewed/unreviewed flag), so this fetches a page of items and filters to
- * `reviewedAt === null` client-side. A future backend addition could push this
+ * a reviewed/unreviewed flag), so this fetches a page of items and filters to the ones
+ * `isAwaitingReview` client-side. A future backend addition could push this
  * server-side; documenting the gap here rather than silently over-claiming precision.
  *
  * Rows are ordered oldest-first by `updatedAt` -- finding 6 is that nothing on the
@@ -1991,5 +2511,5 @@ interface MyReviewQueuePanelProps {
  */
 declare function MyReviewQueuePanel({ onItemClick, onSeeAll, showSectionLabel }: MyReviewQueuePanelProps): react_jsx_runtime.JSX.Element;
 
-export { AlternatesPanel, CONTENT_ITEMS, ContentDistributionDetailPage, ContentDistributionsPage, ContentItemReviewPage, ContentItemsPage, ContentOverviewPage, ContentPipelineWorkspacePage, ContentPipelinesPage, ContentReviewCard, ContentSidebar, ContentSidebarMiddle, DEFAULT_CONTENT_VOCABULARY, MyReviewQueuePanel, PayloadBody, ProcessingStateStrip, ReviewActionBar, contentManifest, deriveContentBoard, firstLine, formatElapsed, getContentItemIdentity, lastLine, resolveContentStepResource, resolveContentVocabulary, swapFirstLine, swapLastLine, useContentConfig };
-export type { AlternatesPanelProps, ContentAlternateOption, ContentBoard, ContentBoardCard, ContentBoardColumn, ContentBoardGate, ContentConfig, ContentDistributionDetailPageSlots, ContentDistributionsPageSlots, ContentFidelityCheck, ContentItemReviewPageSlots, ContentItemsPageSlots, ContentNoun, ContentOverviewPageSlots, ContentPayloadField, ContentPipelineWorkspacePageSlots, ContentPipelinesPageSlots, ContentProcessingStatus, ContentProcessingStep, ContentReviewAction, ContentReviewCardProps, ContentSidebarMiddleProps, ContentSidebarProps, ContentStepResourceBinding, ContentVocabulary, MyReviewQueuePanelProps, PayloadBodyProps, ProcessingStateStripProps, ReviewActionBarProps, ReviewMode };
+export { AlternatesPanel, AssetCropEditor, CAPTION_STEP_KEY, CAPTION_WORKFLOW_ID, CONTENT_DERIVATIVES_BUCKET, CONTENT_ITEMS, CROP_ASPECT_OPTIONS, CaptionPanel, ContentDistributionDetailPage, ContentDistributionsPage, ContentItemReviewPage, ContentItemsPage, ContentOverviewPage, ContentPipelineBoardPage, ContentPipelineBoardPage as ContentPipelineWorkspacePage, ContentPipelinesPage, ContentReviewCard, ContentSidebar, ContentSidebarMiddle, DEFAULT_CONTENT_VOCABULARY, DERIVATIVE_JPEG_QUALITY, DERIVATIVE_MAX_WIDTH, IMAGE_ANALYSIS_WORKFLOW_ID, MyReviewQueuePanel, PayloadBody, PostPreview, ProcessingStateStrip, ReviewActionBar, SelectedAssetStrip, SlideAnalysisPanel, SourceAssetsPanel, contentManifest, cropStyle, derivativeObjectKey, deriveContentBoard, firstLine, formatElapsed, getContentItemIdentity, isDerivativeStale, lastLine, readStoredAnalysis, renderCropToJpeg, resolveContentStepResource, resolveContentVocabulary, swapFirstLine, swapLastLine, useContentConfig };
+export type { AlternatesPanelProps, AssetCropEditorProps, CaptionPanelProps, ContentAlternateOption, ContentBoard, ContentBoardCard, ContentBoardColumn, ContentBoardGate, ContentConfig, ContentDistributionDetailPageSlots, ContentDistributionsPageSlots, ContentFidelityCheck, ContentItemReviewPageSlots, ContentItemsPageSlots, ContentNoun, ContentOverviewPageSlots, ContentPayloadField, ContentPipelineBoardPageSlots, ContentPipelineBoardPageSlots as ContentPipelineWorkspacePageSlots, ContentPipelinesPageSlots, ContentProcessingStatus, ContentProcessingStep, ContentReviewAction, ContentReviewCardProps, ContentSidebarMiddleProps, ContentSidebarProps, ContentStepResourceBinding, ContentVocabulary, CropAspectOption, MyReviewQueuePanelProps, PayloadBodyProps, PostPreviewProps, PostPreviewSlide, ProcessingStateStripProps, RenderCropOptions, ReviewActionBarProps, ReviewMode, SelectedAssetStripProps, SlideAnalysisPanelProps, SourceAssetsPanelProps, StoredSlideAnalysis };