hardened bluesky app fork with microcosm

Restore authenticated microcosm batch path for personalized feeds master

Reverts the earlier disabling. The 400 I saw was from testing with a fake JWT, not from the authorization field being rejected outright - a bad inference. When logged in we mint a real service-auth token (aud = feed generator DID, lxm = app.bsky.feed.getFeedSkeleton) and forward it through Slingshot's batch proxy, so personalized feeds use the fast one-request batch path. AppView fallback remains for any feed/generator that rejects forwarded auth.


+20 -6
1 changed file