@capillarytech/blaze-ui 5.20.0 → 5.22.0

package/CapAlert/README.md

@@ -1,144 +0,0 @@
-# CapAlert
-
-An extended version of Ant Design's Alert component with Capillary-specific styling and enhancements.
-
-## Migration from cap-ui-library
-
-This component has been migrated from `@capillarytech/cap-ui-library` to `@capillarytech/blaze-ui` with the following changes:
-
-### Breaking Changes
-
-**No breaking changes** - The component maintains backward compatibility with the previous version.
-
-### Deprecated Props
-
-The following props are deprecated but still supported for backward compatibility:
-
-#### `message` (deprecated)
-
-- **Status:** Deprecated
-- **Replacement:** Use `title` prop instead
-- **Migration:** Replace `message="..."` with `title="..."`
-- **Removal:** Will be removed in next major version
-
-**Example:**
-
-```tsx
-// ❌ Deprecated
-<CapAlert message="Alert message" />
-
-// ✅ Recommended
-<CapAlert title="Alert message" />
-```
-
-**Note:** If both `title` and `message` are provided, `title` takes precedence. A console warning will be shown in development mode when using the deprecated `message` prop.
-
-### Prop Changes
-
-| Prop | Status | Notes |
-|------|--------|-------|
-| `title` | ✅ New | Preferred prop name for alert message content |
-| `message` | ⚠️ Deprecated | Use `title` instead. Still supported for backward compatibility |
-| `description` | ✅ Unchanged | Additional description text below the title |
-| `type` | ✅ Unchanged | Alert type: `'success'` \| `'info'` \| `'warning'` \| `'error'` |
-| `showIcon` | ✅ Unchanged | Whether to show icon |
-| `className` | ✅ Unchanged | Custom CSS class name |
-| All other Ant Design Alert props | ✅ Unchanged | Passed through to underlying Alert component |
-
-### API Changes
-
-- **TypeScript Support:** Full TypeScript support with exported `CapAlertProps` interface
-- **Ant Design Version:** Upgraded from Ant Design v3 to v5
-- **Styling:** Migrated from styled-components to SCSS modules
-
-### Behavioral Changes
-
-- **Background Colors:** Alert types now have specific background colors:
-  - Success: `$cap-color-01` (light green)
-  - Info: `$cap-color-04` (light yellow)
-  - Warning: `$cap-color-02` (light orange)
-  - Error: `$cap-color-05` (light red)
-- **Border:** Removed border styling for cleaner appearance
-- **Font Size:** Uses `$font-size-s` (0.857rem / 12px)
-- **Padding:** Horizontal padding of `$spacing-12` (0.857rem / 12px)
-
-### Usage Examples
-
-#### Basic Usage
-
-```tsx
-import { CapAlert } from '@capillarytech/blaze-ui';
-
-// Success alert
-<CapAlert type="success" title="Operation completed successfully" />
-
-// Info alert (default)
-<CapAlert title="This is an informational message" />
-
-// Warning alert
-<CapAlert type="warning" title="Please review this action" />
-
-// Error alert
-<CapAlert type="error" title="An error occurred" />
-```
-
-#### With Description
-
-```tsx
-<CapAlert
-  type="info"
-  title="Alert Title"
-  description="Additional detailed description text goes here"
-/>
-```
-
-#### With Icon
-
-```tsx
-<CapAlert
-  type="success"
-  title="Success!"
-  showIcon
-/>
-```
-
-#### Backward Compatibility
-
-```tsx
-// Old API still works (deprecated)
-<CapAlert message="This still works but shows a warning in dev mode" />
-
-// New API (recommended)
-<CapAlert title="Use this instead" />
-```
-
-### Migration Steps for Consumers
-
-1. **Replace `message` prop with `title`:**
-   ```tsx
-   // Before
-   <CapAlert message="Alert text" />
-   
-   // After
-   <CapAlert title="Alert text" />
-   ```
-
-2. **No other changes required** - All other props work exactly as before.
-
-3. **Gradual Migration:** You can migrate at your own pace. The deprecated `message` prop will continue to work until the next major version.
-
-### TypeScript
-
-```tsx
-import { CapAlert, CapAlertProps } from '@capillarytech/blaze-ui';
-
-const props: CapAlertProps = {
-  type: 'success',
-  title: 'Success message',
-  description: 'Optional description',
-  showIcon: true,
-};
-
-<CapAlert {...props} />
-```
-

package/CapAppNotEnabled/README.md

@@ -1,84 +0,0 @@
-# CapAppNotEnabled
-
-A component that displays an empty state message when an app or feature is not enabled.
-
-## Migration Notes (cap-ui-library → blaze-ui)
-
-### Summary of Changes
-
-This component has been migrated from cap-ui-library to blaze-ui with the following changes:
-
-1. **TypeScript Conversion**: Converted from JavaScript to TypeScript with proper interfaces
-2. **Functional Component**: Already a functional component, no conversion needed
-3. **Styling**: Converted from styled-components to SCSS modules with rem units (1rem = 14px)
-4. **Dependency Change**: Removed dependency on `CapHeader` component (not yet migrated)
-
-### Breaking Changes
-
-**None** - No breaking changes from cap-ui-library v8.x
-
-### Prop Changes
-
-All props remain the same:
-
-| Prop | Type | Default | Description |
-|------|------|---------|-------------|
-| `headerText` | `string` | `undefined` | Text to display in the header section |
-| `title` | `string` | `undefined` | Main title text for the empty state |
-| `description` | `string` | `undefined` | Description text below the title |
-| `className` | `string` | `undefined` | Additional CSS class name |
-| `style` | `React.CSSProperties` | `undefined` | Inline styles |
-
-### Behavioral Changes
-
-1. **Header Rendering**: The header is now rendered using `CapHeading` directly instead of `CapHeader` component. The visual appearance and behavior remain the same.
-2. **Layout**: Uses flexbox layout for better responsiveness
-
-### CSS/Styling Changes
-
-1. **px → rem conversion**: All pixel values converted to rem units (base: 14px = 1rem)
-   - Container width: `450px` → `32.143rem`
-   - Margin top: `75px` → `5.357rem`
-   - Title margin: `34px` → `2.429rem`
-   - Description margin: `8px` → `0.571rem`
-
-2. **SCSS Modules**: Replaced styled-components with SCSS modules for better maintainability
-
-### Migration Example
-
-No code changes required! The component API is fully backward compatible:
-
-**cap-ui-library (v8.x)**
-```jsx
-import CapAppNotEnabled from '@capillarytech/cap-ui-library/CapAppNotEnabled';
-
-<CapAppNotEnabled
-  headerText="Settings"
-  title="This feature is not enabled"
-  description="Please contact your administrator to enable this feature"
-/>
-```
-
-**blaze-ui**
-```jsx
-import CapAppNotEnabled from '@capillarytech/blaze-ui/CapAppNotEnabled';
-
-<CapAppNotEnabled
-  headerText="Settings"
-  title="This feature is not enabled"
-  description="Please contact your administrator to enable this feature"
-/>
-```
-
-### Dependencies
-
-This component depends on the following blaze-ui components:
-- `CapHeading` (migrated)
-- `CapLabel` (migrated)
-
-### Internal Implementation Notes
-
-1. The original component used `CapHeader` which is not yet migrated to blaze-ui
-2. For backward compatibility, the header section now uses `CapHeading` with type="h1" which provides the same visual appearance
-3. All styling has been preserved to maintain visual consistency
-4. The component uses SCSS variables from `components/styled/variables.scss` for maintainability

package/CapAskAira/README.md

@@ -1,328 +0,0 @@
-# CapAskAira
-
-CapAskAira is a collection of AI-powered “Ask AiRA” bot components and shared logic built on Redux, Redux-Saga, and React. It lives in **blaze-ui** (published as `@capillarytech/cap-ui-library`) and is consumed by apps such as **cap-loyalty-ui**, **garuda-ui**, **cap-campaigns-v2**, **cap-creatives-ui**, and **reon-bi-webapp**.
-
-This document describes the **technical architecture** of CapAskAira and how to **integrate and test** it in consuming repositories.
-
----
-
-## Table of contents
-
-1. [Overview](#overview)
-2. [Technical architecture](#technical-architecture)
-3. [Bot catalog](#bot-catalog)
-4. [Integration guide](#integration-guide)
-5. [Testing in consuming repos](#testing-in-consuming-repos)
-
----
-
-## Overview
-
-- **Purpose**: Reusable AI assistant UIs (rule writing, summarization, content generation, documentation chat, media generation, configuration, audience filters) that plug into existing Capillary apps.
-- **Stack**: React, Redux (Immutable.js state), Redux-Saga, SCSS, react-intl.
-- **Data sources**: REST APIs and/or WebSockets depending on the bot. APIs are called via a **request + getAPICallObject** contract supplied by the consuming app.
-- **Publishing**: Built and exported from **blaze-ui**; consuming apps depend on `@capillarytech/cap-ui-library` and import from `@capillarytech/cap-ui-library/CapAskAira` (or deeper paths for sagas/selectors).
-
----
-
-## Technical architecture
-
-### Module layout
-
-```
-CapAskAira/
-├── index.ts                    # Public API: default export (bot map) + reducer + domain + sagas
-├── constants.ts                # DOMAIN, WS_DOMAIN, AIRA_REDUCER_DOMAIN, rootClsPrefix
-├── reducer.ts                  # askAiraReducer (combines all bot sub-reducers)
-├── selector.ts                 # selectAskAiraDomain(state)
-├── util.ts                     # getWebsocketConnection, popup positioning, name helpers
-├── rootStyles.ts               # Root SCSS entry
-├── styles.scss                 # Shared styles ($clsPrefix: cap-ask-aira)
-├── hooks/
-│   └── useWebsocket.tsx        # WebSocket hook used by ContentGenerationBot, DocumentationChatBot
-├── UtilComponents/             # Shared UI: AiraContainer, Popup, InputBox, ErrorBar, Icons, etc.
-├── RuleGenerationBot/          # Rule writing (single rule)
-├── RuleSummarizationBot/       # Rule + summarization (write & explain)
-├── ContentGenerationBot/       # Content suggestions over WebSocket
-├── DocumentationBot/          # Documentation UI
-├── DocumentationChatBot/      # Doc Q&A (WebSocket + optional REST feedback)
-├── ConfigurationBot/           # Configuration copilot
-├── CapAiMediaGeneration/       # Image/video generation
-├── AudienceFilterBot/          # Audience filter suggestions
-├── tests/                      # Module-level tests and mock data
-└── README.md                   # This file
-```
-
-### Redux state shape
-
-- The **root** Redux key used by CapAskAira is **`ASK_AIRA`** (`AIRA_REDUCER_DOMAIN`).
-- `askAiraReducer` is a **combined reducer** over four sub-domains:
-
-| Sub-domain constant              | Bot(s)                    | Role                          |
-|----------------------------------|---------------------------|-------------------------------|
-| `RULE_REDUCER_DOMAIN`            | RuleGenerationBot         | Rule generation state         |
-| `DOC_BOT_REDUCER_DOMAIN`         | DocumentationChatBot     | Doc chat messages state       |
-| `AI_MEDIA_GENERATION`            | CapAiMediaGeneration      | Media generation state        |
-| `RULE_SUMMARIZATION_REDUCER_DOMAIN` | RuleSummarizationBot   | Rule + summarization state    |
-
-- State under `ASK_AIRA` is **Immutable.js** (e.g. `fromJS`). Selectors typically use `selectAskAiraDomain(state)` then bot-specific selectors (e.g. `makeSelectRuleGenData`) that read from the corresponding sub-domain and return plain JS where needed.
-
-### Sagas
-
-- **Saga per bot**: Each bot that uses Redux has its own saga module (e.g. `RuleSummarizationBot/saga.ts`, `CapAiMediaGeneration/saga.ts`). They export **watcher** generators (e.g. `watchGetRule`, `watchGetRuleSummarize`) and a **default export** array of watchers.
-- **Exposed from CapAskAira**:
-  - `ruleGenSaga` — RuleGenerationBot
-  - `docChatBotSaga` — DocumentationChatBot
-  - `mediaGenSaga` — CapAiMediaGeneration
-  - `ruleSummarizationBotSaga` — RuleSummarizationBot
-- **Consuming apps** do **not** use a single “root” CapAskAira saga. Instead they:
-  - **Inject** the relevant watchers into the component (or route) that mounts the bot, e.g. by importing watchers from `@capillarytech/cap-ui-library/CapAskAira/RuleSummarizationBot/saga` and composing them in the app’s own saga with `all([...localWatchers, watchGetRule(), watchGetRuleSummarize(), ...])`.
-  - Or add a saga that runs the default export array (e.g. `ruleSummarizationBotSaga`) if the app’s injector supports array-of-sagas.
-- **Bots that don’t need a saga in the app**: ContentGenerationBot and DocumentationChatBot (for the chat stream) use **WebSockets** only; no Redux saga is required for the stream. DocumentationChatBot may still use Redux for feedback; if so, its saga must be run.
-
-### Data flow (high level)
-
-1. **REST-only bots** (e.g. RuleSummarizationBot, RuleGenerationBot):  
-   Component is connected to Redux (state + actions). User action → dispatch → saga → API via `request` + `getAPICallObject` → dispatch success/failure → component reads from selector.
-
-2. **WebSocket bots** (e.g. ContentGenerationBot):  
-   Component uses `useWebsocket(WEBSOCKET_URL, onMessage, onError)`. Messages are processed in the component (or helper); no saga for the stream. Optional two-way binding with parent via `text` / `setText` props.
-
-3. **Hybrid** (e.g. DocumentationChatBot):  
-   WebSocket for streaming answers; optional REST for feedback, with state in Redux and saga for API calls.
-
-### Shared utilities
-
-- **`constants.ts`**
-  - `DOMAIN`: API base URL (dev: e.g. `http://localhost:2100`, prod: often `''` so app host is used).
-  - `WS_DOMAIN`: WebSocket base (prod: `wss://${window.location.host}`; dev can be `ws://localhost:2100`).
-  - `AIRA_REDUCER_DOMAIN = 'ASK_AIRA'`.
-  - `rootClsPrefix = 'cap-ask-aira'`.
-- **`util.ts`**
-  - `getWebsocketConnection(websocketUrl)` — returns a `Promise<WebSocket>`; in dev can pass auth via subprotocol.
-  - `getAnchoredPopupPosition`, `getBottomRightPopupPosition` — for floating popup placement.
-  - `handleEmptyValue`, `getFullNameByFirstNameLastName` — display helpers.
-- **`hooks/useWebsocket.tsx`**
-  - `(websocketUrl, onMessage?, onError?)` → `{ sendMessage, resetConnection }`. Used by ContentGenerationBot and DocumentationChatBot.
-- **`UtilComponents/AiraContainer.tsx`**
-  - Wraps bot content with a floating/fixed Aira icon, popup, title, and optional tooltip. Handles `iconPlacement` (`float-br`, `fixed-br-beamer`), `popupPlacement`, and `rootStyle`. Used by most bots.
-
-### API contract (consuming app)
-
-Bots that call REST APIs expect the **page/container** to provide:
-
-- **`request`**: function `(url: string, options?: unknown) => Promise<unknown>` (e.g. fetch wrapper).
-- **`getAPICallObject`**: function `(method: string, payload: unknown) => unknown` that returns the body/options for the request (e.g. auth headers, JSON body).
-
-URLs are built inside CapAskAira (e.g. RuleSummarizationBot uses `ASK_AIRA_ENDPOINT` from `constants.ts` plus paths like `/rule_expr/write_rule`, `/rule_expr/summarize_rule`). The app only needs to pass a generic `request` + `getAPICallObject` that work with the app’s auth and API layer.
-
----
-
-## Bot catalog
-
-| Bot                     | Description                          | Redux state      | Saga required in app | Typical use case                          |
-|-------------------------|--------------------------------------|------------------|----------------------|-------------------------------------------|
-| RuleGenerationBot      | Generate a single rule from query     | Yes (ruleGen)    | Yes (ruleGenSaga)    | One-off rule writing                      |
-| RuleSummarizationBot    | Write rule + summarize/explain rule  | Yes (rule summarization) | Yes (ruleSummarizationBotSaga) | Workflow/rule editors (e.g. cap-loyalty-ui, garuda-ui) |
-| ContentGenerationBot    | AI content suggestions (streaming)   | No               | No                   | Message/template authoring (e.g. cap-creatives-ui) |
-| DocumentationBot        | Documentation UI                     | No               | No                   | In-app docs                               |
-| DocumentationChatBot    | Doc Q&A (streaming + feedback)      | Yes (doc chat)   | Yes (docChatBotSaga) if using feedback | Help / doc search                         |
-| ConfigurationBot        | Configuration copilot                | No               | No                   | Guided setup                              |
-| CapAiMediaGeneration    | Image/video generation               | Yes (media)      | Yes (mediaGenSaga)   | Creatives (e.g. cap-creatives-ui)         |
-| AudienceFilterBot       | Audience filter suggestions          | No (props)       | No                   | Audience builder UIs                      |
-
-- **ContentGenerationBot** uses `WS_DOMAIN` and a path such as `/arya/api/v1/ask-aira-service/content_gen/get_ai_suggestions` (see `ContentGenerationBot/constants.ts`).
-- **RuleSummarizationBot** uses REST endpoints under `ASK_AIRA_ENDPOINT` (e.g. `/rule_expr/write_rule`, `/rule_expr/summarize_rule`, like/dislike).
-
----
-
-## Integration guide
-
-### 1. Add the reducer
-
-In the app’s root reducer (e.g. `initialReducer.js`):
-
-```javascript
-import { AIRA_REDUCER_DOMAIN, askAiraReducer } from '@capillarytech/cap-ui-library/CapAskAira';
-
-export const initialReducer = {
-  // ...other reducers
-  [AIRA_REDUCER_DOMAIN]: askAiraReducer,
-};
-```
-
-- Use the **exact** key `AIRA_REDUCER_DOMAIN` (`'ASK_AIRA'`) so CapAskAira selectors work.
-
-### 2. Add sagas for the bots you use
-
-Only add sagas for bots that use Redux and expose a saga (see table above).
-
-**Option A – Inject into the same container that renders the bot**
-
-Example: **RuleSummarizationBot** in a workflow config page. In that page’s saga (e.g. `ConfigureWorkflows/saga.js`):
-
-```javascript
-import {
-  watchGetRule,
-  watchGetRuleSummarize,
-  watchUpdateLikeResultRule,
-  watchUpdateLikeResultSummarize,
-  watchUpdateDislikeResultRule,
-  watchUpdateDislikeResultSummarize,
-} from '@capillarytech/cap-ui-library/CapAskAira/RuleSummarizationBot/saga';
-
-export default function* configureWorkflowSaga() {
-  yield all([
-    // ...your existing watchers
-    watchGetRule(),
-    watchGetRuleSummarize(),
-    watchUpdateLikeResultRule(),
-    watchUpdateLikeResultSummarize(),
-    watchUpdateDislikeResultRule(),
-    watchUpdateDislikeResultSummarize(),
-  ]);
-}
-```
-
-Then inject this saga with your existing `injectSaga` (e.g. key `'configureWorkflow'`). The component that renders `CapAskAira.RuleSummarizationBot` must be **connected** to Redux and pass `askAiraData` and `actions` from the store (see step 3).
-
-**Option B – CapAiMediaGeneration**
-
-Example: **cap-creatives-ui** BeeEditor. In `BeeEditor/sagas.js`:
-
-```javascript
-import { watchForMediaGeneration } from '@capillarytech/cap-ui-library/CapAskAira/CapAiMediaGeneration/saga';
-
-export default [
-  watchCreateCustomRow,
-  watchForMediaGeneration,
-];
-```
-
-Ensure this saga is injected where the media generation UI is used (e.g. same route or parent).
-
-### 3. Render the bot and connect to Redux (when required)
-
-**RuleSummarizationBot** (e.g. next to a rule editor):
-
-- The container must be **connected** to Redux and map:
-  - `askAiraData`: from selector `makeSelectRuleGenData()` (or equivalent for rule summarization domain).
-  - `actions`: bound action creators for `getRule`, `getRuleSummarize`, `resetRule`, `updateLikeResultRule`, `updateDislikeResultRule`, `updateLikeResultSummarize`, `updateDislikeResultSummarize`.
-- Pass **request** and **getAPICallObject** from your API layer (e.g. from `services/api` and a method that builds auth/body).
-- Pass **activity** (e.g. event type) so the backend can scope the rule.
-
-Example (conceptually, as in cap-loyalty-ui):
-
-```jsx
-import CapAskAira from '@capillarytech/cap-ui-library/CapAskAira';
-import { request, getAPICallObject } from '../../../services/api';
-
-// In connected component:
-<CapAskAira.RuleSummarizationBot
-  activity={eventType}
-  request={request}
-  getAPICallObject={getAPICallObject}
-  iconPlacement="float-br"
-/>
-```
-
-`askAiraData` and `actions` are usually provided by the same `connect`/`createStructuredSelector` that wraps the page.
-
-**ContentGenerationBot** (no Redux/saga):
-
-- No reducer or saga needed. Just pass **text** and **setText** to bind to parent state, plus optional labels and layout:
-
-```jsx
-<CapAskAira.ContentGenerationBot
-  text={templateMessage || ''}
-  setText={(text) => onTemplateValueChange({ target: { value: text } }, MESSAGE_TEXT)}
-  iconPlacement="float-br"
-  iconSize="1.6rem"
-  rootStyle={{ bottom: '0.5rem', right: '1.2rem', left: 'auto' }}
-/>
-```
-
-**CapAiMediaGeneration**:
-
-- Reducer is already under `ASK_AIRA` via `askAiraReducer`. Inject `watchForMediaGeneration` as above. Connect the component so it receives `imageDetails` (and any other state) and bound actions from the CapAiMediaGeneration reducer/actions.
-
-### 4. Environment / backend
-
-- **DOMAIN** and **WS_DOMAIN** in CapAskAira `constants.ts` drive API and WebSocket URLs. In production they often rely on `window.location.host`. For local dev, point them to your backend (e.g. `http://localhost:2100` and `ws://localhost:2100`).
-- Ensure the consuming app’s auth (e.g. token, org id) is passed through `request` and `getAPICallObject` so that CapAskAira’s API calls are authenticated. WebSocket auth in dev may use subprotocols (see `getWebsocketConnection` in `util.ts`).
-
-### 5. Feature flags
-
-Consuming apps often gate bots with a feature flag or permission (e.g. `!isAiRuleWritingDisabled`, `!isAiContentBotDisabled`). Render the bot only when the feature is enabled.
-
----
-
-## Testing in consuming repos
-
-### Unit tests
-
-- **Reducer**: Ensure the root reducer includes `[AIRA_REDUCER_DOMAIN]: askAiraReducer`. You can snapshot the initial state or dispatch unknown actions and assert the Ask Aira slice still exists.
-- **Selectors**: If you have selectors that depend on `ASK_AIRA`, build a minimal Immutable state with `fromJS({ ASK_AIRA: { ... } })` and test your selectors.
-- **Containers that render a bot**: Mock the CapAskAira module and assert that the correct bot component is rendered with expected props (e.g. `request`, `getAPICallObject`, `activity` for RuleSummarizationBot).
-
-Example pattern (mock default export and named exports):
-
-```javascript
-jest.mock('@capillarytech/cap-ui-library/CapAskAira', () => ({
-  __esModule: true,
-  default: {
-    RuleSummarizationBot: () => null,
-    ContentGenerationBot: () => null,
-    // ...other bots as needed
-  },
-  AIRA_REDUCER_DOMAIN: 'ASK_AIRA',
-  askAiraReducer: jest.fn((state = {}) => state),
-}));
-```
-
-- **Saga tests**: For pages that compose CapAskAira watchers (e.g. RuleSummarizationBot watchers), either:
-  - Test your own saga and mock the CapAskAira saga imports, or
-  - Import the real watchers and run them in `expectSaga` (or similar) and assert on dispatched actions and API calls.
-
-### Integration / E2E
-
-- **Backend**: Point DOMAIN/WS_DOMAIN to a test or stub backend so that opening the bot and submitting a query doesn’t depend on production.
-- **Auth**: Use test tokens/org so that `request` and `getAPICallObject` send valid auth headers; or stub `request`/`getAPICallObject` in tests to return fixed responses.
-- **Feature flags**: Enable the relevant AiRA feature flag (or override) in the test environment so the bot is visible and clickable.
-
-### Snapshot and visual
-
-- **Snapshots**: If you snapshot a container that includes a bot, the snapshot will include the bot’s subtree. Keep snapshots updated when you change bot props or upgrade the library. Mocking the bot (as above) keeps snapshots stable if you only care about the parent layout.
-- **Visual/regression**: Run visual tests against a build that includes the real CapAskAira; ensure the floating icon and popup don’t break layout (z-index, overflow, or positioning).
-
-### Testing CapAskAira in Storybook
-
-- **Storybook on nightly:** When Storybook is run or deployed on the nightly host, it uses the host origin and gets cookies/token automatically; no code change is needed.
-- **Local Storybook against nightly (temporary change):** To test CapAskAira stories locally against a real backend (e.g. nightly), make a **temporary** change in `components/CapAskAira/constants.ts`:
-  - Set `DOMAIN` to your nightly API base (e.g. `'https://crm-nightly-new.cc.capillarytech.com'`).
-  - Set `WS_DOMAIN` to the matching WebSocket base (e.g. `'wss://crm-nightly-new.cc.capillarytech.com'`).
-  - Revert these before committing. Document locally if your team needs to repeat this.
-
-### Running CapAskAira tests in blaze-ui
-
-From the **blaze-ui** repo:
-
-```bash
-npm test -- components/CapAskAira
-```
-
-This runs the tests under `components/CapAskAira/tests` and per-bot test folders (e.g. `RuleSummarizationBot/tests`, `ContentGenerationBot/tests`). Use this to validate changes before publishing and consuming in other repos.
-
----
-
-## Summary
-
-| Step | Action |
-|------|--------|
-| Reducer | Add `[AIRA_REDUCER_DOMAIN]: askAiraReducer` to root reducer. |
-| Saga | For RuleSummarizationBot, RuleGenerationBot, DocumentationChatBot, CapAiMediaGeneration: import their watchers and run them in the saga for the route/container that mounts the bot. |
-| Connect | For bots that use Redux, connect the container and pass `askAiraData`, `actions`, `request`, `getAPICallObject` (and any bot-specific props like `activity`). |
-| REST/WS | Provide `request` + `getAPICallObject`; ensure DOMAIN/WS_DOMAIN and auth work for your environment. |
-| Tests | Mock CapAskAira in unit tests; use real or stubbed backend and auth in integration; run `npm test -- --testPathPattern=CapAskAira` in blaze-ui for library changes. |
-
-For more detail on a specific bot, see its folder under `components/CapAskAira` (e.g. `RuleSummarizationBot/`, `ContentGenerationBot/`) for types, constants, API helpers, and selectors.

package/CapBanner/README.md

@@ -1,4 +0,0 @@
-# CapBanner Migration (v3→v6)
-
-## Breaking Changes from cap-ui-library v8.x
-**No breaking changes from cap-ui-library v8.x**