fix: personalized feeds broke (no JWT forwarded to feed generator) master
The batch hydrateFeedSkeleton path proxied getFeedSkeleton to the generator without forwarding the user's service-auth token, so personalized feeds (For You, personalized Discover) returned 'requires authentication'. - Gate the microcosm custom-feed path to logged-OUT only; logged-in uses the existing AppView path which forwards auth correctly. - Keep the Slingshot batch hydration (hydrateFeedSkeleton + hydratePostFromRecord) for the public/logged-out case: one request for all post records instead of N. Following/author feeds are public listRecords (no auth) and are unaffected. TODO: forward proper service-auth (getServiceAuth scoped to the feed gen DID) via the proxy 'authorization' field to enable batch hydration when logged in.