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

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

@@ -1,261 +0,0 @@
-import { createSlice } from '@reduxjs/toolkit';
-import { toCardPolicyTemplate, toCardPolicyVendorSearchOption, toExtractedCardPolicyRules, toMccCategory, } from './cardPolicyPayload';
-/**
- * Defensive predicate for vendor / merchant names that flow into
- * `buildVendorChipId(name)` (in `@zeniai/web-components`). That helper
- * calls `name.trim().toLowerCase()`, so a null / undefined / whitespace-
- * only value would throw at render time, and an empty string would
- * collapse every nameless row into a single colliding `vendor-` chip-id.
- * Used at the redux ingestion boundary for both the vendor-search results
- * and the BE-suggested merchant seed arrays.
- */
-const isUsableMerchantName = (name) => typeof name === 'string' && name.trim() !== '';
-const initialPolicyDocumentExtractionState = {
-    fetchState: 'Not-Started',
-    error: undefined,
-    extractedRules: undefined,
-    uploadedFileName: undefined,
-};
-const initialPolicyRecommendationFromUploadState = {
-    fetchState: 'Not-Started',
-    answerId: undefined,
-    chatSessionId: undefined,
-    error: undefined,
-};
-const initialVendorSearchState = {
-    fetchState: 'Not-Started',
-    searchString: '',
-    vendors: [],
-    error: undefined,
-};
-export const initialState = {
-    cardPolicyTemplateById: {},
-    mccCategories: [],
-    mccCategoriesError: undefined,
-    mccCategoriesFetchState: 'Not-Started',
-    policyDocumentExtraction: initialPolicyDocumentExtractionState,
-    policyRecommendationFromUpload: initialPolicyRecommendationFromUploadState,
-    suggestedAllowCategories: [],
-    suggestedAllowMerchants: [],
-    suggestedBlockCategories: [],
-    suggestedBlockMerchants: [],
-    vendorSearch: initialVendorSearchState,
-    cardPolicyStats: undefined,
-};
-const cardPolicy = createSlice({
-    name: 'cardPolicy',
-    initialState,
-    reducers: {
-        fetchCardPolicyMccCategories(draft) {
-            draft.mccCategoriesFetchState = 'In-Progress';
-            draft.mccCategoriesError = undefined;
-        },
-        updateCardPolicyMccCategories(draft, action) {
-            draft.mccCategories = (action.payload.categories ?? []).map(toMccCategory);
-            // Persist BE-suggested allow / block seeds alongside the universe.
-            // Both flows (manual create page + AI CFO interactive form) read
-            // these to pre-populate the chip cloud body before the user edits.
-            // Drop empty / nullish merchant names defensively — they feed
-            // `buildVendorChipId(name)` (in @zeniai/web-components) which calls
-            // `.trim().toLowerCase()` and would crash the chip-picker render
-            // path if any entry slipped through as undefined / "".
-            draft.suggestedAllowMerchants = (action.payload.suggested_allow_merchants ?? []).filter(isUsableMerchantName);
-            draft.suggestedBlockMerchants = (action.payload.suggested_block_merchants ?? []).filter(isUsableMerchantName);
-            draft.suggestedAllowCategories = (action.payload.suggested_allow_catagories ?? []).map(toMccCategory);
-            draft.suggestedBlockCategories = (action.payload.suggested_block_catagories ?? []).map(toMccCategory);
-            draft.mccCategoriesFetchState = 'Completed';
-            draft.mccCategoriesError = undefined;
-        },
-        updateCardPolicyMccCategoriesFailure(draft, action) {
-            draft.mccCategoriesFetchState = 'Error';
-            draft.mccCategoriesError = action.payload;
-        },
-        /**
-         * Store a newly-created (or refreshed) card-policy template keyed by
-         * `templateId`. Dispatched by the create / list / get epics; consumed
-         * by both manual and AI-CFO policy flows via `getCardPolicyTemplateById`.
-         */
-        updateCreatedCardPolicyTemplate(draft, action) {
-            const template = toCardPolicyTemplate(action.payload);
-            draft.cardPolicyTemplateById[template.templateId] = template;
-        },
-        /**
-         * Replace the entity store's `cardPolicyTemplateById` map with the
-         * full list returned by the templates-list endpoint. Full replace is
-         * intentional — templates that no longer exist on the server should be
-         * dropped from local state too. The view slice keeps the server-order
-         * ID list separately for stable list rendering.
-         */
-        updateCardPolicyTemplates(draft, action) {
-            const byId = {};
-            for (const template of action.payload) {
-                byId[template.templateId] = template;
-            }
-            draft.cardPolicyTemplateById = byId;
-        },
-        /**
-         * Drop a single template from the entity map. Dispatched by the
-         * archive (DELETE) epic on success; also usable by any future flow
-         * that needs to evict a template (e.g. AI-CFO rejection).
-         */
-        removeCardPolicyTemplate(draft, action) {
-            delete draft.cardPolicyTemplateById[action.payload];
-        },
-        /**
-         * Replace the tenant-wide policy stats. Dispatched alongside
-         * `updateCardPolicyTemplates` from the list epic, but lives on the
-         * entity slice so any consumer can read it without re-fetching the
-         * list.
-         */
-        updateCardPolicyStats(draft, action) {
-            draft.cardPolicyStats = action.payload;
-        },
-        /**
-         * Kick off the `POST /cards/1.0/policy-documents/extract` request.
-         *
-         * Synchronously flips the sub-slice to `In-Progress` and captures the
-         * first uploaded file's name (used by the manual `CardPolicyCreatePage`
-         * to render the "Policy.pdf ×" pill once the request completes) so
-         * downstream callers don't have to keep their own file refs.
-         *
-         * The accompanying `extractPolicyDocumentEpic` listens for this action,
-         * POSTs multipart form-data to the cards micro-service, and dispatches
-         * either `updatePolicyDocumentExtractionSuccess` or
-         * `updatePolicyDocumentExtractionFailure`.
-         *
-         * Designed to be dispatched from both the manual create page and a
-         * future AI CFO composer/upload surface — selectors return a single
-         * source of truth.
-         */
-        extractPolicyDocument: {
-            reducer(draft, action) {
-                draft.policyDocumentExtraction.fetchState = 'In-Progress';
-                draft.policyDocumentExtraction.error = undefined;
-                draft.policyDocumentExtraction.extractedRules = undefined;
-                draft.policyDocumentExtraction.uploadedFileName =
-                    action.meta.uploadedFileName;
-                draft.policyDocumentExtraction.aiCfoAnswerId =
-                    action.payload.aiCfoAnswerId;
-                draft.policyDocumentExtraction.aiCfoChatSessionId =
-                    action.payload.aiCfoChatSessionId;
-                // Reset the chained recommendation slice too — without this a
-                // second upload in the same AI CFO session can read `Completed` or
-                // `Error` from the prior chain while extraction is still
-                // `In-Progress`, leaving lifecycle UI/gating wrong until the new
-                // chain finishes. The two sub-slices model the upload lifecycle
-                // together (see `clearPolicyDocumentExtraction` below).
-                draft.policyRecommendationFromUpload = {
-                    ...initialPolicyRecommendationFromUploadState,
-                };
-            },
-            prepare(files, aiCfoAnswerId, aiCfoChatSessionId) {
-                return {
-                    payload: { files, aiCfoAnswerId, aiCfoChatSessionId },
-                    meta: { uploadedFileName: files[0]?.name },
-                };
-            },
-        },
-        updatePolicyDocumentExtractionSuccess(draft, action) {
-            draft.policyDocumentExtraction.fetchState = 'Completed';
-            draft.policyDocumentExtraction.error = undefined;
-            draft.policyDocumentExtraction.extractedRules =
-                toExtractedCardPolicyRules(action.payload);
-        },
-        updatePolicyDocumentExtractionFailure(draft, action) {
-            draft.policyDocumentExtraction.fetchState = 'Error';
-            draft.policyDocumentExtraction.error = action.payload;
-            draft.policyDocumentExtraction.extractedRules = undefined;
-        },
-        clearPolicyDocumentExtraction(draft) {
-            draft.policyDocumentExtraction = {
-                ...initialPolicyDocumentExtractionState,
-            };
-            // Clear the chained recommendation slice too — the two together
-            // model the upload lifecycle and either both reset (× pill,
-            // unmount) or both advance (drop file → extract → recommend).
-            draft.policyRecommendationFromUpload = {
-                ...initialPolicyRecommendationFromUploadState,
-            };
-        },
-        /**
-         * Kick off `POST /cards/1.0/ai-cfo/policy-recommendation-from-upload`.
-         *
-         * Chained after `extractPolicyDocument` succeeds in the AI CFO
-         * `upload`-mode flow. The accompanying epic forwards the
-         * just-returned `extracted_rules` to the BE and dispatches success /
-         * failure into this slice; on success, a sibling action
-         * (`updateAiCfoAnswerCardPolicyWizardPlan` on the aiCfo slice) is
-         * dispatched by the epic to merge the returned `wizard_plan` + `source`
-         * into the in-flight AI CFO answer's `CardPolicyInitialData`.
-         *
-         * `answerId` + `chatSessionId` identify which AI CFO answer should
-         * receive the patch. Both are required so the wizard reads a single
-         * source of truth for its lifecycle pill (`fetchState`) and the
-         * bridge epic can correlate against the originating answer.
-         */
-        fetchCardPolicyRecommendationFromUpload: {
-            reducer(draft, action) {
-                draft.policyRecommendationFromUpload.fetchState = 'In-Progress';
-                draft.policyRecommendationFromUpload.answerId = action.payload.answerId;
-                draft.policyRecommendationFromUpload.chatSessionId =
-                    action.payload.chatSessionId;
-                draft.policyRecommendationFromUpload.error = undefined;
-            },
-            prepare(answerId, chatSessionId, extractedRules) {
-                return { payload: { answerId, chatSessionId, extractedRules } };
-            },
-        },
-        updatePolicyRecommendationFromUploadSuccess(draft) {
-            draft.policyRecommendationFromUpload.fetchState = 'Completed';
-            draft.policyRecommendationFromUpload.error = undefined;
-        },
-        updatePolicyRecommendationFromUploadFailure(draft, action) {
-            draft.policyRecommendationFromUpload.fetchState = 'Error';
-            draft.policyRecommendationFromUpload.error = action.payload;
-        },
-        /**
-         * Kick off `GET /accounting/1.0/vendors` (card-policy mode). When
-         * `searchString` is empty the BE returns the top vendors sorted by
-         * year-to-date spend; with a non-empty value it filters server-side.
-         *
-         * The accompanying `fetchCardPolicyVendorOptionsEpic` listens for
-         * this action, builds the `query` JSON (matching `fetchVendorsList`'s
-         * `view: "vendor_list"` shape) and dispatches success / failure.
-         *
-         * Designed to be dispatched from both the manual `CardPolicyCreate /
-         * EditScreen` (on mount + on every chip-picker keystroke, debounced)
-         * and the AI CFO interactive form's vendor step.
-         */
-        fetchCardPolicyVendorOptions: {
-            reducer(draft, action) {
-                draft.vendorSearch.fetchState = 'In-Progress';
-                draft.vendorSearch.searchString = action.payload.searchString;
-                draft.vendorSearch.error = undefined;
-            },
-            prepare(searchString) {
-                return { payload: { searchString: searchString ?? '' } };
-            },
-        },
-        updateCardPolicyVendorOptions(draft, action) {
-            // Drop rows with no usable name. The chip-picker keys vendors by
-            // `buildVendorChipId(name)` (in @zeniai/web-components), which calls
-            // `name.trim().toLowerCase()`. A null / undefined / whitespace-only
-            // name would either throw at render time or collapse every nameless
-            // row into a single colliding `vendor-` chip-id.
-            draft.vendorSearch.vendors = (action.payload.vendors ?? [])
-                .map(toCardPolicyVendorSearchOption)
-                .filter((vendor) => isUsableMerchantName(vendor.name));
-            draft.vendorSearch.fetchState = 'Completed';
-            draft.vendorSearch.error = undefined;
-        },
-        updateCardPolicyVendorOptionsFailure(draft, action) {
-            draft.vendorSearch.fetchState = 'Error';
-            draft.vendorSearch.error = action.payload;
-        },
-        clearCardPolicy(draft) {
-            Object.assign(draft, initialState);
-        },
-    },
-});
-export const { fetchCardPolicyMccCategories, fetchCardPolicyVendorOptions, updateCardPolicyMccCategories, updateCardPolicyMccCategoriesFailure, updateCardPolicyVendorOptions, updateCardPolicyVendorOptionsFailure, updateCreatedCardPolicyTemplate, updateCardPolicyTemplates, removeCardPolicyTemplate, updateCardPolicyStats, extractPolicyDocument, updatePolicyDocumentExtractionSuccess, updatePolicyDocumentExtractionFailure, clearPolicyDocumentExtraction, fetchCardPolicyRecommendationFromUpload, updatePolicyRecommendationFromUploadSuccess, updatePolicyRecommendationFromUploadFailure, clearCardPolicy, } = cardPolicy.actions;
-export default cardPolicy.reducer;

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

@@ -1,79 +0,0 @@
-export function getCardPolicyMccCategories(state) {
-    return state.mccCategories;
-}
-export function getCardPolicyMccCategoriesFetchState(state) {
-    return state.mccCategoriesFetchState;
-}
-export function getCardPolicyMccCategoriesError(state) {
-    return state.mccCategoriesError;
-}
-export function getCardPolicyTemplateById(state, templateId) {
-    return state.cardPolicyTemplateById[templateId];
-}
-export function getAllCardPolicyTemplates(state) {
-    return Object.values(state.cardPolicyTemplateById);
-}
-/**
- * Resolve an ordered list of `templateId`s against the entity store and
- * return the corresponding `CardPolicyTemplate[]` in the same order.
- * Missing IDs (e.g. stale local state during a refetch) are silently
- * dropped. Pair with `getCardPolicyTemplateIds` from the view slice to
- * render the Policy List page in server order.
- */
-export function getCardPolicyTemplatesByIds(state, templateIds) {
-    return templateIds
-        .map((id) => state.cardPolicyTemplateById[id])
-        .filter((template) => template != null);
-}
-export function getCardPolicyStats(state) {
-    return state.cardPolicyStats;
-}
-// ── Policy document extraction ───────────────────────────────────────
-export function getPolicyDocumentExtractionFetchState(state) {
-    return state.policyDocumentExtraction.fetchState;
-}
-export function getPolicyDocumentExtractionError(state) {
-    return state.policyDocumentExtraction.error;
-}
-export function getExtractedCardPolicyRules(state) {
-    return state.policyDocumentExtraction.extractedRules;
-}
-export function getUploadedPolicyDocumentFileName(state) {
-    return state.policyDocumentExtraction.uploadedFileName;
-}
-// ── Policy recommendation from upload (AI CFO upload mode) ───────────
-export function getPolicyRecommendationFromUploadFetchState(state) {
-    return state.policyRecommendationFromUpload.fetchState;
-}
-export function getPolicyRecommendationFromUploadError(state) {
-    return state.policyRecommendationFromUpload.error;
-}
-export function getPolicyRecommendationFromUploadAnswerId(state) {
-    return state.policyRecommendationFromUpload.answerId;
-}
-export function getPolicyRecommendationFromUploadChatSessionId(state) {
-    return state.policyRecommendationFromUpload.chatSessionId;
-}
-// ── Suggested allow / block seeds (shipped alongside MCC categories) ─
-export function getCardPolicySuggestedAllowMerchants(state) {
-    return state.suggestedAllowMerchants;
-}
-export function getCardPolicySuggestedBlockMerchants(state) {
-    return state.suggestedBlockMerchants;
-}
-export function getCardPolicySuggestedAllowCategories(state) {
-    return state.suggestedAllowCategories;
-}
-export function getCardPolicySuggestedBlockCategories(state) {
-    return state.suggestedBlockCategories;
-}
-// ── Vendor search dropdown ───────────────────────────────────────────
-export function getCardPolicyVendorSearchOptions(state) {
-    return state.vendorSearch.vendors;
-}
-export function getCardPolicyVendorSearchFetchState(state) {
-    return state.vendorSearch.fetchState;
-}
-export function getCardPolicyVendorSearchString(state) {
-    return state.vendorSearch.searchString;
-}

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

@@ -1,9 +0,0 @@
-import { stringToUnion } from '../../commonStateTypes/stringToUnion';
-export const ALL_CARD_POLICY_TEMPLATE_MODES = ['strict', 'flexible'];
-export const toCardPolicyTemplateMode = (v) => stringToUnion(v, ALL_CARD_POLICY_TEMPLATE_MODES);
-export const ALL_CARD_POLICY_TEMPLATE_STATUSES = [
-    'active',
-    'inactive',
-    'archived',
-];
-export const toCardPolicyTemplateStatus = (v) => stringToUnion(v, ALL_CARD_POLICY_TEMPLATE_STATUSES);

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

@@ -1,64 +0,0 @@
-import { of } from 'rxjs';
-import { catchError, filter, mergeMap, switchMap, takeUntil } from 'rxjs/operators';
-import { createZeniAPIStatus, isSuccessStatus } from '../../responsePayload';
-import { clearPolicyDocumentExtraction, extractPolicyDocument, updatePolicyDocumentExtractionFailure, updatePolicyDocumentExtractionSuccess, } from './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.
- */
-export const extractPolicyDocumentEpic = (actions$, _state$, zeniAPI) => actions$.pipe(filter(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.
-switchMap((action) => {
-    const formData = buildPolicyDocumentFormData(action.payload.files);
-    return zeniAPI
-        .postFormData(`${zeniAPI.apiEndPoints.cardMicroServiceBaseUrl}/1.0/policy-documents/extract`, formData)
-        .pipe(mergeMap((response) => {
-        if (isSuccessStatus(response) &&
-            response.data != null &&
-            response.data.extracted_rules != null) {
-            return of(updatePolicyDocumentExtractionSuccess(response.data.extracted_rules));
-        }
-        return of(updatePolicyDocumentExtractionFailure(response.status));
-    }), catchError((error) => of(updatePolicyDocumentExtractionFailure(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.
-    takeUntil(actions$.pipe(filter(clearPolicyDocumentExtraction.match))));
-}));

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

@@ -1,43 +0,0 @@
-import { of } from 'rxjs';
-import { catchError, filter, switchMap } from 'rxjs/operators';
-import { createZeniAPIStatus, isSuccessStatus } from '../../responsePayload';
-import { fetchCardPolicyVendorOptions, updateCardPolicyVendorOptions, updateCardPolicyVendorOptionsFailure, } from './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)
- */
-export const fetchCardPolicyVendorOptionsEpic = (actions$, _state$, zeniAPI) => actions$.pipe(filter(fetchCardPolicyVendorOptions.match), 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(switchMap((response) => {
-        if (isSuccessStatus(response) && response.data != null) {
-            return of(updateCardPolicyVendorOptions(response.data));
-        }
-        return of(updateCardPolicyVendorOptionsFailure(response.status));
-    }), catchError((error) => of(updateCardPolicyVendorOptionsFailure(createZeniAPIStatus('Unexpected Error', 'Fetch card policy vendor options REST API call errored out' +
-        JSON.stringify(error))))));
-}));

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

@@ -1,35 +0,0 @@
-import { EMPTY, of } from 'rxjs';
-import { filter, mergeMap } from 'rxjs/operators';
-import { fetchCardPolicyRecommendationFromUpload, updatePolicyDocumentExtractionSuccess, } from './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.
- */
-export const policyDocumentExtractionToRecommendationBridgeEpic = (actions$, state$) => actions$.pipe(filter(updatePolicyDocumentExtractionSuccess.match), 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 EMPTY;
-    }
-    void action;
-    return of(fetchCardPolicyRecommendationFromUpload(aiCfoAnswerId, aiCfoChatSessionId, extractedRules));
-}));

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

@@ -1,107 +0,0 @@
-import { of } from 'rxjs';
-import { catchError, filter, mergeMap, switchMap, takeUntil } from 'rxjs/operators';
-import { updateAiCfoAnswerCardPolicyWizardPlan } from '../aiCfo/aiCfoReducer';
-import { createZeniAPIStatus, isSuccessStatus } from '../../responsePayload';
-import { clearPolicyDocumentExtraction, fetchCardPolicyRecommendationFromUpload, updatePolicyRecommendationFromUploadFailure, updatePolicyRecommendationFromUploadSuccess, } from './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.
- */
-export const policyRecommendationFromUploadEpic = (actions$, _state$, zeniAPI) => actions$.pipe(filter(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`.
-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(mergeMap((response) => {
-        if (!isSuccessStatus(response) ||
-            response.data?.wizard_plan?.step_5_review == null) {
-            return of(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 of(updatePolicyRecommendationFromUploadSuccess(), updateAiCfoAnswerCardPolicyWizardPlan({
-            answerId,
-            chatSessionId,
-            wizardPlan,
-            source,
-        }));
-    }), catchError((error) => of(updatePolicyRecommendationFromUploadFailure(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.
-    takeUntil(actions$.pipe(filter(clearPolicyDocumentExtraction.match))));
-}));