/explorer-remote-proxy — local Explorer, remote backend

Stand up ONLY the redesigned Explorer + gateway locally and proxy the entire API surface (/search*, /images, /llm_parse, /vlm_validate, /asset_graph, /dependency_graph, /download, /info, /process) to a hosted USD Search instance. The hosted instance already has a populated index, a populated Asset Graph Service, and storage access, so the features that need a backend — dependency graphs and downloads — work with zero local infra.

Why this exists. A local remote-index (BYO-OpenSearch) stack only borrows the search index; its local AGS is empty, so dependency graphs and multi-file download bundles come back empty. Proxying straight to a fully hosted instance sidesteps that — and avoids the https://…s3….amazonaws.com (index) vs s3://… (AGS) base-key scheme mismatch, because the hosted instance is internally consistent.