@redsift/products 12.5.10 → 12.5.11-muiv6

package/CONTRIBUTING.md

@@ -48,7 +48,7 @@ The Design System is following a monorepo architecture, providing multiple packa
 
 - `@redsift/table`
 
-  This package provides datagrid components and features based on [MUI DataGrid](https://mui.com/x/react-data-grid/). The muiv6 and muiv7 branches use MUI DataGrid Pro; muiv8 (main) uses MUI DataGrid Premium. A [Pro or Premium license](https://mui.com/x/introduction/licensing/) from MUI is required.
+  This package provides datagrid components and features based on [MUI DataGrid](https://mui.com/x/react-data-grid/). The muiv6 branch uses MUI DataGrid Pro; the default line (`main`) uses MUI DataGrid Premium. A [Pro or Premium license](https://mui.com/x/introduction/licensing/) from MUI is required.
 
 - `@redsift/charts`
 
@@ -416,22 +416,22 @@ yarn build:products
 
 ## Publishing a release
 
-> **Canonical process:** the full, up-to-date release workflow — the three parallel MUI DataGrid version lines (muiv6 / muiv7 / muiv8), peer-dependency bumps, docs/MCP regeneration and the pre-release checklist — lives in **`.github/instructions/release.instructions.md`**. Follow that as the source of truth. The steps below are a simplified single-line summary and omit the multi-version release details.
+> **Canonical process:** the full, up-to-date release workflow — the two parallel MUI DataGrid version lines (default / muiv6), peer-dependency bumps, docs/MCP regeneration and the pre-release checklist — lives in **`.github/instructions/release.instructions.md`**. Follow that as the source of truth. The steps below are a simplified single-line summary and omit the multi-version release details.
 
 ### Stable release
 
-Releases go through the one-command `yarn release` CLI — not a manual `lerna publish`. See `.github/instructions/release.instructions.md` for the full flow (all three lines, pre-release checklist, post steps).
+Releases go through the one-command `yarn release` CLI — not a manual `lerna publish`. See `.github/instructions/release.instructions.md` for the full flow (both lines, pre-release checklist, post steps).
 
 1. Login to NPM with an authorized account: `npm login`
-2. Dry-run the readiness gate on all three lines: `yarn release stable X.Y.Z --dry-run` (validates each line and stops before anything irreversible)
-3. When green, publish: `yarn release stable X.Y.Z` — the CLI preflights, then publishes `X.Y.Z-muiv6`, `X.Y.Z-muiv7`, and `X.Y.Z`, pausing only for the per-line npm OTP. It then creates the GitHub release notes, opens (never merges) the `release/X.Y.Z-muiv8` → `main` PR, and cuts the next release branches.
+2. Dry-run the readiness gate on both lines: `yarn release stable X.Y.Z --dry-run` (validates each line and stops before anything irreversible)
+3. When green, publish: `yarn release stable X.Y.Z` — the CLI preflights, then publishes `X.Y.Z-muiv6` and `X.Y.Z`, pausing only for the per-line npm OTP. It then creates the GitHub release notes, opens (never merges) the `release/X.Y.Z` → `main` PR, and cuts the next release branches.
 
 ### Alpha release
 
-If you need to test your contribution in a product before releasing — and you're not using `yarn link` — publish to the live alpha channel (muiv8-based, npm dist-tag `alpha`). There are no per-feature alpha branches to create or recreate.
+If you need to test your contribution in a product before releasing — and you're not using `yarn link` — publish to the live alpha channel (default-line-based, npm dist-tag `alpha`). There are no per-feature alpha branches to create or recreate.
 
 1. Login to NPM with an authorized account: `npm login`
-2. Check out the current muiv8 release branch: `git checkout release/X.Y.Z-muiv8`
-3. Publish: `yarn release alpha` — the CLI derives the next `X.Y.Z-muiv8-alpha.N` from the tags, runs the single-line preflight, and publishes (only the npm OTP is manual)
+2. Check out the current default release branch: `git checkout release/X.Y.Z`
+3. Publish: `yarn release alpha` — the CLI derives the next `X.Y.Z-alpha.N` from the tags, runs the single-line preflight, and publishes (only the npm OTP is manual)
 
-To iterate, push more commits to the muiv8 branch and run `yarn release alpha` again.
+To iterate, push more commits to the default release branch and run `yarn release alpha` again.

package/bimi-checker.d.ts

@@ -1,67 +1,8 @@
 import * as _redsift_design_system from '@redsift/design-system';
-import React, { ReactNode, ComponentProps } from 'react';
+import React, { ComponentProps, ReactNode } from 'react';
 import { CardStatus } from '@redsift/signal-logic';
 export { BIMI_CHECKER_SIGNAL_TYPES, BimiCheckerSignalType, CARD_STATUS, SIGNAL_TYPES, STATUS_COLORS, STATUS_ICONS, STATUS_ICON_STYLES, SignalType, getStatusColor, getStatusIcon, getStatusIconStyle, isCardStatus, isFailureStatus, isSuccessStatus, isWarningStatus, mapStatusToDetailedCardColor, normalizeStatus } from '@redsift/signal-logic';
 
-/**
- * Signal Cards Theme Configuration
- *
- * This context provides theme configuration to signal card components,
- * eliminating the need to pass `useInvestigateColors` through every component layer.
- */
-interface SignalCardTheme {
-    /**
-     * Whether to use Investigate-specific colors and fonts.
-     * When true, applies custom fonts and color palette for the Investigate tool.
-     */
-    useInvestigateColors: boolean;
-}
-interface SignalCardThemeProviderProps {
-    children: ReactNode;
-    /**
-     * Theme configuration to apply to all signal card descendants
-     */
-    theme?: Partial<SignalCardTheme>;
-}
-/**
- * Provider component for Signal Card theming.
- *
- * Wrap signal card components with this provider to set theme options
- * without passing props through every component level.
- *
- * This provider injects CSS custom properties (--sc-*) that components use for styling.
- *
- * @example
- * ```tsx
- * <SignalCardThemeProvider theme={{ useInvestigateColors: true }}>
- *   <SignalCardList signals={signals} />
- * </SignalCardThemeProvider>
- * ```
- */
-declare const SignalCardThemeProvider: React.FC<SignalCardThemeProviderProps>;
-/**
- * Hook to access the current signal card theme.
- *
- * Components can use this hook to access theme configuration
- * without requiring explicit props.
- *
- * @example
- * ```tsx
- * const { useInvestigateColors } = useSignalCardTheme();
- * ```
- */
-declare const useSignalCardTheme: () => SignalCardTheme;
-/**
- * Hook that combines prop value with context value.
- * Prop value takes precedence over context when explicitly provided.
- *
- * Components can receive useInvestigateColors via props or context.
- *
- * @param propValue - Explicitly passed prop value (takes precedence)
- * @returns Resolved theme configuration
- */
-declare const useResolvedTheme: (propValue?: boolean) => SignalCardTheme;
-
 /**
  * Common props shared by all signal card components. These cover layout options
  * that ultimately map to `SignalCardNormal`.
@@ -94,22 +35,34 @@ interface SignalCardSharedProps extends Omit<ComponentProps<'div'>, 'children' |
 }
 
 /**
- * Component props.
+ * SPF report item from the BIMI Checker API
  */
-interface SignalCardBimiProps extends SignalCardSharedProps {
-    /**
-     * JMAP data containing BIMI and DMARC information from the email security report.
-     */
-    jmap: {
-        extsecrep: {
-            bimi?: any;
-            dmarc?: any;
-        };
-    };
+interface SpfReportItem {
+    status?: string;
+    message?: string;
+    spfError?: string;
+}
+interface SpfDetails {
+    raw?: string | string[] | null;
+    status?: string | null;
+    txtExtractedFrom?: string | null;
+    report?: SpfReportItem[];
+    [key: string]: unknown;
+}
+/**
+ * Props for the SignalCardSpfDomain component.
+ *
+ * Simplified SPF Domain Card for BIMI Checker - shows only pass/fail status and raw SPF record.
+ */
+interface SignalCardSpfDomainProps extends SignalCardSharedProps {
     /**
-     * Optional callback invoked when the component mounts.
+     * JMAP data containing SPF authentication results
      */
-    onComponentMount?: () => void;
+    jmap?: {
+        extsecrep?: {
+            spf?: SpfDetails | null;
+        } | null;
+    } | null;
 }
 
 type DmarcResult = {
@@ -138,35 +91,82 @@ interface SignalCardDmarcDomainProps extends SignalCardSharedProps {
 }
 
 /**
- * SPF report item from the BIMI Checker API
+ * Component props.
  */
-interface SpfReportItem {
-    status?: string;
-    message?: string;
-    spfError?: string;
-}
-interface SpfDetails {
-    raw?: string | string[] | null;
-    status?: string | null;
-    txtExtractedFrom?: string | null;
-    report?: SpfReportItem[];
-    [key: string]: unknown;
+interface SignalCardBimiProps extends SignalCardSharedProps {
+    /**
+     * JMAP data containing BIMI and DMARC information from the email security report.
+     */
+    jmap: {
+        extsecrep: {
+            bimi?: any;
+            dmarc?: any;
+        };
+    };
+    /**
+     * Optional callback invoked when the component mounts.
+     */
+    onComponentMount?: () => void;
 }
+
 /**
- * Props for the SignalCardSpfDomain component.
+ * Signal Cards Theme Configuration
  *
- * Simplified SPF Domain Card for BIMI Checker - shows only pass/fail status and raw SPF record.
+ * This context provides theme configuration to signal card components,
+ * eliminating the need to pass `useInvestigateColors` through every component layer.
  */
-interface SignalCardSpfDomainProps extends SignalCardSharedProps {
+interface SignalCardTheme {
     /**
-     * JMAP data containing SPF authentication results
+     * Whether to use Investigate-specific colors and fonts.
+     * When true, applies custom fonts and color palette for the Investigate tool.
      */
-    jmap?: {
-        extsecrep?: {
-            spf?: SpfDetails | null;
-        } | null;
-    } | null;
+    useInvestigateColors: boolean;
+}
+interface SignalCardThemeProviderProps {
+    children: ReactNode;
+    /**
+     * Theme configuration to apply to all signal card descendants
+     */
+    theme?: Partial<SignalCardTheme>;
 }
+/**
+ * Provider component for Signal Card theming.
+ *
+ * Wrap signal card components with this provider to set theme options
+ * without passing props through every component level.
+ *
+ * This provider injects CSS custom properties (--sc-*) that components use for styling.
+ *
+ * @example
+ * ```tsx
+ * <SignalCardThemeProvider theme={{ useInvestigateColors: true }}>
+ *   <SignalCardList signals={signals} />
+ * </SignalCardThemeProvider>
+ * ```
+ */
+declare const SignalCardThemeProvider: React.FC<SignalCardThemeProviderProps>;
+/**
+ * Hook to access the current signal card theme.
+ *
+ * Components can use this hook to access theme configuration
+ * without requiring explicit props.
+ *
+ * @example
+ * ```tsx
+ * const { useInvestigateColors } = useSignalCardTheme();
+ * ```
+ */
+declare const useSignalCardTheme: () => SignalCardTheme;
+/**
+ * Hook that combines prop value with context value.
+ * Prop value takes precedence over context when explicitly provided.
+ *
+ * Components can receive useInvestigateColors via props or context.
+ *
+ * @param propValue - Explicitly passed prop value (takes precedence)
+ * @returns Resolved theme configuration
+ */
+declare const useResolvedTheme: (propValue?: boolean) => SignalCardTheme;
 
 /**
  * BIMI signal card - displays Brand Indicators for Message Identification status.