@riverbankcms/sdk 0.135.1 → 0.137.0

package/dist/_dts/theme-core/src/gradients/types.d.ts

@@ -50,3 +50,8 @@ export declare const gradientConfigSchema: z.ZodObject<{
     }, z.core.$strip>>;
 }, z.core.$strip>;
 export type GradientConfig = z.infer<typeof gradientConfigSchema>;
+export declare const gradientsSchema: z.ZodObject<{
+    button: z.ZodOptional<z.ZodNullable<z.ZodString>>;
+    hero: z.ZodOptional<z.ZodNullable<z.ZodString>>;
+    background: z.ZodOptional<z.ZodNullable<z.ZodString>>;
+}, z.core.$strip>;

package/dist/_dts/theme-core/src/header/interactionPalette.d.ts

@@ -1,9 +1,27 @@
 import { z } from 'zod';
-export declare const headerInteractionPaletteValues: readonly ["primary", "secondary", "accent"];
+/**
+ * The palettes that fill the nav link with a colour on hover and focus. Each
+ * one names a background/foreground token pair.
+ */
+export declare const headerInteractionPillPaletteValues: readonly ["primary", "secondary", "accent"];
+export type HeaderInteractionPillPalette = (typeof headerInteractionPillPaletteValues)[number];
+/**
+ * "No pill": the nav link keeps whatever hover treatment its recipe compiled,
+ * and the palette step writes nothing at all (#1318 Phase 4c decision 2).
+ *
+ * It exists because "a colour change on hover, no filled background" was not
+ * expressible in the vocabulary, and it is what
+ * `anna-raven-therapy-and-yoga` and `kirtan-lucy` have rendered since before
+ * the palette existed. Without it those two rows can only be classified as a
+ * conscious visual change.
+ */
+export declare const headerInteractionQuietPalette = "quiet";
+export declare const headerInteractionPaletteValues: readonly ["primary", "secondary", "accent", "quiet"];
 export declare const headerInteractionPaletteSchema: z.ZodEnum<{
     accent: "accent";
     primary: "primary";
     secondary: "secondary";
+    quiet: "quiet";
 }>;
 export type HeaderInteractionPalette = z.infer<typeof headerInteractionPaletteSchema>;
 export type HeaderInteractionPalettePreference = 'recommended' | HeaderInteractionPalette;
@@ -11,4 +29,9 @@ export type HeaderInteractionPalettePair = Readonly<{
     backgroundToken: 'primary' | 'secondary' | 'accent';
     foregroundToken: 'onPrimary' | 'onSecondary' | 'onAccent';
 }>;
-export declare function headerInteractionPalettePair(palette: HeaderInteractionPalette): HeaderInteractionPalettePair;
+/**
+ * Narrowed to the pill palettes on purpose: `'quiet'` has no token pair, and a
+ * caller that reaches this function without excluding it first is a type error
+ * rather than a runtime surprise.
+ */
+export declare function headerInteractionPalettePair(palette: HeaderInteractionPillPalette): HeaderInteractionPalettePair;

package/dist/_dts/theme-core/src/header/legacyHeaderVariant.d.ts

@@ -44,12 +44,8 @@ export type LegacyHeaderVariantValue = keyof typeof legacyHeaderVariants;
  * `@riverbankcms/api` is `z.input<typeof themeSchema>`, so a widened input here
  * would leak straight into a public type.
  *
- * Not every read of a persisted theme goes through the schema:
- * `resolveRuntimeTheme` in
- * `apps/dashboard/src/server/services/sites/runtimeSiteResponse.ts` returns the
- * raw database JSON asserted as `Theme` with no parse, so a theme still
- * carrying a legacy spelling reaches the theme editor un-aliased. That gap
- * predates this alias and is harmless while persisted usage is zero.
+ * Persisted runtime themes are admitted through `parseThemeForPersistence`
+ * before reaching consumers, so legacy spellings normalize at that boundary.
  */
 export declare const headerVariantWithLegacyAliasSchema: z.ZodPipe<z.ZodEnum<{
     classic: "classic";