Can OAuth2 (atproto) access tokens satisfy com.atproto.repo.* endpoints req's yet?

[reflectivist]

Right now the OAuth2 flow seems limited to scopes "atproto transition:generic", but it isn't clear if those scopes grant access to com.atproto.repo.* endpoints yet, and, if not, is there any vague ETA of when OAuth will be able to?

As for details, I also have this question posted:
#3211 (comment)

https://docs.bsky.app/blog/oauth-atproto
"While that work is in progress, we are interested in feedback from SDK developers and early adopters. What pain points do you encounter? Are there requirements which could be relaxed without reducing user security?"

So, as an early adopter, in the dark and twisting in the wind, this IS a pain point, since some blood sweat and tears went into getting a prototype of atproto OAuth working on iOS. Because I don't know if I've properly done everything I needed to (e.g. is the simple receipt of the OAuth access token is as far as I can get now), or whether there's something else that might be wrong with the access token that makes the scope error I'm getting from the com.atproto.repo endpoint is a red herring?