@zeniai/client-epic-state 5.0.83 → 5.0.84-beta24RJ

package/lib/entity/cardPolicy/extractPolicyDocumentEpic.js

@@ -1,68 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.extractPolicyDocumentEpic = void 0;
-const rxjs_1 = require("rxjs");
-const operators_1 = require("rxjs/operators");
-const responsePayload_1 = require("../../responsePayload");
-const cardPolicyReducer_1 = require("./cardPolicyReducer");
-/**
- * Build a multipart `FormData` body for `POST /cards/1.0/policy-documents/extract`.
- *
- * Uses the same `attachment_file_<i>` / `attachment_json_<i>` field-naming
- * convention as the charge-card receipt upload (`uploadReceipts.ts` in
- * `web-components`) so backends that already support that wire shape
- * accept this endpoint without bespoke parsing.
- */
-const buildPolicyDocumentFormData = (files) => {
-    const data = new FormData();
-    files.forEach((file, index) => {
-        data.append(`attachment_file_${index}`, file);
-        const attachmentJson = JSON.stringify({
-            file_name: file.name,
-            content_type: file.type,
-            size: file.size,
-        });
-        data.append(`attachment_json_${index}`, attachmentJson);
-    });
-    return data;
-};
-/**
- * Listens for `extractPolicyDocument`, POSTs the file(s) as multipart
- * form-data to the cards micro-service's policy-document extract endpoint,
- * and dispatches success / failure into the entity slice.
- *
- * Consumed by:
- *  - Manual `CardPolicyCreatePage` (read result via
- *    `getExtractedCardPolicyRules` then pre-fill the RHF form via
- *    `applyExtractedPolicyRulesToFormValues` from `@zeniai/web-components`).
- *  - (Future) AI CFO upload surface — same action + selector contract.
- */
-const extractPolicyDocumentEpic = (actions$, _state$, zeniAPI) => actions$.pipe((0, operators_1.filter)(cardPolicyReducer_1.extractPolicyDocument.match), 
-// `switchMap` (vs `mergeMap`) cancels any in-flight extract whenever a
-// new upload is dispatched. With `mergeMap` an older, slower response
-// could win the race: `updatePolicyDocumentExtractionSuccess` would
-// fire with stale `extractedRules` and the chained bridge epic would
-// pair them with whatever `aiCfoAnswerId` / `aiCfoChatSessionId` are
-// currently in state — recommending the old file's rules against the
-// wrong AI CFO answer.
-(0, operators_1.switchMap)((action) => {
-    const formData = buildPolicyDocumentFormData(action.payload.files);
-    return zeniAPI
-        .postFormData(`${zeniAPI.apiEndPoints.cardMicroServiceBaseUrl}/1.0/policy-documents/extract`, formData)
-        .pipe((0, operators_1.mergeMap)((response) => {
-        if ((0, responsePayload_1.isSuccessStatus)(response) &&
-            response.data != null &&
-            response.data.extracted_rules != null) {
-            return (0, rxjs_1.of)((0, cardPolicyReducer_1.updatePolicyDocumentExtractionSuccess)(response.data.extracted_rules));
-        }
-        return (0, rxjs_1.of)((0, cardPolicyReducer_1.updatePolicyDocumentExtractionFailure)(response.status));
-    }), (0, operators_1.catchError)((error) => (0, rxjs_1.of)((0, cardPolicyReducer_1.updatePolicyDocumentExtractionFailure)((0, responsePayload_1.createZeniAPIStatus)('Unexpected Error', 'Extract card-policy document REST API call errored out' +
-        JSON.stringify(error))))), 
-    // `clearPolicyDocumentExtraction` (e.g. user clicks the "× Policy.pdf"
-    // pill) tears down the in-flight extract subscription, so a late
-    // response can't re-flip `policyDocumentExtraction.fetchState` back
-    // to `Completed` or repopulate `extractedRules` after the user
-    // already dismissed the upload.
-    (0, operators_1.takeUntil)(actions$.pipe((0, operators_1.filter)(cardPolicyReducer_1.clearPolicyDocumentExtraction.match))));
-}));
-exports.extractPolicyDocumentEpic = extractPolicyDocumentEpic;

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

@@ -1,26 +0,0 @@
-import { ActionsObservable, StateObservable } from 'redux-observable';
-import { Observable } from 'rxjs';
-import { RootState } from '../../reducer';
-import { ZeniAPI } from '../../zeniAPI';
-import { fetchCardPolicyVendorOptions, updateCardPolicyVendorOptions, updateCardPolicyVendorOptionsFailure } from './cardPolicyReducer';
-export type ActionType = ReturnType<typeof fetchCardPolicyVendorOptions> | ReturnType<typeof updateCardPolicyVendorOptions> | ReturnType<typeof updateCardPolicyVendorOptionsFailure>;
-/**
- * Card-policy vendor search.
- *
- * Listens for `fetchCardPolicyVendorOptions` and hits the same
- * `/accounting/1.0/vendors` endpoint the Vendors-tab uses, but writes
- * results onto the dedicated `cardPolicyState.vendorSearch` slice — no
- * fan-out to the global `vendor` / `account` / `class` / `vendorList`
- * entities. That isolation is important: the user may be configuring a
- * card policy in parallel with browsing the Vendors tab, and we don't
- * want either flow to clobber the other's list state.
- *
- * Uses `switchMap` so the latest typed search wins — earlier in-flight
- * requests are abandoned, which is the right semantics for a
- * search-as-you-type UX.
- *
- * Consumers:
- *  - Manual `CardPolicyCreate / EditScreen`
- *  - AI CFO `CardPolicyInteractiveForm` (vendor step)
- */
-export declare const fetchCardPolicyVendorOptionsEpic: (actions$: ActionsObservable<ActionType>, _state$: StateObservable<RootState>, zeniAPI: ZeniAPI) => Observable<ActionType>;

package/lib/entity/cardPolicy/fetchCardPolicyVendorOptionsEpic.js

@@ -1,47 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.fetchCardPolicyVendorOptionsEpic = void 0;
-const rxjs_1 = require("rxjs");
-const operators_1 = require("rxjs/operators");
-const responsePayload_1 = require("../../responsePayload");
-const cardPolicyReducer_1 = require("./cardPolicyReducer");
-const buildQuery = (searchString) => ({
-    view: 'vendor_list',
-    page_token: null,
-    sort_by: 'year_to_date_spend',
-    sort_order: 'desc',
-    search_text: searchString,
-    vendor_name: searchString,
-});
-/**
- * Card-policy vendor search.
- *
- * Listens for `fetchCardPolicyVendorOptions` and hits the same
- * `/accounting/1.0/vendors` endpoint the Vendors-tab uses, but writes
- * results onto the dedicated `cardPolicyState.vendorSearch` slice — no
- * fan-out to the global `vendor` / `account` / `class` / `vendorList`
- * entities. That isolation is important: the user may be configuring a
- * card policy in parallel with browsing the Vendors tab, and we don't
- * want either flow to clobber the other's list state.
- *
- * Uses `switchMap` so the latest typed search wins — earlier in-flight
- * requests are abandoned, which is the right semantics for a
- * search-as-you-type UX.
- *
- * Consumers:
- *  - Manual `CardPolicyCreate / EditScreen`
- *  - AI CFO `CardPolicyInteractiveForm` (vendor step)
- */
-const fetchCardPolicyVendorOptionsEpic = (actions$, _state$, zeniAPI) => actions$.pipe((0, operators_1.filter)(cardPolicyReducer_1.fetchCardPolicyVendorOptions.match), (0, operators_1.switchMap)((action) => {
-    const query = buildQuery(action.payload.searchString);
-    const apiUrl = `${zeniAPI.apiEndPoints.accountMicroServiceBaseUrl}/1.0/vendors` +
-        `?query=${encodeURIComponent(JSON.stringify(query))}`;
-    return zeniAPI.getJSON(apiUrl).pipe((0, operators_1.switchMap)((response) => {
-        if ((0, responsePayload_1.isSuccessStatus)(response) && response.data != null) {
-            return (0, rxjs_1.of)((0, cardPolicyReducer_1.updateCardPolicyVendorOptions)(response.data));
-        }
-        return (0, rxjs_1.of)((0, cardPolicyReducer_1.updateCardPolicyVendorOptionsFailure)(response.status));
-    }), (0, operators_1.catchError)((error) => (0, rxjs_1.of)((0, cardPolicyReducer_1.updateCardPolicyVendorOptionsFailure)((0, responsePayload_1.createZeniAPIStatus)('Unexpected Error', 'Fetch card policy vendor options REST API call errored out' +
-        JSON.stringify(error))))));
-}));
-exports.fetchCardPolicyVendorOptionsEpic = fetchCardPolicyVendorOptionsEpic;

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

@@ -1,25 +0,0 @@
-import { ActionsObservable, StateObservable } from 'redux-observable';
-import { Observable } from 'rxjs';
-import { RootState } from '../../reducer';
-import { fetchCardPolicyRecommendationFromUpload, updatePolicyDocumentExtractionSuccess } from './cardPolicyReducer';
-export type ActionType = ReturnType<typeof updatePolicyDocumentExtractionSuccess> | ReturnType<typeof fetchCardPolicyRecommendationFromUpload>;
-/**
- * Bridge epic — chains the AI CFO `upload`-mode flow's two API hops.
- *
- * The first hop (`extractPolicyDocument` → multipart POST to
- * `policy-documents/extract`) lives on the cardPolicy slice and is
- * shared with the manual `CardPolicyCreatePage`. The second hop
- * (`fetchCardPolicyRecommendationFromUpload` → JSON POST to
- * `ai-cfo/policy-recommendation-from-upload`) is AI-CFO only.
- *
- * The chain is gated on `policyDocumentExtraction.aiCfoAnswerId` being
- * populated — manual callers leave it undefined, so the bridge is a
- * silent no-op there.
- *
- * Splitting this off from `policyRecommendationFromUploadEpic` keeps
- * the wizard component a pure renderer: it dispatches
- * `extractPolicyDocument(files, answerId, chatSessionId)` once, then
- * subscribes to `cardPolicyState` lifecycle flags to drive its
- * "Extracting…" / "Recommending…" pill.
- */
-export declare const policyDocumentExtractionToRecommendationBridgeEpic: (actions$: ActionsObservable<ActionType>, state$: StateObservable<RootState>) => Observable<ActionType>;

package/lib/entity/cardPolicy/policyDocumentExtractionToRecommendationBridgeEpic.js

@@ -1,39 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.policyDocumentExtractionToRecommendationBridgeEpic = void 0;
-const rxjs_1 = require("rxjs");
-const operators_1 = require("rxjs/operators");
-const cardPolicyReducer_1 = require("./cardPolicyReducer");
-/**
- * Bridge epic — chains the AI CFO `upload`-mode flow's two API hops.
- *
- * The first hop (`extractPolicyDocument` → multipart POST to
- * `policy-documents/extract`) lives on the cardPolicy slice and is
- * shared with the manual `CardPolicyCreatePage`. The second hop
- * (`fetchCardPolicyRecommendationFromUpload` → JSON POST to
- * `ai-cfo/policy-recommendation-from-upload`) is AI-CFO only.
- *
- * The chain is gated on `policyDocumentExtraction.aiCfoAnswerId` being
- * populated — manual callers leave it undefined, so the bridge is a
- * silent no-op there.
- *
- * Splitting this off from `policyRecommendationFromUploadEpic` keeps
- * the wizard component a pure renderer: it dispatches
- * `extractPolicyDocument(files, answerId, chatSessionId)` once, then
- * subscribes to `cardPolicyState` lifecycle flags to drive its
- * "Extracting…" / "Recommending…" pill.
- */
-const policyDocumentExtractionToRecommendationBridgeEpic = (actions$, state$) => actions$.pipe((0, operators_1.filter)(cardPolicyReducer_1.updatePolicyDocumentExtractionSuccess.match), (0, operators_1.mergeMap)((action) => {
-    const extraction = state$.value.cardPolicyState.policyDocumentExtraction;
-    const aiCfoAnswerId = extraction.aiCfoAnswerId;
-    const aiCfoChatSessionId = extraction.aiCfoChatSessionId;
-    const extractedRules = extraction.extractedRules;
-    if (aiCfoAnswerId == null ||
-        aiCfoChatSessionId == null ||
-        extractedRules == null) {
-        return rxjs_1.EMPTY;
-    }
-    void action;
-    return (0, rxjs_1.of)((0, cardPolicyReducer_1.fetchCardPolicyRecommendationFromUpload)(aiCfoAnswerId, aiCfoChatSessionId, extractedRules));
-}));
-exports.policyDocumentExtractionToRecommendationBridgeEpic = policyDocumentExtractionToRecommendationBridgeEpic;

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

@@ -1,23 +0,0 @@
-import { ActionsObservable, StateObservable } from 'redux-observable';
-import { Observable } from 'rxjs';
-import { updateAiCfoAnswerCardPolicyWizardPlan } from '../aiCfo/aiCfoReducer';
-import { RootState } from '../../reducer';
-import { ZeniAPI } from '../../zeniAPI';
-import { clearPolicyDocumentExtraction, fetchCardPolicyRecommendationFromUpload, updatePolicyRecommendationFromUploadFailure, updatePolicyRecommendationFromUploadSuccess } from './cardPolicyReducer';
-export type ActionType = ReturnType<typeof fetchCardPolicyRecommendationFromUpload> | ReturnType<typeof updatePolicyRecommendationFromUploadSuccess> | ReturnType<typeof updatePolicyRecommendationFromUploadFailure> | ReturnType<typeof updateAiCfoAnswerCardPolicyWizardPlan> | ReturnType<typeof clearPolicyDocumentExtraction>;
-/**
- * Listens for `fetchCardPolicyRecommendationFromUpload` and POSTs the
- * just-extracted policy rules to the AI-CFO recommendation endpoint.
- *
- * On success — dispatches BOTH:
- *  - `updatePolicyRecommendationFromUploadSuccess` (flips the
- *    cardPolicy slice's recommendation lifecycle to `Completed`), and
- *  - `updateAiCfoAnswerCardPolicyWizardPlan` (patches the in-flight AI
- *    CFO answer's `CardPolicyInitialData` so the wizard can advance from
- *    Step 1 → Step 2 in the upload variant).
- *
- * The reducer payload originally captured at kickoff (`answerId` +
- * `chatSessionId`) re-enters via the action so the patch can find the
- * right answer to merge into.
- */
-export declare const policyRecommendationFromUploadEpic: (actions$: ActionsObservable<ActionType>, _state$: StateObservable<RootState>, zeniAPI: ZeniAPI) => Observable<ActionType>;

package/lib/entity/cardPolicy/policyRecommendationFromUploadEpic.js

@@ -1,111 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.policyRecommendationFromUploadEpic = void 0;
-const rxjs_1 = require("rxjs");
-const operators_1 = require("rxjs/operators");
-const aiCfoReducer_1 = require("../aiCfo/aiCfoReducer");
-const responsePayload_1 = require("../../responsePayload");
-const cardPolicyReducer_1 = require("./cardPolicyReducer");
-/**
- * Listens for `fetchCardPolicyRecommendationFromUpload` and POSTs the
- * just-extracted policy rules to the AI-CFO recommendation endpoint.
- *
- * On success — dispatches BOTH:
- *  - `updatePolicyRecommendationFromUploadSuccess` (flips the
- *    cardPolicy slice's recommendation lifecycle to `Completed`), and
- *  - `updateAiCfoAnswerCardPolicyWizardPlan` (patches the in-flight AI
- *    CFO answer's `CardPolicyInitialData` so the wizard can advance from
- *    Step 1 → Step 2 in the upload variant).
- *
- * The reducer payload originally captured at kickoff (`answerId` +
- * `chatSessionId`) re-enters via the action so the patch can find the
- * right answer to merge into.
- */
-const policyRecommendationFromUploadEpic = (actions$, _state$, zeniAPI) => actions$.pipe((0, operators_1.filter)(cardPolicyReducer_1.fetchCardPolicyRecommendationFromUpload.match), 
-// `switchMap` (vs `mergeMap`) cancels any in-flight recommendation
-// whenever a new upload kicks off another one. Without this an older,
-// slower recommendation response could still resolve after a fresh
-// extract has started — that late response would dispatch
-// `updateAiCfoAnswerCardPolicyWizardPlan` against the *current*
-// `answerId`/`chatSessionId` (the ones captured at its kickoff) and
-// overwrite the wizard plan with stale draft policies from the prior
-// document. Pairs with the matching `switchMap` in
-// `extractPolicyDocumentEpic`.
-(0, operators_1.switchMap)((action) => {
-    const { answerId, chatSessionId, extractedRules } = action.payload;
-    const body = {
-        extracted_rules: {
-            allowed_entity: {
-                category_codes: extractedRules.allowedEntity.categoryCodes,
-                merchant_names: extractedRules.allowedEntity.merchantNames,
-            },
-            blocked_entity: {
-                category_codes: extractedRules.blockedEntity.categoryCodes,
-                merchant_names: extractedRules.blockedEntity.merchantNames,
-            },
-            confidence_score: extractedRules.confidenceScore,
-            policy_name: extractedRules.policyName,
-            required_receipt_threshold: extractedRules.requiredReceiptThreshold,
-            transaction_limit: extractedRules.transactionLimit,
-        },
-    };
-    return zeniAPI
-        .postAndGetJSON(`${zeniAPI.apiEndPoints.cardMicroServiceBaseUrl}/1.0/ai-cfo/policy-recommendation-from-upload`, body)
-        .pipe((0, operators_1.mergeMap)((response) => {
-        if (!(0, responsePayload_1.isSuccessStatus)(response) ||
-            response.data?.wizard_plan?.step_5_review == null) {
-            return (0, rxjs_1.of)((0, cardPolicyReducer_1.updatePolicyRecommendationFromUploadFailure)(response.status));
-        }
-        const data = response.data;
-        const review = data.wizard_plan.step_5_review;
-        const wizardPlan = {
-            step5Review: {
-                draftPolicies: (review.draft_policies ?? []).map((draft, index) => ({
-                    id: `draft-${index}`,
-                    name: draft.name,
-                    description: draft.description ?? '',
-                    mode: draft.mode,
-                    allowedEntity: {
-                        categoryCodes: draft.allowed_entity?.category_codes ?? [],
-                        merchantNames: draft.allowed_entity?.merchant_names ?? [],
-                    },
-                    blockedEntity: {
-                        categoryCodes: draft.blocked_entity?.category_codes ?? [],
-                        merchantNames: draft.blocked_entity?.merchant_names ?? [],
-                    },
-                    applyToCards: draft.apply_to_cards ?? [],
-                    requiredReceiptThreshold: draft.required_receipt_threshold ?? 0,
-                    spendLimits: {
-                        transaction: draft.spend_limits?.transaction ?? 0,
-                    },
-                })),
-                groupingSource: review.grouping_source ?? 'none',
-                prompt: review.prompt ?? '',
-            },
-        };
-        const source = data.source != null
-            ? {
-                confidenceScore: data.source.confidence_score,
-                fileName: data.source.file_name,
-                lowConfidenceFields: data.source.low_confidence_fields ?? [],
-            }
-            : undefined;
-        return (0, rxjs_1.of)((0, cardPolicyReducer_1.updatePolicyRecommendationFromUploadSuccess)(), (0, aiCfoReducer_1.updateAiCfoAnswerCardPolicyWizardPlan)({
-            answerId,
-            chatSessionId,
-            wizardPlan,
-            source,
-        }));
-    }), (0, operators_1.catchError)((error) => (0, rxjs_1.of)((0, cardPolicyReducer_1.updatePolicyRecommendationFromUploadFailure)((0, responsePayload_1.createZeniAPIStatus)('Unexpected Error', 'Policy recommendation from upload REST API call errored out' +
-        JSON.stringify(error))))), 
-    // `clearPolicyDocumentExtraction` (× pill) tears down the in-flight
-    // recommendation subscription so a late response can't dispatch
-    // `updateAiCfoAnswerCardPolicyWizardPlan` against the captured-at-
-    // kickoff `answerId`/`chatSessionId` and patch the AI CFO answer
-    // with a wizard plan the user already dismissed. The outer
-    // `switchMap` only handles the "another upload kicks off another
-    // recommendation" race; this guards the orthogonal "user cleared
-    // mid-flight" case.
-    (0, operators_1.takeUntil)(actions$.pipe((0, operators_1.filter)(cardPolicyReducer_1.clearPolicyDocumentExtraction.match))));
-}));
-exports.policyRecommendationFromUploadEpic = policyRecommendationFromUploadEpic;

package/lib/esm/entity/cardPolicy/cardPolicyPayload.js

@@ -1,130 +0,0 @@
-import { date } from '../../zeniDayJS';
-import { toCardPolicyTemplateMode, toCardPolicyTemplateStatus, } from './cardPolicyState';
-export const toMccCategory = (payload) => ({
-    count: payload.count,
-    mccCodes: payload.mcc_codes ?? [],
-    name: payload.name,
-});
-export const toCardPolicyVendorSearchOption = (payload) => ({
-    vendorId: payload.vendor_id,
-    name: payload.vendor_name,
-});
-export const toCardPolicyStats = (payload) => ({
-    activePolicies: payload.active_policies,
-    totalCards: payload.total_cards,
-    totalTemplates: payload.total_templates,
-});
-export const toCardPolicyTemplateList = (data) => (data.templates ?? []).map((row) => toCardPolicyTemplate(row.data.template));
-const toCardPolicyTemplateEntityList = (payload) => ({
-    categoryCodes: payload.category_codes ?? [],
-    merchantNames: payload.merchant_names ?? [],
-});
-export const toCardPolicyTemplate = (payload) => ({
-    allowedEntity: toCardPolicyTemplateEntityList(payload.allowed_entity),
-    appliedCards: payload.applied_cards ?? [],
-    blockedEntity: toCardPolicyTemplateEntityList(payload.blocked_entity),
-    cardsCount: payload.cards_count,
-    categoryRestrictions: payload.category_restrictions ?? [],
-    createdAt: date(payload.created_at),
-    createdBy: payload.created_by,
-    description: payload.description,
-    mode: toCardPolicyTemplateMode(payload.mode),
-    name: payload.name,
-    requiredReceiptThreshold: payload.required_receipt_threshold,
-    spendLimits: {
-        transaction: payload.spend_limits.transaction,
-    },
-    status: toCardPolicyTemplateStatus(payload.status),
-    templateId: payload.template_id,
-    tenantId: payload.tenant_id,
-    updatedAt: date(payload.updated_at),
-});
-/**
- * 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 const toCreateCardPolicyTemplateRequestBody = (request) => ({
-    allowed_entity: {
-        category_codes: request.allowedEntity.categoryCodes,
-        merchant_names: request.allowedEntity.merchantNames,
-    },
-    apply_to_cards: request.applyToCards,
-    blocked_entity: {
-        category_codes: request.blockedEntity.categoryCodes,
-        merchant_names: request.blockedEntity.merchantNames,
-    },
-    description: request.description,
-    mode: request.mode ?? 'strict',
-    name: request.name,
-    required_receipt_threshold: request.requiredReceiptThreshold,
-    spend_limits: {
-        transaction: request.spendLimits.transaction,
-    },
-});
-/**
- * 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 const toCreateCardPolicyTemplatesRequestBody = (request) => {
-    const body = {
-        templates: request.templates.map(toCreateCardPolicyTemplateRequestBody),
-    };
-    if (request.sourceChatSessionId != null) {
-        body.source_chat_session_id = request.sourceChatSessionId;
-    }
-    return body;
-};
-/**
- * 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 const toBulkCreateCardPolicyTemplateError = (payload) => ({
-    message: payload.message,
-    code: payload.code,
-    index: payload.index,
-    name: payload.name,
-});
-// Update body uses the exact same wire shape as create — the PUT
-// endpoint is a full replace and was not affected by the bulk migration.
-export const toUpdateCardPolicyTemplateRequestBody = toCreateCardPolicyTemplateRequestBody;
-/**
- * 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 const toCardPolicyEditFormDraft = (template) => ({
-    allowedEntity: {
-        categoryCodes: [...template.allowedEntity.categoryCodes],
-        merchantNames: [...template.allowedEntity.merchantNames],
-    },
-    applyToCards: [...template.appliedCards],
-    blockedEntity: {
-        categoryCodes: [...template.blockedEntity.categoryCodes],
-        merchantNames: [...template.blockedEntity.merchantNames],
-    },
-    description: template.description,
-    mode: template.mode,
-    name: template.name,
-    requiredReceiptThreshold: template.requiredReceiptThreshold,
-    spendLimits: { transaction: template.spendLimits.transaction },
-});
-export const toExtractedCardPolicyRules = (payload) => ({
-    allowedEntity: {
-        categoryCodes: payload.allowed_entity?.category_codes ?? [],
-        merchantNames: payload.allowed_entity?.merchant_names ?? [],
-    },
-    blockedEntity: {
-        categoryCodes: payload.blocked_entity?.category_codes ?? [],
-        merchantNames: payload.blocked_entity?.merchant_names ?? [],
-    },
-    confidenceScore: payload.confidence_score,
-    policyName: payload.policy_name,
-    requiredReceiptThreshold: payload.required_receipt_threshold,
-    transactionLimit: payload.transaction_limit,
-});