@designcrowd/library.brand-page 6.2.11 → 6.2.12

package/lib/src/metadata-builder/parsers/section-tool-arguments.d.ts

@@ -4,7 +4,7 @@
  * Canonical reference: service.ai-pipelines/src/agents/website/section_schemas.py
  * Every field defined there has a corresponding TS field here.
  */
-import type { ContentType } from '../../brand-page/models';
+import type { ContentType, CanonicalTextStyleType } from '../../brand-page/models';
 /** Content types not supported by the AI builder. */
 type UnsupportedContentType = 'logo' | 'video' | 'map' | 'request-payment' | 'shop-section';
 export type SectionType = Exclude<ContentType, UnsupportedContentType>;
@@ -17,6 +17,10 @@ export interface TiptapMark {
         fontFamily?: string;
         letterSpacing?: string;
         lineHeight?: string;
+        fontWeight?: string;
+        fontStyle?: string;
+        textDecoration?: string;
+        textDecorationReset?: boolean;
     };
 }
 export interface TiptapTextNode {
@@ -46,6 +50,15 @@ export type RichTextField = string | TiptapDocument;
 /** Type guard: checks if a value is a TiptapDocument object. */
 export declare const isTiptapDocument: (value: unknown) => value is TiptapDocument;
 export interface TextStyleArguments {
+    /**
+     * BP-5969 — the canonical text role this element links to. The AI names a role (roles are the
+     * site's predefined styling); typography then follows the role and only a genuinely divergent
+     * property is sent below as a sparse override. Absent, a retired key, or `none` reconnects
+     * instead (`applyAiStyle`, `reconnectTextStyle`): the field's starting role, else the retired
+     * role's successor, else the role nearest its size — keeping the look as overrides, never fully
+     * detached from a role.
+     */
+    textStyleType?: CanonicalTextStyleType | null;
     fontSize?: string | null;
     color?: string | null;
     fontWeight?: string | null;
@@ -72,6 +85,8 @@ export interface TextStyleArguments {
  * (`_button_text_style_field`) for the AI-side mirror.
  */
 export interface ButtonTextStyleArguments {
+    /** BP-5969 — the canonical role a button label links to. See `TextStyleArguments.textStyleType`. */
+    textStyleType?: CanonicalTextStyleType | null;
     color?: string | null;
     fontSize?: string | null;
     fontWeight?: string | null;
@@ -218,8 +233,10 @@ export interface SocialLink {
     url?: string;
 }
 export interface SocialLinksSectionArguments {
+    title?: RichTextField;
     links?: SocialLink[];
     icon_style?: 'none' | 'square' | 'circle';
+    title_style?: TextStyleArguments;
     /** Style for the social-icon SVG fill (filled from the palette by the slot router). */
     icon_fill_style?: TextStyleArguments;
     /** Style for the icon container background (used when icon_style is 'square' or 'circle'). */

package/lib/src/metadata-builder/sanitizers/rte-schema-check.js

@@ -1,5 +1,5 @@
 import { getSchema } from '@tiptap/core';
-import { getRteExtensions } from '../../brand-page-maker/composables/rich-text-editor/getRteExtensions';
+import { getRteExtensions } from '@shared/rte-extensions.util';
 import { isTiptapDocument } from '../parsers/section-tool-arguments';
 import { rteStyleCheck, textCheck, } from './section-args-validator';
 /**

package/lib/src/metadata-builder/sanitizers/sanitizer-rules.d.ts

@@ -21,7 +21,6 @@ export declare const STYLE_RULES: {
         readonly max: 100;
     };
     readonly fontFamilyNames: Set<string>;
-    readonly fontFamilyKeys: Set<string>;
 };
 export declare const LOGO_SIZE_RULES: {
     readonly unit: "rem";

package/lib/src/metadata-builder/sanitizers/sanitizer-rules.js

@@ -4,7 +4,7 @@
  * Shared style/logo/page constraint rules and the SectionRules interface.
  * Per-section rules live colocated with each builder (e.g. banner-section.rules.ts).
  */
-import { MIN_TEXT_SIZE_PX, MAX_TEXT_SIZE_PX, MIN_LINE_HEIGHT, MAX_LINE_HEIGHT, MIN_LETTER_SPACING_PERCENT, MAX_LETTER_SPACING_PERCENT, FONT_FAMILY_CONFIGS, FONT_FAMILY_KEYS, } from '../../brand-page/constants/font.constants';
+import { MIN_TEXT_SIZE_PX, MAX_TEXT_SIZE_PX, MIN_LINE_HEIGHT, MAX_LINE_HEIGHT, MIN_LETTER_SPACING_PERCENT, MAX_LETTER_SPACING_PERCENT, FONT_FAMILY_CONFIGS, } from '../../brand-page/constants/font.constants';
 import { MAX_PAGE_TITLE_LENGTH, MAX_SUBPAGE_TITLE_LENGTH, } from '../../shared/page-settings/utils';
 import { LOGO_SLIDER_DESKTOP_MIN, LOGO_SLIDER_DESKTOP_MAX, LOGO_SLIDER_MOBILE_MIN, LOGO_SLIDER_MOBILE_MAX, } from '../../brand-page/constants/styles.constants';
 import { pxToEm } from '../../brand-page-maker/utils/text.util';
@@ -12,9 +12,9 @@ import { pxToEm } from '../../brand-page-maker/utils/text.util';
 // Applies to any TextStyleArguments object (section styles, global styles,
 // header/footer viewport overrides).
 //
-// fontFamilyNames / fontFamilyKeys use Set (not readonly arrays) because both
-// are derived dynamically from FONT_FAMILY_CONFIGS at runtime — as const
-// literal narrowing is not possible. Consumers call .has(value).
+// fontFamilyNames uses a Set (not a readonly array) because it is derived
+// dynamically from FONT_FAMILY_CONFIGS at runtime — as const literal narrowing
+// is not possible. Consumers call .has(value).
 export const STYLE_RULES = {
     // fontSize bounds are in px (natural unit for clamping).
     // Flow: parse input unit → convert to px → clamp → pxToEm(clampedPx)
@@ -33,14 +33,11 @@ export const STYLE_RULES = {
         min: MIN_LETTER_SPACING_PERCENT,
         max: MAX_LETTER_SPACING_PERCENT,
     },
-    // Two separate sets because the format differs by context:
-    //   TextStyleArguments.fontFamily             → display name (e.g. 'Playfair Display')
-    //   UpdateGlobalStylesArguments.textFontFamily → camelCase key (e.g. 'playfairDisplay')
+    // Every font the AI sends is a display name (e.g. 'Playfair Display').
     fontFamilyNames: new Set(Object.values(FONT_FAMILY_CONFIGS).map((c) => 
     // Some font names are stored with surrounding single-quotes (e.g. "'Exo 2'").
     // Strip them so the Set matches the bare names the AI sends.
     c.name.replace(/^'(.*)'$/, '$1'))),
-    fontFamilyKeys: new Set(Object.keys(FONT_FAMILY_KEYS)),
 };
 // ─── 2. Logo size rules ───────────────────────────────────────────────────────
 // Applies to logo_image_height / logo_image_width in UpdateHeaderArguments and

package/lib/src/metadata-builder/sanitizers/section-args-validator.d.ts

@@ -1,24 +1,18 @@
 import { type ItemCapRule } from './sanitizer-rules';
-/**
- * Validates CSS string-format style attrs (fontSize em, fontFamily name,
- * lineHeight unitless, letterSpacing em) against STYLE_RULES bounds.
- * Used for both RTE textStyle mark attrs and GlobalStyles textStyleOptions.
- * Returns the first error string, or null if all attrs are valid / absent.
- */
-export declare function validateStringStyleAttrs(path: string, attrs: {
+interface ValidatableStyleAttrs {
     fontSize?: string | null;
     fontFamily?: string | null;
     lineHeight?: string | null;
     letterSpacing?: string | null;
-}): string | null;
+    fontWeight?: string | null;
+    fontStyle?: string | null;
+    textDecoration?: string | null;
+}
+export declare function validateStringStyleAttrs(path: string, attrs: ValidatableStyleAttrs): string | null;
 export interface ValidationContext {
     brandPageType?: string;
     mode?: 'create' | 'update';
 }
-/**
- * A pure validation check: record + context → one error string or null.
- * All checks operate on Record<string, unknown> — no concrete section type casting.
- */
 export type SectionCheck = (record: Record<string, unknown>, ctx: ValidationContext) => string | null;
 export declare const textCheck: (field: string, max: number) => SectionCheck;
 export declare const styleCheck: (field: string) => SectionCheck;
@@ -28,10 +22,6 @@ export declare const itemStyleCheck: (arrayField: string, itemField: string) =>
 export declare const itemRteStyleCheck: (arrayField: string, itemField: string) => SectionCheck;
 export declare const enumCheck: (field: string, allowed: readonly string[], label?: string) => SectionCheck;
 export declare const itemCapCheck: (cap: ItemCapRule, label?: string) => SectionCheck;
-/**
- * Runs an array of SectionChecks against the given args and context.
- * Returns all non-null error strings.
- */
 export declare function runChecks(checks: SectionCheck[], args: Record<string, unknown>, ctx: ValidationContext): string[];
 /**
  * Validates a logo size value against LOGO_SIZE_RULES for the given viewport.
@@ -39,3 +29,4 @@ export declare function runChecks(checks: SectionCheck[], args: Record<string, u
  * Returns an error string, or null if valid / absent.
  */
 export declare function validateLogoSize(fieldLabel: string, value: string | undefined | null, viewport: 'desktop' | 'mobile'): string | null;
+export {};

package/lib/src/metadata-builder/sanitizers/section-args-validator.js

@@ -1,6 +1,15 @@
 import { isTiptapDocument, } from '../parsers/section-tool-arguments';
 import { LOGO_SIZE_RULES, STYLE_RULES, } from './sanitizer-rules';
-// ─── Helpers ──────────────────────────────────────────────────────────────────
+// Kept local to avoid the validator/schema import cycle.
+const ROLE_VAR_REF = {
+    fontFamily: 'var(--role-font-family)',
+    fontSize: 'var(--role-font-size)',
+    lineHeight: 'var(--role-line-height)',
+    letterSpacing: 'var(--role-letter-spacing)',
+    fontWeight: 'var(--role-font-weight)',
+    fontStyle: 'var(--role-font-style)',
+    textDecoration: 'var(--role-text-decoration)',
+};
 function extractPlainText(value) {
     if (typeof value === 'string')
         return value;
@@ -60,11 +69,48 @@ function validateStyleArgs(fieldLabel, style) {
         return err ? [err] : [];
     });
 }
+const isNoValue = (value) => value == null || value === '';
+const FONT_WEIGHT_VALUES = new Set([
+    'normal',
+    'bold',
+    'bolder',
+    'lighter',
+    '100',
+    '200',
+    '300',
+    '400',
+    '500',
+    '600',
+    '700',
+    '800',
+    '900',
+]);
+const FONT_STYLE_VALUES = new Set(['normal', 'italic', 'oblique']);
+const TEXT_DECORATION_KEYWORDS = new Set([
+    'underline',
+    'line-through',
+    'overline',
+]);
+const isValidTextDecoration = (value, allowRoleReset = false) => {
+    const flags = value.trim().toLowerCase().split(/\s+/).filter(Boolean);
+    if (flags.length === 0)
+        return false;
+    if (flags[0] === 'none') {
+        return ((flags.length === 1 ||
+            (allowRoleReset &&
+                flags
+                    .slice(1)
+                    .every((flag) => TEXT_DECORATION_KEYWORDS.has(flag)))) &&
+            new Set(flags).size === flags.length);
+    }
+    return (flags.every((flag) => TEXT_DECORATION_KEYWORDS.has(flag)) &&
+        new Set(flags).size === flags.length);
+};
 const RTE_MARK_PROPERTY_CHECKS = [
     (path, attrs) => {
-        if (attrs.fontSize == null)
+        if (isNoValue(attrs.fontSize))
             return null;
-        const raw = attrs.fontSize.trim().toLowerCase();
+        const raw = String(attrs.fontSize).trim().toLowerCase();
         const unit = fontUnit.allowedUnits[0];
         const match = raw.match(new RegExp(`^(\\d+(?:\\.\\d+)?)${unit}$`));
         if (!match) {
@@ -78,17 +124,17 @@ const RTE_MARK_PROPERTY_CHECKS = [
             : null;
     },
     (path, attrs) => {
-        if (attrs.fontFamily == null)
+        if (isNoValue(attrs.fontFamily))
             return null;
         return !fontFamilyNames.has(attrs.fontFamily)
             ? `"${path}.fontFamily" "${attrs.fontFamily}" is not a recognized font family`
             : null;
     },
     (path, attrs) => {
-        if (attrs.lineHeight == null)
+        if (isNoValue(attrs.lineHeight))
             return null;
         const val = parseFloat(attrs.lineHeight);
-        const isUnitless = !isNaN(val) && attrs.lineHeight.trim() === String(val);
+        const isUnitless = !isNaN(val) && String(attrs.lineHeight).trim() === String(val);
         if (!isUnitless) {
             return `"${path}.lineHeight" must be a unitless number (got "${attrs.lineHeight}")`;
         }
@@ -97,11 +143,10 @@ const RTE_MARK_PROPERTY_CHECKS = [
             : null;
     },
     (path, attrs) => {
-        if (attrs.letterSpacing == null)
+        if (isNoValue(attrs.letterSpacing))
             return null;
-        const raw = attrs.letterSpacing.trim().toLowerCase();
-        // "0" is valid CSS without units — treat as 0em.
-        if (raw === '0')
+        const raw = String(attrs.letterSpacing).trim().toLowerCase();
+        if (raw === '0' || raw === 'normal')
             return null;
         const match = raw.match(/^(\d+(?:\.\d+)?)em$/);
         if (!match) {
@@ -114,13 +159,28 @@ const RTE_MARK_PROPERTY_CHECKS = [
             ? `"${path}.letterSpacing" ${attrs.letterSpacing} is out of bounds (${minEm}em–${maxEm}em)`
             : null;
     },
+    (path, attrs) => {
+        if (isNoValue(attrs.fontWeight))
+            return null;
+        return !FONT_WEIGHT_VALUES.has(String(attrs.fontWeight).trim().toLowerCase())
+            ? `"${path}.fontWeight" "${attrs.fontWeight}" is not a recognized value`
+            : null;
+    },
+    (path, attrs) => {
+        if (isNoValue(attrs.fontStyle))
+            return null;
+        return !FONT_STYLE_VALUES.has(String(attrs.fontStyle).trim().toLowerCase())
+            ? `"${path}.fontStyle" "${attrs.fontStyle}" is not a recognized value`
+            : null;
+    },
+    (path, attrs) => {
+        if (isNoValue(attrs.textDecoration))
+            return null;
+        return !isValidTextDecoration(String(attrs.textDecoration))
+            ? `"${path}.textDecoration" "${attrs.textDecoration}" is not a recognized value`
+            : null;
+    },
 ];
-/**
- * Validates CSS string-format style attrs (fontSize em, fontFamily name,
- * lineHeight unitless, letterSpacing em) against STYLE_RULES bounds.
- * Used for both RTE textStyle mark attrs and GlobalStyles textStyleOptions.
- * Returns the first error string, or null if all attrs are valid / absent.
- */
 export function validateStringStyleAttrs(path, attrs) {
     for (const check of RTE_MARK_PROPERTY_CHECKS) {
         const err = check(path, attrs);
@@ -130,7 +190,25 @@ export function validateStringStyleAttrs(path, attrs) {
     return null;
 }
 function validateRteMarkStyle(path, attrs) {
-    return validateStringStyleAttrs(path, attrs);
+    const literalOnly = {};
+    for (const [attr, value] of Object.entries(attrs)) {
+        if (attr === 'textDecorationReset') {
+            if (value !== true && value !== false && value != null) {
+                return `"${path}.textDecorationReset" must be a boolean`;
+            }
+            continue;
+        }
+        if (attr === 'textDecoration' &&
+            typeof value === 'string' &&
+            value.trim().startsWith('none ') &&
+            isValidTextDecoration(value, true)) {
+            continue;
+        }
+        if (value !== ROLE_VAR_REF[attr]) {
+            literalOnly[attr] = value;
+        }
+    }
+    return validateStringStyleAttrs(path, literalOnly);
 }
 function validateRteDocument(fieldLabel, doc) {
     for (const block of doc.content) {
@@ -148,7 +226,6 @@ function validateRteDocument(fieldLabel, doc) {
     }
     return null;
 }
-// ─── Check factories ──────────────────────────────────────────────────────────
 export const textCheck = (field, max) => (record) => {
     const value = record[field];
     if (value == null)
@@ -240,10 +317,6 @@ export const itemCapCheck = (cap, label) => (record, ctx) => {
         ? `"${cap.arrayField}" has ${items.length} items but "${label ?? 'section'}" supports a maximum of ${limit}`
         : null;
 };
-/**
- * Runs an array of SectionChecks against the given args and context.
- * Returns all non-null error strings.
- */
 export function runChecks(checks, args, ctx) {
     return checks.flatMap((check) => {
         const err = check(args, ctx);

package/lib/src/shared/color-palette/section-color-matches.js

@@ -1,12 +1,9 @@
-// Leaf import, not the `@brand-page/utils` barrel: the barrel cycles through the
-// settings-component graph this module is reached from.
-import { resolveTextColor } from '@brand-page/utils/text-style.util';
 import { collectRteTextColors } from '@shared/color-strategies/rte-color';
 import { showsTextBackgroundColor } from '@shared/content-settings/text-background-color.util';
 import { pairedRteTextField } from '@shared/color-strategies/rte-field-pairs';
 // From the leaf, not `rich-text-editor.util` — that module drags dompurify and the
 // render helpers in at runtime, which this pure collector must not.
-import { isRteHtmlString } from '@brand-page-maker/utils/rte-shape';
+import { isRteHtmlString } from '@shared/rte-shape.util';
 import { resolveColorMatchState, resolveShapeMatchState, } from './color-match-state';
 /**
  * The fields that paint a layer. Deliberately NOT derived from `FIELD_SLOT_MAP`,
@@ -121,20 +118,12 @@ export const collectSectionColorMatches = (config, content, { context, textStyle
     };
     const buildTextStyleMatch = (style, fieldName, label) => {
         const linkedStyleType = style.textStyleType;
-        const inheritedColor = linkedStyleType
-            ? textStyleOptions?.[linkedStyleType]?.style?.color
-            : undefined;
-        // The renderer's cascade — element colour over the global style's — via the
-        // same helper `TextStyleField.selectedTextStyle` uses.
-        const cascaded = resolveTextColor(style, inheritedColor ? { color: inheritedColor } : undefined);
-        // The third level, which `resolveTextColor` does not model because the
-        // renderer gets it free from root CSS inheritance.
-        const value = cascaded || defaultTextColor;
-        const state = resolveColorMatchState({
-            value,
-            linkedStyleType,
-            inheritedColor,
-        });
+        // ADR-0020: a role carries no colour, so a field with no colour of its own renders
+        // the page base coat (defaultTextColor), never a role colour. Element-first, else
+        // the base coat — there is no longer a `global-style` rung.
+        const ownColour = style.color;
+        const value = ownColour || defaultTextColor;
+        const state = resolveColorMatchState({ value, linkedStyleType });
         if (!state) {
             return undefined;
         }
@@ -143,13 +132,8 @@ export const collectSectionColorMatches = (config, content, { context, textStyle
             label,
             source: 'field',
             group: 'element',
-            origin: style.color
-                ? 'element'
-                : inheritedColor
-                    ? 'global-style'
-                    : 'site-default',
-            // Named on the site-default level too: "lands on the site default *through*
-            // Titles" is what tells the admin where to fix it.
+            origin: ownColour ? 'element' : 'site-default',
+            // Names the link so a site-default readout can say which role's text it is.
             originStyleType: linkedStyleType,
             entries: [toEntry(value, state, resolveColor)],
         };

package/lib/src/shared/color-strategies/color-strategies.d.ts

@@ -106,6 +106,21 @@ export declare const raisedLayerFor: (content?: unknown) => RaisedLayer | undefi
  * has no muted role, and adding one would revise the derivation, not this table.
  */
 export declare const FIELD_SLOT_MAP: Record<string, ColorSlot>;
+/**
+ * Style fields a strategy writes although no settings config declares them, per section type,
+ * each with the config field it `follows` and the `textField` it colours: written only when the
+ * followed field is assignable, so it shares its visibility gate, and its slot still comes from
+ * `FIELD_SLOT_MAP`. A rich-text `textField` is recoloured with it, as a pair is.
+ *
+ * The payment and shop success message is edited through its `successMessage` text field, so
+ * the config walk never reaches its style. It follows the description it is seeded from
+ * (`text-role-reconnect.util.ts`). The contact form's is not listed. Not in
+ * `RTE_SECTION_FIELD_PAIRS`: released migration-21 reads that table.
+ */
+export declare const STYLE_FIELDS_OUTSIDE_CONFIG: Record<string, Record<string, {
+    follows: string;
+    textField: string;
+}>>;
 /**
  * Resolve a field's slot: its default placement, promoted to the raised layer when this
  * section puts it there AND that layer is actually being painted.

package/lib/src/shared/color-strategies/color-strategies.js

@@ -222,6 +222,37 @@ export const FIELD_SLOT_MAP = {
     positionStyle: 'onSurface',
     testimonialStyle: 'onSurface',
 };
+/**
+ * Style fields a strategy writes although no settings config declares them, per section type,
+ * each with the config field it `follows` and the `textField` it colours: written only when the
+ * followed field is assignable, so it shares its visibility gate, and its slot still comes from
+ * `FIELD_SLOT_MAP`. A rich-text `textField` is recoloured with it, as a pair is.
+ *
+ * The payment and shop success message is edited through its `successMessage` text field, so
+ * the config walk never reaches its style. It follows the description it is seeded from
+ * (`text-role-reconnect.util.ts`). The contact form's is not listed. Not in
+ * `RTE_SECTION_FIELD_PAIRS`: released migration-21 reads that table.
+ */
+export const STYLE_FIELDS_OUTSIDE_CONFIG = {
+    'request-payment': {
+        successMessageStyle: {
+            follows: 'descriptionStyle',
+            textField: 'successMessage',
+        },
+    },
+    'support-me': {
+        successMessageStyle: {
+            follows: 'descriptionStyle',
+            textField: 'successMessage',
+        },
+    },
+    'shop-section': {
+        successMessageStyle: {
+            follows: 'descriptionStyle',
+            textField: 'successMessage',
+        },
+    },
+};
 /**
  * Resolve a field's slot: its default placement, promoted to the raised layer when this
  * section puts it there AND that layer is actually being painted.

package/lib/src/shared/color-strategies/rte-color.d.ts

@@ -1,4 +1,12 @@
 import type { JSONContent } from '@tiptap/vue-3';
+/**
+ * True when the doc has at least one run `setRteTextColor` will actually colour:
+ * `docHasTextRun` (rte-authoring.util.ts) counts any text node, unmarked whitespace included, so
+ * a doc whose only run IS unmarked whitespace passes that check, `setRteTextColor` walks it and
+ * returns a (structurally unchanged) doc, and a caller that then deletes the style colour on any
+ * truthy return loses the colour with nowhere left to hold it.
+ */
+export declare const docHasColourableRun: (doc: JSONContent) => boolean;
 /**
  * Set `color` on every text node in an RTE document, returning a NEW document.
  *

package/lib/src/shared/color-strategies/rte-color.js

@@ -16,6 +16,9 @@ import { DEFAULT_LINK_COLOR } from '@src/constants/rich-text-editor.constants';
  *
  * **Overwrites deliberate literal colours** — a hand-picked `#FF0000` becomes the slot
  * colour. Consistent with the macro's replace-not-merge semantics, and one undo reverts it.
+ *
+ * MIGRATION-22 SNAPSHOT DEPENDENCY: its colour bake uses `collectRteTextColors` and
+ * `fillUncolouredRteText`. Pin the v22 implementation before changing either after release.
  */
 /**
  * The `highlight` mark — the text BACKGROUND colour — is STRIPPED. A strategy owns the
@@ -33,6 +36,19 @@ const HIGHLIGHT_MARK = 'highlight';
  * visible line, so it still gets the colour.
  */
 const isUnmarkedWhitespace = (node) => !node.marks?.length && typeof node.text === 'string' && !node.text.trim();
+/**
+ * True when the doc has at least one run `setRteTextColor` will actually colour:
+ * `docHasTextRun` (rte-authoring.util.ts) counts any text node, unmarked whitespace included, so
+ * a doc whose only run IS unmarked whitespace passes that check, `setRteTextColor` walks it and
+ * returns a (structurally unchanged) doc, and a caller that then deletes the style colour on any
+ * truthy return loses the colour with nowhere left to hold it.
+ */
+export const docHasColourableRun = (doc) => {
+    const walk = (node) => node.type === 'text'
+        ? !isUnmarkedWhitespace(node)
+        : (node.content ?? []).some(walk);
+    return walk(doc);
+};
 /**
  * A hyperlink run. Exempt from the strategy colour on both sides: the setter forces
  * `DEFAULT_LINK_COLOR` instead (links are always the same blue, per `AutoLink`), and the

package/lib/src/shared/color-strategies/rte-field-pairs.d.ts

@@ -5,6 +5,9 @@
  * lookup, so keeping it out of `rich-text-editor.util.ts` (which pulls `dompurify`
  * at runtime) lets both read one source of truth without the strategy path dragging
  * in the editor toolchain.
+ *
+ * MIGRATION-22 SNAPSHOT DEPENDENCY: this list controls that migration's RTE conversion and colour
+ * walk. Preserve its v22 interpretation in the migration before changing this list after release.
  */
 export interface RTEFieldPair {
     textField: string;
@@ -21,3 +24,23 @@ export declare const RTE_SECTION_FIELD_PAIRS: Record<string, RTEFieldPair[]>;
  * brandSite caller would need the `textItems[]` walk instead.
  */
 export declare const pairedRteTextField: (sectionType: string, styleField: string) => string | undefined;
+/**
+ * Sections whose title/description are plain `string` (rendered by `TextWrapper`'s plain path from
+ * `style.color`, never an RTE mark) rather than RTE-managed docs. A section listed here is excluded
+ * from the RTE style-field set below, the migration's plain→doc conversion, the maker's add-time doc
+ * authoring, AND the editor gate (`RTE_ALLOWED_SECTION_TYPES`) — the single classification for
+ * "this field is plain, not RTE".
+ *
+ * **Currently empty.** shop/request-payment/support-me were RTE-editable on `develop` (title stored
+ * as `string`, editor mounted via the pairs map, the runtime mapper converting on the fly); BP-5969
+ * briefly classified them plain, which regressed that. They are RTE again — authored as docs at the
+ * factory and converted for existing sites by migration-22 — so this set is empty. Kept as the seam:
+ * to make a future section's title/description plain, add its type here and every consumer honours it.
+ */
+export declare const PLAIN_TEXT_PAIR_SECTIONS: Set<string>;
+/**
+ * The genuinely-RTE style fields for a content type: the pairs map (minus the plain-by-design
+ * sections) plus the `text` section's own `textStyle`. Single source of truth shared by the
+ * migration (conversion + colour decouple) and the maker's content authoring.
+ */
+export declare const rteStyleFieldsFor: (type: string) => string[];

package/lib/src/shared/color-strategies/rte-field-pairs.js

@@ -5,6 +5,9 @@
  * lookup, so keeping it out of `rich-text-editor.util.ts` (which pulls `dompurify`
  * at runtime) lets both read one source of truth without the strategy path dragging
  * in the editor toolchain.
+ *
+ * MIGRATION-22 SNAPSHOT DEPENDENCY: this list controls that migration's RTE conversion and colour
+ * walk. Preserve its v22 interpretation in the migration before changing this list after release.
  */
 export const RTE_SECTION_FIELD_PAIRS = {
     'banner-section': [
@@ -80,3 +83,28 @@ export const pairedRteTextField = (sectionType, styleField) => {
     }
     return RTE_SECTION_FIELD_PAIRS[sectionType]?.find((pair) => pair.styleField === styleField)?.textField;
 };
+/**
+ * Sections whose title/description are plain `string` (rendered by `TextWrapper`'s plain path from
+ * `style.color`, never an RTE mark) rather than RTE-managed docs. A section listed here is excluded
+ * from the RTE style-field set below, the migration's plain→doc conversion, the maker's add-time doc
+ * authoring, AND the editor gate (`RTE_ALLOWED_SECTION_TYPES`) — the single classification for
+ * "this field is plain, not RTE".
+ *
+ * **Currently empty.** shop/request-payment/support-me were RTE-editable on `develop` (title stored
+ * as `string`, editor mounted via the pairs map, the runtime mapper converting on the fly); BP-5969
+ * briefly classified them plain, which regressed that. They are RTE again — authored as docs at the
+ * factory and converted for existing sites by migration-22 — so this set is empty. Kept as the seam:
+ * to make a future section's title/description plain, add its type here and every consumer honours it.
+ */
+export const PLAIN_TEXT_PAIR_SECTIONS = new Set([]);
+/**
+ * The genuinely-RTE style fields for a content type: the pairs map (minus the plain-by-design
+ * sections) plus the `text` section's own `textStyle`. Single source of truth shared by the
+ * migration (conversion + colour decouple) and the maker's content authoring.
+ */
+export const rteStyleFieldsFor = (type) => {
+    if (PLAIN_TEXT_PAIR_SECTIONS.has(type))
+        return [];
+    const fields = (RTE_SECTION_FIELD_PAIRS[type] ?? []).map((pair) => pair.styleField);
+    return type === 'text' ? [...fields, 'textStyle'] : fields;
+};