Which order should we implement these?

[KC-2001MS]

Some upstream lexicons ship in bluesky-social/atproto but aren't yet exposed in ATProtoKit
(verified against main — all additive):

• chat.bsky.convo message replyTo (+ group-convo #groupConvo bits)
• chat.bsky.group.* + chat.bsky.embed.joinLink
• chat.bsky.notification get/put preferences
• tools.ozone.queue + tools.ozone.report
• OAuth permission-sets (app.bsky.auth*, chat.bsky.authFullChatClient)
• app.bsky.contact.*
• app.bsky.feed.searchPostsV2 / app.bsky.embed.getEmbedExternalView / app.bsky.graph.getStarterPacksWithMembership
• app.bsky.unspecced.* (thread v2, Explore/onboarding rails)

Which order should these be tackled in?

[MasterJ93]

Permission sets don't need to be added because they're mainly server-only, as I understand it. But also, I haven't figured out how to shape permission-set lexicons yet. I'm actively investigating on what's the best approach to making them.

As for the order, I'm not sure if there's an order; typically, I work from top to bottom of the lexicon list. If there's a lexicon that needs to be made at a later stage that relies on a previous lexicon, then I make the prerequisite one first, and then continue down the list.

So, to clarify, in the bluesky-social/atproto repository, there's the lexicon list. I generally work from the first one to the last one. That's how I generally work on the lexicons.

Hopefully this makes sense. If not, please let me know. But thank you for taking the interest in making those lexicons for me; I know I'm very, very far behind on it.