Class ComponentRegistryExtendedResolver

Get a component from a registry with optional hash for caching.

Caching strategy (three tiers):

1. Client sends hash from a previous fetch → server can return 304 if unchanged
2. Server checks in-memory LRU cache for a cached spec from a recent fetch
3. On miss, fetches from the external registry, caches the result, and returns it

Resolve component dependencies

Search for components in registries

Send feedback for a component from any registry This is a registry-agnostic mutation that allows feedback collection for components from any source registry (Skip, MJ Central, etc.)