buildCustomFeed now calls the feed generator's getFeedSkeleton DIRECTLY - resolving its endpoint via Slingshot's resolveService - and forwards the viewer's service-auth token in a normal Authorization header. The generator personalizes the feed itself; we then hydrate the returned post uris via Slingshot record reads (no auth needed). This bypasses both the AppView and Slingshot's batch proxy (whose auth-forwarding is broken, returning 'oop/sorry'). Result: on native this fully replaces the AppView for custom feeds, including personalized ones like For You. On web it works for any generator that sends CORS headers; generators without CORS (e.g. foryou.club) still fall back to the AppView, since a browser can't read their cross-origin response - a generator- side limitation, not ours.