@zeniai/client-epic-state 5.2.39 → 5.2.40

package/lib/entity/aiCfo/aiCfoReducer.js

@@ -7,6 +7,7 @@ const rootActions_1 = require("../../rootActions");
 const zeniDayJS_1 = require("../../zeniDayJS");
 const aiCfoState_1 = require("./aiCfoState");
 exports.initialAiCfoState = {
+    deletedChatSessionIds: [],
     aiCfoByChatSessionId: {},
     partialQuestionAnswers: {},
     syntheticAnswersByChatSessionId: {},
@@ -474,6 +475,11 @@ const toResponseBlockType = (answer, userId) => {
         createdAt: (0, zeniDayJS_1.date)(timestamp),
     };
 };
+// How many deleted session ids to remember. The tombstone only has to outlive
+// an in-flight history request, which is seconds, so this is generous. Capped
+// because `clearSession` would otherwise grow the array for the life of the
+// store and every `setChatHistory` scans it.
+const DELETED_SESSION_MEMORY = 100;
 const aiCfo = (0, toolkit_1.createSlice)({
     name: 'aiCfo',
     initialState: exports.initialAiCfoState,
@@ -495,8 +501,25 @@ const aiCfo = (0, toolkit_1.createSlice)({
         setSessions(draft, action) {
             action.payload.forEach((chatSessionPayload) => {
                 const { chat_session_id } = chatSessionPayload;
-                // This is to prevent overwriting the session if it is already in state
-                if (draft.aiCfoByChatSessionId[chat_session_id] == null) {
+                if (draft.aiCfoByChatSessionId[chat_session_id] != null) {
+                    // The list is authoritative for a session's metadata, and a session
+                    // seeded by `setChatHistory` has guessed metadata: no summary, and a
+                    // `createdAt` taken from one page of a newest-first paginated
+                    // history, which is later than the session really started.
+                    // `questionAnswers` is left alone — the list must never wipe a
+                    // thread that is on screen.
+                    const entry = draft.aiCfoByChatSessionId[chat_session_id];
+                    const incoming = toChatSession(chatSessionPayload);
+                    entry.chatSession = {
+                        ...incoming,
+                        // Never downgrade a title already in state: a page of the list can
+                        // carry a nullish summary, and assigning it wholesale would blank
+                        // a header that was correct.
+                        chatSessionSummary: incoming.chatSessionSummary ??
+                            entry.chatSession.chatSessionSummary,
+                    };
+                }
+                else {
                     draft.aiCfoByChatSessionId[chat_session_id] = {
                         chatSession: toChatSession(chatSessionPayload),
                         questionAnswers: [],
@@ -509,8 +532,52 @@ const aiCfo = (0, toolkit_1.createSlice)({
         setChatHistory(draft, action) {
             const { chatSessionId, history, isPaginationComplete = false, } = action.payload;
             if (draft.aiCfoByChatSessionId[chatSessionId] == null) {
-                console.warn(`session with id ${chatSessionId} not found in setChatHistory`);
-                return;
+                // Sessions created server-side (a routine run) are opened by deep
+                // link, so their history can arrive before the sessions list has
+                // registered them. Dropping it here loses the messages for good: the
+                // response's null page token sets `hasMore: false`, which is the
+                // condition the refetch is guarded on. The response is itself proof
+                // the session exists, so seed the entry from the messages.
+                if (history.length === 0) {
+                    return;
+                }
+                // A deleted session. Its history request is never cancelled
+                // (`mergeMap`), so seeding would resurrect the conversation into the
+                // rail, where clicking it 404s. Only this path is guarded:
+                // `clearSession` is optimistic, so if the server still lists the
+                // session, `setSessions` re-adding it is correct.
+                if (draft.deletedChatSessionIds?.includes(chatSessionId) === true) {
+                    return;
+                }
+                // The human's id, taken off a message they actually sent. The API
+                // returns newest first, so `history[0]` is usually the agent's reply,
+                // and `chatSession.userId` is read as "whose conversation is this".
+                const owner = history.find((message) => message.sender === 'user') ?? history[0];
+                // Oldest message in the page, not `history[0]`: a session cannot
+                // start after its own messages, and the API returns newest first.
+                //
+                // Compared as instants, not strings. The wire format is an RFC 1123
+                // HTTP-date ("Thu, 03 Sep 2026 12:34:56 GMT") because `set_200`
+                // bypasses chat's isoformat encoder, and lexically "Mon…" precedes
+                // "Sat…" while being the later day. Unparseable values are filtered
+                // out, not compared: every comparison against NaN is false, so one
+                // used as the reduce's seed would carry through to an Invalid Date.
+                const oldest = history
+                    .map((message) => ({ at: Date.parse(message.created_at), message }))
+                    .filter(({ at }) => !Number.isNaN(at))
+                    .reduce((min, entry) => (min == null || entry.at < min.at ? entry : min), undefined)?.message;
+                draft.aiCfoByChatSessionId[chatSessionId] = {
+                    chatSession: {
+                        chatSessionId,
+                        userId: owner.user_id,
+                        chatSessionSummary: undefined,
+                        // Nothing in the page carried a usable timestamp. "Now" is a
+                        // guess, but it is a sane one and it keeps the row out of the
+                        // Invalid-Date behaviour above; the sessions list corrects it.
+                        createdAt: oldest != null ? (0, zeniDayJS_1.date)(oldest.created_at) : (0, zeniDayJS_1.dateNow)(),
+                    },
+                    questionAnswers: [],
+                };
             }
             const session = draft.aiCfoByChatSessionId[chatSessionId];
             // Check if we have an existing partial Q&A pair for this session
@@ -790,6 +857,13 @@ const aiCfo = (0, toolkit_1.createSlice)({
         },
         clearSession(draft, action) {
             const sessionId = action.payload;
+            draft.deletedChatSessionIds ?? (draft.deletedChatSessionIds = []);
+            if (!draft.deletedChatSessionIds.includes(sessionId)) {
+                draft.deletedChatSessionIds.push(sessionId);
+                if (draft.deletedChatSessionIds.length > DELETED_SESSION_MEMORY) {
+                    draft.deletedChatSessionIds.splice(0, draft.deletedChatSessionIds.length - DELETED_SESSION_MEMORY);
+                }
+            }
             delete draft.aiCfoByChatSessionId[sessionId];
             delete draft.syntheticAnswersByChatSessionId[sessionId];
             if (draft.partialQuestionAnswers?.[sessionId] != null) {

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

@@ -241,4 +241,20 @@ export interface AiCfoState {
     aiCfoByChatSessionId: Record<ID, ChatSessionWithMessages>;
     partialQuestionAnswers: Record<ID, AiCfoQuestionWithAnswer | undefined>;
     syntheticAnswersByChatSessionId: Record<ID, SyntheticAiCfoAnswer[]>;
+    /**
+     * Sessions this client has deleted. `setChatHistory` seeds an entry for a
+     * session it has not seen, so without a tombstone an in-flight history
+     * response arriving after the delete would recreate the whole conversation
+     * and put the deleted chat back in the rail. `fetchChatHistoryEpic` uses
+     * `mergeMap`, so that request is never cancelled. Same race, and the same
+     * reasoning, as `deletedScheduleIds` on the view slice. Bounded — it only
+     * needs to outlive an in-flight request.
+     *
+     * Optional because `AiCfoState` is public API of a package four apps
+     * consume: making it required turns a bug fix into a compile break for
+     * every literal of this type, in this repo and in theirs. The reducer's
+     * initial state always sets it, so it is only ever absent on a
+     * hand-built literal — which is exactly the case that must keep working.
+     */
+    deletedChatSessionIds?: ID[];
 }

package/lib/esm/entity/aiCfo/aiCfoReducer.js

@@ -1,8 +1,9 @@
 import { createSlice } from '@reduxjs/toolkit';
 import { clearAll } from '../../rootActions';
-import { date as zeniDate } from '../../zeniDayJS';
+import { dateNow, date as zeniDate } from '../../zeniDayJS';
 import { ALL_AI_CFO_ANSWER_RESPONSE_TYPES, toAiCfoAnswerResponseType, toAiCfoAnswerResponseTypeStrict, toAiCfoAnswerStateType, toAiCfoVisualizationTypeStrict, toInteractiveFormTypeStrict, toMessageSender, toMessageType, toYFormatScaleStrict, toYFormatTypeStrict, toYFormatUnitStrict, } from './aiCfoState';
 export const initialAiCfoState = {
+    deletedChatSessionIds: [],
     aiCfoByChatSessionId: {},
     partialQuestionAnswers: {},
     syntheticAnswersByChatSessionId: {},
@@ -468,6 +469,11 @@ const toResponseBlockType = (answer, userId) => {
         createdAt: zeniDate(timestamp),
     };
 };
+// How many deleted session ids to remember. The tombstone only has to outlive
+// an in-flight history request, which is seconds, so this is generous. Capped
+// because `clearSession` would otherwise grow the array for the life of the
+// store and every `setChatHistory` scans it.
+const DELETED_SESSION_MEMORY = 100;
 const aiCfo = createSlice({
     name: 'aiCfo',
     initialState: initialAiCfoState,
@@ -489,8 +495,25 @@ const aiCfo = createSlice({
         setSessions(draft, action) {
             action.payload.forEach((chatSessionPayload) => {
                 const { chat_session_id } = chatSessionPayload;
-                // This is to prevent overwriting the session if it is already in state
-                if (draft.aiCfoByChatSessionId[chat_session_id] == null) {
+                if (draft.aiCfoByChatSessionId[chat_session_id] != null) {
+                    // The list is authoritative for a session's metadata, and a session
+                    // seeded by `setChatHistory` has guessed metadata: no summary, and a
+                    // `createdAt` taken from one page of a newest-first paginated
+                    // history, which is later than the session really started.
+                    // `questionAnswers` is left alone — the list must never wipe a
+                    // thread that is on screen.
+                    const entry = draft.aiCfoByChatSessionId[chat_session_id];
+                    const incoming = toChatSession(chatSessionPayload);
+                    entry.chatSession = {
+                        ...incoming,
+                        // Never downgrade a title already in state: a page of the list can
+                        // carry a nullish summary, and assigning it wholesale would blank
+                        // a header that was correct.
+                        chatSessionSummary: incoming.chatSessionSummary ??
+                            entry.chatSession.chatSessionSummary,
+                    };
+                }
+                else {
                     draft.aiCfoByChatSessionId[chat_session_id] = {
                         chatSession: toChatSession(chatSessionPayload),
                         questionAnswers: [],
@@ -503,8 +526,52 @@ const aiCfo = createSlice({
         setChatHistory(draft, action) {
             const { chatSessionId, history, isPaginationComplete = false, } = action.payload;
             if (draft.aiCfoByChatSessionId[chatSessionId] == null) {
-                console.warn(`session with id ${chatSessionId} not found in setChatHistory`);
-                return;
+                // Sessions created server-side (a routine run) are opened by deep
+                // link, so their history can arrive before the sessions list has
+                // registered them. Dropping it here loses the messages for good: the
+                // response's null page token sets `hasMore: false`, which is the
+                // condition the refetch is guarded on. The response is itself proof
+                // the session exists, so seed the entry from the messages.
+                if (history.length === 0) {
+                    return;
+                }
+                // A deleted session. Its history request is never cancelled
+                // (`mergeMap`), so seeding would resurrect the conversation into the
+                // rail, where clicking it 404s. Only this path is guarded:
+                // `clearSession` is optimistic, so if the server still lists the
+                // session, `setSessions` re-adding it is correct.
+                if (draft.deletedChatSessionIds?.includes(chatSessionId) === true) {
+                    return;
+                }
+                // The human's id, taken off a message they actually sent. The API
+                // returns newest first, so `history[0]` is usually the agent's reply,
+                // and `chatSession.userId` is read as "whose conversation is this".
+                const owner = history.find((message) => message.sender === 'user') ?? history[0];
+                // Oldest message in the page, not `history[0]`: a session cannot
+                // start after its own messages, and the API returns newest first.
+                //
+                // Compared as instants, not strings. The wire format is an RFC 1123
+                // HTTP-date ("Thu, 03 Sep 2026 12:34:56 GMT") because `set_200`
+                // bypasses chat's isoformat encoder, and lexically "Mon…" precedes
+                // "Sat…" while being the later day. Unparseable values are filtered
+                // out, not compared: every comparison against NaN is false, so one
+                // used as the reduce's seed would carry through to an Invalid Date.
+                const oldest = history
+                    .map((message) => ({ at: Date.parse(message.created_at), message }))
+                    .filter(({ at }) => !Number.isNaN(at))
+                    .reduce((min, entry) => (min == null || entry.at < min.at ? entry : min), undefined)?.message;
+                draft.aiCfoByChatSessionId[chatSessionId] = {
+                    chatSession: {
+                        chatSessionId,
+                        userId: owner.user_id,
+                        chatSessionSummary: undefined,
+                        // Nothing in the page carried a usable timestamp. "Now" is a
+                        // guess, but it is a sane one and it keeps the row out of the
+                        // Invalid-Date behaviour above; the sessions list corrects it.
+                        createdAt: oldest != null ? zeniDate(oldest.created_at) : dateNow(),
+                    },
+                    questionAnswers: [],
+                };
             }
             const session = draft.aiCfoByChatSessionId[chatSessionId];
             // Check if we have an existing partial Q&A pair for this session
@@ -784,6 +851,13 @@ const aiCfo = createSlice({
         },
         clearSession(draft, action) {
             const sessionId = action.payload;
+            draft.deletedChatSessionIds ?? (draft.deletedChatSessionIds = []);
+            if (!draft.deletedChatSessionIds.includes(sessionId)) {
+                draft.deletedChatSessionIds.push(sessionId);
+                if (draft.deletedChatSessionIds.length > DELETED_SESSION_MEMORY) {
+                    draft.deletedChatSessionIds.splice(0, draft.deletedChatSessionIds.length - DELETED_SESSION_MEMORY);
+                }
+            }
             delete draft.aiCfoByChatSessionId[sessionId];
             delete draft.syntheticAnswersByChatSessionId[sessionId];
             if (draft.partialQuestionAnswers?.[sessionId] != null) {

package/lib/esm/view/financeStatement/financeStatementReducer.js

@@ -33,9 +33,18 @@ const financeStatement = createSlice({
             },
         },
         updateFinanceStatementTimeframe(draft, action) {
+            // Unrelated UI re-dispatches the *current* timeframe as a side effect (the
+            // reports page hangs its table scroll reset off that callback); dropping the
+            // anchor there would silently reset the user's period to the latest one.
+            if (draft.timeframe === action.payload) {
+                return;
+            }
             draft.timeframe = action.payload;
+            // A month anchor is meaningless once the timeframe becomes quarter/year, so
+            // a real change drops it and returns the width to the default — 12 months
+            // must not become 12 quarters. Order is the user's, so it survives.
             draft.selectedCOABalancesRange = {
-                numberOfPeriods: draft.selectedCOABalancesRange.numberOfPeriods,
+                numberOfPeriods: initialFinanceStatementState.selectedCOABalancesRange.numberOfPeriods,
                 orderBy: draft.selectedCOABalancesRange.orderBy,
             };
         },
@@ -77,8 +86,7 @@ const financeStatement = createSlice({
             draft.selectedReportId = action.payload;
         },
         updateFinanceStatementAdditionalBalancesSelection(draft, action) {
-            const { firstMonthOfFY, additionalBalances: additionalBalancesPayload, coaBalances, maxNumOfPeriodsToHighlight, } = action.payload;
-            const safeCoaBalances = coaBalances != null ? coaBalances : [];
+            const { additionalBalances: additionalBalancesPayload, maxNumOfPeriodsToHighlight, } = action.payload;
             const additionalBalances = additionalBalancesPayload ?? [];
             let tempAdditionalBalances = [...additionalBalances];
             if (additionalBalances.includes('this_period_vs_last_period') ||
@@ -94,30 +102,12 @@ const financeStatement = createSlice({
             draft.maxNumOfPeriodsToHighlight = maxNumOfPeriodsToHighlight;
             draft.isAdditionalBalancesShown =
                 additionalBalances.length != 0 ? true : false;
-            const { timeframe, selectedCOABalancesRange } = draft;
-            if (safeCoaBalances.length > 0) {
-                const thisPeriod = extractThisPeriod(action.payload.firstMonthOfFY, timeframe, selectedCOABalancesRange, safeCoaBalances);
-                if (thisPeriod != null) {
-                    const selectedCoaBalancesRangeWithThisPeriod = {
-                        ...selectedCOABalancesRange,
-                        thisPeriod,
-                    };
-                    const selectionRanges = getSelectedAndHighlightedRangesForThisPeriod({
-                        firstMonthOfFY,
-                        thisPeriod: thisPeriod,
-                        coaBalances: safeCoaBalances,
-                        timeframe,
-                        maxNumOfPeriodsToHighlight: maxNumOfPeriodsToHighlight,
-                        currentSelection: {
-                            selectedCOABalancesRange: selectedCoaBalancesRangeWithThisPeriod,
-                        },
-                        orderBy: 'ascending_date',
-                        maxNumOfPeriodsToSelect: maxNumOfPeriodsToHighlight,
-                    });
-                    draft.selectedCOABalancesRange =
-                        selectionRanges.selectedCOABalancesRange;
-                }
-            }
+            // Column metadata only — must not touch selectedCOABalancesRange. The
+            // reports page fires this on load, on resize and on every fetch-state
+            // transition (so also on report switch and on remount after a drill-down)
+            // with a viewport-derived period count that knows nothing about the range
+            // the user picked. The width default comes from initial state, and from
+            // updateFinanceStatementTimeframe on a real timeframe change.
         },
         updateDownloadState(draft, action) {
             draft.downloadState = action.payload;

package/lib/view/financeStatement/financeStatementReducer.js

@@ -37,9 +37,18 @@ const financeStatement = (0, toolkit_1.createSlice)({
             },
         },
         updateFinanceStatementTimeframe(draft, action) {
+            // Unrelated UI re-dispatches the *current* timeframe as a side effect (the
+            // reports page hangs its table scroll reset off that callback); dropping the
+            // anchor there would silently reset the user's period to the latest one.
+            if (draft.timeframe === action.payload) {
+                return;
+            }
             draft.timeframe = action.payload;
+            // A month anchor is meaningless once the timeframe becomes quarter/year, so
+            // a real change drops it and returns the width to the default — 12 months
+            // must not become 12 quarters. Order is the user's, so it survives.
             draft.selectedCOABalancesRange = {
-                numberOfPeriods: draft.selectedCOABalancesRange.numberOfPeriods,
+                numberOfPeriods: exports.initialFinanceStatementState.selectedCOABalancesRange.numberOfPeriods,
                 orderBy: draft.selectedCOABalancesRange.orderBy,
             };
         },
@@ -81,8 +90,7 @@ const financeStatement = (0, toolkit_1.createSlice)({
             draft.selectedReportId = action.payload;
         },
         updateFinanceStatementAdditionalBalancesSelection(draft, action) {
-            const { firstMonthOfFY, additionalBalances: additionalBalancesPayload, coaBalances, maxNumOfPeriodsToHighlight, } = action.payload;
-            const safeCoaBalances = coaBalances != null ? coaBalances : [];
+            const { additionalBalances: additionalBalancesPayload, maxNumOfPeriodsToHighlight, } = action.payload;
             const additionalBalances = additionalBalancesPayload ?? [];
             let tempAdditionalBalances = [...additionalBalances];
             if (additionalBalances.includes('this_period_vs_last_period') ||
@@ -98,30 +106,12 @@ const financeStatement = (0, toolkit_1.createSlice)({
             draft.maxNumOfPeriodsToHighlight = maxNumOfPeriodsToHighlight;
             draft.isAdditionalBalancesShown =
                 additionalBalances.length != 0 ? true : false;
-            const { timeframe, selectedCOABalancesRange } = draft;
-            if (safeCoaBalances.length > 0) {
-                const thisPeriod = (0, thisPeriodHelpers_1.extractThisPeriod)(action.payload.firstMonthOfFY, timeframe, selectedCOABalancesRange, safeCoaBalances);
-                if (thisPeriod != null) {
-                    const selectedCoaBalancesRangeWithThisPeriod = {
-                        ...selectedCOABalancesRange,
-                        thisPeriod,
-                    };
-                    const selectionRanges = (0, getSelectedAndHighlightedRanges_1.getSelectedAndHighlightedRangesForThisPeriod)({
-                        firstMonthOfFY,
-                        thisPeriod: thisPeriod,
-                        coaBalances: safeCoaBalances,
-                        timeframe,
-                        maxNumOfPeriodsToHighlight: maxNumOfPeriodsToHighlight,
-                        currentSelection: {
-                            selectedCOABalancesRange: selectedCoaBalancesRangeWithThisPeriod,
-                        },
-                        orderBy: 'ascending_date',
-                        maxNumOfPeriodsToSelect: maxNumOfPeriodsToHighlight,
-                    });
-                    draft.selectedCOABalancesRange =
-                        selectionRanges.selectedCOABalancesRange;
-                }
-            }
+            // Column metadata only — must not touch selectedCOABalancesRange. The
+            // reports page fires this on load, on resize and on every fetch-state
+            // transition (so also on report switch and on remount after a drill-down)
+            // with a viewport-derived period count that knows nothing about the range
+            // the user picked. The width default comes from initial state, and from
+            // updateFinanceStatementTimeframe on a real timeframe change.
         },
         updateDownloadState(draft, action) {
             draft.downloadState = action.payload;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zeniai/client-epic-state",
-  "version": "5.2.39",
+  "version": "5.2.40",
   "description": "Shared module between Web & Mobile containing required abstractions for state management, async network communication. ",
   "main": "lib/index.js",
   "module": "lib/esm/index.js",