@wildo-ai/saas-frontend-lib 1.1.1 → 1.1.3

package/dist/esm/components/resources/skeleton/Section.shared.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"Section.shared.d.ts","sourceRoot":"","sources":["../../../../../../src/components/resources/skeleton/Section.shared.ts"],"names":[],"mappings":"AAAA,oBAAY,sBAAsB;IAChC,IAAI,SAAS;IACb,OAAO,YAAY;IACnB,SAAS,cAAc;CACxB"}
+{"version":3,"file":"Section.shared.d.ts","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/Section.shared.ts"],"names":[],"mappings":"AAAA,oBAAY,sBAAsB;IAChC,IAAI,SAAS;IACb,OAAO,YAAY;IACnB,SAAS,cAAc;CACxB"}

package/dist/esm/components/resources/skeleton/Section.shared.js.map

@@ -1 +1 @@
-{"version":3,"file":"Section.shared.js","sourceRoot":"","sources":["../../../../../../src/components/resources/skeleton/Section.shared.ts"],"names":[],"mappings":"AAAA,MAAM,CAAN,IAAY,sBAIX;AAJD,WAAY,sBAAsB;IAChC,uCAAa,CAAA;IACb,6CAAmB,CAAA;IACnB,iDAAuB,CAAA;AACzB,CAAC,EAJW,sBAAsB,KAAtB,sBAAsB,QAIjC","sourcesContent":["export enum GroupedSectionHostKind {\n  FORM = 'form',\n  DISPLAY = 'display',\n  COMPOSITE = 'composite',\n}\n"]}
+{"version":3,"file":"Section.shared.js","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/Section.shared.ts"],"names":[],"mappings":"AAAA,MAAM,CAAN,IAAY,sBAIX;AAJD,WAAY,sBAAsB;IAChC,uCAAa,CAAA;IACb,6CAAmB,CAAA;IACnB,iDAAuB,CAAA;AACzB,CAAC,EAJW,sBAAsB,KAAtB,sBAAsB,QAIjC","sourcesContent":["export enum GroupedSectionHostKind {\n  FORM = 'form',\n  DISPLAY = 'display',\n  COMPOSITE = 'composite',\n}\n"]}

package/dist/esm/components/resources/skeleton/SectionFieldsContext.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"SectionFieldsContext.d.ts","sourceRoot":"","sources":["../../../../../../src/components/resources/skeleton/SectionFieldsContext.tsx"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AACH,MAAM,WAAW,yBAAyB;IACxC,aAAa,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,CAAC;IACtC,eAAe,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,CAAC;IACxC;;;;;OAKG;IACH,mBAAmB,EAAE,MAAM,MAAM,EAAE,CAAC;IACpC;;;;OAIG;IACH,2BAA2B,EAAE,CAAC,QAAQ,EAAE,MAAM,IAAI,KAAK,MAAM,IAAI,CAAC;CACnE;AAED,eAAO,MAAM,oBAAoB,oDAAwD,CAAC;AAE1F;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,wBAAgB,wBAAwB,IAAI,yBAAyB,CA6BpE;AAED;;;;;;;;;GASG;AACH,wBAAgB,2BAA2B,CAAC,SAAS,EAAE,MAAM,GAAG,IAAI,CAQnE;AAKD;;;;;GAKG;AACH,wBAAgB,0BAA0B,IAAI,MAAM,EAAE,CAMrD"}
+{"version":3,"file":"SectionFieldsContext.d.ts","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/SectionFieldsContext.tsx"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AACH,MAAM,WAAW,yBAAyB;IACxC,aAAa,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,CAAC;IACtC,eAAe,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,CAAC;IACxC;;;;;OAKG;IACH,mBAAmB,EAAE,MAAM,MAAM,EAAE,CAAC;IACpC;;;;OAIG;IACH,2BAA2B,EAAE,CAAC,QAAQ,EAAE,MAAM,IAAI,KAAK,MAAM,IAAI,CAAC;CACnE;AAED,eAAO,MAAM,oBAAoB,oDAAwD,CAAC;AAE1F;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,wBAAgB,wBAAwB,IAAI,yBAAyB,CA6BpE;AAED;;;;;;;;;GASG;AACH,wBAAgB,2BAA2B,CAAC,SAAS,EAAE,MAAM,GAAG,IAAI,CAQnE;AAKD;;;;;GAKG;AACH,wBAAgB,0BAA0B,IAAI,MAAM,EAAE,CAMrD"}

package/dist/esm/components/resources/skeleton/SectionFieldsContext.js.map

@@ -1 +1 @@
-{"version":3,"file":"SectionFieldsContext.js","sourceRoot":"","sources":["../../../../../../src/components/resources/skeleton/SectionFieldsContext.tsx"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,UAAU,EAAE,SAAS,EAAE,QAAQ,EAAE,oBAAoB,EAAE,MAAM,OAAO,CAAC;AA+B7F,MAAM,CAAC,MAAM,oBAAoB,GAAG,aAAa,CAAmC,IAAI,CAAC,CAAC;AAE1F;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,UAAU,wBAAwB;IACtC,MAAM,CAAC,QAAQ,CAAC,GAAG,QAAQ,CAAC,GAA8B,EAAE;QAC1D,2FAA2F;QAC3F,IAAI,gBAAgB,GAAa,EAAE,CAAC;QACpC,MAAM,SAAS,GAAG,IAAI,GAAG,EAAc,CAAC;QACxC,MAAM,MAAM,GAAG,GAAS,EAAE;YACxB,KAAK,MAAM,QAAQ,IAAI,SAAS;gBAAE,QAAQ,EAAE,CAAC;QAC/C,CAAC,CAAC;QACF,OAAO;YACL,aAAa,EAAE,CAAC,IAAY,EAAQ,EAAE;gBACpC,IAAI,gBAAgB,CAAC,QAAQ,CAAC,IAAI,CAAC;oBAAE,OAAO;gBAC5C,gBAAgB,GAAG,CAAC,GAAG,gBAAgB,EAAE,IAAI,CAAC,CAAC;gBAC/C,MAAM,EAAE,CAAC;YACX,CAAC;YACD,eAAe,EAAE,CAAC,IAAY,EAAQ,EAAE;gBACtC,IAAI,CAAC,gBAAgB,CAAC,QAAQ,CAAC,IAAI,CAAC;oBAAE,OAAO;gBAC7C,gBAAgB,GAAG,gBAAgB,CAAC,MAAM,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,KAAK,IAAI,CAAC,CAAC;gBAC1E,MAAM,EAAE,CAAC;YACX,CAAC;YACD,mBAAmB,EAAE,GAAa,EAAE,CAAC,gBAAgB;YACrD,2BAA2B,EAAE,CAAC,QAAoB,EAAgB,EAAE;gBAClE,SAAS,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAC;gBACxB,OAAO,GAAG,EAAE;oBACV,SAAS,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAC;gBAC7B,CAAC,CAAC;YACJ,CAAC;SACF,CAAC;IACJ,CAAC,CAAC,CAAC;IACH,OAAO,QAAQ,CAAC;AAClB,CAAC;AAED;;;;;;;;;GASG;AACH,MAAM,UAAU,2BAA2B,CAAC,SAAiB;IAC3D,MAAM,GAAG,GAAG,UAAU,CAAC,oBAAoB,CAAC,CAAC;IAC7C,SAAS,CAAC,GAAG,EAAE;QACb,GAAG,EAAE,aAAa,CAAC,SAAS,CAAC,CAAC;QAC9B,OAAO,GAAG,EAAE;YACV,GAAG,EAAE,eAAe,CAAC,SAAS,CAAC,CAAC;QAClC,CAAC,CAAC;IACJ,CAAC,EAAE,CAAC,GAAG,EAAE,SAAS,CAAC,CAAC,CAAC;AACvB,CAAC;AAED,MAAM,uBAAuB,GAAa,EAAE,CAAC;AAC7C,MAAM,kBAAkB,GAAG,GAAiB,EAAE,CAAC,GAAG,EAAE,GAAE,CAAC,CAAC;AAExD;;;;;GAKG;AACH,MAAM,UAAU,0BAA0B;IACxC,MAAM,GAAG,GAAG,UAAU,CAAC,oBAAoB,CAAC,CAAC;IAC7C,OAAO,oBAAoB,CACzB,GAAG,CAAC,CAAC,CAAC,GAAG,CAAC,2BAA2B,CAAC,CAAC,CAAC,kBAAkB,EAC1D,GAAG,CAAC,CAAC,CAAC,GAAG,CAAC,mBAAmB,CAAC,CAAC,CAAC,GAAa,EAAE,CAAC,uBAAuB,CACxE,CAAC;AACJ,CAAC","sourcesContent":["import { createContext, useContext, useEffect, useState, useSyncExternalStore } from 'react';\n\n/**\n * Registry contract a form-hosted section exposes to its descendants.\n *\n * IDENTITY CONTRACT: providers MUST keep the context value identity-stable for\n * the lifetime of the section (see `useSectionFieldsRegistry`). Every\n * `FormField` registers itself through an effect that depends on this value;\n * a value whose identity tracks the registry contents re-fires every field's\n * registration effect on each mutation (unregister + register → new contents\n * → new value → …), which loops until React throws \"Maximum update depth\n * exceeded\" (recovered 2026-06-10 on the Wonder Todos todoLists create form).\n */\nexport interface SectionFieldsContextValue {\n  registerField: (name: string) => void;\n  unregisterField: (name: string) => void;\n  /**\n   * Current registered field names (insertion-ordered, deduplicated).\n   * Returns the live immutable snapshot — a new array identity is produced\n   * only when the contents actually change, so it is safe to use as a\n   * `useSyncExternalStore` snapshot.\n   */\n  getRegisteredFields: () => string[];\n  /**\n   * Subscribe to registry mutations. Returns the unsubscribe function.\n   * Render-reactive consumers should prefer `useRegisteredSectionFields`\n   * over wiring this manually.\n   */\n  subscribeToRegisteredFields: (listener: () => void) => () => void;\n}\n\nexport const SectionFieldsContext = createContext<SectionFieldsContextValue | null>(null);\n\n/**\n * Builds the identity-stable registry backing `SectionFieldsContext`.\n * Used by both section form hosts (`Section` solo modes and\n * `GroupedSectionBody` for grouped container panels) — keep them on this\n * single implementation so the identity contract cannot drift between hosts.\n *\n * Why the registry lives OUTSIDE React state: registrations arrive from\n * descendant effects. If the registered names were `useState` data baked into\n * the provider value (e.g. a `useMemo` with the names in its deps), every\n * registration would change the value identity, re-fire every field's\n * registration effect (cleanup unregister + register), change the state\n * again, and re-render forever — register/unregister pairs always transition\n * through fresh array identities, so any state-derived value loops by\n * construction. Instead the store is created once per section; mutations swap\n * an immutable snapshot and notify subscribers, so registry churn re-renders\n * only the components that opted in via `useRegisteredSectionFields` — never\n * the provider, never the registrants.\n *\n * Same family as the `WizardStep` field registry (stable mutable container),\n * extended with subscription because section save buttons render from the\n * registry contents (disabled-when-empty) and need to observe changes.\n */\nexport function useSectionFieldsRegistry(): SectionFieldsContextValue {\n  const [registry] = useState((): SectionFieldsContextValue => {\n    /** Immutable snapshot — swapped (never mutated) so subscribers can compare by identity. */\n    let registeredFields: string[] = [];\n    const listeners = new Set<() => void>();\n    const notify = (): void => {\n      for (const listener of listeners) listener();\n    };\n    return {\n      registerField: (name: string): void => {\n        if (registeredFields.includes(name)) return;\n        registeredFields = [...registeredFields, name];\n        notify();\n      },\n      unregisterField: (name: string): void => {\n        if (!registeredFields.includes(name)) return;\n        registeredFields = registeredFields.filter((current) => current !== name);\n        notify();\n      },\n      getRegisteredFields: (): string[] => registeredFields,\n      subscribeToRegisteredFields: (listener: () => void): (() => void) => {\n        listeners.add(listener);\n        return () => {\n          listeners.delete(listener);\n        };\n      },\n    };\n  });\n  return registry;\n}\n\n/**\n * Hook for `FormField` to register with the enclosing saveable section so the\n * section save action can validate and submit only the fields it actually\n * owns. No-op outside a section provider.\n *\n * Depends on the context value identity on purpose (React contract: re-bind\n * if the provider genuinely changes). This is safe only because providers\n * honor the identity contract documented on `SectionFieldsContextValue` —\n * the effect then runs once per field mount.\n */\nexport function useSectionFieldRegistration(fieldName: string): void {\n  const ctx = useContext(SectionFieldsContext);\n  useEffect(() => {\n    ctx?.registerField(fieldName);\n    return () => {\n      ctx?.unregisterField(fieldName);\n    };\n  }, [ctx, fieldName]);\n}\n\nconst EMPTY_REGISTERED_FIELDS: string[] = [];\nconst subscribeToNothing = (): (() => void) => () => {};\n\n/**\n * Render-reactive view of the enclosing section's registered field names.\n * Re-renders the caller when fields register/unregister (e.g. conditionally\n * shown fields), without ever invalidating the provider value. Returns a\n * stable empty array outside any section provider.\n */\nexport function useRegisteredSectionFields(): string[] {\n  const ctx = useContext(SectionFieldsContext);\n  return useSyncExternalStore(\n    ctx ? ctx.subscribeToRegisteredFields : subscribeToNothing,\n    ctx ? ctx.getRegisteredFields : (): string[] => EMPTY_REGISTERED_FIELDS,\n  );\n}\n"]}
+{"version":3,"file":"SectionFieldsContext.js","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/SectionFieldsContext.tsx"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,UAAU,EAAE,SAAS,EAAE,QAAQ,EAAE,oBAAoB,EAAE,MAAM,OAAO,CAAC;AA+B7F,MAAM,CAAC,MAAM,oBAAoB,GAAG,aAAa,CAAmC,IAAI,CAAC,CAAC;AAE1F;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,UAAU,wBAAwB;IACtC,MAAM,CAAC,QAAQ,CAAC,GAAG,QAAQ,CAAC,GAA8B,EAAE;QAC1D,2FAA2F;QAC3F,IAAI,gBAAgB,GAAa,EAAE,CAAC;QACpC,MAAM,SAAS,GAAG,IAAI,GAAG,EAAc,CAAC;QACxC,MAAM,MAAM,GAAG,GAAS,EAAE;YACxB,KAAK,MAAM,QAAQ,IAAI,SAAS;gBAAE,QAAQ,EAAE,CAAC;QAC/C,CAAC,CAAC;QACF,OAAO;YACL,aAAa,EAAE,CAAC,IAAY,EAAQ,EAAE;gBACpC,IAAI,gBAAgB,CAAC,QAAQ,CAAC,IAAI,CAAC;oBAAE,OAAO;gBAC5C,gBAAgB,GAAG,CAAC,GAAG,gBAAgB,EAAE,IAAI,CAAC,CAAC;gBAC/C,MAAM,EAAE,CAAC;YACX,CAAC;YACD,eAAe,EAAE,CAAC,IAAY,EAAQ,EAAE;gBACtC,IAAI,CAAC,gBAAgB,CAAC,QAAQ,CAAC,IAAI,CAAC;oBAAE,OAAO;gBAC7C,gBAAgB,GAAG,gBAAgB,CAAC,MAAM,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,KAAK,IAAI,CAAC,CAAC;gBAC1E,MAAM,EAAE,CAAC;YACX,CAAC;YACD,mBAAmB,EAAE,GAAa,EAAE,CAAC,gBAAgB;YACrD,2BAA2B,EAAE,CAAC,QAAoB,EAAgB,EAAE;gBAClE,SAAS,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAC;gBACxB,OAAO,GAAG,EAAE;oBACV,SAAS,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAC;gBAC7B,CAAC,CAAC;YACJ,CAAC;SACF,CAAC;IACJ,CAAC,CAAC,CAAC;IACH,OAAO,QAAQ,CAAC;AAClB,CAAC;AAED;;;;;;;;;GASG;AACH,MAAM,UAAU,2BAA2B,CAAC,SAAiB;IAC3D,MAAM,GAAG,GAAG,UAAU,CAAC,oBAAoB,CAAC,CAAC;IAC7C,SAAS,CAAC,GAAG,EAAE;QACb,GAAG,EAAE,aAAa,CAAC,SAAS,CAAC,CAAC;QAC9B,OAAO,GAAG,EAAE;YACV,GAAG,EAAE,eAAe,CAAC,SAAS,CAAC,CAAC;QAClC,CAAC,CAAC;IACJ,CAAC,EAAE,CAAC,GAAG,EAAE,SAAS,CAAC,CAAC,CAAC;AACvB,CAAC;AAED,MAAM,uBAAuB,GAAa,EAAE,CAAC;AAC7C,MAAM,kBAAkB,GAAG,GAAiB,EAAE,CAAC,GAAG,EAAE,GAAE,CAAC,CAAC;AAExD;;;;;GAKG;AACH,MAAM,UAAU,0BAA0B;IACxC,MAAM,GAAG,GAAG,UAAU,CAAC,oBAAoB,CAAC,CAAC;IAC7C,OAAO,oBAAoB,CACzB,GAAG,CAAC,CAAC,CAAC,GAAG,CAAC,2BAA2B,CAAC,CAAC,CAAC,kBAAkB,EAC1D,GAAG,CAAC,CAAC,CAAC,GAAG,CAAC,mBAAmB,CAAC,CAAC,CAAC,GAAa,EAAE,CAAC,uBAAuB,CACxE,CAAC;AACJ,CAAC","sourcesContent":["import { createContext, useContext, useEffect, useState, useSyncExternalStore } from 'react';\n\n/**\n * Registry contract a form-hosted section exposes to its descendants.\n *\n * IDENTITY CONTRACT: providers MUST keep the context value identity-stable for\n * the lifetime of the section (see `useSectionFieldsRegistry`). Every\n * `FormField` registers itself through an effect that depends on this value;\n * a value whose identity tracks the registry contents re-fires every field's\n * registration effect on each mutation (unregister + register → new contents\n * → new value → …), which loops until React throws \"Maximum update depth\n * exceeded\" (recovered 2026-06-10 on the Wonder Todos todoLists create form).\n */\nexport interface SectionFieldsContextValue {\n  registerField: (name: string) => void;\n  unregisterField: (name: string) => void;\n  /**\n   * Current registered field names (insertion-ordered, deduplicated).\n   * Returns the live immutable snapshot — a new array identity is produced\n   * only when the contents actually change, so it is safe to use as a\n   * `useSyncExternalStore` snapshot.\n   */\n  getRegisteredFields: () => string[];\n  /**\n   * Subscribe to registry mutations. Returns the unsubscribe function.\n   * Render-reactive consumers should prefer `useRegisteredSectionFields`\n   * over wiring this manually.\n   */\n  subscribeToRegisteredFields: (listener: () => void) => () => void;\n}\n\nexport const SectionFieldsContext = createContext<SectionFieldsContextValue | null>(null);\n\n/**\n * Builds the identity-stable registry backing `SectionFieldsContext`.\n * Used by both section form hosts (`Section` solo modes and\n * `GroupedSectionBody` for grouped container panels) — keep them on this\n * single implementation so the identity contract cannot drift between hosts.\n *\n * Why the registry lives OUTSIDE React state: registrations arrive from\n * descendant effects. If the registered names were `useState` data baked into\n * the provider value (e.g. a `useMemo` with the names in its deps), every\n * registration would change the value identity, re-fire every field's\n * registration effect (cleanup unregister + register), change the state\n * again, and re-render forever — register/unregister pairs always transition\n * through fresh array identities, so any state-derived value loops by\n * construction. Instead the store is created once per section; mutations swap\n * an immutable snapshot and notify subscribers, so registry churn re-renders\n * only the components that opted in via `useRegisteredSectionFields` — never\n * the provider, never the registrants.\n *\n * Same family as the `WizardStep` field registry (stable mutable container),\n * extended with subscription because section save buttons render from the\n * registry contents (disabled-when-empty) and need to observe changes.\n */\nexport function useSectionFieldsRegistry(): SectionFieldsContextValue {\n  const [registry] = useState((): SectionFieldsContextValue => {\n    /** Immutable snapshot — swapped (never mutated) so subscribers can compare by identity. */\n    let registeredFields: string[] = [];\n    const listeners = new Set<() => void>();\n    const notify = (): void => {\n      for (const listener of listeners) listener();\n    };\n    return {\n      registerField: (name: string): void => {\n        if (registeredFields.includes(name)) return;\n        registeredFields = [...registeredFields, name];\n        notify();\n      },\n      unregisterField: (name: string): void => {\n        if (!registeredFields.includes(name)) return;\n        registeredFields = registeredFields.filter((current) => current !== name);\n        notify();\n      },\n      getRegisteredFields: (): string[] => registeredFields,\n      subscribeToRegisteredFields: (listener: () => void): (() => void) => {\n        listeners.add(listener);\n        return () => {\n          listeners.delete(listener);\n        };\n      },\n    };\n  });\n  return registry;\n}\n\n/**\n * Hook for `FormField` to register with the enclosing saveable section so the\n * section save action can validate and submit only the fields it actually\n * owns. No-op outside a section provider.\n *\n * Depends on the context value identity on purpose (React contract: re-bind\n * if the provider genuinely changes). This is safe only because providers\n * honor the identity contract documented on `SectionFieldsContextValue` —\n * the effect then runs once per field mount.\n */\nexport function useSectionFieldRegistration(fieldName: string): void {\n  const ctx = useContext(SectionFieldsContext);\n  useEffect(() => {\n    ctx?.registerField(fieldName);\n    return () => {\n      ctx?.unregisterField(fieldName);\n    };\n  }, [ctx, fieldName]);\n}\n\nconst EMPTY_REGISTERED_FIELDS: string[] = [];\nconst subscribeToNothing = (): (() => void) => () => {};\n\n/**\n * Render-reactive view of the enclosing section's registered field names.\n * Re-renders the caller when fields register/unregister (e.g. conditionally\n * shown fields), without ever invalidating the provider value. Returns a\n * stable empty array outside any section provider.\n */\nexport function useRegisteredSectionFields(): string[] {\n  const ctx = useContext(SectionFieldsContext);\n  return useSyncExternalStore(\n    ctx ? ctx.subscribeToRegisteredFields : subscribeToNothing,\n    ctx ? ctx.getRegisteredFields : (): string[] => EMPTY_REGISTERED_FIELDS,\n  );\n}\n"]}

package/dist/esm/components/resources/skeleton/SectionHostHeadingContext.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"SectionHostHeadingContext.d.ts","sourceRoot":"","sources":["../../../../../../src/components/resources/skeleton/SectionHostHeadingContext.tsx"],"names":[],"mappings":"AAIA;;;;;;;;;;;;;;;;;;;GAmBG;AACH,eAAO,MAAM,yBAAyB,kCAAgC,CAAC;AAEvE;;;;GAIG;AACH,wBAAgB,6BAA6B,IAAI,OAAO,CAEvD"}
+{"version":3,"file":"SectionHostHeadingContext.d.ts","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/SectionHostHeadingContext.tsx"],"names":[],"mappings":"AAIA;;;;;;;;;;;;;;;;;;;GAmBG;AACH,eAAO,MAAM,yBAAyB,kCAAgC,CAAC;AAEvE;;;;GAIG;AACH,wBAAgB,6BAA6B,IAAI,OAAO,CAEvD"}

package/dist/esm/components/resources/skeleton/SectionHostHeadingContext.js.map

@@ -1 +1 @@
-{"version":3,"file":"SectionHostHeadingContext.js","sourceRoot":"","sources":["../../../../../../src/components/resources/skeleton/SectionHostHeadingContext.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAC;AAEb,OAAO,EAAE,aAAa,EAAE,UAAU,EAAE,MAAM,OAAO,CAAC;AAElD;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,CAAC,MAAM,yBAAyB,GAAG,aAAa,CAAU,KAAK,CAAC,CAAC;AAEvE;;;;GAIG;AACH,MAAM,UAAU,6BAA6B;IAC3C,OAAO,UAAU,CAAC,yBAAyB,CAAC,CAAC;AAC/C,CAAC","sourcesContent":["'use client';\n\nimport { createContext, useContext } from 'react';\n\n/**\n * Signals that the nearest enclosing section host already renders a visible\n * heading (a `<Section>` legend / title) for the region a descendant occupies.\n *\n * A resource operation surface embedded inside a titled section (e.g. a LIST\n * embedded in a composite `<Section name=\"todoLists\">`) would otherwise render\n * its OWN generic resource heading directly under the section's heading — two\n * headings naming the same thing (\"To-Do Lists\" then \"Todo Lists\"). The\n * embedded header reads this context (via {@link useSectionHostProvidesHeading})\n * and suppresses its generic title so the host section owns the heading.\n *\n * This is the heading analogue of the surface frame de-duplication: the host\n * owns the chrome, the embedded content does not duplicate it. It is scoped to\n * GENERIC titles only — a record-specific `displayLabel` (a READ view showing\n * an instance's name) is data, not a duplicate heading, and is never\n * suppressed (the consumer gates on the absence of a displayLabel).\n *\n * Default `false`: with no titled section ancestor (a standalone list/read\n * page), the embedded header renders its heading normally.\n */\nexport const SectionHostHeadingContext = createContext<boolean>(false);\n\n/**\n * `true` when an ancestor `<Section>` already renders a heading for this region.\n * Resource headers use it to avoid emitting a duplicate generic heading when\n * embedded inside a titled section host.\n */\nexport function useSectionHostProvidesHeading(): boolean {\n  return useContext(SectionHostHeadingContext);\n}\n"]}
+{"version":3,"file":"SectionHostHeadingContext.js","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/SectionHostHeadingContext.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAC;AAEb,OAAO,EAAE,aAAa,EAAE,UAAU,EAAE,MAAM,OAAO,CAAC;AAElD;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,CAAC,MAAM,yBAAyB,GAAG,aAAa,CAAU,KAAK,CAAC,CAAC;AAEvE;;;;GAIG;AACH,MAAM,UAAU,6BAA6B;IAC3C,OAAO,UAAU,CAAC,yBAAyB,CAAC,CAAC;AAC/C,CAAC","sourcesContent":["'use client';\n\nimport { createContext, useContext } from 'react';\n\n/**\n * Signals that the nearest enclosing section host already renders a visible\n * heading (a `<Section>` legend / title) for the region a descendant occupies.\n *\n * A resource operation surface embedded inside a titled section (e.g. a LIST\n * embedded in a composite `<Section name=\"todoLists\">`) would otherwise render\n * its OWN generic resource heading directly under the section's heading — two\n * headings naming the same thing (\"To-Do Lists\" then \"Todo Lists\"). The\n * embedded header reads this context (via {@link useSectionHostProvidesHeading})\n * and suppresses its generic title so the host section owns the heading.\n *\n * This is the heading analogue of the surface frame de-duplication: the host\n * owns the chrome, the embedded content does not duplicate it. It is scoped to\n * GENERIC titles only — a record-specific `displayLabel` (a READ view showing\n * an instance's name) is data, not a duplicate heading, and is never\n * suppressed (the consumer gates on the absence of a displayLabel).\n *\n * Default `false`: with no titled section ancestor (a standalone list/read\n * page), the embedded header renders its heading normally.\n */\nexport const SectionHostHeadingContext = createContext<boolean>(false);\n\n/**\n * `true` when an ancestor `<Section>` already renders a heading for this region.\n * Resource headers use it to avoid emitting a duplicate generic heading when\n * embedded inside a titled section host.\n */\nexport function useSectionHostProvidesHeading(): boolean {\n  return useContext(SectionHostHeadingContext);\n}\n"]}

package/dist/esm/components/resources/skeleton/SectionPresentationContext.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"SectionPresentationContext.d.ts","sourceRoot":"","sources":["../../../../../../src/components/resources/skeleton/SectionPresentationContext.tsx"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,EAAsC,KAAK,SAAS,EAAE,MAAM,OAAO,CAAC;AAElF,MAAM,WAAW,wBAAwB;IACvC,KAAK,CAAC,EAAE,SAAS,CAAC;IAClB,WAAW,CAAC,EAAE,SAAS,CAAC;IACxB,IAAI,CAAC,EAAE,SAAS,CAAC;CAClB;AAED,MAAM,WAAW,+BAA+B;IAC9C,cAAc,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,wBAAwB,CAAC,CAAC;CAC3D;AAID,wBAAgB,2BAA2B,CAAC,EAC1C,KAAK,EACL,QAAQ,GACT,EAAE;IACD,KAAK,EAAE,+BAA+B,CAAC;IACvC,QAAQ,EAAE,SAAS,CAAC;CACrB,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAQpB;AAED,wBAAgB,qCAAqC,IAAI,+BAA+B,GAAG,IAAI,CAE9F"}
+{"version":3,"file":"SectionPresentationContext.d.ts","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/SectionPresentationContext.tsx"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,EAAsC,KAAK,SAAS,EAAE,MAAM,OAAO,CAAC;AAElF,MAAM,WAAW,wBAAwB;IACvC,KAAK,CAAC,EAAE,SAAS,CAAC;IAClB,WAAW,CAAC,EAAE,SAAS,CAAC;IACxB,IAAI,CAAC,EAAE,SAAS,CAAC;CAClB;AAED,MAAM,WAAW,+BAA+B;IAC9C,cAAc,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,wBAAwB,CAAC,CAAC;CAC3D;AAID,wBAAgB,2BAA2B,CAAC,EAC1C,KAAK,EACL,QAAQ,GACT,EAAE;IACD,KAAK,EAAE,+BAA+B,CAAC;IACvC,QAAQ,EAAE,SAAS,CAAC;CACrB,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAQpB;AAED,wBAAgB,qCAAqC,IAAI,+BAA+B,GAAG,IAAI,CAE9F"}

package/dist/esm/components/resources/skeleton/SectionPresentationContext.js.map

@@ -1 +1 @@
-{"version":3,"file":"SectionPresentationContext.js","sourceRoot":"","sources":["../../../../../../src/components/resources/skeleton/SectionPresentationContext.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAC;;AAEb,OAAc,EAAE,aAAa,EAAE,UAAU,EAAE,OAAO,EAAkB,MAAM,OAAO,CAAC;AAYlF,MAAM,0BAA0B,GAAG,aAAa,CAAyC,IAAI,CAAC,CAAC;AAE/F,MAAM,UAAU,2BAA2B,CAAC,EAC1C,KAAK,EACL,QAAQ,GAIT;IACC,MAAM,YAAY,GAAG,OAAO,CAAC,GAAG,EAAE,CAAC,KAAK,EAAE,CAAC,KAAK,CAAC,CAAC,CAAC;IAEnD,OAAO,CACL,KAAC,0BAA0B,CAAC,QAAQ,IAAC,KAAK,EAAE,YAAY,YACrD,QAAQ,GAC2B,CACvC,CAAC;AACJ,CAAC;AAED,MAAM,UAAU,qCAAqC;IACnD,OAAO,UAAU,CAAC,0BAA0B,CAAC,CAAC;AAChD,CAAC","sourcesContent":["'use client';\n\nimport React, { createContext, useContext, useMemo, type ReactNode } from 'react';\n\nexport interface SectionPresentationEntry {\n  title?: ReactNode;\n  description?: ReactNode;\n  icon?: ReactNode;\n}\n\nexport interface SectionPresentationContextValue {\n  sectionEntries?: Record<string, SectionPresentationEntry>;\n}\n\nconst SectionPresentationContext = createContext<SectionPresentationContextValue | null>(null);\n\nexport function SectionPresentationProvider({\n  value,\n  children,\n}: {\n  value: SectionPresentationContextValue;\n  children: ReactNode;\n}): React.JSX.Element {\n  const contextValue = useMemo(() => value, [value]);\n\n  return (\n    <SectionPresentationContext.Provider value={contextValue}>\n      {children}\n    </SectionPresentationContext.Provider>\n  );\n}\n\nexport function useOptionalSectionPresentationContext(): SectionPresentationContextValue | null {\n  return useContext(SectionPresentationContext);\n}\n"]}
+{"version":3,"file":"SectionPresentationContext.js","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/SectionPresentationContext.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAC;;AAEb,OAAc,EAAE,aAAa,EAAE,UAAU,EAAE,OAAO,EAAkB,MAAM,OAAO,CAAC;AAYlF,MAAM,0BAA0B,GAAG,aAAa,CAAyC,IAAI,CAAC,CAAC;AAE/F,MAAM,UAAU,2BAA2B,CAAC,EAC1C,KAAK,EACL,QAAQ,GAIT;IACC,MAAM,YAAY,GAAG,OAAO,CAAC,GAAG,EAAE,CAAC,KAAK,EAAE,CAAC,KAAK,CAAC,CAAC,CAAC;IAEnD,OAAO,CACL,KAAC,0BAA0B,CAAC,QAAQ,IAAC,KAAK,EAAE,YAAY,YACrD,QAAQ,GAC2B,CACvC,CAAC;AACJ,CAAC;AAED,MAAM,UAAU,qCAAqC;IACnD,OAAO,UAAU,CAAC,0BAA0B,CAAC,CAAC;AAChD,CAAC","sourcesContent":["'use client';\n\nimport React, { createContext, useContext, useMemo, type ReactNode } from 'react';\n\nexport interface SectionPresentationEntry {\n  title?: ReactNode;\n  description?: ReactNode;\n  icon?: ReactNode;\n}\n\nexport interface SectionPresentationContextValue {\n  sectionEntries?: Record<string, SectionPresentationEntry>;\n}\n\nconst SectionPresentationContext = createContext<SectionPresentationContextValue | null>(null);\n\nexport function SectionPresentationProvider({\n  value,\n  children,\n}: {\n  value: SectionPresentationContextValue;\n  children: ReactNode;\n}): React.JSX.Element {\n  const contextValue = useMemo(() => value, [value]);\n\n  return (\n    <SectionPresentationContext.Provider value={contextValue}>\n      {children}\n    </SectionPresentationContext.Provider>\n  );\n}\n\nexport function useOptionalSectionPresentationContext(): SectionPresentationContextValue | null {\n  return useContext(SectionPresentationContext);\n}\n"]}

package/dist/esm/components/resources/skeleton/SubmitButton.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"SubmitButton.d.ts","sourceRoot":"","sources":["../../../../../../src/components/resources/skeleton/SubmitButton.tsx"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AASvC,MAAM,WAAW,iBAAiB;IAChC,wEAAwE;IACxE,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,0FAA0F;IAC1F,eAAe,CAAC,EAAE,MAAM,CAAC;IACzB,uDAAuD;IACvD,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,+DAA+D;IAC/D,SAAS,CAAC,EAAE,OAAO,CAAC;CACrB;AAED;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,wBAAgB,YAAY,CAAC,EAAE,SAAS,EAAE,KAAK,EAAE,eAAe,EAAE,SAAS,EAAE,EAAE,iBAAiB,GAAG,SAAS,CAmC3G;yBAnCe,YAAY"}
+{"version":3,"file":"SubmitButton.d.ts","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/SubmitButton.tsx"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AASvC,MAAM,WAAW,iBAAiB;IAChC,wEAAwE;IACxE,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,0FAA0F;IAC1F,eAAe,CAAC,EAAE,MAAM,CAAC;IACzB,uDAAuD;IACvD,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,+DAA+D;IAC/D,SAAS,CAAC,EAAE,OAAO,CAAC;CACrB;AAED;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,wBAAgB,YAAY,CAAC,EAAE,SAAS,EAAE,KAAK,EAAE,eAAe,EAAE,SAAS,EAAE,EAAE,iBAAiB,GAAG,SAAS,CAmC3G;yBAnCe,YAAY"}

package/dist/esm/components/resources/skeleton/SubmitButton.js.map

@@ -1 +1 @@
-{"version":3,"file":"SubmitButton.js","sourceRoot":"","sources":["../../../../../../src/components/resources/skeleton/SubmitButton.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAC;;AAGb,OAAO,EAAE,cAAc,EAAE,MAAM,iBAAiB,CAAC;AACjD,OAAO,EAAE,qBAAqB,EAAE,MAAM,qCAAqC,CAAC;AAC5E,OAAO,EAAE,MAAM,EAAE,MAAM,+CAA+C,CAAC;AACvE,OAAO,EAAE,YAAY,EAAE,MAAM,uDAAuD,CAAC;AACrF,OAAO,EAAE,OAAO,EAAE,MAAM,uCAAuC,CAAC;AAChE,OAAO,EAAE,8BAA8B,EAAE,MAAM,mEAAmE,CAAC;AACnH,OAAO,EAAE,mBAAmB,EAAE,MAAM,yBAAyB,CAAC;AAa9D;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,UAAU,YAAY,CAAC,EAAE,SAAS,EAAE,KAAK,EAAE,eAAe,EAAE,SAAS,EAAqB;IAC9F,mBAAmB,CAAC,cAAc,CAAC,CAAC;IAEpC,MAAM,EAAE,SAAS,EAAE,GAAG,cAAc,EAAE,CAAC;IACvC,MAAM,WAAW,GAAG,8BAA8B,EAAE,CAAC;IACrD,MAAM,EAAE,UAAU,EAAE,OAAO,EAAE,GAAG,OAAO,CAAC;QACtC,SAAS,EAAE,qBAAqB,CAAC,sBAAsB;KACxD,CAAC,CAAC;IAEH,8EAA8E;IAC9E,6EAA6E;IAC7E,2EAA2E;IAC3E,+EAA+E;IAC/E,oBAAoB;IACpB,MAAM,gBAAgB,GAAG,KAAK,KAAK,SAAS,CAAC;IAC7C,MAAM,YAAY,GAAG,gBAAgB,IAAI,CAAC,OAAO,CAAC;IAElD,MAAM,aAAa,GAAG,KAAK;WACtB,CAAC,OAAO,CAAC,CAAC,CAAC,UAAU,CAAC,qBAAqB,CAAC,sBAAsB,EAAE,YAAY,CAAC,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC;IAEpG,4EAA4E;IAC5E,gCAAgC;IAChC,MAAM,UAAU,GAAG,SAAS,CAAC,YAAY,IAAI,CAAC,CAAC,WAAW,EAAE,QAAQ,IAAI,YAAY,CAAC;IAErF,MAAM,YAAY,GAAG,SAAS,CAAC,YAAY,IAAI,eAAe;QAC5D,CAAC,CAAC,eAAe;QACjB,CAAC,CAAC,aAAa,CAAC;IAElB,OAAO,CACL,cAAK,SAAS,EAAE,SAAS,YACvB,KAAC,MAAM,IAAC,IAAI,EAAC,QAAQ,EAAC,QAAQ,EAAE,UAAU,EAAE,SAAS,EAAE,SAAS,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,CAAC,SAAS,YACrF,KAAC,YAAY,IAAC,OAAO,EAAE,YAAY,EAAE,KAAK,EAAC,KAAK,YAAE,YAAY,GAAgB,GACvE,GACL,CACP,CAAC;AACJ,CAAC;AAED,YAAY,CAAC,WAAW,GAAG,cAAc,CAAC","sourcesContent":["'use client';\n\nimport type { ReactNode } from 'react';\nimport { useFormContext } from 'react-hook-form';\nimport { FrontendComponentType } from '@wildo-ai/presets-components-models';\nimport { Button } from '~wildo-frontend-lib/components/actions/button';\nimport { SkeletonText } from '~wildo-frontend-lib/components/feedback/skeleton-text';\nimport { useI18n } from '~wildo-frontend-lib/core/i18n/useI18n';\nimport { useOptionalFormTemplateContext } from '~wildo-frontend-lib/components/form/automated/FormTemplateContext';\nimport { useSlotRegistration } from './FormLayoutSlotContext';\n\nexport interface SubmitButtonProps {\n  /** Label for the submit button. Falls back to i18n default (\"Save\"). */\n  label?: string;\n  /** Label shown while the form is submitting. Falls back to `label` (no visual change). */\n  submittingLabel?: string;\n  /** Additional CSS classes for the button container. */\n  className?: string;\n  /** When true, the button stretches to full container width. */\n  fullWidth?: boolean;\n}\n\n/**\n * Form submit action slot — placed by the template author where desired.\n *\n * Labels are resolved from explicit props, falling back to i18n (\"Save\").\n * Templates pass labels directly — no context dependency for label text.\n *\n * Disabled when `formState.isSubmitting` or `FormTemplateContext.disabled` is true.\n * (FormTemplateContext is used only for the disabled flag — a skeleton-layer concern.)\n *\n * In wizard mode, the wizard layout manages its own submit/next buttons,\n * so this component is only used in non-wizard templates.\n *\n * @example\n * ```tsx\n * <FormLayout>\n *   <Section name=\"general\">\n *     <FormField name=\"title\" />\n *   </Section>\n *   <SubmitButton label=\"Create\" submittingLabel=\"Creating...\" fullWidth />\n * </FormLayout>\n * ```\n */\nexport function SubmitButton({ className, label, submittingLabel, fullWidth }: SubmitButtonProps): ReactNode {\n  useSlotRegistration('submitButton');\n\n  const { formState } = useFormContext();\n  const templateCtx = useOptionalFormTemplateContext();\n  const { tComponent, isReady } = useI18n({\n    component: FrontendComponentType.LOW_LEVEL_FORM_MESSAGE,\n  });\n\n  // An explicit `label` needs no i18n; only the default (\"Save\") fallback waits\n  // on the form-message bundle. Render the button structure immediately either\n  // way (no `return null`, which would unmount the slot and stall the form's\n  // single-wave reveal) and skeleton ONLY the label text while a needed fallback\n  // is still loading.\n  const usesI18nFallback = label === undefined;\n  const labelLoading = usesI18nFallback && !isReady;\n\n  const resolvedLabel = label\n    ?? (isReady ? tComponent(FrontendComponentType.LOW_LEVEL_FORM_MESSAGE, 'submitSave') : undefined);\n\n  // Disabled while the label is still resolving — can't submit a button whose\n  // action label isn't known yet.\n  const isDisabled = formState.isSubmitting || !!templateCtx?.disabled || labelLoading;\n\n  const displayLabel = formState.isSubmitting && submittingLabel\n    ? submittingLabel\n    : resolvedLabel;\n\n  return (\n    <div className={className}>\n      <Button type=\"submit\" disabled={isDisabled} className={fullWidth ? 'w-full' : undefined}>\n        <SkeletonText loading={labelLoading} width=\"5em\">{displayLabel}</SkeletonText>\n      </Button>\n    </div>\n  );\n}\n\nSubmitButton.displayName = 'SubmitButton';\n"]}
+{"version":3,"file":"SubmitButton.js","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/SubmitButton.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAC;;AAGb,OAAO,EAAE,cAAc,EAAE,MAAM,iBAAiB,CAAC;AACjD,OAAO,EAAE,qBAAqB,EAAE,MAAM,qCAAqC,CAAC;AAC5E,OAAO,EAAE,MAAM,EAAE,MAAM,+CAA+C,CAAC;AACvE,OAAO,EAAE,YAAY,EAAE,MAAM,uDAAuD,CAAC;AACrF,OAAO,EAAE,OAAO,EAAE,MAAM,uCAAuC,CAAC;AAChE,OAAO,EAAE,8BAA8B,EAAE,MAAM,mEAAmE,CAAC;AACnH,OAAO,EAAE,mBAAmB,EAAE,MAAM,yBAAyB,CAAC;AAa9D;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,UAAU,YAAY,CAAC,EAAE,SAAS,EAAE,KAAK,EAAE,eAAe,EAAE,SAAS,EAAqB;IAC9F,mBAAmB,CAAC,cAAc,CAAC,CAAC;IAEpC,MAAM,EAAE,SAAS,EAAE,GAAG,cAAc,EAAE,CAAC;IACvC,MAAM,WAAW,GAAG,8BAA8B,EAAE,CAAC;IACrD,MAAM,EAAE,UAAU,EAAE,OAAO,EAAE,GAAG,OAAO,CAAC;QACtC,SAAS,EAAE,qBAAqB,CAAC,sBAAsB;KACxD,CAAC,CAAC;IAEH,8EAA8E;IAC9E,6EAA6E;IAC7E,2EAA2E;IAC3E,+EAA+E;IAC/E,oBAAoB;IACpB,MAAM,gBAAgB,GAAG,KAAK,KAAK,SAAS,CAAC;IAC7C,MAAM,YAAY,GAAG,gBAAgB,IAAI,CAAC,OAAO,CAAC;IAElD,MAAM,aAAa,GAAG,KAAK;WACtB,CAAC,OAAO,CAAC,CAAC,CAAC,UAAU,CAAC,qBAAqB,CAAC,sBAAsB,EAAE,YAAY,CAAC,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC;IAEpG,4EAA4E;IAC5E,gCAAgC;IAChC,MAAM,UAAU,GAAG,SAAS,CAAC,YAAY,IAAI,CAAC,CAAC,WAAW,EAAE,QAAQ,IAAI,YAAY,CAAC;IAErF,MAAM,YAAY,GAAG,SAAS,CAAC,YAAY,IAAI,eAAe;QAC5D,CAAC,CAAC,eAAe;QACjB,CAAC,CAAC,aAAa,CAAC;IAElB,OAAO,CACL,cAAK,SAAS,EAAE,SAAS,YACvB,KAAC,MAAM,IAAC,IAAI,EAAC,QAAQ,EAAC,QAAQ,EAAE,UAAU,EAAE,SAAS,EAAE,SAAS,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,CAAC,SAAS,YACrF,KAAC,YAAY,IAAC,OAAO,EAAE,YAAY,EAAE,KAAK,EAAC,KAAK,YAAE,YAAY,GAAgB,GACvE,GACL,CACP,CAAC;AACJ,CAAC;AAED,YAAY,CAAC,WAAW,GAAG,cAAc,CAAC","sourcesContent":["'use client';\n\nimport type { ReactNode } from 'react';\nimport { useFormContext } from 'react-hook-form';\nimport { FrontendComponentType } from '@wildo-ai/presets-components-models';\nimport { Button } from '~wildo-frontend-lib/components/actions/button';\nimport { SkeletonText } from '~wildo-frontend-lib/components/feedback/skeleton-text';\nimport { useI18n } from '~wildo-frontend-lib/core/i18n/useI18n';\nimport { useOptionalFormTemplateContext } from '~wildo-frontend-lib/components/form/automated/FormTemplateContext';\nimport { useSlotRegistration } from './FormLayoutSlotContext';\n\nexport interface SubmitButtonProps {\n  /** Label for the submit button. Falls back to i18n default (\"Save\"). */\n  label?: string;\n  /** Label shown while the form is submitting. Falls back to `label` (no visual change). */\n  submittingLabel?: string;\n  /** Additional CSS classes for the button container. */\n  className?: string;\n  /** When true, the button stretches to full container width. */\n  fullWidth?: boolean;\n}\n\n/**\n * Form submit action slot — placed by the template author where desired.\n *\n * Labels are resolved from explicit props, falling back to i18n (\"Save\").\n * Templates pass labels directly — no context dependency for label text.\n *\n * Disabled when `formState.isSubmitting` or `FormTemplateContext.disabled` is true.\n * (FormTemplateContext is used only for the disabled flag — a skeleton-layer concern.)\n *\n * In wizard mode, the wizard layout manages its own submit/next buttons,\n * so this component is only used in non-wizard templates.\n *\n * @example\n * ```tsx\n * <FormLayout>\n *   <Section name=\"general\">\n *     <FormField name=\"title\" />\n *   </Section>\n *   <SubmitButton label=\"Create\" submittingLabel=\"Creating...\" fullWidth />\n * </FormLayout>\n * ```\n */\nexport function SubmitButton({ className, label, submittingLabel, fullWidth }: SubmitButtonProps): ReactNode {\n  useSlotRegistration('submitButton');\n\n  const { formState } = useFormContext();\n  const templateCtx = useOptionalFormTemplateContext();\n  const { tComponent, isReady } = useI18n({\n    component: FrontendComponentType.LOW_LEVEL_FORM_MESSAGE,\n  });\n\n  // An explicit `label` needs no i18n; only the default (\"Save\") fallback waits\n  // on the form-message bundle. Render the button structure immediately either\n  // way (no `return null`, which would unmount the slot and stall the form's\n  // single-wave reveal) and skeleton ONLY the label text while a needed fallback\n  // is still loading.\n  const usesI18nFallback = label === undefined;\n  const labelLoading = usesI18nFallback && !isReady;\n\n  const resolvedLabel = label\n    ?? (isReady ? tComponent(FrontendComponentType.LOW_LEVEL_FORM_MESSAGE, 'submitSave') : undefined);\n\n  // Disabled while the label is still resolving — can't submit a button whose\n  // action label isn't known yet.\n  const isDisabled = formState.isSubmitting || !!templateCtx?.disabled || labelLoading;\n\n  const displayLabel = formState.isSubmitting && submittingLabel\n    ? submittingLabel\n    : resolvedLabel;\n\n  return (\n    <div className={className}>\n      <Button type=\"submit\" disabled={isDisabled} className={fullWidth ? 'w-full' : undefined}>\n        <SkeletonText loading={labelLoading} width=\"5em\">{displayLabel}</SkeletonText>\n      </Button>\n    </div>\n  );\n}\n\nSubmitButton.displayName = 'SubmitButton';\n"]}

package/dist/esm/components/resources/skeleton/SummaryHeader.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"SummaryHeader.d.ts","sourceRoot":"","sources":["../../../../../../src/components/resources/skeleton/SummaryHeader.tsx"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AAEH,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AAGvC,MAAM,WAAW,kBAAkB;IACjC,6DAA6D;IAC7D,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,iFAAiF;IACjF,QAAQ,CAAC,EAAE,SAAS,CAAC;CACtB;AAED,wBAAgB,aAAa,CAAC,EAAE,SAAS,EAAE,QAAQ,EAAE,EAAE,kBAAkB,GAAG,SAAS,CAoBpF"}
+{"version":3,"file":"SummaryHeader.d.ts","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/SummaryHeader.tsx"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AAEH,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AAGvC,MAAM,WAAW,kBAAkB;IACjC,6DAA6D;IAC7D,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,iFAAiF;IACjF,QAAQ,CAAC,EAAE,SAAS,CAAC;CACtB;AAED,wBAAgB,aAAa,CAAC,EAAE,SAAS,EAAE,QAAQ,EAAE,EAAE,kBAAkB,GAAG,SAAS,CAoBpF"}

package/dist/esm/components/resources/skeleton/SummaryHeader.js.map

@@ -1 +1 @@
-{"version":3,"file":"SummaryHeader.js","sourceRoot":"","sources":["../../../../../../src/components/resources/skeleton/SummaryHeader.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAC;;AA6Bb,OAAO,EAAE,EAAE,EAAE,MAAM,gCAAgC,CAAC;AASpD,MAAM,UAAU,aAAa,CAAC,EAAE,SAAS,EAAE,QAAQ,EAAsB;IACvE,OAAO;IACL,+EAA+E;IAC/E,6EAA6E;IAC7E,6EAA6E;IAC7E,iFAAiF;IACjF,6EAA6E;IAC7E,8EAA8E;IAC9E,6EAA6E;IAC7E,qCAAqC;IACrC,cACE,SAAS,EAAE,EAAE,CACX,0CAA0C,EAC1C,iEAAiE,EACjE,SAAS,CACV,YAEA,QAAQ,GACL,CACP,CAAC;AACJ,CAAC","sourcesContent":["'use client';\n\n/**\n * SummaryHeader — a single-line header row for summary templates: the primary\n * title plus one or more inline accessories (a status badge, a marker) on the\n * same line.\n *\n * Replaces the old `layout.summaryTitleAccessory` bolt-on. Where authors used to\n * declare a SECOND template just to place a badge beside the host-owned title,\n * they now compose it directly in the template flow:\n *\n * ```tsx\n * <SummaryLayout titlePlacement={SummaryTitlePlacement.TEMPLATE_OWNED}>\n *   <SummaryHeader>\n *     <SummaryTitle />\n *     <DisplayField name=\"status\" hideLabel />\n *   </SummaryHeader>\n *   <DisplayField name=\"createdAt\" />\n * </SummaryLayout>\n * ```\n *\n * The title (first child, typically `<SummaryTitle />`) truncates and shrinks;\n * trailing accessories keep their intrinsic size (`shrink-0`). This is the same\n * geometry the list-card host used to hand-roll for the accessory slot, now owned\n * once here so every summary surface (list card AND FK popover) renders it\n * identically.\n */\n\nimport type { ReactNode } from 'react';\nimport { cn } from '~wildo-frontend-lib/core/ui/cn';\n\nexport interface SummaryHeaderProps {\n  /** Extra classes merged over the default flex-row layout. */\n  className?: string;\n  /** Title element (usually `<SummaryTitle />`) followed by inline accessories. */\n  children?: ReactNode;\n}\n\nexport function SummaryHeader({ className, children }: SummaryHeaderProps): ReactNode {\n  return (\n    // The title (`<SummaryTitle />`) grows + truncates via `flex-1 min-w-0` on the\n    // title element ITSELF (not a `:first-child` selector here — that would hand\n    // the grow to a trailing accessory when the title renders null). Accessories\n    // keep intrinsic size: `shrink-0` stops them shrinking, and `w-auto` NEUTRALISES\n    // the `w-full` field-chrome root a `<DisplayField>` accessory renders with —\n    // without it, a `w-full` badge claims the whole row and squashes the title to\n    // zero width (title text present but invisible). Higher specificity than the\n    // field's own `.w-full`, so it wins.\n    <div\n      className={cn(\n        'flex min-w-0 items-center gap-element-sm',\n        '[&>*:not(:first-child)]:shrink-0 [&>*:not(:first-child)]:w-auto',\n        className,\n      )}\n    >\n      {children}\n    </div>\n  );\n}\n"]}
+{"version":3,"file":"SummaryHeader.js","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/SummaryHeader.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAC;;AA6Bb,OAAO,EAAE,EAAE,EAAE,MAAM,gCAAgC,CAAC;AASpD,MAAM,UAAU,aAAa,CAAC,EAAE,SAAS,EAAE,QAAQ,EAAsB;IACvE,OAAO;IACL,+EAA+E;IAC/E,6EAA6E;IAC7E,6EAA6E;IAC7E,iFAAiF;IACjF,6EAA6E;IAC7E,8EAA8E;IAC9E,6EAA6E;IAC7E,qCAAqC;IACrC,cACE,SAAS,EAAE,EAAE,CACX,0CAA0C,EAC1C,iEAAiE,EACjE,SAAS,CACV,YAEA,QAAQ,GACL,CACP,CAAC;AACJ,CAAC","sourcesContent":["'use client';\n\n/**\n * SummaryHeader — a single-line header row for summary templates: the primary\n * title plus one or more inline accessories (a status badge, a marker) on the\n * same line.\n *\n * Replaces the old `layout.summaryTitleAccessory` bolt-on. Where authors used to\n * declare a SECOND template just to place a badge beside the host-owned title,\n * they now compose it directly in the template flow:\n *\n * ```tsx\n * <SummaryLayout titlePlacement={SummaryTitlePlacement.TEMPLATE_OWNED}>\n *   <SummaryHeader>\n *     <SummaryTitle />\n *     <DisplayField name=\"status\" hideLabel />\n *   </SummaryHeader>\n *   <DisplayField name=\"createdAt\" />\n * </SummaryLayout>\n * ```\n *\n * The title (first child, typically `<SummaryTitle />`) truncates and shrinks;\n * trailing accessories keep their intrinsic size (`shrink-0`). This is the same\n * geometry the list-card host used to hand-roll for the accessory slot, now owned\n * once here so every summary surface (list card AND FK popover) renders it\n * identically.\n */\n\nimport type { ReactNode } from 'react';\nimport { cn } from '~wildo-frontend-lib/core/ui/cn';\n\nexport interface SummaryHeaderProps {\n  /** Extra classes merged over the default flex-row layout. */\n  className?: string;\n  /** Title element (usually `<SummaryTitle />`) followed by inline accessories. */\n  children?: ReactNode;\n}\n\nexport function SummaryHeader({ className, children }: SummaryHeaderProps): ReactNode {\n  return (\n    // The title (`<SummaryTitle />`) grows + truncates via `flex-1 min-w-0` on the\n    // title element ITSELF (not a `:first-child` selector here — that would hand\n    // the grow to a trailing accessory when the title renders null). Accessories\n    // keep intrinsic size: `shrink-0` stops them shrinking, and `w-auto` NEUTRALISES\n    // the `w-full` field-chrome root a `<DisplayField>` accessory renders with —\n    // without it, a `w-full` badge claims the whole row and squashes the title to\n    // zero width (title text present but invisible). Higher specificity than the\n    // field's own `.w-full`, so it wins.\n    <div\n      className={cn(\n        'flex min-w-0 items-center gap-element-sm',\n        '[&>*:not(:first-child)]:shrink-0 [&>*:not(:first-child)]:w-auto',\n        className,\n      )}\n    >\n      {children}\n    </div>\n  );\n}\n"]}

package/dist/esm/components/resources/skeleton/SummaryLayout.d.ts

@@ -19,7 +19,21 @@ export declare enum SummaryTitlePlacement {
      */
     TEMPLATE_OWNED = "template-owned"
 }
+/**
+ * How a summary's own children are arranged.
+ *
+ * A behavior, not a style: the caller says which of the two summaries this is, and the classes each
+ * resolves to stay here where a theme can reach them.
+ */
+export declare enum SummaryFlow {
+    /** Title above a short body — the ordinary card, list-row and popover summary. */
+    STACK = "stack",
+    /** One wrapping line of values — for a summary that IS its meta row, with no title above it. */
+    ROW = "row"
+}
 export interface SummaryLayoutProps {
+    /** How the children are arranged. Defaults to {@link SummaryFlow.STACK}. */
+    flow?: SummaryFlow;
     /** Additional CSS classes for the root container. */
     className?: string;
     /**
@@ -44,6 +58,26 @@ export interface SummaryLayoutProps {
  * FK-field references) `<SummaryTitle />` renders nothing, so `AUTO` shows no
  * empty title slot.
  *
+ * ## It owns its own root chrome, and the FLOW is declared rather than drawn
+ *
+ * The geometry used to be passed in by every caller, and enumerating those callers is what settled
+ * the shape of this prop. Across the engine's own resource presets there are exactly two summaries:
+ *
+ * - **39 stacked** — `className="flex flex-col gap-2 text-sm"` (22) or a bare `text-sm` (4), plus
+ *   the workbench's own; a title with a short body beneath it.
+ * - **13 in a single wrapping row** — `className="flex flex-wrap items-center gap-x-3 gap-y-1
+ *   text-sm"`; a summary that IS its meta line, with no title above it.
+ *
+ * So the honest default is not one geometry but a CHOICE of two, and shipping only the stack would
+ * have been actively wrong: `flex-wrap` and `flex-col` are different conflict groups, so a caller
+ * passing the row geometry over a `flex-col` default gets a wrapping COLUMN — thirteen surfaces
+ * silently rearranged. Naming the two lets a caller say which one it is and lets the theme own what
+ * each looks like.
+ *
+ * `SummaryFlow.ROW` is deliberately the same geometry as {@link SummaryMeta}: a summary that is only
+ * a meta line and a meta line inside a stacked summary are the same thing at different levels, and
+ * they should not be able to drift apart.
+ *
  * Provides a root `FieldScopeContext` with empty prefix.
  *
  * @example
@@ -63,5 +97,5 @@ export interface SummaryLayoutProps {
  * </SummaryLayout>
  * ```
  */
-export declare function SummaryLayout({ className, titlePlacement, children, }: SummaryLayoutProps): ReactNode;
+export declare function SummaryLayout({ flow, className, titlePlacement, children, }: SummaryLayoutProps): ReactNode;
 //# sourceMappingURL=SummaryLayout.d.ts.map

package/dist/esm/components/resources/skeleton/SummaryLayout.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"SummaryLayout.d.ts","sourceRoot":"","sources":["../../../../../../src/components/resources/skeleton/SummaryLayout.tsx"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AAIvC;;;;GAIG;AACH,oBAAY,qBAAqB;IAC/B;;;;OAIG;IACH,IAAI,SAAS;IACb;;;;;OAKG;IACH,cAAc,mBAAmB;CAClC;AAED,MAAM,WAAW,kBAAkB;IACjC,qDAAqD;IACrD,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB;;;;OAIG;IACH,cAAc,CAAC,EAAE,qBAAqB,CAAC;IACvC,QAAQ,CAAC,EAAE,SAAS,CAAC;CACtB;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgCG;AACH,wBAAgB,aAAa,CAAC,EAC5B,SAAS,EACT,cAA2C,EAC3C,QAAQ,GACT,EAAE,kBAAkB,GAAG,SAAS,CAShC"}
+{"version":3,"file":"SummaryLayout.d.ts","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/SummaryLayout.tsx"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AAKvC;;;;GAIG;AACH,oBAAY,qBAAqB;IAC/B;;;;OAIG;IACH,IAAI,SAAS;IACb;;;;;OAKG;IACH,cAAc,mBAAmB;CAClC;AAED;;;;;GAKG;AACH,oBAAY,WAAW;IACrB,kFAAkF;IAClF,KAAK,UAAU;IACf,gGAAgG;IAChG,GAAG,QAAQ;CACZ;AAQD,MAAM,WAAW,kBAAkB;IACjC,4EAA4E;IAC5E,IAAI,CAAC,EAAE,WAAW,CAAC;IACnB,qDAAqD;IACrD,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB;;;;OAIG;IACH,cAAc,CAAC,EAAE,qBAAqB,CAAC;IACvC,QAAQ,CAAC,EAAE,SAAS,CAAC;CACtB;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoDG;AACH,wBAAgB,aAAa,CAAC,EAC5B,IAAwB,EACxB,SAAS,EACT,cAA2C,EAC3C,QAAQ,GACT,EAAE,kBAAkB,GAAG,SAAS,CAShC"}

package/dist/esm/components/resources/skeleton/SummaryLayout.js

@@ -1,5 +1,6 @@
 'use client';
 import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
+import { cn } from '../../../core/ui/cn.js';
 import { FieldScopeProvider } from './FieldScopeContext.js';
 import { SummaryTitle } from './SummaryTitle.js';
 /**
@@ -23,6 +24,24 @@ export var SummaryTitlePlacement;
      */
     SummaryTitlePlacement["TEMPLATE_OWNED"] = "template-owned";
 })(SummaryTitlePlacement || (SummaryTitlePlacement = {}));
+/**
+ * How a summary's own children are arranged.
+ *
+ * A behavior, not a style: the caller says which of the two summaries this is, and the classes each
+ * resolves to stay here where a theme can reach them.
+ */
+export var SummaryFlow;
+(function (SummaryFlow) {
+    /** Title above a short body — the ordinary card, list-row and popover summary. */
+    SummaryFlow["STACK"] = "stack";
+    /** One wrapping line of values — for a summary that IS its meta row, with no title above it. */
+    SummaryFlow["ROW"] = "row";
+})(SummaryFlow || (SummaryFlow = {}));
+/** The geometry each flow resolves to. Tokens, not raw steps: `gap-element` IS `gap-2`. */
+const SUMMARY_FLOW_CLASSES = {
+    [SummaryFlow.STACK]: 'flex flex-col gap-element text-sm',
+    [SummaryFlow.ROW]: 'flex flex-wrap items-center gap-x-group gap-y-item text-sm',
+};
 /**
  * Root wrapper for summary layout templates (cards, list items, FK references).
  *
@@ -37,6 +56,26 @@ export var SummaryTitlePlacement;
  * FK-field references) `<SummaryTitle />` renders nothing, so `AUTO` shows no
  * empty title slot.
  *
+ * ## It owns its own root chrome, and the FLOW is declared rather than drawn
+ *
+ * The geometry used to be passed in by every caller, and enumerating those callers is what settled
+ * the shape of this prop. Across the engine's own resource presets there are exactly two summaries:
+ *
+ * - **39 stacked** — `className="flex flex-col gap-2 text-sm"` (22) or a bare `text-sm` (4), plus
+ *   the workbench's own; a title with a short body beneath it.
+ * - **13 in a single wrapping row** — `className="flex flex-wrap items-center gap-x-3 gap-y-1
+ *   text-sm"`; a summary that IS its meta line, with no title above it.
+ *
+ * So the honest default is not one geometry but a CHOICE of two, and shipping only the stack would
+ * have been actively wrong: `flex-wrap` and `flex-col` are different conflict groups, so a caller
+ * passing the row geometry over a `flex-col` default gets a wrapping COLUMN — thirteen surfaces
+ * silently rearranged. Naming the two lets a caller say which one it is and lets the theme own what
+ * each looks like.
+ *
+ * `SummaryFlow.ROW` is deliberately the same geometry as {@link SummaryMeta}: a summary that is only
+ * a meta line and a meta line inside a stacked summary are the same thing at different levels, and
+ * they should not be able to drift apart.
+ *
  * Provides a root `FieldScopeContext` with empty prefix.
  *
  * @example
@@ -56,7 +95,7 @@ export var SummaryTitlePlacement;
  * </SummaryLayout>
  * ```
  */
-export function SummaryLayout({ className, titlePlacement = SummaryTitlePlacement.AUTO, children, }) {
-    return (_jsx(FieldScopeProvider, { pathPrefix: "", children: _jsxs("div", { className: className, children: [titlePlacement === SummaryTitlePlacement.AUTO && _jsx(SummaryTitle, {}), children] }) }));
+export function SummaryLayout({ flow = SummaryFlow.STACK, className, titlePlacement = SummaryTitlePlacement.AUTO, children, }) {
+    return (_jsx(FieldScopeProvider, { pathPrefix: "", children: _jsxs("div", { className: cn(SUMMARY_FLOW_CLASSES[flow], className), children: [titlePlacement === SummaryTitlePlacement.AUTO && _jsx(SummaryTitle, {}), children] }) }));
 }
 //# sourceMappingURL=SummaryLayout.js.map

package/dist/esm/components/resources/skeleton/SummaryLayout.js.map

@@ -1 +1 @@
-{"version":3,"file":"SummaryLayout.js","sourceRoot":"","sources":["../../../../../../src/components/resources/skeleton/SummaryLayout.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAC;;AAGb,OAAO,EAAE,kBAAkB,EAAE,MAAM,qBAAqB,CAAC;AACzD,OAAO,EAAE,YAAY,EAAE,MAAM,gBAAgB,CAAC;AAE9C;;;;GAIG;AACH,MAAM,CAAN,IAAY,qBAcX;AAdD,WAAY,qBAAqB;IAC/B;;;;OAIG;IACH,sCAAa,CAAA;IACb;;;;;OAKG;IACH,0DAAiC,CAAA;AACnC,CAAC,EAdW,qBAAqB,KAArB,qBAAqB,QAchC;AAcD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgCG;AACH,MAAM,UAAU,aAAa,CAAC,EAC5B,SAAS,EACT,cAAc,GAAG,qBAAqB,CAAC,IAAI,EAC3C,QAAQ,GACW;IACnB,OAAO,CACL,KAAC,kBAAkB,IAAC,UAAU,EAAC,EAAE,YAC/B,eAAK,SAAS,EAAE,SAAS,aACtB,cAAc,KAAK,qBAAqB,CAAC,IAAI,IAAI,KAAC,YAAY,KAAG,EACjE,QAAQ,IACL,GACa,CACtB,CAAC;AACJ,CAAC","sourcesContent":["'use client';\n\nimport type { ReactNode } from 'react';\nimport { FieldScopeProvider } from './FieldScopeContext';\nimport { SummaryTitle } from './SummaryTitle';\n\n/**\n * Where the primary title (`<SummaryTitle />`) is placed within a summary\n * template. The placement decision lives HERE, in the template markup that\n * governs it — not in a parallel `layout.*` config field.\n */\nexport enum SummaryTitlePlacement {\n  /**\n   * Framework places the title automatically at the top of the template, above\n   * the authored children. The zero-boilerplate, title-above-body default —\n   * matches the classic list/card summary look.\n   */\n  AUTO = 'auto',\n  /**\n   * The author owns title placement: `SummaryLayout` renders only its children,\n   * and the author drops `<SummaryTitle />` wherever it belongs (e.g. inside a\n   * `<SummaryHeader>` beside a status badge). Required whenever the title must\n   * share a line with other content.\n   */\n  TEMPLATE_OWNED = 'template-owned',\n}\n\nexport interface SummaryLayoutProps {\n  /** Additional CSS classes for the root container. */\n  className?: string;\n  /**\n   * Title placement. Defaults to {@link SummaryTitlePlacement.AUTO} (title\n   * rendered at the top). Switch to `TEMPLATE_OWNED` to place `<SummaryTitle />`\n   * yourself within the flow.\n   */\n  titlePlacement?: SummaryTitlePlacement;\n  children?: ReactNode;\n}\n\n/**\n * Root wrapper for summary layout templates (cards, list items, FK references).\n *\n * Owns TITLE PLACEMENT for the template: under `AUTO` (default) it renders\n * `<SummaryTitle />` at the top, then the children body — so an author who just\n * wants \"title above a couple of fields\" writes nothing about the title. Under\n * `TEMPLATE_OWNED` it renders only the children, and the author composes\n * `<SummaryTitle />` into the flow (see {@link SummaryHeader}).\n *\n * The title resolves its text from `SummaryContext` (provided by\n * `ResourceSummaryDisplayer`); on body-only surfaces with no title (inline\n * FK-field references) `<SummaryTitle />` renders nothing, so `AUTO` shows no\n * empty title slot.\n *\n * Provides a root `FieldScopeContext` with empty prefix.\n *\n * @example\n * ```tsx\n * // AUTO — title rendered above the body automatically:\n * <SummaryLayout>\n *   <DisplayField name=\"createdAt\" />\n * </SummaryLayout>\n *\n * // TEMPLATE_OWNED — badge on the same line as the title:\n * <SummaryLayout titlePlacement={SummaryTitlePlacement.TEMPLATE_OWNED}>\n *   <SummaryHeader>\n *     <SummaryTitle />\n *     <DisplayField name=\"status\" hideLabel />\n *   </SummaryHeader>\n *   <DisplayField name=\"createdAt\" />\n * </SummaryLayout>\n * ```\n */\nexport function SummaryLayout({\n  className,\n  titlePlacement = SummaryTitlePlacement.AUTO,\n  children,\n}: SummaryLayoutProps): ReactNode {\n  return (\n    <FieldScopeProvider pathPrefix=\"\">\n      <div className={className}>\n        {titlePlacement === SummaryTitlePlacement.AUTO && <SummaryTitle />}\n        {children}\n      </div>\n    </FieldScopeProvider>\n  );\n}\n"]}
+{"version":3,"file":"SummaryLayout.js","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/SummaryLayout.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAC;;AAGb,OAAO,EAAE,EAAE,EAAE,MAAM,gCAAgC,CAAC;AACpD,OAAO,EAAE,kBAAkB,EAAE,MAAM,qBAAqB,CAAC;AACzD,OAAO,EAAE,YAAY,EAAE,MAAM,gBAAgB,CAAC;AAE9C;;;;GAIG;AACH,MAAM,CAAN,IAAY,qBAcX;AAdD,WAAY,qBAAqB;IAC/B;;;;OAIG;IACH,sCAAa,CAAA;IACb;;;;;OAKG;IACH,0DAAiC,CAAA;AACnC,CAAC,EAdW,qBAAqB,KAArB,qBAAqB,QAchC;AAED;;;;;GAKG;AACH,MAAM,CAAN,IAAY,WAKX;AALD,WAAY,WAAW;IACrB,kFAAkF;IAClF,8BAAe,CAAA;IACf,gGAAgG;IAChG,0BAAW,CAAA;AACb,CAAC,EALW,WAAW,KAAX,WAAW,QAKtB;AAED,2FAA2F;AAC3F,MAAM,oBAAoB,GAAgC;IACxD,CAAC,WAAW,CAAC,KAAK,CAAC,EAAE,mCAAmC;IACxD,CAAC,WAAW,CAAC,GAAG,CAAC,EAAE,4DAA4D;CAChF,CAAC;AAgBF;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoDG;AACH,MAAM,UAAU,aAAa,CAAC,EAC5B,IAAI,GAAG,WAAW,CAAC,KAAK,EACxB,SAAS,EACT,cAAc,GAAG,qBAAqB,CAAC,IAAI,EAC3C,QAAQ,GACW;IACnB,OAAO,CACL,KAAC,kBAAkB,IAAC,UAAU,EAAC,EAAE,YAC/B,eAAK,SAAS,EAAE,EAAE,CAAC,oBAAoB,CAAC,IAAI,CAAC,EAAE,SAAS,CAAC,aACtD,cAAc,KAAK,qBAAqB,CAAC,IAAI,IAAI,KAAC,YAAY,KAAG,EACjE,QAAQ,IACL,GACa,CACtB,CAAC;AACJ,CAAC","sourcesContent":["'use client';\n\nimport type { ReactNode } from 'react';\nimport { cn } from '~wildo-frontend-lib/core/ui/cn';\nimport { FieldScopeProvider } from './FieldScopeContext';\nimport { SummaryTitle } from './SummaryTitle';\n\n/**\n * Where the primary title (`<SummaryTitle />`) is placed within a summary\n * template. The placement decision lives HERE, in the template markup that\n * governs it — not in a parallel `layout.*` config field.\n */\nexport enum SummaryTitlePlacement {\n  /**\n   * Framework places the title automatically at the top of the template, above\n   * the authored children. The zero-boilerplate, title-above-body default —\n   * matches the classic list/card summary look.\n   */\n  AUTO = 'auto',\n  /**\n   * The author owns title placement: `SummaryLayout` renders only its children,\n   * and the author drops `<SummaryTitle />` wherever it belongs (e.g. inside a\n   * `<SummaryHeader>` beside a status badge). Required whenever the title must\n   * share a line with other content.\n   */\n  TEMPLATE_OWNED = 'template-owned',\n}\n\n/**\n * How a summary's own children are arranged.\n *\n * A behavior, not a style: the caller says which of the two summaries this is, and the classes each\n * resolves to stay here where a theme can reach them.\n */\nexport enum SummaryFlow {\n  /** Title above a short body — the ordinary card, list-row and popover summary. */\n  STACK = 'stack',\n  /** One wrapping line of values — for a summary that IS its meta row, with no title above it. */\n  ROW = 'row',\n}\n\n/** The geometry each flow resolves to. Tokens, not raw steps: `gap-element` IS `gap-2`. */\nconst SUMMARY_FLOW_CLASSES: Record<SummaryFlow, string> = {\n  [SummaryFlow.STACK]: 'flex flex-col gap-element text-sm',\n  [SummaryFlow.ROW]: 'flex flex-wrap items-center gap-x-group gap-y-item text-sm',\n};\n\nexport interface SummaryLayoutProps {\n  /** How the children are arranged. Defaults to {@link SummaryFlow.STACK}. */\n  flow?: SummaryFlow;\n  /** Additional CSS classes for the root container. */\n  className?: string;\n  /**\n   * Title placement. Defaults to {@link SummaryTitlePlacement.AUTO} (title\n   * rendered at the top). Switch to `TEMPLATE_OWNED` to place `<SummaryTitle />`\n   * yourself within the flow.\n   */\n  titlePlacement?: SummaryTitlePlacement;\n  children?: ReactNode;\n}\n\n/**\n * Root wrapper for summary layout templates (cards, list items, FK references).\n *\n * Owns TITLE PLACEMENT for the template: under `AUTO` (default) it renders\n * `<SummaryTitle />` at the top, then the children body — so an author who just\n * wants \"title above a couple of fields\" writes nothing about the title. Under\n * `TEMPLATE_OWNED` it renders only the children, and the author composes\n * `<SummaryTitle />` into the flow (see {@link SummaryHeader}).\n *\n * The title resolves its text from `SummaryContext` (provided by\n * `ResourceSummaryDisplayer`); on body-only surfaces with no title (inline\n * FK-field references) `<SummaryTitle />` renders nothing, so `AUTO` shows no\n * empty title slot.\n *\n * ## It owns its own root chrome, and the FLOW is declared rather than drawn\n *\n * The geometry used to be passed in by every caller, and enumerating those callers is what settled\n * the shape of this prop. Across the engine's own resource presets there are exactly two summaries:\n *\n * - **39 stacked** — `className=\"flex flex-col gap-2 text-sm\"` (22) or a bare `text-sm` (4), plus\n *   the workbench's own; a title with a short body beneath it.\n * - **13 in a single wrapping row** — `className=\"flex flex-wrap items-center gap-x-3 gap-y-1\n *   text-sm\"`; a summary that IS its meta line, with no title above it.\n *\n * So the honest default is not one geometry but a CHOICE of two, and shipping only the stack would\n * have been actively wrong: `flex-wrap` and `flex-col` are different conflict groups, so a caller\n * passing the row geometry over a `flex-col` default gets a wrapping COLUMN — thirteen surfaces\n * silently rearranged. Naming the two lets a caller say which one it is and lets the theme own what\n * each looks like.\n *\n * `SummaryFlow.ROW` is deliberately the same geometry as {@link SummaryMeta}: a summary that is only\n * a meta line and a meta line inside a stacked summary are the same thing at different levels, and\n * they should not be able to drift apart.\n *\n * Provides a root `FieldScopeContext` with empty prefix.\n *\n * @example\n * ```tsx\n * // AUTO — title rendered above the body automatically:\n * <SummaryLayout>\n *   <DisplayField name=\"createdAt\" />\n * </SummaryLayout>\n *\n * // TEMPLATE_OWNED — badge on the same line as the title:\n * <SummaryLayout titlePlacement={SummaryTitlePlacement.TEMPLATE_OWNED}>\n *   <SummaryHeader>\n *     <SummaryTitle />\n *     <DisplayField name=\"status\" hideLabel />\n *   </SummaryHeader>\n *   <DisplayField name=\"createdAt\" />\n * </SummaryLayout>\n * ```\n */\nexport function SummaryLayout({\n  flow = SummaryFlow.STACK,\n  className,\n  titlePlacement = SummaryTitlePlacement.AUTO,\n  children,\n}: SummaryLayoutProps): ReactNode {\n  return (\n    <FieldScopeProvider pathPrefix=\"\">\n      <div className={cn(SUMMARY_FLOW_CLASSES[flow], className)}>\n        {titlePlacement === SummaryTitlePlacement.AUTO && <SummaryTitle />}\n        {children}\n      </div>\n    </FieldScopeProvider>\n  );\n}\n"]}

package/dist/esm/components/resources/skeleton/SummaryMeta.d.ts

@@ -0,0 +1,52 @@
+/**
+ * SummaryMeta — the row of QUALIFYING fields beneath a summary's headline.
+ *
+ * A summary answers two questions in order: *which one is this* (the headline) and *what do I need
+ * to know about it at a glance* (this). The second is a wrapping row of short values — a status
+ * badge, a date, an owner, a count — that reads as one line on a wide card and folds on a narrow
+ * one.
+ *
+ * ## Why this exists as a component
+ *
+ * It was written out by hand **34 times** across the engine's own resource presets and the
+ * workbench, always as the identical literal:
+ *
+ *     <div className="flex flex-wrap items-center gap-x-3 gap-y-1">
+ *
+ * Three things follow from a concept having no name. No theme can change it, because it is a string
+ * in a configuration file rather than a recipe. It uses raw Tailwind spacing while the design system
+ * defines the `element / item / group / field` token ladder every other surface spends. And the
+ * thirty-fifth author copies whichever of the thirty-four they happened to read, so the row drifts
+ * a gap at a time with nothing able to notice.
+ *
+ * The geometry here is that literal expressed in TOKENS — `gap-x-group` is the same 0.75rem as
+ * `gap-x-3`, `gap-y-item` the same 0.25rem as `gap-y-1` — so adopting it is pixel-neutral, and
+ * moving the ladder afterwards moves every meta row at once.
+ *
+ * ## The `w-auto` on children is not cosmetic
+ *
+ * A `<DisplayField>` renders a field chrome whose root is `w-full`. In a wrapping flex row that
+ * makes every value claim its own line, so the row silently renders as a stack — the same defect
+ * `SummaryHeader` neutralises for its accessories, and the same one `objectUI displayMode:
+ * HORIZONTAL` had until it was fixed. Neutralising it here is what makes the row a row.
+ *
+ * @example
+ * ```tsx
+ * <SummaryLayout>
+ *   <SummaryTitle name="email" />
+ *   <SummaryMeta>
+ *     <DisplayField name="status" />
+ *     <DisplayField name="createdAt" />
+ *   </SummaryMeta>
+ * </SummaryLayout>
+ * ```
+ */
+import type { ReactNode } from 'react';
+export interface SummaryMetaProps {
+    /** Extra classes merged over the default wrapping-row geometry. */
+    className?: string;
+    /** The qualifying fields — typically `<DisplayField>`s. */
+    children?: ReactNode;
+}
+export declare function SummaryMeta({ className, children }: SummaryMetaProps): ReactNode;
+//# sourceMappingURL=SummaryMeta.d.ts.map

package/dist/esm/components/resources/skeleton/SummaryMeta.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"SummaryMeta.d.ts","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/SummaryMeta.tsx"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA0CG;AAEH,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AAGvC,MAAM,WAAW,gBAAgB;IAC/B,mEAAmE;IACnE,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,2DAA2D;IAC3D,QAAQ,CAAC,EAAE,SAAS,CAAC;CACtB;AAED,wBAAgB,WAAW,CAAC,EAAE,SAAS,EAAE,QAAQ,EAAE,EAAE,gBAAgB,GAAG,SAAS,CAahF"}

package/dist/esm/components/resources/skeleton/SummaryMeta.js

@@ -0,0 +1,9 @@
+'use client';
+import { jsx as _jsx } from "react/jsx-runtime";
+import { cn } from '../../../core/ui/cn.js';
+export function SummaryMeta({ className, children }) {
+    return (_jsx("div", { className: cn('flex min-w-0 flex-wrap items-center gap-x-group gap-y-item', 
+        // See the docstring: a `w-full` field chrome turns a wrapping row into a stack.
+        '[&>*]:w-auto', className), children: children }));
+}
+//# sourceMappingURL=SummaryMeta.js.map

package/dist/esm/components/resources/skeleton/SummaryMeta.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"SummaryMeta.js","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/SummaryMeta.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAC;;AA+Cb,OAAO,EAAE,EAAE,EAAE,MAAM,gCAAgC,CAAC;AASpD,MAAM,UAAU,WAAW,CAAC,EAAE,SAAS,EAAE,QAAQ,EAAoB;IACnE,OAAO,CACL,cACE,SAAS,EAAE,EAAE,CACX,4DAA4D;QAC5D,gFAAgF;QAChF,cAAc,EACd,SAAS,CACV,YAEA,QAAQ,GACL,CACP,CAAC;AACJ,CAAC","sourcesContent":["'use client';\n\n/**\n * SummaryMeta — the row of QUALIFYING fields beneath a summary's headline.\n *\n * A summary answers two questions in order: *which one is this* (the headline) and *what do I need\n * to know about it at a glance* (this). The second is a wrapping row of short values — a status\n * badge, a date, an owner, a count — that reads as one line on a wide card and folds on a narrow\n * one.\n *\n * ## Why this exists as a component\n *\n * It was written out by hand **34 times** across the engine's own resource presets and the\n * workbench, always as the identical literal:\n *\n *     <div className=\"flex flex-wrap items-center gap-x-3 gap-y-1\">\n *\n * Three things follow from a concept having no name. No theme can change it, because it is a string\n * in a configuration file rather than a recipe. It uses raw Tailwind spacing while the design system\n * defines the `element / item / group / field` token ladder every other surface spends. And the\n * thirty-fifth author copies whichever of the thirty-four they happened to read, so the row drifts\n * a gap at a time with nothing able to notice.\n *\n * The geometry here is that literal expressed in TOKENS — `gap-x-group` is the same 0.75rem as\n * `gap-x-3`, `gap-y-item` the same 0.25rem as `gap-y-1` — so adopting it is pixel-neutral, and\n * moving the ladder afterwards moves every meta row at once.\n *\n * ## The `w-auto` on children is not cosmetic\n *\n * A `<DisplayField>` renders a field chrome whose root is `w-full`. In a wrapping flex row that\n * makes every value claim its own line, so the row silently renders as a stack — the same defect\n * `SummaryHeader` neutralises for its accessories, and the same one `objectUI displayMode:\n * HORIZONTAL` had until it was fixed. Neutralising it here is what makes the row a row.\n *\n * @example\n * ```tsx\n * <SummaryLayout>\n *   <SummaryTitle name=\"email\" />\n *   <SummaryMeta>\n *     <DisplayField name=\"status\" />\n *     <DisplayField name=\"createdAt\" />\n *   </SummaryMeta>\n * </SummaryLayout>\n * ```\n */\n\nimport type { ReactNode } from 'react';\nimport { cn } from '~wildo-frontend-lib/core/ui/cn';\n\nexport interface SummaryMetaProps {\n  /** Extra classes merged over the default wrapping-row geometry. */\n  className?: string;\n  /** The qualifying fields — typically `<DisplayField>`s. */\n  children?: ReactNode;\n}\n\nexport function SummaryMeta({ className, children }: SummaryMetaProps): ReactNode {\n  return (\n    <div\n      className={cn(\n        'flex min-w-0 flex-wrap items-center gap-x-group gap-y-item',\n        // See the docstring: a `w-full` field chrome turns a wrapping row into a stack.\n        '[&>*]:w-auto',\n        className,\n      )}\n    >\n      {children}\n    </div>\n  );\n}\n"]}

package/dist/esm/components/resources/skeleton/SummaryTitle.d.ts

@@ -1,26 +1,77 @@
 /**
- * SummaryTitle — the resource's PRIMARY LABEL (title) as a first-class, composable
- * element of the summary template flow.
- *
- * Reads the resolved label from {@link SummaryContext} (provided by
- * `ResourceSummaryDisplayer`). Renders the same medium-weight, truncating title
- * the card/list/popover hosts render, so moving the title into the template flow
- * is pixel-neutral for the common `AUTO` case.
- *
- * Usage:
- * - `<SummaryLayout>` (default `titlePlacement={AUTO}`) renders this automatically
- *   at the top of the template — authors write nothing.
- * - `<SummaryLayout titlePlacement={TEMPLATE_OWNED}>` cedes placement to the
- *   author, who drops `<SummaryTitle />` wherever it belongs — e.g. inside a
- *   `<SummaryHeader>` beside a status badge.
- *
- * Renders nothing when there is no title to show (body-only surfaces such as an
- * inline FK-field reference pass a `null` label — see {@link SummaryContext}).
+ * SummaryTitle — the value that NAMES the record, as a first-class element of the summary flow.
+ *
+ * It answers "which one is this" in two ways, and which one you want depends on who computed the
+ * name:
+ *
+ * - **No `name`** — the resource's resolved PRIMARY LABEL, read from {@link SummaryContext} (the
+ *   card / list / popover host computed it with the right `t`, junction forwarding and so on). This
+ *   is what `<SummaryLayout>`'s `AUTO` placement renders, so an author who wants "title above a
+ *   couple of fields" writes nothing at all.
+ * - **With `name`** — a FIELD of the record, rendered through the display pipeline. Use it when the
+ *   title is a particular authored value (`email`, `oneSentence`, `statement`) rather than whatever
+ *   the host resolved as the label.
+ *
+ * ## Why the `name` form exists
+ *
+ * The second form was written out by hand **18 times** across the engine's own resource presets,
+ * always as the identical literal:
+ *
+ *     <div className="font-medium leading-tight">
+ *       <DisplayField name="email" hideLabel />
+ *     </div>
+ *
+ * Eighteen copies of a treatment this component already owns, sitting next to eighteen calls to
+ * this component that could not express it. No theme can reach those literals, and each new author
+ * copies whichever one they happened to read.
+ *
+ * ## Scale — declared as a ROLE, resolved by the theme
+ *
+ * A title that must read larger than its surroundings says WHICH TITLE IT IS, not how big. The four
+ * roles below are the four levels the repository actually had, each previously written as a literal
+ * step: a card title at `font-medium`, an entry headline at `text-base`, a section's at `text-lg`, a
+ * document's own lead at `text-xl`. They now resolve through the theme's HEADING ladder, which the
+ * eight themes each define differently — editorial runs large, trading and terminal run dense — so
+ * the same declaration reads correctly in all of them and in the next one.
+ *
+ * The mechanism is a {@link TypographyScope} rather than a class on this element, and the reason is
+ * worth keeping: font WEIGHT and LINE-HEIGHT inherit — which is why the wrapper idiom worked at all
+ * — but font SIZE does not, because the formatter's `<Text>` sets its own. A class here would lose
+ * to it, and mirroring one through `[&_p]:` cannot work either, since a Tailwind variant composed
+ * at runtime from a theme value is never generated. The scope reaches the `<Text>` itself.
+ *
+ * Renders nothing when there is no title to show: the no-`name` form on a body-only surface (an
+ * inline FK reference passes a `null` label), so `AUTO` shows no empty title slot.
  */
 import type { ReactNode } from 'react';
+/**
+ * WHICH title this is — a role, never a size.
+ *
+ * Each maps to a step of the theme's HEADING ladder, so what a role looks like is the theme's answer
+ * and the same declaration holds across all eight.
+ */
+export declare enum SummaryTitleScale {
+    /** The ordinary card / list-row / popover title: medium weight at the surrounding size. */
+    DEFAULT = "default",
+    /** Names ONE ENTRY inside a collection — the ladder's smallest in-content step. */
+    ENTRY = "entry",
+    /** Leads a SECTION of a document. */
+    SECTION = "section",
+    /** The DOCUMENT's own lead. */
+    DOCUMENT = "document"
+}
 export interface SummaryTitleProps {
+    /**
+     * Render THIS FIELD as the title instead of the host-resolved primary label.
+     *
+     * The field renders through the ordinary display pipeline with its label hidden — the title IS
+     * the value, and a label reading "Email" above an email address is a row that says nothing.
+     */
+    name?: string;
+    /** Which title this is. Defaults to {@link SummaryTitleScale.DEFAULT}. */
+    scale?: SummaryTitleScale;
     /** Extra classes merged over the default `font-medium text-foreground` title styling. */
     className?: string;
 }
-export declare function SummaryTitle({ className }: SummaryTitleProps): ReactNode;
+export declare function SummaryTitle({ name, scale, className }: SummaryTitleProps): ReactNode;
 //# sourceMappingURL=SummaryTitle.d.ts.map

package/dist/esm/components/resources/skeleton/SummaryTitle.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"SummaryTitle.d.ts","sourceRoot":"","sources":["../../../../../../src/components/resources/skeleton/SummaryTitle.tsx"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;GAkBG;AAEH,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AAKvC,MAAM,WAAW,iBAAiB;IAChC,yFAAyF;IACzF,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED,wBAAgB,YAAY,CAAC,EAAE,SAAS,EAAE,EAAE,iBAAiB,GAAG,SAAS,CAqBxE"}
+{"version":3,"file":"SummaryTitle.d.ts","sourceRoot":"","sources":["../../../../../src/components/resources/skeleton/SummaryTitle.tsx"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4CG;AAEH,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AASvC;;;;;GAKG;AACH,oBAAY,iBAAiB;IAC3B,2FAA2F;IAC3F,OAAO,YAAY;IACnB,mFAAmF;IACnF,KAAK,UAAU;IACf,qCAAqC;IACrC,OAAO,YAAY;IACnB,+BAA+B;IAC/B,QAAQ,aAAa;CACtB;AAUD,MAAM,WAAW,iBAAiB;IAChC;;;;;OAKG;IACH,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,0EAA0E;IAC1E,KAAK,CAAC,EAAE,iBAAiB,CAAC;IAC1B,yFAAyF;IACzF,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED,wBAAgB,YAAY,CAAC,EAAE,IAAI,EAAE,KAAiC,EAAE,SAAS,EAAE,EAAE,iBAAiB,GAAG,SAAS,CA4DjH"}

package/dist/esm/components/resources/skeleton/SummaryTitle.js

@@ -1,10 +1,49 @@
 'use client';
 import { jsx as _jsx } from "react/jsx-runtime";
+import { TypographyVariant, UIBehavior } from '@wildo-ai/presets-components-models';
 import { cn } from '../../../core/ui/cn.js';
+import { useUI } from '../../../core/ui/useUI.js';
+import { TypographyScope } from '../../../core/ui/TypographyScopeContext.js';
 import { Text } from '../../../components/typography/text.js';
+import { DisplayField } from '../../../components/data-display/DisplayField.js';
 import { useOptionalSummaryContext } from '../../../components/data-display/SummaryContext.js';
-export function SummaryTitle({ className }) {
+/**
+ * WHICH title this is — a role, never a size.
+ *
+ * Each maps to a step of the theme's HEADING ladder, so what a role looks like is the theme's answer
+ * and the same declaration holds across all eight.
+ */
+export var SummaryTitleScale;
+(function (SummaryTitleScale) {
+    /** The ordinary card / list-row / popover title: medium weight at the surrounding size. */
+    SummaryTitleScale["DEFAULT"] = "default";
+    /** Names ONE ENTRY inside a collection — the ladder's smallest in-content step. */
+    SummaryTitleScale["ENTRY"] = "entry";
+    /** Leads a SECTION of a document. */
+    SummaryTitleScale["SECTION"] = "section";
+    /** The DOCUMENT's own lead. */
+    SummaryTitleScale["DOCUMENT"] = "document";
+})(SummaryTitleScale || (SummaryTitleScale = {}));
+/** Which rung of the heading ladder each role reads. `DEFAULT` takes none — it is not a heading. */
+const SCALE_LADDER_KEY = {
+    [SummaryTitleScale.DEFAULT]: undefined,
+    [SummaryTitleScale.ENTRY]: 'h5',
+    [SummaryTitleScale.SECTION]: 'h4',
+    [SummaryTitleScale.DOCUMENT]: 'h3',
+};
+export function SummaryTitle({ name, scale = SummaryTitleScale.DEFAULT, className }) {
     const summary = useOptionalSummaryContext();
+    const { getRecipe } = useUI();
+    const ladderKey = SCALE_LADDER_KEY[scale];
+    const headingRecipe = getRecipe(UIBehavior.TYPOGRAPHY, TypographyVariant.HEADING);
+    /*
+     * Resolved HERE, where the theme's recipe is in hand, and handed to the scope as classes. The
+     * scope stays a transport — a second place that decided type scale would be the thing this
+     * component exists to remove.
+     */
+    const headingClassName = ladderKey
+        ? cn(headingRecipe.base, headingRecipe.sizes?.[ladderKey])
+        : undefined;
     // Register with the displayer's missing-title diagnostic BEFORE the empty-label
     // early return: mounting `<SummaryTitle />` discharges the template's contract
     // even when the current record resolves no label (that is data-driven, not an
@@ -12,6 +51,21 @@ export function SummaryTitle({ className }) {
     // after render and must not schedule updates.
     if (summary?.titleMountTracker)
         summary.titleMountTracker.titleMounted = true;
+    if (name) {
+        /*
+         * The FIELD form. `leading-tight` joins the weight because both INHERIT — that is the whole
+         * reason the eighteen hand-written wrappers worked, and the reason this replacement is exact.
+         *
+         * No `truncate` here, unlike the label form below: a field's own display params decide whether
+         * its value truncates (`StringDisplayMode.TRUNCATE`), and forcing it from the outside would
+         * overrule an author who chose to wrap.
+         */
+        return (_jsx(TypographyScope, { className: headingClassName, children: _jsx("div", { className: cn('min-w-0 flex-1 text-foreground', 
+                // At DEFAULT there is no heading recipe, so the weight has to come from here — and it
+                // reaches the value because weight INHERITS. At the heading scales the recipe carries
+                // its own weight and tracking, and applies them to the text element itself.
+                headingClassName ? 'leading-tight' : 'font-medium leading-tight', className), children: _jsx(DisplayField, { name: name, hideLabel: true }) }) }));
+    }
     const primaryLabel = summary?.primaryLabel;
     if (!primaryLabel)
         return null;