@zeniai/client-epic-state 5.0.82-betaAS1 → 5.0.83-betaRR0

package/lib/entity/aiCfo/aiCfoState.d.ts

@@ -9,9 +9,13 @@ export interface AiCfoAnswerParagraph {
     }>;
 }
 export declare const ALL_AI_CFO_CHARTS_TYPES: readonly ["bar_chart", "pie_chart", "line_chart"];
-export declare const ALL_AI_CFO_VISUALIZATION_TYPES: readonly ["bar_chart", "pie_chart", "line_chart", "table"];
-export declare const toAiCfoVisualizationType: (v: string) => "bar_chart" | "pie_chart" | "line_chart" | "table";
-export declare const toAiCfoVisualizationTypeStrict: (v: string) => "bar_chart" | "pie_chart" | "line_chart" | "table" | undefined;
+export declare const ALL_AI_CFO_VISUALIZATION_TYPES: readonly ["bar_chart", "pie_chart", "line_chart", "table", "interactive_form"];
+export declare const ALL_INTERACTIVE_FORM_TYPES: readonly ["cards_creation", "card_policy"];
+export declare const toInteractiveFormType: (v: string) => "cards_creation" | "card_policy";
+export declare const toInteractiveFormTypeStrict: (v: string) => "cards_creation" | "card_policy" | undefined;
+export type InteractiveFormType = ReturnType<typeof toInteractiveFormType>;
+export declare const toAiCfoVisualizationType: (v: string) => "bar_chart" | "pie_chart" | "line_chart" | "table" | "interactive_form";
+export declare const toAiCfoVisualizationTypeStrict: (v: string) => "bar_chart" | "pie_chart" | "line_chart" | "table" | "interactive_form" | undefined;
 export type AiCfoVisualizationType = ReturnType<typeof toAiCfoVisualizationType>;
 export declare const toAiCfoChartType: (v: string) => "bar_chart" | "pie_chart" | "line_chart";
 export declare const toAiCfoChartTypeStrict: (v: string) => "bar_chart" | "pie_chart" | "line_chart" | undefined;
@@ -53,8 +57,196 @@ export interface ChartVisualization {
     lines?: string[];
     yFormat?: YFormat;
 }
+export interface CardsCardOption {
+    id: string;
+    label: string;
+    description?: string;
+}
+/**
+ * Card kind for AI Card Creation rows.
+ * - `vendor` = vendor-bound card.
+ * - `class` = department-scoped card. The wire format ships `department`;
+ *   the reducer maps it to `class` (the FE-side term for accounting class /
+ *   department) so it lines up with the rest of the codebase.
+ * - `category` = MCC category-scoped card. The wire format ships `category`
+ *   verbatim; there is no FE-side alias, so we keep the wire term.
+ *
+ * The Step 2 Card-cell dropdown filters by this kind so a row of one kind
+ * only sees swap targets of the same kind.
+ */
+export type CardsCardKind = 'vendor' | 'class' | 'category';
+/**
+ * Single entry in the unified vendor + department dropdown universe shipped
+ * by the AI controller for the `review` flow. Powers both the
+ * step-2 Card cell dropdown (filtered to entries with matching `kind`) and
+ * the step-1 "Add something else" search (no kind filter — user can add
+ * either).
+ */
+export interface CardNameOption {
+    id: string;
+    kind: CardsCardKind;
+    label: string;
+}
+/**
+ * Default `cardOptionId` (physical / virtual / subscription) assigned to
+ * every seeded card row. The AI Card Creation flow currently issues virtual
+ * credit cards only — this constant is kept in sync with
+ * `AI_CARD_CREATION_VIRTUAL_ONLY_CARD_OPTIONS` in `zeni-web-app-ui`.
+ */
+export declare const CARDS_CREATION_DEFAULT_CARD_OPTION_ID = "virtual";
+/**
+ * Shared base shape across both `review` and `create` AI Card Creation
+ * states. Holds the data derived from the controller's `suggested_cards[]`
+ * that's identical regardless of which step UX the user sees.
+ */
+export interface CardsCreationCommonData {
+    /**
+     * Full vendor + department + category universe (suggested +
+     * not-suggested), used to power the step-2 Card-cell dropdown (filtered
+     * by row kind) and, in `review` mode, the step-1 "Add something else"
+     * search.
+     */
+    cardNameOptions: CardNameOption[];
+    /**
+     * Physical / virtual / subscription dropdown options. Not shipped on the
+     * wire; populated at render time from the FE-owned
+     * `AI_CARD_CREATION_VIRTUAL_ONLY_CARD_OPTIONS` constant.
+     */
+    cardOptions: CardsCardOption[];
+    /**
+     * Map of `teamRow.id` / `cardRow.id` -> suggested owner `userId`.
+     * Resolved against `allUsers` (sourced from the tenant) at render time.
+     */
+    suggestedOwnerUserIdByTeamId: Record<string, ID | undefined>;
+}
+/**
+ * Initial data for the AI Card Creation interactive form. Discriminated on
+ * `mode`:
+ *
+ * - `review` (default, 2-step): AI suggests rows (mix of vendors +
+ *   departments + categories); user reviews them in step 1, then configures
+ *   one card per surviving row in step 2.
+ * - `create` (1-step): the FE seeds the step-2 editable table directly
+ *   from the `is_suggested: true` rows; step 1 is skipped.
+ *
+ * Both modes carry the same `cardNameOptions` universe so the step-2 Card
+ * dropdown behaves identically across modes.
+ */
+export type CardsCreationInitialData = (CardsCreationCommonData & {
+    mode: 'review';
+    teamRows: Array<{
+        avgMonthlySpend: string;
+        cardKind: CardsCardKind;
+        id: string;
+        label: string;
+        recommendedLimit: string;
+        recommendedLimitCadence?: string;
+    }>;
+}) | (CardsCreationCommonData & {
+    cardRows: Array<{
+        cardKind: CardsCardKind;
+        cardOptionId: string;
+        id: string;
+        /**
+         * Team-derived display label rendered in the card cell trigger
+         * (e.g. "Engineering"). Drives the row's first-letter avatar in
+         * step 2. Always populated for AI-seeded rows.
+         */
+        label: string;
+        recommendedLimit?: number;
+        suggestedOwnerUserId?: ID;
+    }>;
+    mode: 'create';
+});
+/**
+ * Per-policy allow / block bucket. CamelCase mirror of
+ * `DraftPolicyEntityPayload`.
+ */
+export interface CardPolicyDraftPolicyEntity {
+    categoryCodes: string[];
+    merchantNames: string[];
+}
+/**
+ * Spend-limit bucket per policy. `transaction` is the only cadence the
+ * BE ships today.
+ */
+export interface CardPolicySpendLimits {
+    transaction: number;
+}
+/**
+ * Single draft policy in FE state. Identity is positional — the reducer
+ * synthesizes a stable `id` (`draft-0`, `draft-1`, ...) at decode time
+ * since the BE doesn't ship one today.
+ */
+export interface CardPolicyDraftPolicy {
+    allowedEntity: CardPolicyDraftPolicyEntity;
+    applyToCards: string[];
+    blockedEntity: CardPolicyDraftPolicyEntity;
+    description: string;
+    id: string;
+    /** Enforcement mode (e.g. `"strict"`). Carried for guided submit;
+     * ignored by auto / upload submit. */
+    mode: string;
+    name: string;
+    requiredReceiptThreshold: number;
+    spendLimits: CardPolicySpendLimits;
+}
+export interface CardPolicyStep5Review {
+    draftPolicies: CardPolicyDraftPolicy[];
+    groupingSource: string;
+    prompt: string;
+}
+export interface CardPolicyWizardPlan {
+    step5Review: CardPolicyStep5Review;
+}
+/**
+ * Upload-mode metadata returned by the
+ * `policy-recommendation-from-upload` API alongside the wizard plan.
+ */
+export interface CardPolicyUploadSource {
+    confidenceScore: number;
+    fileName: string;
+    lowConfidenceFields: string[];
+}
+/**
+ * Initial data for the AI Card Policy interactive form. Discriminated on
+ * `policyKind`. All three modes consume the same `wizardPlan.step5Review`
+ * envelope; the wizard renders different surfaces per mode.
+ *
+ * - `auto` (1-step review): chip groups built directly from each draft
+ *   policy. Submit omits `mode` + `spend_limits` + `required_receipt_threshold`.
+ * - `guided` (5-step wizard): Steps 1–4 seeded from `draftPolicies[0]`,
+ *   Step 5 lists every draft. Submit includes all keys.
+ * - `upload` (3-step): upload → cards → review. `wizardPlan` is
+ *   `undefined` until the upload-recommendation API succeeds, then
+ *   populated alongside `source` metadata. Submit includes
+ *   `spend_limits` + `required_receipt_threshold`; omits `mode`.
+ */
+export type CardPolicyInitialData = {
+    policyKind: 'auto';
+    wizardPlan: CardPolicyWizardPlan;
+} | {
+    policyKind: 'guided';
+    wizardPlan: CardPolicyWizardPlan;
+} | {
+    policyKind: 'upload';
+    source?: CardPolicyUploadSource;
+    wizardPlan?: CardPolicyWizardPlan;
+};
+/**
+ * Visualization variant rendered as an interactive RHF form (in lieu of a
+ * chart or table). Discriminated on `formType`; each branch carries its own
+ * payload shape.
+ */
+export type InteractiveFormVisualization = {
+    formType: 'cards_creation';
+    payload: CardsCreationInitialData;
+} | {
+    formType: 'card_policy';
+    payload: CardPolicyInitialData;
+};
 export interface AiCfoVisualization {
-    data: TableVisualization | ChartVisualization;
+    data: TableVisualization | ChartVisualization | InteractiveFormVisualization;
     type: AiCfoVisualizationType;
 }
 export declare const toMessageSender: (v: string) => "user" | "agent";
@@ -112,7 +304,36 @@ export interface ChatSessionWithMessages {
     chatSession: ChatSession;
     questionAnswers: AiCfoQuestionWithAnswer[];
 }
+/**
+ * Discriminator for client-synthesized AI CFO answer bubbles. These are not
+ * Q/A pairs streamed from the backend — they are pushed locally by the AI
+ * CFO flow when it kicks off a cards or policy create from an interactive
+ * form, so the drawer can render a "Creating…" placeholder and later a
+ * "Created" success bubble while the corresponding mutation epic runs.
+ */
+export declare const ALL_SYNTHETIC_AI_CFO_ANSWER_KINDS: readonly ["creating_cards", "creating_policy", "created_cards", "created_policy"];
+export type SyntheticAiCfoAnswerKind = (typeof ALL_SYNTHETIC_AI_CFO_ANSWER_KINDS)[number];
+/**
+ * A locally-synthesized answer bubble (e.g. "Creating cards…", or "2 policies
+ * are created and saved" with preview tiles). Lives parallel to the streamed
+ * `questionAnswers` so the AI CFO renderer can swap the source answer's
+ * interactive form in-place with the bubble (and then with the success tile
+ * once the mutation completes).
+ *
+ * `sourceQuestionAnswerId` is the `questionAnswerId` of the streamed Q/A
+ * whose answer hosted the interactive form the user just submitted. Every
+ * synthetic is dispatched from a form-submit handler and every form lives
+ * inside an AI CFO answer, so this id is always known at dispatch time.
+ */
+export interface SyntheticAiCfoAnswer {
+    createdAt: ZeniDate;
+    entityIds: ID[];
+    id: ID;
+    kind: SyntheticAiCfoAnswerKind;
+    sourceQuestionAnswerId: ID;
+}
 export interface AiCfoState {
     aiCfoByChatSessionId: Record<ID, ChatSessionWithMessages>;
     partialQuestionAnswers: Record<ID, AiCfoQuestionWithAnswer | undefined>;
+    syntheticAnswersByChatSessionId: Record<ID, SyntheticAiCfoAnswer[]>;
 }

package/lib/entity/aiCfo/aiCfoState.js

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.toMessageTypeStrict = exports.toMessageSenderStrict = exports.toMessageType = exports.toMessageSender = exports.toAiCfoAnswerResponseTypeStrict = exports.toAiCfoAnswerStateTypeStrict = exports.toAiCfoAnswerResponseType = exports.toAiCfoAnswerStateType = exports.toYFormatScaleStrict = exports.toYFormatUnitStrict = exports.toYFormatTypeStrict = exports.toYFormatScale = exports.toYFormatUnit = exports.toYFormatType = exports.ALL_Y_FORMAT_SCALES = exports.ALL_Y_FORMAT_NON_CURRENCY_UNITS = exports.ALL_Y_FORMAT_TYPES = exports.ALL_AI_CFO_ANSWER_RESPONSE_TYPES = exports.ALL_AI_CFO_ANSWER_STATE_TYPES = exports.toAiCfoChartTypeStrict = exports.toAiCfoChartType = exports.toAiCfoVisualizationTypeStrict = exports.toAiCfoVisualizationType = exports.ALL_AI_CFO_VISUALIZATION_TYPES = exports.ALL_AI_CFO_CHARTS_TYPES = void 0;
+exports.ALL_SYNTHETIC_AI_CFO_ANSWER_KINDS = exports.toMessageTypeStrict = exports.toMessageSenderStrict = exports.toMessageType = exports.toMessageSender = exports.CARDS_CREATION_DEFAULT_CARD_OPTION_ID = exports.toAiCfoAnswerResponseTypeStrict = exports.toAiCfoAnswerStateTypeStrict = exports.toAiCfoAnswerResponseType = exports.toAiCfoAnswerStateType = exports.toYFormatScaleStrict = exports.toYFormatUnitStrict = exports.toYFormatTypeStrict = exports.toYFormatScale = exports.toYFormatUnit = exports.toYFormatType = exports.ALL_Y_FORMAT_SCALES = exports.ALL_Y_FORMAT_NON_CURRENCY_UNITS = exports.ALL_Y_FORMAT_TYPES = exports.ALL_AI_CFO_ANSWER_RESPONSE_TYPES = exports.ALL_AI_CFO_ANSWER_STATE_TYPES = exports.toAiCfoChartTypeStrict = exports.toAiCfoChartType = exports.toAiCfoVisualizationTypeStrict = exports.toAiCfoVisualizationType = exports.toInteractiveFormTypeStrict = exports.toInteractiveFormType = exports.ALL_INTERACTIVE_FORM_TYPES = exports.ALL_AI_CFO_VISUALIZATION_TYPES = exports.ALL_AI_CFO_CHARTS_TYPES = void 0;
 const stringToUnion_1 = require("../../commonStateTypes/stringToUnion");
 exports.ALL_AI_CFO_CHARTS_TYPES = [
     'bar_chart',
@@ -10,7 +10,16 @@ exports.ALL_AI_CFO_CHARTS_TYPES = [
 exports.ALL_AI_CFO_VISUALIZATION_TYPES = [
     ...exports.ALL_AI_CFO_CHARTS_TYPES,
     'table',
+    'interactive_form',
 ];
+exports.ALL_INTERACTIVE_FORM_TYPES = [
+    'cards_creation',
+    'card_policy',
+];
+const toInteractiveFormType = (v) => (0, stringToUnion_1.stringToUnion)(v, exports.ALL_INTERACTIVE_FORM_TYPES);
+exports.toInteractiveFormType = toInteractiveFormType;
+const toInteractiveFormTypeStrict = (v) => (0, stringToUnion_1.stringToUnionStrict)(v, exports.ALL_INTERACTIVE_FORM_TYPES);
+exports.toInteractiveFormTypeStrict = toInteractiveFormTypeStrict;
 const toAiCfoVisualizationType = (v) => (0, stringToUnion_1.stringToUnion)(v, exports.ALL_AI_CFO_VISUALIZATION_TYPES);
 exports.toAiCfoVisualizationType = toAiCfoVisualizationType;
 const toAiCfoVisualizationTypeStrict = (v) => (0, stringToUnion_1.stringToUnionStrict)(v, exports.ALL_AI_CFO_VISUALIZATION_TYPES);
@@ -69,6 +78,13 @@ const toAiCfoAnswerStateTypeStrict = (v) => (0, stringToUnion_1.stringToUnionStr
 exports.toAiCfoAnswerStateTypeStrict = toAiCfoAnswerStateTypeStrict;
 const toAiCfoAnswerResponseTypeStrict = (v) => (0, stringToUnion_1.stringToUnionStrict)(v, exports.ALL_AI_CFO_ANSWER_RESPONSE_TYPES);
 exports.toAiCfoAnswerResponseTypeStrict = toAiCfoAnswerResponseTypeStrict;
+/**
+ * Default `cardOptionId` (physical / virtual / subscription) assigned to
+ * every seeded card row. The AI Card Creation flow currently issues virtual
+ * credit cards only — this constant is kept in sync with
+ * `AI_CARD_CREATION_VIRTUAL_ONLY_CARD_OPTIONS` in `zeni-web-app-ui`.
+ */
+exports.CARDS_CREATION_DEFAULT_CARD_OPTION_ID = 'virtual';
 const ALL_MESSAGE_SENDERS = ['user', 'agent'];
 const ALL_MESSAGE_TYPES = ['plain_text', 'json'];
 const toMessageSender = (v) => (0, stringToUnion_1.stringToUnion)(v, ALL_MESSAGE_SENDERS);
@@ -79,3 +95,16 @@ const toMessageSenderStrict = (v) => (0, stringToUnion_1.stringToUnionStrict)(v,
 exports.toMessageSenderStrict = toMessageSenderStrict;
 const toMessageTypeStrict = (v) => (0, stringToUnion_1.stringToUnionStrict)(v, ALL_MESSAGE_TYPES);
 exports.toMessageTypeStrict = toMessageTypeStrict;
+/**
+ * Discriminator for client-synthesized AI CFO answer bubbles. These are not
+ * Q/A pairs streamed from the backend — they are pushed locally by the AI
+ * CFO flow when it kicks off a cards or policy create from an interactive
+ * form, so the drawer can render a "Creating…" placeholder and later a
+ * "Created" success bubble while the corresponding mutation epic runs.
+ */
+exports.ALL_SYNTHETIC_AI_CFO_ANSWER_KINDS = [
+    'creating_cards',
+    'creating_policy',
+    'created_cards',
+    'created_policy',
+];

package/lib/entity/cardPolicy/cardPolicyPayload.d.ts

@@ -0,0 +1,277 @@
+import { ID } from '../../commonStateTypes/common';
+import { ZeniAPIResponse } from '../../responsePayload';
+import { CardPolicyStats, CardPolicyTemplate, CardPolicyTemplateEntityList, CardPolicyTemplateMode, CardPolicyTemplateSpendLimits, ExtractedCardPolicyRules, MccCategory } from './cardPolicyState';
+export interface MccCategoryPayload {
+    count: number;
+    mcc_codes: string[];
+    name: string;
+}
+/**
+ * Wire shape for `GET /cards/1.0/cards/mcc-codes`. Beyond the universe of
+ * MCC categories used to populate the category search dropdown, the
+ * endpoint also ships **suggested** allow / block merchants and categories
+ * that the chip-pickers seed into their cloud body before the user starts
+ * editing.
+ *
+ * Field spellings (`*_catagories`) preserve the BE wire format verbatim;
+ * the camelCase mapper below corrects to `Categories`.
+ */
+export interface CardPolicyMccCategoriesPayload {
+    categories: MccCategoryPayload[];
+    suggested_allow_catagories?: MccCategoryPayload[];
+    suggested_allow_merchants?: string[];
+    suggested_block_catagories?: MccCategoryPayload[];
+    suggested_block_merchants?: string[];
+}
+export type CardPolicyMccCategoriesResponse = ZeniAPIResponse<CardPolicyMccCategoriesPayload>;
+export declare const toMccCategory: (payload: MccCategoryPayload) => MccCategory;
+/**
+ * Vendor row returned by `/accounting/1.0/vendors`. The card-policy
+ * vendor search dropdown only needs `vendor_id` + `vendor_name`; we
+ * deliberately ignore the rest of the payload to keep this slice
+ * independent of the heavy `vendor` entity store.
+ */
+export interface CardPolicyVendorSearchVendorPayload {
+    vendor_id: string;
+    vendor_name: string;
+}
+export interface CardPolicyVendorSearchData {
+    vendors: CardPolicyVendorSearchVendorPayload[];
+}
+export type CardPolicyVendorSearchResponse = ZeniAPIResponse<CardPolicyVendorSearchData>;
+export interface CardPolicyVendorSearchOption {
+    name: string;
+    vendorId: string;
+}
+export declare const toCardPolicyVendorSearchOption: (payload: CardPolicyVendorSearchVendorPayload) => CardPolicyVendorSearchOption;
+interface CardPolicyTemplateEntityListPayload {
+    category_codes: string[];
+    merchant_names: string[];
+}
+interface CardPolicyTemplateSpendLimitsPayload {
+    transaction: number | null;
+}
+/**
+ * Per-template request shape. `POST /cards/1.0/policy-templates` now
+ * accepts a bulk wrapper (`CreateCardPolicyTemplatesRequest`); this
+ * interface describes a single entry inside the `templates` array.
+ *
+ * `PUT /cards/1.0/policy-templates/{id}` (update) still consumes this
+ * shape directly — see `UpdateCardPolicyTemplateRequest` below.
+ */
+export interface CreateCardPolicyTemplateRequest {
+    allowedEntity: CardPolicyTemplateEntityList;
+    applyToCards: ID[];
+    blockedEntity: CardPolicyTemplateEntityList;
+    description: string;
+    mode: CardPolicyTemplateMode;
+    name: string;
+    /**
+     * `null` indicates the require-receipt toggle is off (no threshold
+     * configured). The BE accepts `null` and treats it as "no requirement";
+     * `0` means the user explicitly entered zero with the toggle on.
+     */
+    requiredReceiptThreshold: number | null;
+    spendLimits: CardPolicyTemplateSpendLimits;
+}
+export interface CreateCardPolicyTemplateRequestBody {
+    allowed_entity: CardPolicyTemplateEntityListPayload;
+    apply_to_cards: ID[];
+    blocked_entity: CardPolicyTemplateEntityListPayload;
+    description: string;
+    mode: string;
+    name: string;
+    required_receipt_threshold: number | null;
+    spend_limits: CardPolicyTemplateSpendLimitsPayload;
+}
+/**
+ * Bulk request for `POST /cards/1.0/policy-templates`. The single-policy
+ * create flow wraps its one request in a length-1 `templates` array;
+ * future multi-policy submit (AI CFO review step) sends N entries in a
+ * single round-trip.
+ *
+ * `sourceChatSessionId` ties the submit back to an AI CFO chat session so
+ * the BE can attribute the created templates to it. Manual create-page
+ * callers omit it.
+ */
+export interface CreateCardPolicyTemplatesRequest {
+    templates: CreateCardPolicyTemplateRequest[];
+    sourceChatSessionId?: string;
+}
+export interface CreateCardPolicyTemplatesRequestBody {
+    templates: CreateCardPolicyTemplateRequestBody[];
+    source_chat_session_id?: string;
+}
+export interface CardPolicyTemplatePayload {
+    allowed_entity: CardPolicyTemplateEntityListPayload;
+    applied_cards: ID[];
+    blocked_entity: CardPolicyTemplateEntityListPayload;
+    cards_count: number;
+    category_restrictions: unknown[];
+    created_at: string;
+    created_by: ID;
+    description: string;
+    mode: string;
+    name: string;
+    required_receipt_threshold: number | null;
+    spend_limits: CardPolicyTemplateSpendLimitsPayload;
+    status: string;
+    template_id: ID;
+    tenant_id: ID;
+    updated_at: string;
+}
+/**
+ * Per-template response envelope. Still returned by `PUT /policy-templates/{id}`,
+ * `GET /policy-templates/{id}`, and (as the row payload) the list endpoint.
+ * Also nested inside `CreateCardPolicyTemplatesResponseData.templates_created`.
+ */
+export interface CreateCardPolicyTemplateResponseData {
+    cards_applied: number;
+    template: CardPolicyTemplatePayload;
+}
+export type CreateCardPolicyTemplateResponse = ZeniAPIResponse<CreateCardPolicyTemplateResponseData>;
+/**
+ * Per-item error returned by the bulk POST when one or more templates in
+ * the request fail validation / persistence. The exact field shape is
+ * **TBD** with the BE — `message` is the only guaranteed field today; the
+ * rest are best-effort placeholders that callers should not assume to be
+ * present.
+ *
+ * TODO: lock down the shape (`index`, `name`, `code`) once the BE
+ * documents it. See plan §"Open question to resolve with BE".
+ */
+export interface BulkCreateCardPolicyTemplateErrorPayload {
+    message: string;
+    code?: string;
+    index?: number;
+    name?: string;
+}
+/**
+ * Wire shape returned by the bulk `POST /cards/1.0/policy-templates`.
+ * Partial success is allowed — `templates_created` holds the successfully
+ * created rows (each in the same envelope as the single endpoint), and
+ * `errors` holds per-item failures for the rest. `status.message` follows
+ * the "N of M templates created" convention.
+ */
+export interface CreateCardPolicyTemplatesResponseData {
+    errors: BulkCreateCardPolicyTemplateErrorPayload[];
+    templates_created: CreateCardPolicyTemplateResponseData[];
+}
+export type CreateCardPolicyTemplatesResponse = ZeniAPIResponse<CreateCardPolicyTemplatesResponseData>;
+/**
+ * Camel-cased mirror of `BulkCreateCardPolicyTemplateErrorPayload` stored
+ * on the create-card-policy view slice so the UI can render a partial-success
+ * banner without re-touching the wire types.
+ */
+export interface BulkCreateCardPolicyTemplateError {
+    message: string;
+    code?: string;
+    index?: number;
+    name?: string;
+}
+export type UpdateCardPolicyTemplateRequest = CreateCardPolicyTemplateRequest;
+export type UpdateCardPolicyTemplateRequestBody = CreateCardPolicyTemplateRequestBody;
+export type UpdateCardPolicyTemplateResponseData = CreateCardPolicyTemplateResponseData;
+export type UpdateCardPolicyTemplateResponse = CreateCardPolicyTemplateResponse;
+export type CardPolicyDetailResponseData = CreateCardPolicyTemplateResponseData;
+export type CardPolicyDetailResponse = CreateCardPolicyTemplateResponse;
+/**
+ * Aggregate counters returned alongside the templates list. Stored on
+ * the entity slice (alongside `cardPolicyTemplateById`) so any list
+ * surface can read it without re-fetching.
+ */
+export interface CardPolicyStatsPayload {
+    active_policies: number;
+    total_cards: number;
+    total_templates: number;
+}
+/**
+ * Each list row is wrapped in the same `{cards_applied, template}`
+ * envelope the create endpoint returns. Only the `template` portion is
+ * stored on the entity slice; `cards_applied` is a one-shot summary
+ * carried over from create and not surfaced in the list state today.
+ */
+export interface CardPolicyListRowPayload {
+    data: CreateCardPolicyTemplateResponseData;
+}
+export interface ListCardPolicyTemplatesResponseData {
+    stats: CardPolicyStatsPayload;
+    templates: CardPolicyListRowPayload[];
+}
+export type ListCardPolicyTemplatesResponse = ZeniAPIResponse<ListCardPolicyTemplatesResponseData>;
+export declare const toCardPolicyStats: (payload: CardPolicyStatsPayload) => CardPolicyStats;
+export declare const toCardPolicyTemplateList: (data: ListCardPolicyTemplatesResponseData) => CardPolicyTemplate[];
+export declare const toCardPolicyTemplate: (payload: CardPolicyTemplatePayload) => CardPolicyTemplate;
+/**
+ * Re-shape a single camelCase create request into the snake_case wire
+ * body. Used by the bulk-create mapper to build each entry of the
+ * `templates` array, and directly by the update epic (PUT) since the
+ * update endpoint still consumes a single object.
+ */
+export declare const toCreateCardPolicyTemplateRequestBody: (request: CreateCardPolicyTemplateRequest) => CreateCardPolicyTemplateRequestBody;
+/**
+ * Re-shape a bulk create request into the snake_case wire body for
+ * `POST /cards/1.0/policy-templates`. Maps each entry through
+ * `toCreateCardPolicyTemplateRequestBody` and only emits
+ * `source_chat_session_id` when the camelCase counterpart is defined,
+ * so manual-create callers don't ship a stray `undefined` over the wire.
+ */
+export declare const toCreateCardPolicyTemplatesRequestBody: (request: CreateCardPolicyTemplatesRequest) => CreateCardPolicyTemplatesRequestBody;
+/**
+ * Map a single bulk-response error payload to its camelCased view shape.
+ * Defensive against missing optional fields (see `BulkCreateCardPolicyTemplateErrorPayload`
+ * docstring — the BE contract isn't fully locked yet).
+ */
+export declare const toBulkCreateCardPolicyTemplateError: (payload: BulkCreateCardPolicyTemplateErrorPayload) => BulkCreateCardPolicyTemplateError;
+export declare const toUpdateCardPolicyTemplateRequestBody: (request: CreateCardPolicyTemplateRequest) => CreateCardPolicyTemplateRequestBody;
+/**
+ * Seed an edit-form draft (`CreateCardPolicyTemplateRequest`) from an
+ * existing camelCased `CardPolicyTemplate`. Used by the detail-fetch
+ * epic so the edit page can render with the saved values pre-populated.
+ */
+export declare const toCardPolicyEditFormDraft: (template: CardPolicyTemplate) => CreateCardPolicyTemplateRequest;
+/**
+ * Wire shape returned by `POST /cards/1.0/policy-documents/extract`.
+ * The backend OCRs / parses an uploaded policy document (PDF, image, etc.)
+ * and returns a best-effort set of policy rules + a confidence score.
+ *
+ * Consumers (manual `CardPolicyCreatePage` + AI CFO `CardPolicyInteractiveForm`)
+ * use `toExtractedCardPolicyRules` to map this onto the camelCase FE shape
+ * and then feed the result through `applyExtractedPolicyRulesToFormValues`
+ * (`@zeniai/web-components`) to seed the RHF form.
+ */
+export interface ExtractedCardPolicyRulesPayload {
+    allowed_entity: CardPolicyTemplateEntityListPayload;
+    blocked_entity: CardPolicyTemplateEntityListPayload;
+    confidence_score: number;
+    policy_name: string;
+    required_receipt_threshold: number;
+    transaction_limit: number;
+}
+export interface PolicyDocumentExtractResponseData {
+    extracted_rules: ExtractedCardPolicyRulesPayload;
+    message: string;
+}
+export type PolicyDocumentExtractResponse = ZeniAPIResponse<PolicyDocumentExtractResponseData>;
+export declare const toExtractedCardPolicyRules: (payload: ExtractedCardPolicyRulesPayload) => ExtractedCardPolicyRules;
+/**
+ * Wire shape returned by `POST /cards/1.0/ai-cfo/policy-recommendation-from-upload`.
+ * Chained after `extractPolicyDocument` succeeds in the AI CFO `upload`
+ * flow: the FE forwards the just-returned `extracted_rules` and the BE
+ * synthesizes a wizard plan + upload source metadata.
+ *
+ * The response mirrors the same `mode`-discriminated envelope the
+ * controller API ships for `auto` / `guided`, but always with `mode:
+ * "upload"` and a populated `wizard_plan.step_5_review`. The FE merges
+ * the returned `wizard_plan` + `source` into the in-flight AI CFO
+ * answer's `CardPolicyInitialData` via
+ * `updateAiCfoAnswerCardPolicyWizardPlan`.
+ */
+export interface CardPolicyRecommendationFromUploadResponseData {
+    mode: 'upload';
+    source: import('../aiCfo/aiCfoPayload').CardPolicyUploadSourcePayload;
+    tenant_id: string;
+    wizard_plan: import('../aiCfo/aiCfoPayload').CardPolicyWizardPlanPayload;
+}
+export type CardPolicyRecommendationFromUploadResponse = ZeniAPIResponse<CardPolicyRecommendationFromUploadResponseData>;
+export {};