What problem does it solve? Building .NET applications on ATProtocol requires wiring up lexicon-based type generation, authenticated XRPC clients, OAuth 2.0 DPoP flows, and real-time event streams, which is error-prone without guidance on CarpaNet's source-generator architecture. ## Core Features & Use Cases - Lexicon-Driven Source Generation: Declare lexicons in .csproj via LexiconResolve, LexiconFiles, or authority resolution to generate type-safe bindings with NativeAOT-compatible JSON/CBOR contexts. - XRPC Client Operations: Create public or authenticated ATProtoClient instances to query profiles, create and delete records, and fetch timelines using NSID-named extension methods. - OAuth 2.0 with DPoP: Implement desktop and web OAuth flows with OAuthSession and persistent IOAuthSessionStore for secure token lifecycle management. - Real-Time Event Streaming: Subscribe to Jetstream v2 or the ATProtocol firehose with deterministic resume via persisted sequence numbers. - Use Case: A developer building a Bluesky bot declares the needed lexicons, authenticates with an app password, posts records via ComAtprotoRepoCreateRecordAsync, and monitors the firehose for mentions. ## Quick Start Ask the assistant to set up a CarpaNet .NET project that fetches a Bluesky profile and subscribes to the Jetstream post feed.