@iblai/data-layer 1.28.0 → 1.29.0

package/dist/index.esm.js

@@ -42296,7 +42296,8 @@ const chatPrivacyApiSlice = createApi({
     reducerPath: 'chatPrivacyApiSlice',
     // Callers read the failure itself: the 403 a locked mentor answers to a
     // `disable-chathistory` flip carries its reason in `data.detail`, and the
-    // one-way 400 carries it under the field name. `iblFetchBaseQuery` throws
+    // 400 refusing to re-enable an orphaned session carries it under the field
+    // name. `iblFetchBaseQuery` throws
     // its errors, which reach `.unwrap()` and the hooks as `{}`.
     baseQuery: withReturnedErrors(iblFetchBaseQuery),
     tagTypes: ['TenantChatPrivacyConfig', 'UserChatPrivacySettings', 'ChatPrivacyEffective'],
@@ -42348,10 +42349,11 @@ const chatPrivacyApiSlice = createApi({
             },
             providesTags: ['ChatPrivacyEffective'],
         }),
-        // One-way switch: flipping a session to disable_chathistory: true also
-        // removes it from the user's history list (backend nulls Session.student).
-        // Per the spec, true → false is rejected with 400; the user must start a
-        // new conversation to resume history.
+        // Two-way flip. `true` stops saving new messages; a session that already
+        // has history keeps its owner (stays listed), an EMPTY one is orphaned
+        // (backend nulls Session.student). `false` resumes history on the same
+        // session, refused only for an orphaned session (400 for an admin, 404
+        // for its own user — the ownership check fails first).
         //
         // Important — this endpoint lives under `/api/ai-mentor/…`, NOT under
         // `/api/ai-account/…` like the other chat-privacy endpoints. The