[Feature Request]: Add `app.bsky.contact` namespace support

[KC-2001MS]

Summary

The upstream app.bsky.contact.* namespace (phone verification, contact import, matching, sync state, contact data removal, match notification) is missing from ATProtoKit. The namespace is a coherent "friend finder via phone book" surface that Bluesky has been adding to the lexicon, with no SDK access available today.

Pain points

• No way to enroll a user into the contact import flow through typed wrappers (startPhoneVerification / verifyPhone / importContacts).
• No way to query the resulting matches (getMatches / dismissMatch) or sync state (getSyncStatus).
• No way to purge previously uploaded contact data (removeData) — a likely compliance requirement.
• No way to trigger the match notification surface (sendNotification).

Considered Alternatives

Raw XRPC for the entire contact surface — viable but every consumer re-implements the same auth + endpoint plumbing.

Is this a breaking change?

No

Library Examples

N/A

Additional Context

Missing lexicons

Lexicon	Suggested wrapper
app.bsky.contact.defs	types only
app.bsky.contact.startPhoneVerification	startContactPhoneVerification(phoneNumber:)
app.bsky.contact.verifyPhone	verifyContactPhone(code:)
app.bsky.contact.importContacts	importContacts(_:)
app.bsky.contact.getSyncStatus	getContactSyncStatus()
app.bsky.contact.getMatches	getContactMatches(limit:cursor:)
app.bsky.contact.dismissMatch	dismissContactMatch(did:)
app.bsky.contact.removeData	removeContactData()
app.bsky.contact.sendNotification	sendContactNotification(to:)

References

• Lexicon root: https://github.com/bluesky-social/atproto/tree/main/lexicons/app/bsky/contact
• Affected directory: Sources/ATProtoKit/Models/Lexicons/app.bsky/Contact/ (new), Sources/ATProtoKit/APIReference/AppBskyAPI/ (new method files)

[MasterJ93]

Yes, I should work on that. This will take a little bit of time, however, as manually typing this all out can be frustrating after a while. You are, however, more than welcome to help out with this and I can ask for corrections after that. Hopefully by the time ATLexiconC is out, we will no longer have to do this anymore.

[KC-2001MS]

As we discussed, I've filed the missing features as separate feature requests for tracking. None of them are urgent on my end, so I plan to follow up on each as the need actually arises.

Given that ATLexiconC is on the horizon, please feel free to handle these at your own pace — there's no rush, and it may well make sense to let ATLexiconC cover some of them rather than typing everything out by hand. I'm happy to help and provide corrections whenever it's useful.