Lexicon schema consumption post-merge

[ebwinters]

I want to discuss what our process looks like post-merge of a new Lexicon schema, since we exist outside of the atproto/Bluesky code boundaries. Specifically with a focus on how we expect to go from json schema → app view usage

A couple ideas for a path forward, not mutually exclusive

1. We own and maintain an npm package for publishing concrete types generated from our lexicons using the lex-cli tool or similar toolset
2. We contribute our lexicon.community types into the atproto client package
3. We provide a script to generate types for multiple languages which can be copied into projects. The script is maintained by lexicon.community in a new repository/gist

Ideally, I would like to dry run this on #12 (bookmarking lexicon), with the goal of exposing bookmarking as a feature inside of the Bluesky app view. Having a concrete path forward will both help drive adoption of community lexicons and make the development process more straightforward