@elevasis/ui 2.70.0 → 2.72.0

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

@@ -100,7 +100,7 @@ declare const OntologyScopeSchema: z.ZodDefault<z.ZodObject<{
         aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
         route: z.ZodOptional<z.ZodString>;
     }, z.core.$loose>>>>;
-}, z.core.$strip>>;
+}, z.core.$strict>>;
 type OntologyScope = z.infer<typeof OntologyScopeSchema>;
 
 declare const SystemApiInterfaceSchema: z.ZodObject<{
@@ -241,6 +241,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 +256,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`. */
@@ -796,7 +808,7 @@ declare const OrganizationModelSchema: z.ZodObject<{
             aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
             route: z.ZodOptional<z.ZodString>;
         }, z.core.$loose>>>>;
-    }, z.core.$strip>>>;
+    }, z.core.$strict>>>;
     resources: z.ZodDefault<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodDiscriminatedUnion<[z.ZodObject<{
         id: z.ZodString;
         order: z.ZodDefault<z.ZodNumber>;
@@ -1266,9 +1278,13 @@ declare const ContentItemResponseSchema: 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>>;
     reviewedAt: z.ZodNullable<z.ZodString>;
@@ -1282,6 +1298,96 @@ declare const ContentItemResponseSchema: z.ZodObject<{
 }, z.core.$strip>;
 type ContentItemResponse = z.infer<typeof ContentItemResponseSchema>;
 
+/**
+ * `deriveContentBoard` -- a pure function of `(items, pipeline, now)`. No React, no
+ * hooks, no fetching. `content_items` has NO `step_key` column (only
+ * `content_item_attempts` does), so an item's current step is derived from
+ * `processingState`, whose declared shape is
+ * `Record<stepKey, { status: 'running' | 'success' | 'no_result' | 'skipped' | 'error';
+ * attemptId: string; executionId: string | null; attemptedAt: string; data?: unknown }>`.
+ * `'running'` (added 2026-08-14, the step-state model) is the only in-flight value;
+ * every other member is terminal.
+ *
+ * Placement rule (implemented exactly as follows):
+ *
+ * 1. Sort the pipeline's steps ascending by `order`. Ties break by `key` so the result
+ *    is deterministic.
+ * 2. An item's current step is the first step in that order whose `processingState`
+ *    entry is missing, or present with a status other than `'success'`. Rationale:
+ *    `processingState` records what has run; a step recorded `'success'` is behind the
+ *    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 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
+ *    keys appear in the catalog. This is the honest bucket for an item produced against
+ *    a step catalog that has since changed; unplaced items are never silently dropped
+ *    into column 1.
+ */
+interface ContentBoardCard {
+    item: ContentItemResponse;
+    /** Step key this item currently sits at. `null` when every declared step has succeeded. */
+    stepKey: string | null;
+    /** Milliseconds since `item.updatedAt`, measured against the `now` argument. */
+    ageMs: number;
+    /** True when this card is waiting on a person: its step's reviewMode is not 'none' and `reviewedAt` is null. */
+    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'>;
+    /** 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. */
+    gate?: ContentBoardGate;
+}
+interface ContentBoard {
+    columns: ContentBoardColumn[];
+    /** Cards whose every declared step succeeded. */
+    done: ContentBoardCard[];
+    /** Cards whose processingState names only step keys the catalog does not declare. */
+    unplaced: ContentBoardCard[];
+    /** True when the pipeline declares 0 or 1 steps -- the consumer renders pick-then-review, not columns. */
+    isCollapsed: boolean;
+}
+declare function deriveContentBoard(items: ContentItemResponse[], pipeline: ContentPipelineTemplate, now: number): ContentBoard;
+
+/**
+ * `getContentItemIdentity` -- a pure function that names a content item for display when
+ * `title` cannot be trusted to do it. The tenant `nirvana-marketing`'s drafts have no
+ * titles at all, so a title-first surface renders an empty or meaningless column. A
+ * post's identity is its opening line.
+ *
+ * Resolution order, first non-empty wins:
+ * 1. First non-blank line of `item.body`.
+ * 2. The first string-valued field of `item.payload`, taken in `payloadFields`
+ *    declaration order when that argument is supplied, otherwise `Object.keys` order.
+ *    Only a non-blank string value counts.
+ * 3. `item.title`, when non-blank.
+ * 4. The literal `'Untitled'`.
+ *
+ * The resolved candidate is then normalized: runs of whitespace collapse to one space,
+ * the result is trimmed, and anything longer than `maxLength` is truncated at the last
+ * word boundary at or before `maxLength` with a trailing `'…'` -- never mid-word.
+ * The source complaint this fixes is titles clipped mid-word
+ * (`MOCK Pipeline Walk S…`).
+ */
+declare function getContentItemIdentity(item: Pick<ContentItemResponse, 'title' | 'body' | 'payload'>, payloadFields?: ContentPayloadFieldDeclaration[], maxLength?: number): string;
+
 type SystemSidebarComponent = ComponentType;
 type SystemIconComponent = ComponentType<{
     size?: number;
@@ -1351,7 +1457,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;
 }
@@ -1359,9 +1465,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. */
@@ -1386,14 +1492,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;
@@ -1414,8 +1525,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
@@ -1582,6 +1700,14 @@ interface ContentReviewAction {
      * a one-click irreversible action.
      */
     consequence?: 'standard' | 'irreversible';
+    /**
+     * Disables this action's button -- e.g. the item has no open review gate to clear.
+     * Renders inert rather than firing a call that the server rejects. Pair with
+     * `disabledReason` so the reviewer sees why, not just a greyed-out button.
+     */
+    disabled?: boolean;
+    /** Shown in a Tooltip over the button while `disabled` is true. */
+    disabledReason?: string;
 }
 interface ReviewActionBarProps {
     /**
@@ -1663,6 +1789,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
@@ -1670,7 +1805,7 @@ 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;
 
 /** A single tenant-facing noun with singular and plural forms, e.g. `{ singular: 'Post', plural: 'Posts' }`. */
 interface ContentNoun {
@@ -1785,84 +1920,6 @@ interface ContentConfig {
  */
 declare function useContentConfig(): ContentConfig;
 
-/**
- * `deriveContentBoard` -- a pure function of `(items, pipeline, now)`. No React, no
- * hooks, no fetching. `content_items` has NO `step_key` column (only
- * `content_item_attempts` does), so an item's current step is derived from
- * `processingState`, whose declared shape is
- * `Record<stepKey, { status: 'success' | 'no_result' | 'skipped' | 'error'; data?: unknown }>`.
- *
- * Placement rule (implemented exactly as follows):
- *
- * 1. Sort the pipeline's steps ascending by `order`. Ties break by `key` so the result
- *    is deterministic.
- * 2. An item's current step is the first step in that order whose `processingState`
- *    entry is missing, or present with a status other than `'success'`. Rationale:
- *    `processingState` records what has run; a step recorded `'success'` is behind the
- *    item.
- * 3. If every declared step has a `'success'` entry, `stepKey` is `null` and the card
- *    goes in `done`.
- * 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
- *    keys appear in the catalog. This is the honest bucket for an item produced against
- *    a step catalog that has since changed; unplaced items are never silently dropped
- *    into column 1.
- */
-interface ContentBoardCard {
-    item: ContentItemResponse;
-    /** Step key this item currently sits at. `null` when every declared step has succeeded. */
-    stepKey: string | null;
-    /** Milliseconds since `item.updatedAt`, measured against the `now` argument. */
-    ageMs: number;
-    /** True when this card is waiting on a person: its step's reviewMode is not 'none' and `reviewedAt` is null. */
-    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'>;
-    /** 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. */
-    gate?: ContentBoardGate;
-}
-interface ContentBoard {
-    columns: ContentBoardColumn[];
-    /** Cards whose every declared step succeeded. */
-    done: ContentBoardCard[];
-    /** Cards whose processingState names only step keys the catalog does not declare. */
-    unplaced: ContentBoardCard[];
-    /** True when the pipeline declares 0 or 1 steps -- the consumer renders pick-then-review, not columns. */
-    isCollapsed: boolean;
-}
-declare function deriveContentBoard(items: ContentItemResponse[], pipeline: ContentPipelineTemplate, now: number): ContentBoard;
-
-/**
- * `getContentItemIdentity` -- a pure function that names a content item for display when
- * `title` cannot be trusted to do it. The tenant `nirvana-marketing`'s drafts have no
- * titles at all, so a title-first surface renders an empty or meaningless column. A
- * post's identity is its opening line.
- *
- * Resolution order, first non-empty wins:
- * 1. First non-blank line of `item.body`.
- * 2. The first string-valued field of `item.payload`, taken in `payloadFields`
- *    declaration order when that argument is supplied, otherwise `Object.keys` order.
- *    Only a non-blank string value counts.
- * 3. `item.title`, when non-blank.
- * 4. The literal `'Untitled'`.
- *
- * The resolved candidate is then normalized: runs of whitespace collapse to one space,
- * the result is trimmed, and anything longer than `maxLength` is truncated at the last
- * word boundary at or before `maxLength` with a trailing `'…'` -- never mid-word.
- * The source complaint this fixes is titles clipped mid-word
- * (`MOCK Pipeline Walk S…`).
- */
-declare function getContentItemIdentity(item: Pick<ContentItemResponse, 'title' | 'body' | 'payload'>, payloadFields?: ContentPayloadFieldDeclaration[], maxLength?: number): string;
-
 /**
  * Shared nav-item shape used by feature sidebar middle components.
  *
@@ -1897,19 +1954,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
@@ -1920,14 +1983,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. */
@@ -1936,22 +2006,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;
@@ -1974,5 +2048,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, CONTENT_ITEMS, ContentDistributionDetailPage, ContentDistributionsPage, ContentItemReviewPage, ContentItemsPage, ContentOverviewPage, ContentPipelineBoardPage, ContentPipelineBoardPage as 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, ContentPipelineBoardPageSlots, ContentPipelineBoardPageSlots as ContentPipelineWorkspacePageSlots, ContentPipelinesPageSlots, ContentProcessingStatus, ContentProcessingStep, ContentReviewAction, ContentReviewCardProps, ContentSidebarMiddleProps, ContentSidebarProps, ContentStepResourceBinding, ContentVocabulary, MyReviewQueuePanelProps, PayloadBodyProps, ProcessingStateStripProps, ReviewActionBarProps, ReviewMode };