diff --git a/.fork/customizations.yaml b/.fork/customizations.yaml index 84789ee2ace8f..47f5c4980cf4f 100644 --- a/.fork/customizations.yaml +++ b/.fork/customizations.yaml @@ -2067,9 +2067,31 @@ not successes, and caching them would pin a transient failure for the element's lifetime. + Third, the resolver snapshots the rendering component's primitive props + (strings/numbers/booleans, `children` excluded, capped at 12 entries and + 64 chars per string) off the composite fiber whose displayName matches + the reported component name — no match, no props, so the request never + labels props with a component they do not belong to. The snapshot crosses + the bridge only beside a component name, is re-validated by the guest + twin (designProps.ts's readDesignProps, mirroring DesignSourceResult.ts's + normalizeResolvedProps), rides the element as `data-t3-props`, is + re-validated AGAIN when the request builder reads that page-controlled + attribute back, and renders as "Rendered by `