Confirmed with a real service-auth token in-app: Slingshot's batch proxy returns 400 for ANY authorization value (Bearer or raw) - it can't forward auth to the generator server-side, the schema field notwithstanding. So sending a token just guaranteed a 400 + wasted round-trip before the AppView fallback. Now the batch path runs for everyone but never sends auth: logged-in users still get the fast one-request batch hydration on feeds with a usable public skeleton (Discover etc.), and personalized feeds that need viewer auth fall through to the AppView. The getAuthorization plumbing stays in place for if/when the proxy supports forwarded auth.