@elevasis/ui 2.69.0 → 2.71.0

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

@@ -1251,6 +1251,124 @@ declare const OrganizationModelSchema: z.ZodObject<{
 type OrganizationModel = z.infer<typeof OrganizationModelSchema>;
 type OrganizationModelResourceKind = z.infer<typeof ResourceKindSchema>;
 
+declare const ContentItemResponseSchema: z.ZodObject<{
+    id: z.ZodString;
+    organizationId: z.ZodString;
+    title: z.ZodString;
+    body: z.ZodNullable<z.ZodString>;
+    payload: z.ZodUnknown;
+    status: z.ZodString;
+    pillar: z.ZodNullable<z.ZodString>;
+    pipelineId: z.ZodNullable<z.ZodString>;
+    clientId: z.ZodNullable<z.ZodString>;
+    sourceAssetId: z.ZodNullable<z.ZodString>;
+    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>>;
+    reviewedAt: z.ZodNullable<z.ZodString>;
+    reviewedBy: z.ZodNullable<z.ZodString>;
+    reviewerFeedback: z.ZodNullable<z.ZodString>;
+    rejectReason: z.ZodNullable<z.ZodString>;
+    createdBy: z.ZodNullable<z.ZodString>;
+    updatedBy: z.ZodNullable<z.ZodString>;
+    createdAt: z.ZodString;
+    updatedAt: z.ZodString;
+}, 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, `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;
+
 type SystemSidebarComponent = ComponentType;
 type SystemIconComponent = ComponentType<{
     size?: number;
@@ -1293,6 +1411,12 @@ interface ContentItemsPageSlots {
     /** Optional content rendered after the page title. Default: nothing rendered. */
     headerActions?: ReactNode;
 }
+/**
+ * Flat, cross-pipeline items report -- kept as a reachable filtered view rather than
+ * primary navigation (usability review Proposal, Decision 3; finding 1). The sidebar's
+ * review-queue nav entry links here with `?review=pending`; `MyReviewQueuePanel`'s
+ * "See all" does the same.
+ */
 declare function ContentItemsPage({ headerActions }?: ContentItemsPageSlots): react_jsx_runtime.JSX.Element;
 
 interface ContentItemReviewPageSlots {
@@ -1314,44 +1438,18 @@ interface ContentPipelinesPageSlots {
  */
 declare function ContentPipelinesPage({ headerActions }?: ContentPipelinesPageSlots): react_jsx_runtime.JSX.Element;
 
-interface ContentProduceSlotProps {
-    pipeline: ContentPipelineTemplate;
-}
-
 interface ContentPipelineWorkspacePageSlots {
     /** Optional content rendered after the page title. Default: nothing rendered. */
     headerActions?: ReactNode;
-    /** Overrides the `produce` tab's default content. See `ProduceTabProps.render`. */
-    renderProduce?: (props: ContentProduceSlotProps) => ReactNode;
 }
 /**
  * Pipeline workspace -- tabbed via `?tab=`, matching how `LeadGenListDetailPage`
- * (`../../../lead-gen/pages/list-detail/ListDetailPage.tsx`) already does it: `overview`
- * / `sources` / `produce` / `runs`.
+ * (`../../../lead-gen/pages/list-detail/ListDetailPage.tsx`) already does it.
  */
-declare function ContentPipelineWorkspacePage({ pipelineId, headerActions, renderProduce }: {
+declare function ContentPipelineWorkspacePage({ pipelineId, headerActions }: {
     pipelineId: string;
 } & ContentPipelineWorkspacePageSlots): react_jsx_runtime.JSX.Element;
 
-interface ContentSettingsPageSlots {
-    /** Optional content rendered after the page title. Default: nothing rendered. */
-    headerActions?: ReactNode;
-}
-/**
- * Rules and artifacts -- browses `content:`-prefixed artifacts for a pipeline: version
- * history and activation state, read-only. Mirrors `CrmSettingsPage`, but actually
- * mounted (`CrmSettingsPage` exists in the package with no Command Center route).
- *
- * Only `GET /acquisition/artifacts` and `POST /acquisition/artifacts` exist -- there is
- * no route to update, deactivate, or re-version an artifact. `isActive` and `version`
- * render as read-only state; this page does not add an activate/deactivate control
- * wired to nothing (binding constraint c). It also does not add a create form: the API
- * supports create, but nothing in this wave's scope specifies what a rules document's
- * `content` shape should be per artifact kind, so authoring stays out of this page for
- * now rather than guessing a schema.
- */
-declare function ContentSettingsPage({ headerActions }?: ContentSettingsPageSlots): react_jsx_runtime.JSX.Element;
-
 interface ContentDistributionsPageSlots {
     /** Optional content rendered after the page title. Default: nothing rendered. */
     headerActions?: ReactNode;
@@ -1403,10 +1501,8 @@ interface ContentPageOverrides {
     itemReview?: ContentItemReviewPageSlots;
     /** Slot props injected into `ContentPipelinesPage`. */
     pipelines?: ContentPipelinesPageSlots;
-    /** Slot props (including the `produce` tab's `renderProduce` render prop) injected into `ContentPipelineWorkspacePage`. */
+    /** Slot props injected into `ContentPipelineWorkspacePage`. */
     pipelineWorkspace?: ContentPipelineWorkspacePageSlots;
-    /** Slot props injected into `ContentSettingsPage`. */
-    settings?: ContentSettingsPageSlots;
 }
 /**
  * Extended `SystemModule` for the content feature that carries optional page overrides
@@ -1424,11 +1520,11 @@ interface ContentSystemModule extends SystemModule {
  * plain string matching the System path rather than an import from `@repo/core/content`
  * or the OM System declaration -- this package stays data-free by design (D6).
  *
- * `sidebar` wires in `ContentSidebar` (nav items + `MyReviewQueue`). Page overrides and
- * OM-derived config are consumed by the caller via `useContentConfig` and the individual
- * page components, matching the `LeadGenSystemModule` pattern. `pages` is left unset
- * here -- every page above renders its byte-identical default until a consumer supplies
- * an override, most notably `pipelineWorkspace.renderProduce` for the `produce` tab slot.
+ * `sidebar` wires in `ContentSidebar` (the two-entry nav). Page overrides and OM-derived
+ * config are consumed by the caller via `useContentConfig` and the individual page
+ * components, matching the `LeadGenSystemModule` pattern. `pages` is left unset here --
+ * every page above renders its byte-identical default until a consumer supplies an
+ * override.
  */
 declare const contentManifest: ContentSystemModule;
 
@@ -1560,6 +1656,27 @@ interface ContentReviewAction {
     feedbackPlaceholder?: string;
     /** Feedback below one non-whitespace character disables the modal's submit button. */
     feedbackRequired?: boolean;
+    /**
+     * Grades this action by consequence (proposal "grade actions by consequence" /
+     * finding 10): publishing is irreversible and outward-facing -- the video pipeline's
+     * Gate C says "never automate this one away" -- while approving a draft costs nothing
+     * to undo. Defaults to `'standard'`, which reproduces today's rendering exactly
+     * (`variant="light"`, no forced confirmation). `'irreversible'` renders the button
+     * filled in `var(--color-warning)` (or `var(--color-error)` when `tone: 'danger'` is
+     * also set) instead of light, and always gates behind a confirmation or feedback modal
+     * carrying a standing warning line, even if the action itself set neither
+     * `requiresConfirmation` nor `requiresFeedback` -- so a caller cannot accidentally ship
+     * 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 {
     /**
@@ -1595,8 +1712,12 @@ interface ContentFidelityCheck {
     note?: string;
 }
 interface ContentReviewCardProps {
-    /** Display handle -- `content_items.title` in the eventual schema. */
-    title: string;
+    /**
+     * Display handle -- `content_items.title` in the eventual schema. Omit it where the
+     * surrounding page already carries the same identity as its heading; repeating it
+     * inside the card puts the same sentence on screen twice.
+     */
+    title?: string;
     /** Presentational only; the caller decides what to render for each mode. */
     reviewMode: ReviewMode;
     /** The human's canonical, editable text. */
@@ -1646,6 +1767,36 @@ interface ContentReviewCardProps {
  */
 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;
 
+/** A single tenant-facing noun with singular and plural forms, e.g. `{ singular: 'Post', plural: 'Posts' }`. */
+interface ContentNoun {
+    singular: string;
+    plural: string;
+}
+/**
+ * The shell's vocabulary for the content feature: what a tenant calls its content
+ * items, where they get distributed, and the fixed labels around the pipeline and
+ * board chrome. Every field defaults to the generic table-name-shaped label so a
+ * tenant that has not declared a `vocabulary` block still gets a coherent shell.
+ */
+interface ContentVocabulary {
+    item: ContentNoun;
+    distribution: ContentNoun;
+    pipeline: ContentNoun;
+    board: string;
+    reviewQueue: string;
+}
+declare const DEFAULT_CONTENT_VOCABULARY: ContentVocabulary;
+/**
+ * Reads the content System's declared vocabulary off `system.config.vocabulary` --
+ * the same optional, tenant-authored slice of `config` that `getDefaultPipelineId`
+ * already reads for `defaultPipelineId` in `useContentConfig.ts` (no schema change:
+ * `config` is `Record<string, JsonValue>` and this is a second key on it). Merges over
+ * `DEFAULT_CONTENT_VOCABULARY` field by field, so a partial declaration only overrides
+ * what it actually names. `undefined` model, a missing `vocabulary` block, or any
+ * wrongly-shaped value all resolve to the defaults -- this never throws.
+ */
+declare function resolveContentVocabulary(model: OrganizationModel | undefined): ContentVocabulary;
+
 interface ContentStepResourceBinding {
     /** The OM Resource id that runs this step. */
     resourceId: string;
@@ -1704,6 +1855,13 @@ interface ContentConfig {
      * configured" rather than throwing.
      */
     resolveStepResource: (step: Pick<ContentPipelineStepEntry, 'actionId'>) => ContentStepResourceBinding | undefined;
+    /**
+     * The tenant's declared vocabulary for the content shell -- item / distribution /
+     * pipeline nouns and the fixed board labels. See {@link resolveContentVocabulary}.
+     * Defaults to {@link DEFAULT_CONTENT_VOCABULARY} when the model or its `vocabulary`
+     * declaration is absent, so consuming shell chrome never renders a blank label.
+     */
+    vocabulary: ContentVocabulary;
 }
 /**
  * `useContentConfig` is `useLeadGenConfig`'s twin for the content System: a pure
@@ -1722,14 +1880,6 @@ interface ContentConfig {
  */
 declare function useContentConfig(): ContentConfig;
 
-interface ContentSidebarProps {
-    /** Replace the default `ContentSidebarMiddle` with custom middle content. Leave unset for the default layout. */
-    children?: ReactNode;
-}
-declare const ContentSidebar: ({ children }?: ContentSidebarProps) => react_jsx_runtime.JSX.Element;
-
-declare const ContentSidebarTop: () => react_jsx_runtime.JSX.Element;
-
 /**
  * Shared nav-item shape used by feature sidebar middle components.
  *
@@ -1762,12 +1912,63 @@ interface NavItem {
     exact: boolean;
 }
 
+interface ContentSidebarProps {
+    /**
+     * Tenant-authored authoring surfaces for the `Create` 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:
+     *
+     * ```tsx
+     * const sidebar = () => <ContentSidebar createItems={[{ label: 'Draft a Post', to: '/content/write', icon: IconPencil, exact: false }]} />
+     * ```
+     */
+    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;
+
+/**
+ * Static two-entry default, built from {@link DEFAULT_CONTENT_VOCABULARY}. Exists for
+ * consumers that spread it at module load time (see `extend-content.md`), where a
+ * tenant's declared vocabulary isn't available. `ContentSidebarMiddle` itself renders
+ * the live, vocabulary-aware version instead of this constant.
+ */
 declare const CONTENT_ITEMS: NavItem[];
 interface ContentSidebarMiddleProps {
-    /** Override the default nav items. Defaults to {@link CONTENT_ITEMS}. */
+    /**
+     * 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.
+     *
+     * 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.
+     */
+    createItems?: NavItem[];
+    /** Override the pipeline nav items. Defaults to the two-entry nav built from the tenant's declared vocabulary. */
     items?: NavItem[];
 }
-declare const ContentSidebarMiddle: ({ items }?: ContentSidebarMiddleProps) => react_jsx_runtime.JSX.Element;
+/**
+ * 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.
+ *
+ * **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
+ * 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;
 
 interface MyReviewQueuePanelProps {
     onItemClick: (itemId: string) => void;
@@ -1775,14 +1976,20 @@ interface MyReviewQueuePanelProps {
     showSectionLabel?: boolean;
 }
 /**
- * `MyReviewQueue` -- mirrors `MyTasksPanel` for the content System's sidebar workbench.
+ * `MyReviewQueue` -- mirrors `MyTasksPanel` for the content System's sidebar workbench,
+ * and is the review queue's second way in (usability review Proposal, Decision 3): a
+ * 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
  * 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
+ * screen ages, and the operational question is always what has been sitting the
+ * longest.
  */
 declare function MyReviewQueuePanel({ onItemClick, onSeeAll, showSectionLabel }: MyReviewQueuePanelProps): react_jsx_runtime.JSX.Element;
 
-export { AlternatesPanel, CONTENT_ITEMS, ContentDistributionDetailPage, ContentDistributionsPage, ContentItemReviewPage, ContentItemsPage, ContentOverviewPage, ContentPipelineWorkspacePage, ContentPipelinesPage, ContentReviewCard, ContentSettingsPage, ContentSidebar, ContentSidebarMiddle, ContentSidebarTop, MyReviewQueuePanel, PayloadBody, ProcessingStateStrip, ReviewActionBar, contentManifest, firstLine, formatElapsed, lastLine, resolveContentStepResource, swapFirstLine, swapLastLine, useContentConfig };
-export type { AlternatesPanelProps, ContentAlternateOption, ContentConfig, ContentDistributionDetailPageSlots, ContentDistributionsPageSlots, ContentFidelityCheck, ContentItemReviewPageSlots, ContentItemsPageSlots, ContentOverviewPageSlots, ContentPayloadField, ContentPipelineWorkspacePageSlots, ContentPipelinesPageSlots, ContentProcessingStatus, ContentProcessingStep, ContentProduceSlotProps, ContentReviewAction, ContentReviewCardProps, ContentSettingsPageSlots, ContentSidebarMiddleProps, ContentSidebarProps, ContentStepResourceBinding, MyReviewQueuePanelProps, PayloadBodyProps, ProcessingStateStripProps, ReviewActionBarProps, ReviewMode };
+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 };