Summary

Loading a page in the builder canvas was slow when a collection is repeated across many component instances (common with reference collections). Each instance fired its own identical API request; on large collections these ran concurrently and saturated the event loop, making the canvas take a long time to load.

Changes

• Add a shared in-flight/result cache in useCollectionLayerStore, keyed by the full request signature (collection + sort + limit + offset + filters)
• Layers bound to the same collection with identical params now reuse a single request instead of each firing its own
• Applied to both initial load (fetchLayerData) and post-edit refetch (refetchLayersForCollection)
• Cache is cleared on invalidateLayerData (per collection) and clearAllLayerData (all) so CMS edits and page switches still refetch fresh data
• Failed requests are dropped from the cache so retries work

Test plan

• Open a page with a collection repeated across many instances — only one network request fires per unique collection/params
• Edit a CMS item in that collection — canvas refetches and shows the update
• Switch pages and back — data still loads correctly
• Verify a collection used with different sort/limit/offset still fetches separately